Skip to main content
Ask your agent data a question in plain English and get an answer that links straight to the evidence. No SQL to write, no dashboards to dig through — the Failproof AI Observability assistant is the fastest way for anyone on your team to get answers about your agents. The Failproof AI Observability assistant answering a plain-English question inside the dashboard, showing a live Agent Activity table, a per-agent model-usage breakdown, and written takeaways, with the queries it ran shown inline Ask in plain English and get an answer built from your own data. Here it breaks down which agents are busiest and which models they use, and shows the queries it ran so you can verify every number. There is nothing to learn. Open the chat, type what you want to know, and follow the links it hands back:

​
Just ask, and jump straight to the proof

You stop guessing and you stop writing queries. Ask “how is quality trending in prod this week?”, “which sessions errored today?”, or “summarize this session,” and you get a straight answer in seconds instead of building a query and reading it yourself. Every answer comes with its receipts. The assistant links the exact sessions, saved queries, and dashboards it used to reach the answer, so you can click through and confirm rather than take its word for it. It is also page-aware: ask about “this session” while you are viewing one and it already knows which run you mean. Reopen any earlier conversation later from the history switcher and pick up where you left off.

​
Turn a good answer into a saved query or dashboard

When an answer is worth keeping, ask the assistant to save it. It drafts the SQL for a saved query, or assembles a dashboard from those queries, then shows you an Approve / Reject card. Nothing is written until you click Approve, so you get the speed of “just ask” with the last word always yours. On the Queries page it goes a step further and becomes a SQL author: describe the query you want (“show error rate by agent for the last 7 days”) and it streams SQL straight into the editor, opening a diff view so you can Accept or Reject the change before it lands. The Observability Queries page and its SQL editor The Queries page: this editor is where the assistant streams a draft, read-only query for you to accept or reject. Authoring SQL by asking here uses the queries:run permission, the same one behind the editor’s Run button. Chat everywhere else needs agent:use.

​
Safe to hand to the whole team

You can open the assistant up to everyone without worrying about what it might touch:
  • It reads only what you can already see. Answers are scoped to your own read permissions, so it never widens your data surface.
  • Every write waits for you. Saved queries and dashboards are created only after your explicit Approve click, and there is no setting that turns that gate off.
  • It can never delete anything. No delete tool is exposed and the assistant holds no delete permission. Deletions stay in your hands, in the dashboard.
  • It stays inside your org. The assistant only ever sees the organization you are currently viewing.
  • Your questions stay yours. Prompts and answers live in your own Observability database; product analytics records usage metadata only, never your prompt text.

​
Where to find it

The assistant rides along on the right edge of every page under your org (/<org-slug>/...). Click the rail, or press ⌘J / Ctrl+J, to expand it into the full chat panel, and drag its edge to resize; your width is remembered across reloads. You need the agent:use permission to use it, otherwise the rail is greyed out. If it has not been switched on for your deployment yet (it needs an LLM connection), you will see a muted rail in place of a working chat.