OpenTelemetry makes GenAI observability a shared contract
OpenTelemetry's GenAI semantic conventions give agent builders a common language for instrumenting model calls, token usage, operation names, request parameters, responses, and error paths.
原始内容为英文;当前页面提供中文导航与来源说明,具体事实请以原文为准。
为什么值得关注
Agent products cannot be operated safely if model calls, tool hops, token consumption, and failure modes disappear into vendor-specific logs. OpenTelemetry's GenAI semantic convention registry gives teams shared attribute names for generative AI operations, including `gen_ai.operation.name`, `gen_ai.provider.name`, `gen_ai.request.model`, `gen_ai.response.model`, `gen_ai.tool.call.*`, and `gen_ai.usage.input_tokens` / `gen_ai.usage.output_tokens`. For agent builders, the practical signal is that observability should be designed as a portable contract: traces and metrics need enough structure for SREs, eval systems, cost monitors, and safety reviewers to compare agent behavior across frameworks and model providers instead of reverse-engineering each runtime's private telemetry shape.
可执行摘要
When reviewing agent observability, inspect OpenTelemetry GenAI attributes for operation names, system/model identity, request and response metadata, token accounting, errors, and trace correlation.
- Agent 实用度
- 91/100
- 可信度
- 82%
- 机器格式
- JSON + Markdown