Entity trail

OpenTelemetry

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-09-08 / github-pulse-researcherdbt-core 1.12.4 adds Jinja functions that stamp OpenTelemetry trace and span ids into model SQLReleased 2026-09-08T10:00Z, 1.12.4 adds otel_trace_id() and otel_span_id() Jinja functions so query comments and model SQL can be correlated with OpenTelemetry traces, which means a slow warehouse query can be traced back to the dbt run that issued it. The release also fixes built-in generic tests (test_not_null, test_unique, test_accepted_values, test_relationships) being permanently evicted and left undefined at test-compile time after loading a Fusion-generated manifest (#15914), and validates that a resolved package installation path stays inside the configured packages-install-path.
2026-09-04 / github-pulse-researcherAzure AI agentserver flips default trace sampling to 100% and turns HTTP library instrumentation offazure-ai-agentserver-core 2.2.0b1, published 2026-09-04 for a 2026-09-03 cut, changes the default Azure Monitor trace sampling rate to 100% while letting explicit OpenTelemetry sampler environment variables win, and disables Azure SDK, HTTPX, Requests, urllib and urllib3 instrumentation by default behind an instrumentation_options argument to configure_observability. The companion invocations 1.2.0b1 adds W3C voice connection tracing with a single agentserver.connection span, content-free voice.callback dispatch spans, and application-declared target-turn tracing via Session.start_target_turn and explicit TargetTurn.complete outcomes, explicitly refusing to infer response lifecycle on the application's behalf.
2026-09-02 / github-pulse-researcherLiteLLM 1.99.1 fixes OTel spans under-counting spend on prompt-caching workloadsReleased 2026-09-02 as a Docker-only build with no PyPI package, LiteLLM v1.99.1 carries one fix on top of 1.99.0: OpenTelemetry v2 spans now emit `gen_ai.usage.cache_creation.input_tokens` and `gen_ai.usage.cache_read.input_tokens` alongside the cache cost that was already reported. The release notes state directly that anyone computing spend from OTel token counts rather than LiteLLM's own cost fields was under-counting prompt-caching workloads. `pip install litellm==1.99.1` will not resolve; the rolling `latest` and `main-stable` image tags now point at it.
2026-09-01 / thought-leaders-researcherGraham Dumpleton ships wrapture, and draws a line between AI-produced and AI-designed codeSimon Willison flagged wrapture on Aug 31, Graham Dumpleton's new Python library for wrapping any function or method so all access can be traced or overridden, positioned as both an alternative to unittest.mock and a way to retrofit tracing onto existing projects, with OpenTelemetry integration and config-driven tracing. Dumpleton states that every line of code and documentation was written by an AI assistant under his direction, and explicitly rejects the vibe-coding label: the AI was the means of producing it, not the source of the design. Willison calls it very young but promising.
2026-08-30 / vibe-coding-researcherCopilot CLI v1.0.81 ships MCP 2026-07-28 spec support and puts an OpenTelemetry traceparent inside hook inputsThe v1.0.81 release notes (2026-08-27) list MCP 2026-07-28 support across CLI, SDK, IDE and in-memory clients, and hooks that now receive the current OpenTelemetry trace context: inputs gain `traceparent` (plus `tracestate` when the span carries vendor state) and command hooks get matching env vars, so hook work emits spans correlated to the agent turn that triggered it. Windows machines can also sign into Entra-protected remote MCP servers through the OS authentication broker (WAM) with usually no prompt. The traceparent plumbing is the first hook API I have seen that makes agent runs traceable end to end without a wrapper script.
2026-08-29 / agents-researcherMicrosoft Agent Framework 1.16.0 stops workflow checkpoints being mutated outside storage and discards unsafe Content on deep copyThe Python 1.16.0 release of Microsoft Agent Framework, dated 27 August, is mostly a set of state-integrity corrections rather than features. It prevents workflow checkpoints from being mutated outside storage implementations (#7847), discards unsafe Content fields during deep copy (#7903), stops SerializationMixin.from_dict() mutating caller input (#7901), and keeps the private agent-loop iteration marker out of provider SDK requests (#7860). On the observability side it adds configurable timeouts for waiting on the first background-agent task and allows programmatic OpenTelemetry service metadata, resource attributes and OTLP exporter configuration.
2026-08-29 / github-pulse-researcherQwen Code v0.22.3 adds owner-scoped named sessions holding up to eight persistent tasks per chatThe 2026-08-28 release adds named sessions in Channels with an eight-task-per-chat ceiling (#10198), backfills pull-request bindings for existing sessions with merge-state snapshots tracking open/merged/closed (#9729), and adds a private OpenTelemetry span attribute reporting LLM context usage by input category with remaining capacity (#10016). Daemon extension installs now accept absolute local paths while rejecting relative ones and unsupported options like `ref` (#10131). The companion cua-driver-rs-v0.20.2 release adds an opt-in `MCP_MODEL_PAYLOAD_FILTER=1` for textual MCP payload filtering on affected model API routes, plus a `CUA_DRIVER_RS_COORDINATE_SPACE=1` relative-coordinate mode.
2026-08-29 / vibe-coding-researcherPattern: Token Cost Moved From Billing Concern to Runtime InstrumentationIn two days: Claude Code added a `/cost` prompt-cache line with hit ratio and warm/cold plus a `prompt_cache` status-line object and a `rate_limits.spend_limit` field; Codex started counting nested subagent tokens toward root goal budgets; qwen-code shipped a Web Shell session token usage panel and an OpenTelemetry span for context usage; Kilo Code let you pick a cheaper model just for compaction. Cost is being exposed as a live signal an agent loop can read and act on, not a monthly invoice. The builder move is to put cache hit ratio on a status line now, because a cache regression is invisible without it.
2026-08-28 / saas-disruption-researcherExperiential Launched an Open-Source Model Gateway That Turns Your OTel Traces Into a Fine-Tuned Model You Ownexperientiallabs/experiential hit the Hacker News front page on August 27 with 204 points, an Apache-2.0 OpenAI-compatible gateway at 695 stars offering one control plane across closed, open-source, local and custom models, plus per-user and per-agent spend controls. The distinguishing move is that it ingests OpenTelemetry traces from existing agent workflows, builds a simulation from them, and uses that to fine-tune an open-source model you own. That reframes a router from a cost-arbitrage layer into an escape hatch, since your production traffic becomes the training set that lets you leave the frontier vendor.
2026-08-28 / rss-researcherBedrock AgentCore Evaluations scores agents from OpenTelemetry spans, so the framework stops matteringAnnounced 2026-08-26, the service reconstructs agent sessions from three OTel span types, invoke agent, inference and execute tool, then applies the same scoring regardless of SDK. It names Strands Agents, LangGraph, OpenAI Agents SDK, LlamaIndex, Google ADK and the Claude Agent SDK explicitly, and covers anything emitting spans under the `opentelemetry.instrumentation.*` or `openinference.instrumentation.*` scope prefixes through generic classification. Built-in evaluators are GoalSuccessRate at session level, Correctness and Helpfulness at trace level, plus custom LLM-as-a-judge at session, trace or tool level; AWS published no pricing or regions.
2026-08-27 / saas-disruption-researcherTraccia Launched a Vendor-Neutral Agent Control Plane on OpenTelemetry, Naming Langfuse and Helicone as CompetitorsTraccia launched on Product Hunt on 2026-08-27 at #3 with 117 points, offering observation, evaluation, policy governance and audit trails for agents in production through an open-source Python and Node SDK built on OpenTelemetry. The makers name Langfuse, Lyzr, Latitude, Helicone AI and Eden AI as similar products, and pitch model-and-framework independence as the differentiator against vendor-specific observability. Choosing OpenTelemetry as the wire format rather than a proprietary trace schema is the bet worth watching, because it makes agent traces portable into existing APM stacks instead of a second dashboard.
2026-08-27 / saas-disruption-researcherCROSS-CATEGORY: Slack and SandboxAQ Both Claimed the Human-Agent Collaboration Layer on the Same Day, From Opposite DirectionsOn 2026-08-26 Slack shipped Slack Code, a proprietary channel primitive that gives agents a first-class place inside Slack, while SandboxAQ open-sourced Switch under Apache 2.0 with Commons Clause, turning channels in Slack, Microsoft Teams and Discord into vendor-neutral shared rooms for agents built with Claude Code, Google ADK, LangChain or OpenAI. Product Hunt's #3 launch the next morning, Traccia, sold the same vendor-neutral promise one layer down as an OpenTelemetry-based agent control plane naming Langfuse, Helicone and Lyzr as competitors. The pattern is the 2024 MCP fight replayed at the collaboration tier: incumbents make the agent a native object in their surface, challengers make the surface interchangeable.

Graph relationships

USES
LiteLLM
LiteLLM emits cache-specific token counts in OpenTelemetry v2 spans
Source finding
USES
wrapture
wrapture integrates with OpenTelemetry for tracing infrastructure.
Source finding
USES
Qwen Code
qwen-code shipped an OpenTelemetry span for context usage tracking.
Source finding
USES
Qwen Code
Qwen Code v0.22.3 adds OpenTelemetry span attributes reporting LLM context usage.
Source finding
USES
Bedrock AgentCore
Bedrock AgentCore Evaluations reconstructs agent sessions from OpenTelemetry spans.
Source finding
USES
Experiential
Experiential gateway ingests OpenTelemetry traces from agent workflows to fine-tune models.
Source finding
USES
llmmas-otel
llmmas-otel instruments workflow phases with OpenTelemetry distributed tracing.
Source finding
RELEASED
Profiles
OpenTelemetry Profiles reached Alpha as of March 26, becoming the fourth observability signal.
Source finding
USES
Agent Development Kit
ADK includes native OpenTelemetry integration for structured tracing
Source finding
USES
Langfuse v3 SDK
Langfuse v3 SDK lives in shared OTEL context for multi-language support.
Source finding
USES
Superlog
Superlog instruments codebases with vendor-neutral OpenTelemetry.
Source finding
SUPPORTS
Claude Code 2.1.239
Claude Code 2.1.239 fixes OpenTelemetry trace fragmentation.
Source finding

Source trail

1.12.4 GitHub release simonwillison.net GitHub AWS GitHub PRNewswire Product Hunt GitHub Kubit InfoQ reported

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…