Tensile Docs

Error Captures

Group failed tool calls and agent turns by operation and result, then open the matching events.

Watch the workflow: Inspect a repeated failure group · Authored dummy data

Inspect an authored timeout group, read its original result and open the failed operation requests. Matching text is not a root cause.

Read the walkthrough transcript
  • 00:00 — Open a repeated failure group in Tensile. These are authored demo events.
  • 00:05 — Read the recorded timeout. Matching text does not establish one root cause.
  • 00:11 — Open this operation's failed requests. Each row is an event, not a customer outcome.

Open Error Captures to see which failures repeat. The page groups failed event rows by operation and recorded result. A group is an observation. It is not a confirmed incident or a cause.

Before you start, send events to Tensile. A row appears here when an event is recorded as failed. Detector-created incidents are separate. Find them in Triage.

Read the summary

The first three cards summarize the failed rows in the selected time range and scope. The subtitle states the window and how many failed rows are in scope. Failed rows can include redeliveries.

Choose a view

Use the Failure views tabs.

  • Message groups lists the top groups of exact operation and result. Similar messages can be separate groups. The list shows eight groups. Select Show all to see the rest.
  • Recent events lists the latest failed rows, 12 to a page. Use Previous and Next to move between pages.

Use the search box to filter the current view.

Inspect a failure

  1. Select a group or an event. A details pane opens.
  2. Read the operation, the failed rows, the sessions and the last seen time. The sessions value says Not measured when it cannot be counted.
  3. Open View original result to read the recorded text. It can include customer or model content.
  4. Select an inspect link under Matching events to open the session. A group shows up to five examples.
  5. Select Open all failed requests for this operation to open Raw Logs for failed calls of that operation.

Affected operations lists the top operations by failed rows with their error rate. Select Inspect to open Raw Logs for one operation.

Empty and failed states

  • No errors in this range appears when no failed call or turn matches. Widen the range or clear the customer filter.
  • If page filters hide every failure but the scope has some, the page says so and lets you remove each filter.
  • If the query fails, an error state appears.
  • If raw trace access is held for the workspace, a notice replaces the page.

Next steps

Select Review detected incidents to go to Triage.

On this page