Traceloop's observability tool for LLM applications is now generally available. The company also announced a $6.1 million seed funding round. The platform extends OpenTelemetry to provide better observability for LLM applications, offering insights into model behavior and facilitating experimentation.
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.
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.
OpenInference is a set of conventions and plugins that complements OpenTelemetry to enable tracing of AI applications, with native support from arize-phoenix and compatibility with other OpenTelemetry-compatible backends.
The article discusses the future of observability in 2025, highlighting the significant role of OpenTelemetry and AI in improving observability and reducing costs.
This Splunk Lantern blog post highlights new articles on instrumenting LLMs with Splunk, leveraging Kubernetes for Splunk, and using Splunk Asset and Risk Intelligence.
