One change
Observability with OpenTelemetry
agent-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.
agent-sdk/observability Changed · +2 / -3 lines
from line 9
* how many tokens were spent * where failures occurred -The 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. +The 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. This 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).
from line 105
The `console` exporter writes telemetry to standard output, which the SDK uses as its message channel. Do not set `console` as an exporter value when running through the SDK. To inspect telemetry locally, point - `OTEL_EXPORTER_OTLP_ENDPOINT` at a local collector or an all-in-one Jaeger - container instead. + `OTEL_EXPORTER_OTLP_ENDPOINT` at a local OpenTelemetry Collector instead. </Note> ### Flush telemetry from short-lived calls