buildOne report1 publisher MCP's 2026-07-28 spec deprecated protocol-level Logging and left it at least twelve months of support. A dev.to guide says OpenTelemetry's MCP conventions replace it, and since they are still unstable, teams should pin instrumentation versions.
Reality
- Evidence45
- Adoption
- Insufficient
- Hype gap+10
- Incentives20
- Confidence45
buildOne report1 publisher LangChain's survey of 1,340 practitioners found 89% had observability on their agents and 37.3% ran online evaluations. The OpenTelemetry GenAI attribute registry explains why only the second number measures quality.
Reality
- Evidence58
- Adoption64
- Hype gap+10
- Incentives42
- Confidence52
buildOne report1 publisher Microsoft Foundry writes agent runs as OpenTelemetry spans with gen_ai attributes and exports them to Azure Monitor, where evaluators score sampled production traffic off the same records. Those attributes include tool arguments.
Reality
- Evidence40
- Adoption
- Insufficient
- Hype gap+10
- Incentives55
- Confidence45
buildOne report1 publisher Kept's tracing layer went in before the agent loop, which produced one design decision worth copying and a promised accounting of the drawbacks that the available text never reaches.
Reality
- Evidence42
- Adoption8
- Hype gap+18
- Incentives45
- Confidence55
buildConfirmed2 publishers Bedrock AgentCore Evaluations promises to score agents built on LangGraph, LlamaIndex, OpenAI's SDK, Google ADK or the Claude Agent SDK. The catch sits in the instrumentation.
Reality
- Evidence52
- Adoption20
- Hype gap+28
- Incentives78
- Confidence48
buildOne report1 publisher The New Stack argues an agent run record is application data with a telemetry-shaped workload. Flatten one reported event rate and the daily average hides a burst about 19 times larger.
Reality
- Evidence34
- Adoption22
- Hype gap+16
- Incentives
- Insufficient
- Confidence44