Observability with OpenTelemetry changedagent-sdk/observability
Nearest release: v2.1.248, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−3removed
From line
9
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits12to this page, all time
The whole hunk
from line 9, old and new numbered
/
from line 9
99* how many tokens were spent
1010* where failures occurred
1111
12The Agent SDK can export this data as OpenTelemetry traces, metrics, and log events to any backend that accepts the OpenTelemetry Protocol (OTLP), such as Honeycomb, Datadog, Grafana, Langfuse, or a self-hosted collector.
12The Agent SDK can export this data as OpenTelemetry traces, metrics, and log events to any backend that accepts the OpenTelemetry Protocol (OTLP), whether a hosted observability platform or a self-hosted collector.
1313
1414This guide explains how the SDK emits telemetry, how to configure the export, and how to tag and filter the data once it reaches your backend. To read token usage and cost directly from the SDK response stream instead of exporting to a backend, see [Track cost and usage](/docs/en/agent-sdk/cost-tracking).
1515
from line 105
105105 The `console` exporter writes telemetry to standard output, which the SDK uses
106106 as its message channel. Do not set `console` as an exporter value when running
107107 through the SDK. To inspect telemetry locally, point
108 `OTEL_EXPORTER_OTLP_ENDPOINT` at a local collector or an all-in-one Jaeger
109 container instead.
108 `OTEL_EXPORTER_OTLP_ENDPOINT` at a local OpenTelemetry Collector instead.
110109</Note>
111110
112111### Flush telemetry from short-lived calls
No line in this hunk matches that.