OpenTelemetry Articles
AI agent observability for Microsoft Foundry: two env vars, no collector
Set up LLM tracing once and every model call, tool execution and handoff from your Foundry agent arrives in Kibana as one queryable trace, with token counts on each span and code for Agent Framework, LangGraph and Node.js.
OpenTelemetry Java extensions: customize traces without forking the agent
One JAR, loaded at startup by the OpenTelemetry Java agent, lets you filter health checks, rename spans, add resource attributes, and control sampling with no application code changes.
Kubernetes observability: SLO templates that turn alerts into error budgets
Two bad rollouts burned 88% of a 30-day error budget while the SLI still read 99.56%. This post adds four SLO templates that bring burn-rate tracking to the OTel-based alert rules from Part 1, no new instrumentation required.
Elastic Agent now runs as an OpenTelemetry Collector: Less memory overhead, zero config changes
Elastic Agent 9.3 sends logs, metrics and traces through one OTel Collector pipeline, running Beats integrations alongside native OTel sources in a single Fleet-managed agent.
Correlate logs, metrics, and traces in one ES|QL query
Walk through four investigations, from CPU saturation to pod memory pressure, each answered by a single query across signal types.
Android application monitoring with OpenTelemetry: distributed tracing from tap to backend
EDOT Android adds mobile APM to your Android app with one Gradle dependency: crash reporting, session tracking and distributed tracing visible in Kibana.
From CrashLoopBackOff to OOMKilled with PromQL in Elasticsearch and Kibana
Use PromQL in Elasticsearch and Kibana to move from a CrashLoopBackOff alert to OOMKilled, memory versus the limit, and a verified fix.
Skip writing alert rules: 6 ready-made ES|QL templates ship inside the NGINX OTel integration
Elastic integrations come with alerting rule templates, each one an ES|QL query with a threshold already set. Create Elasticsearch alert rules in minutes, tune them to your traffic, and catch silent data streams early.
You have the IP, you want the hostname: building a lookup processor for OpenTelemetry
Look up any value from YAML, CSV or DNS inside the OpenTelemetry Collector or wire in your own source through a processor Elastic built and shipped to Collector Contrib.
Four clicks from alert to root cause: how Elastic Observability links APM services to Kubernetes infrastructure
Check service dependencies and compare per-pod CPU, memory and network trends on the Infrastructure tab to find which instance is causing trouble, all without leaving the alert investigation.
Three clicks from alert to error log: breaking down RED metrics by any span attribute in Elastic Observability
See which pod, deployment or version is driving a RED metrics change by breaking down span attributes in Discover, then trace a failing span to the error log behind it.
From alert to failing dependency in four clicks: Elastic APM's embedded service map
The APM service map is now embedded on alert pages with filters, connection metrics and a service fly-out so you can analyse dependencies and find the root cause without leaving the alert.