Blog Post

Azure Observability Blog
2 MIN READ

Troubleshoot with OpenTelemetry in Azure Monitor – Now Generally Available

KayodePrince's avatar
KayodePrince
Icon for Microsoft rankMicrosoft
Nov 16, 2026

Send OpenTelemetry logs, metrics, and traces to Azure Monitor, for full-stack performance monitoring with Application Insights and Grafana dashboards

OpenTelemetry is fast becoming the industry standard for modern telemetry pipelines. Now Azure Monitor speaks it natively. With OpenTelemetry Protocol (OTLP) support generally available, you can ship logs, metrics, and traces from wherever your workloads run to analyze and act on it in one place. Direct OTLP ingestion into Azure Monitor has been generally available since May 2026. Now, we are expanding the scope to include automated onboarding for Azure Kubernetes Service (AKS) and using the Azure Monitor Agent (AMA) to receive and forward OTLP.

OTLP Support in Azure Monitor

  • Ingest OTLP signals directly into Azure Monitor logs, metrics, and traces.
  • Automatically onboard AKS workloads.
  • Receive and forward OTLP with (AMA) on Linux Azure VMs and VM Scale sets.
  • Use Application Insights on OTLP for distributed tracing, performance and troubleshooting experiences.
  • Visualize signals in Grafana with Azure-supported and community dashboards.
  • Store and query OTLP metrics using PromQL
  • Use OTLP semantic conventions for logs and traces, so your data lands in a familiar standards-based schema.

Choose your OTLP path

  • VMs/VM Scale Sets (and Azure Arc-enabled compute): Use the Azure Monitor Agent to receive OTLP from your apps and export it to Azure Monitor. Get started
  • AKS: Auto-instrument Java, Node.js, Python and .NET workloads using the Azure Monitor OpenTelemetry distro, or auto-configure any OpenTelemetry SDK-instrumented workload to export OTLP to Azure Monitor. Get started
  • Any environment: Use the OpenTelemetry Collector to receive OTLP signals and export directly to Azure Monitor cloud ingestion endpoints. Get started

Where your telemetry lands

  • Metrics: Stored in an Azure Monitor Workspace, a Prometheus metrics store.
  • Logs + traces: Stored in a Log Analytics workspace using an OpenTelemetry semantic conventions–based schema.
  • Troubleshooting: Application Insights lights up distributed tracing and end-to-end performance investigations, backed by Azure Monitor.

Why it matters

  • Standardize once: Instrument with OpenTelemetry and keep your telemetry portable and reusable.
  • Reduce overhead: Fewer vendor-specific components and pipelines to maintain.
  • Debug faster: Correlate metrics, logs, and traces using consistent labels to get from notifications to root cause faster.
  • Observe with confidence: Use pre-built dashboards and tracing views and enable agent-assisted workflows through Azure Monitor MCPs and APIs.

Next step: Onboard using direct ingestion, AKS or AMA, then validate end-to-end signal flow with Application Insights and Grafana dashboards. Learn More

Updated Nov 16, 2026
Version 1.0
No CommentsBe the first to comment