Bidlo Status Frontend

Chat tool telemetry

Find slow, failing, and repetitive agent tools without exposing prompts, arguments, or outputs.

Detailed production timing active

6101 of 6166 saved tool calls include execution duration.

98.9% timing coverage

Tool calls

111

+66% vs previous 7d39 saved production turns

p50 latency

0 ms

-100% vs previous 7d111 timed calls

p95 latency

138 ms

+35% vs previous 7d111 timed calls

Tool failures

9.9%

+9.9 pts vs previous 7d11 excluding NoResults

No result

0.0%

No change vs previous 7d0 product outcomes

Calls / turn

2.8

+40% vs previous 7d97.4% of turns at 5+ calls

What changed

Material regressions ranked by severity and affected call volume.

Current 7 days compared with the previous equal window

Reliability regression

read_tool_result failures increased

9.9% now vs 0.0% previously across 111 calls; NotFound is the leading code.

Inspect recent failures, then check the tool handler and upstream dependency logs.

Investigate

Latency regression

read_tool_result p95 slowed 35%

138 ms now vs 102 ms previously across 111 calls.

Open the tool view and inspect the slowest recent calls for a repeatable bottleneck.

Investigate

Agent loop pressure

More turns are using five or more tools

97.4% now vs 87.9% previously (38 turns).

Inspect the affected turn sequences for repeated or avoidable tool selection.

Investigate

Regression checks require at least 3 calls in both windows. Latency is flagged at +20%; failure and no-result rates are flagged at +1 and +3 points respectively.

Execution volume

Successful calls, no-results, and failures combined.

Calls
46 calls on 2026-10-0114 calls on 2026-10-024 calls on 2026-10-0413 calls on 2026-10-053 calls on 2026-10-06
Oct 1Oct 4Oct 7

Payload pressure

How often results exceed the 20 KB inline cap.

5.0%

handle rows / all calls

309 stored handles in this period. This is a payload-size proxy, not a one-to-one call classification.

Tool comparison

Each change is measured against the previous equal window; latency appears only where detailed timing exists.

Sorted by current p95 latency
ToolCallsp50p95FailuresNo result
read_tool_result111+66% vs prior0 ms-100% vs prior138 ms+35% vs prior9.9%+9.9 pts vs prior0.0%No change vs prior

Failure codes

Operational failures only; NoResults is excluded.

NotFound11

Interpretation notes

The data has known edges that change what a chart means.

Blocked loops are invisible
Rate-limited and identical-argument calls are rejected before telemetry fires.
NoResults is not downtime
It remains a failed tool outcome, but is separated from runtime reliability here.
Preview volume lives elsewhere
Preview and threadless chats reach PostHog but are intentionally absent from Postgres.
Latency is partially instrumented
Saved tool parts provide production outcomes and volume; duration appears only on calls with detailed telemetry.
Partial turns are retained
They remain in volume counts but are excluded from failures and latency percentiles.
Comparisons use equal windows
Every delta compares the selected period with the immediately preceding period under the same tool and team filters.

Recent sanitized calls

Arguments, outputs, user IDs, and message content are never rendered.

Privacy safe
read_tool_resultHJC146 msOct 6, 7:36 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_kuh…

Turn sequence

28 of 41

Turn state

Completed

read_tool_resultHJC0 msOct 6, 6:08 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_Vz3…

Turn sequence

12 of 28

Turn state

Completed

read_tool_resultHJC0 msOct 6, 6:09 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_TKo…

Turn sequence

17 of 28

Turn state

Completed

read_tool_resultHJC164 msOct 5, 9:24 PM UTC

Outcome

Success

Thread

8baa70ed…

Tool call

call_kbx…

Turn sequence

18 of 49

Turn state

Completed

read_tool_resultHJC99 msOct 5, 9:24 PM UTC

Outcome

Success

Thread

8baa70ed…

Tool call

call_7EG…

Turn sequence

19 of 49

Turn state

Completed

read_tool_resultHJC0 msOct 5, 8:06 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

19 of 38

Turn state

Completed

read_tool_resultHJC0 msOct 5, 8:06 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

20 of 38

Turn state

Completed

read_tool_resultHJC0 msOct 5, 8:07 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

29 of 38

Turn state

Completed

read_tool_resultHJC0 msOct 5, 8:08 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

30 of 38

Turn state

Completed

read_tool_resultHJC0 msOct 5, 8:08 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

32 of 38

Turn state

Completed

read_tool_resultTexas Materials1 msOct 5, 8:01 PM UTC

Outcome

Success

Thread

464fa3c3…

Tool call

call_ZiC…

Turn sequence

3 of 18

Turn state

Completed

read_tool_resultHJC34 msOct 5, 7:31 PM UTC

Outcome

NotFound

Thread

10f9fa7b…

Tool call

call_MQj…

Turn sequence

8 of 11

Turn state

Completed

read_tool_resultRagle62 msOct 5, 4:20 PM UTC

Outcome

Success

Thread

a7a7a1cd…

Tool call

call_Yqz…

Turn sequence

1 of 13

Turn state

Completed

read_tool_resultHJC1 msOct 5, 10:21 AM UTC

Outcome

Success

Thread

ca157012…

Tool call

chatcmpl…

Turn sequence

21 of 33

Turn state

Completed

read_tool_resultHJC0 msOct 5, 10:21 AM UTC

Outcome

Success

Thread

ca157012…

Tool call

chatcmpl…

Turn sequence

24 of 33

Turn state

Completed

read_tool_resultHJC0 msOct 5, 10:22 AM UTC

Outcome

Success

Thread

ca157012…

Tool call

chatcmpl…

Turn sequence

28 of 33

Turn state

Completed

read_tool_resultHJC1 msOct 4, 6:51 PM UTC

Outcome

Success

Thread

913d4f54…

Tool call

chatcmpl…

Turn sequence

3 of 16

Turn state

Completed

read_tool_resultHJC0 msOct 4, 6:47 PM UTC

Outcome

Success

Thread

913d4f54…

Tool call

chatcmpl…

Turn sequence

13 of 22

Turn state

Completed

read_tool_resultHJC0 msOct 4, 6:47 PM UTC

Outcome

Success

Thread

913d4f54…

Tool call

chatcmpl…

Turn sequence

14 of 22

Turn state

Completed

read_tool_resultHJC0 msOct 4, 3:25 PM UTC

Outcome

Success

Thread

94d1ea5b…

Tool call

chatcmpl…

Turn sequence

15 of 21

Turn state

Completed

read_tool_resultBidlo1 msOct 2, 11:57 PM UTC

Outcome

Success

Thread

593e57f5…

Tool call

call_Oe3…

Turn sequence

6 of 8

Turn state

Completed

read_tool_resultHJC1 msOct 2, 7:55 PM UTC

Outcome

Success

Thread

c1a79eab…

Tool call

chatcmpl…

Turn sequence

2 of 28

Turn state

Completed

read_tool_resultHJC0 msOct 2, 7:55 PM UTC

Outcome

Success

Thread

c1a79eab…

Tool call

chatcmpl…

Turn sequence

3 of 28

Turn state

Completed

read_tool_resultHJC0 msOct 2, 7:55 PM UTC

Outcome

Success

Thread

c1a79eab…

Tool call

chatcmpl…

Turn sequence

4 of 28

Turn state

Completed

Source: Production chat_messages.tool_results (saved tool parts and detailed telemetry) Tool execution time starts after approval gates.