awesome-agent-observability

Awesome Agent Observability Awesome

A neutral list of resources for observing AI agents in development and production: standards, instrumentation, frameworks, platforms, gateways, evaluation, cost, safety signals, and on-chain agents and payments, with an OpenTelemetry focus.

The list covers every kind of agent, from coding and customer support agents to enterprise workflows, research and agents that make payments, and every place they run, from cloud providers and enterprise vendors to open source projects. It holds 441 entries.

Open source and commercial entries are listed side by side, in alphabetical order inside each section, never by preference or payment. There is no sponsored placement. Inclusion says nothing about quality, and the list takes no side between competing projects. Disclosure: the maintainer of this list also builds hashspan, which is listed under On-chain agents and payments like any other entry, and reported some of the issues listed under Findings. Entries submitted by people who work on the project carry a vendor_affiliation field in their data file.

Legend

Short tags after an entry:

A missing tag means the point was not confirmed, not that the answer is no. Every entry is a data file in entries/ with more fields: the evidence link for OTel support, the license, the kinds of agents it is specific to (agent_types), and repository metadata refreshed by a script (stars, archived, last push, last release). The same data is in entries.json and llms.txt for programs and agents.

Use the data

The list is also data, for scripts and agents:

Examples with jq:

# Self-hosted open source tools that send or receive OTLP
jq -r '.entries[] | select(.historical_section | not) | select(.otel and (.tags | index("self-hosted")) and (.tags | index("oss"))) | .name' entries.json

# Python instrumentation that follows the OpenTelemetry GenAI semantic conventions
jq -r '.entries[] | select(.category == "instrumentation" and (.tags | index("python")) and (.tags | index("genai-semconv"))) | "\(.name) \(.url)"' entries.json

# How each agent framework emits telemetry, with the page it was read from
jq -r '.entries[] | select(.category == "frameworks") | "\(.name): \(.telemetry) \(.telemetry_docs // "")"' entries.json

A missing or unknown value means the point was not confirmed, not that the answer is no.

Contents

Standards and specifications

Semantic conventions, wire protocols and context propagation standards that agent telemetry is built on.

Back to top

Instrumentation

Libraries and SDKs that produce telemetry from LLM clients, agent frameworks and services.

Back to top

Agent frameworks

Frameworks for building agents, with a note on how each one emits telemetry.

Back to top

Agent protocols and tool servers

SDKs and servers for agent protocols such as MCP and A2A, and how they carry traces.

Back to top

Collectors and pipelines

Collector distributions and components that receive, process, redact and route agent telemetry.

Back to top

Platforms

Products and backends that store, query and visualize agent telemetry.

LLM and agent observability platforms

Platforms built for tracing, evaluating and monitoring LLM applications and agents.

General APM with GenAI support

Application performance monitoring products with features for LLM and agent workloads.

Trace backends and UIs

General backends and front ends for traces, metrics and logs that accept agent telemetry.

Cloud provider offerings

Observability features of the agent runtimes and AI platforms of cloud providers.

Model serving

Inference and serving engines and the telemetry they expose, such as Prometheus metrics.

Back to top

Gateways and proxies

Gateways and proxies for model and agent traffic that record or export telemetry.

Back to top

Evaluation and testing

Evaluation, testing and simulation tools with a documented link to traces or observability.

Back to top

Cost and usage

Token accounting, budgets and cost attribution for agents.

Back to top

Safety signals

Guardrails and runtime monitoring that emit telemetry, limited to their observability side.

Back to top

On-chain agents and payments

Tracing, protocols and infrastructure for agents that send transactions or make payments.

Transaction tracing

Tools and documentation for tracing, replaying and debugging on-chain transactions, including those sent by agents and services.

Payment protocols

Protocols and SDKs for payments made by agents, such as x402, MPP, AP2 and ACP.

RPC and node observability

RPC interfaces, proxies and nodes, and the telemetry they expose.

Wallets and smart accounts

Wallet SDKs, client libraries and smart account infrastructure used by agents.

Local and test chains

Local nodes and toolkits for testing transactions without a public network.

Back to top

Findings

Compatibility notes and bugs that affect agent telemetry, each with public evidence such as an upstream issue.

Back to top

Benchmarks and datasets

Agent trace datasets and observability benchmarks.

Back to top

Learning

Articles, books, talks, papers, courses and case studies on observing agents.

Articles and guides

Blog posts, official guides and demo applications.

Books

Books on agent or LLM observability, and on the observability and OpenTelemetry practice they build on.

Talks and videos

Conference sessions, videos and podcast episodes with a public page.

Papers

Research papers on agent tracing, evaluation and monitoring.

Courses

Courses and workshops.

Case studies

Public write-ups of how organizations observe agents in production, by industry.

Newsletters and podcasts

Regular publications on the topic.

Back to top

Community

Working groups, meetings and channels where agent observability is discussed.

Back to top

Other curated lists that cover parts of this topic.

Back to top

Archived and historical

Entries kept for reference: archived upstream, superseded, or historical. - [OpenTelemetry contrib Vertex AI instrumentation for Python](https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation-genai/opentelemetry-instrumentation-vertexai) - Deprecated OpenTelemetry instrumentation package for the Vertex AI client library in Python. `OSS` Kept because: Deprecated in the GenAI package migration of opentelemetry-python-contrib, with no replacement package planned (README, 2026-10-20).

Back to top

Contributing

Contributions are welcome. Read CONTRIBUTING.md first: one entry per pull request, a neutral one-sentence description, and public evidence for every OTel claim. Submissions may be prepared with AI tools; a person submits them and answers the review.

License

CC0

To the extent possible under law, the contributors have waived all copyright and related rights to this work.