THE PERMISSION [LAYER]

Tools · Agent observability

AI agent and LLM observability tools

These tools record what an agent actually did: each prompt and response, each tool call and its result, and the data it retrieved, and some add the latency, tokens and cost of each step. Most also run evaluations against those traces to catch failures and regressions before and after a release. A team needs one when agents run in production, because without a trace there is no record to check when an agent does something nobody asked for, and incident review and audit both start from that record.

9 tools from 8 vendors. Last updated October 20, 2026. Part of the AI agent governance tools directory.

Agent observability 9

Recent launches

Announced in the last 90 days. Each launch on New tools links the vendor's own announcement.

Questions to ask vendors

Neutral questions for a request for proposal (RFP) or a security questionnaire. No product here is named as the answer.

  1. Does the log capture the full tool call and the full response, and can we export it to our existing security tooling?

    Why it matters

  2. When an agent acts for a user, does the log capture both the agent and the user it acted on behalf of?

    Why it matters

  3. Can an agent, or code it writes, change or switch off its own tracing, and would anyone be told?

  4. How is sensitive data in prompts, tool results and retrieved documents redacted before traces are stored?

  5. Where are traces stored and for how long, and can we host the tool ourselves?

  6. Are traces in OpenTelemetry format, so they can move with us if we change tools?

More questions, grouped by topic: Questions to ask AI agent security vendors.

Related incidents

Every record in the AI agent incident database links the sources that reported it.

Missing a product, or found an entry that is out of date? Write to [email protected]. A submission is read, never paid for, and does not guarantee a listing. The glossary defines the terms used here.

The Permission Layer

Get the briefing by email

At least one email a week on AI agent identity, permissions, security and spend, written for the people who approve agent access. Five-minute read, free.

You confirm by email. Unsubscribe in one click.