Raw Logs
Read the most recent events your agents sent, newest first, with the scope you choose.
Watch the workflow: Inspect a recorded tool failure · Authored dummy data
Filter authored requests, inspect one failed tool call and read its recorded timeout. An event failure does not establish a customer outcome.
This recording predates the integration-owned logs route and the main-navigation change. The authenticated Raw Logs destination remains available by direct SDK link and from Pulse or Error Captures drilldowns; saved Braintrust and Langfuse connections also offer logs inside Settings → Integrations, with their own source scope. The recorded clip does not demonstrate those new routes.
Read the walkthrough transcript
- 00:00 — Filter the loaded requests to Failed. These are authored demo events.
- 00:05 — Inspect one failed tool call. Its identity and latency remain visible.
- 00:10 — Read the recorded timeout. An event failure is separate from a customer outcome.
Open /raw-logs directly or follow a Raw Logs link from Pulse or Error Captures to read individual events as Tensile received them. Use it to check what an agent sent, or to look at the calls behind a number on another page. For one connected Braintrust project or a Langfuse connection, open View logs within Settings → Integrations instead.
Before you start, send events through the ingestion API or connect a supported trace source.
Read the list
The list shows the 200 most recent events that match your scope, newest first. The count above the list shows how many events match. When more events match, the page tells you how many it loaded. Narrow the filters or the time range to reach older events.
Each row is one event. It is not a customer task outcome.
Inspect one request
Select a request to open its details. Use Info, Attributes, Input and Output to inspect the selected event. The payload loads for that request. Open full session opens the related conversation.
Use Show loaded status to filter the loaded rows to Success or Failed. This filter does not change the full matching-event count.
Set the scope
- Use the time control and the customer filter. Selected scope appears as removable chips.
- Raw Logs does not default to Production. Choose an environment yourself when you want one.
- A line above the list states what share of events carry an environment tag.
Come from Pulse or Error Captures
When you open Raw Logs from a tool in Pulse, the page shows Back to Pulse tools. It also explains how these rows relate to the Pulse numbers. Pulse counts every matching call. The list shows at most 200, so it can omit some failures. If the time range or scope differs from the Pulse view, the page says that the rows do not correspond to its metrics.
When you open Raw Logs from Error Captures, the list shows failed calls of the chosen operation.
Empty and failed states
- No requests in this range appears when no event matches. Widen the range or clear the customer filter.
- A message names the environment tag when the range has events but none carry that tag. Select Show all environments.
- If page filters hide every event 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
Open a conversation in User Stories.