Pulse
Compare tool-call volume, success rate and latency across the tools your agents call.
Watch the workflow: Follow tool failures into recorded calls · Authored dummy data
Compare authored tool performance, follow failed calls into Raw Logs and inspect one failure. A tool failure is not a customer outcome.
Read the walkthrough transcript
- 00:00 — Compare tool success and latency in Tensile. These are authored demo events.
- 00:05 — Open the failed lookup_order calls. The scope follows the link to Raw Logs.
- 00:11 — Inspect one recorded failure. Tool success does not prove customer success.
Open Pulse to see which tools your agents call, how often those calls succeed and how long they take. Use it to find a slow or failing tool before you read single events.
Before you start, send tool-call events through the ingestion API or connect a supported trace source.
Set the scope
Use the time control and the customer filter at the top of the page. Pulse does not default to Production. Choose an environment yourself when you want one.
Read the page
- The four cards show Tools shown, Invocations shown, Tool success shown and the lowest-success tool. They cover the tool rows now on the page.
- Tool Performance lists each tool with its latency percentiles and success rate.
- Latency Percentiles charts p50, p90 and p99 for each tool.
- Success vs Failure shows the share of successful and failed calls.
- Calls by Type shows No per-type breakdown available yet. for a live workspace.
A tool call that succeeds does not show that the customer task succeeded.
Look at the calls behind a number
Select a tool to open Raw Logs for that tool with the same scope. The Raw Logs page lists at most the 200 most recent matching calls. It does not list every call that Pulse counted, so the two counts can differ.
Empty and failed states
- No tool activity in this range appears when no tool call matches. Widen the range or clear the customer filter.
- If page filters hide every row but the scope has events, Pulse says so and lets you remove each filter.
- If the query fails, an error state appears. Pulse never shows sample data in its place for a live workspace.
Next steps
Open Error Captures to group failed calls by result.