PII Guard is an LLM-powered tool that detects and manages Personally Identifiable Information (PII) in logs — designed to support data privacy and GDPR compliance. It uses the gemma:3b model running locally via Ollama.
Edge Delta announces its new MCP Server, an open standard for streamlining communication between AI models and external data sources. It enables intelligent telemetry data analysis, adaptive pipelines, and effortless cross-tool orchestration directly within your IDE.
Edge Delta’s MCP Server acts as a bridge between developer tools and the Edge Delta platform, enabling generative AI to be integrated into observability workflows. Key benefits include:
* **Instant Root Cause Analysis:** Quickly identify the causes of errors using logs, metrics, and probable root causes.
* **Adaptive Pipelines:** AI-driven suggestions for optimizing telemetry pipeline configurations.
* **Effortless Orchestration:** Seamless integration of Edge Delta anomalies with other tools like Slack and AWS KB.
The server is built on Go and requires minimal authentication (Org ID + API Token). It can be easily integrated into IDEs with a simple configuration. The author anticipates that, despite current limitations like context window size and latency, this technology represents a significant step forward, similar to the impact of early algorithmic breakthroughs.
Edge Delta’s MCP Server acts as a bridge between developer tools and the Edge Delta platform, enabling generative AI to be integrated into observability workflows. Key benefits include:
* **Instant Root Cause Analysis:** Quickly identify the causes of errors using logs, metrics, and probable root causes.
* **Adaptive Pipelines:** AI-driven suggestions for optimizing telemetry pipeline configurations.
* **Effortless Orchestration:** Seamless integration of Edge Delta anomalies with other tools like Slack and AWS KB.
The server is built on Go and requires minimal authentication (Org ID + API Token). It can be easily integrated into IDEs with a simple configuration. The author anticipates that, despite current limitations like context window size and latency, this technology represents a significant step forward, similar to the impact of early algorithmic breakthroughs.
Why developers are spinning up AI behind your back — and how to detect it. The article discusses the rise of 'Shadow AI' - developers integrating LLMs into production without approval, the risks involved, and strategies for organizations to manage it effectively.
>We’ve seen LLMs used to auto-tag infrastructure, classify alerts, generate compliance doc stubs, and spin up internal search tools on top of knowledge bases. We’ve also seen them quietly embedded into CI/CD workflows...
>We’ve seen LLMs used to auto-tag infrastructure, classify alerts, generate compliance doc stubs, and spin up internal search tools on top of knowledge bases. We’ve also seen them quietly embedded into CI/CD workflows...
vLLM Production Stack provides a reference implementation on how to build an inference stack on top of vLLM, allowing for scalable, monitored, and performant LLM deployments using Kubernetes and Helm.
Articles on logging, tracing, and observability including Echopraxia, Blindsight, structured log analysis, and more.
This article details the Model Context Protocol (MCP), a new approach to integrating Large Language Models (LLMs) like Azure OpenAI with tools. MCP focuses on structured data exchange to improve reliability, observability, and functionality, moving beyond simple text-in, text-out interactions. It aims to standardize how LLMs interact with tools, enhancing their ability to utilize those tools effectively.
This Splunk Lantern article outlines the steps to monitor Gen AI applications with Splunk Observability Cloud, covering setup with OpenTelemetry, NVIDIA GPU metrics, Python instrumentation, and OpenLIT integration to monitor GenAI applications built with technologies like Python, LLMs (OpenAI's GPT-4o, Anthropic's Claude 3.5 Haiku, Meta’s Llama), NVIDIA GPUs, Langchain, and vector databases (Pinecone, Chroma) using Splunk Observability Cloud. It outlines a six-step process:
1. **Access Splunk Observability Cloud:** Sign up for a free trial if needed.
2. **Deploy Splunk Distribution of OpenTelemetry Collector:** Use a Helm chart to install the collector in Kubernetes.
3. **Capture NVIDIA GPU Metrics:** Utilize the NVIDIA GPU Operator and Prometheus receiver in the OpenTelemetry Collector.
4. **Instrument Python Applications:** Use the Splunk Distribution of OpenTelemetry Python agent for automatic instrumentation and enable Always On Profiling.
5. **Enhance with OpenLIT:** Install and initialize OpenLIT to capture detailed trace data, including LLM calls and interactions with vector databases (with options to disable PII capture).
6. **Start Using the Data:** Leverage the collected metrics and traces, including features like Tag Spotlight, to identify and resolve performance issues (example given: OpenAI rate limits).
The article emphasizes OpenTelemetry's role in GenAI observability and highlights how Splunk Observability Cloud facilitates monitoring these complex applications, providing insights into performance, cost, and potential bottlenecks. It also points to resources for help and further information on specific aspects of the process.
1. **Access Splunk Observability Cloud:** Sign up for a free trial if needed.
2. **Deploy Splunk Distribution of OpenTelemetry Collector:** Use a Helm chart to install the collector in Kubernetes.
3. **Capture NVIDIA GPU Metrics:** Utilize the NVIDIA GPU Operator and Prometheus receiver in the OpenTelemetry Collector.
4. **Instrument Python Applications:** Use the Splunk Distribution of OpenTelemetry Python agent for automatic instrumentation and enable Always On Profiling.
5. **Enhance with OpenLIT:** Install and initialize OpenLIT to capture detailed trace data, including LLM calls and interactions with vector databases (with options to disable PII capture).
6. **Start Using the Data:** Leverage the collected metrics and traces, including features like Tag Spotlight, to identify and resolve performance issues (example given: OpenAI rate limits).
The article emphasizes OpenTelemetry's role in GenAI observability and highlights how Splunk Observability Cloud facilitates monitoring these complex applications, providing insights into performance, cost, and potential bottlenecks. It also points to resources for help and further information on specific aspects of the process.
The article discusses the challenges faced due to differing observability tools and naming conventions, and how OpenTelemetry's standard naming schemas can streamline workflows and enhance interoperability.
Grafana Loki version 3.4 introduces enhancements such as standardized storage with Thanos, a sizing guidance page, merging of Promtail into Grafana Alloy, and support for out-of-order logs.
