Claude OTel traces: the Azure Monitor path and Foundry gap
Anthropic's OpenTelemetry trace export went to public beta on 14 October 2026, but Azure Monitor is not a listed destination and Claude in Microsoft Foundry gets client-side SDK spans only. Three Azure paths (Collector on Container Apps, Microsoft OpenTelemetry Distro with managed identity, Agent SDK signals), the Entra-versus-static-header mismatch that forces the design, and the Application Insights cost math for full-content mode.
Agent Framework Harness GA: build or buy your agent loop
Microsoft's Agent Framework Harness and Foundry Hosted Agents reached general availability in early August 2026, wrapping models with function invocation, context compaction, planning, memory, tool approvals and OpenTelemetry in a runtime that runs locally, in containers, or consumption-billed on Foundry. A decision framework for Azure teams weighing the GA runtime against a hand-rolled agent loop, with cost levers and the Swedish compliance picture.
Agent Observability: Tracing Decisions and Tool Calls
Standard APM was built for HTTP requests and database queries. Agent runs produce a different signal shape: nested decisions, tool calls, hallucination signals, accumulating context. The observability stack has caught up. Here is the production setup that makes agents debuggable.
LLM Observability: OpenTelemetry, Langfuse, App Insights
A production observability stack for LLM applications on Azure — wiring OpenTelemetry, Langfuse, and Application Insights together so traces, token usage, eval scores, and platform metrics land in the same view.