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

473

+134% vs previous 7d117 saved production turns

p50 latency

267 ms

No change vs previous 7d471 timed calls

p95 latency

3.6 s

+191% vs previous 7d471 timed calls

Tool failures

8.2%

-5.1 pts vs previous 7d39 excluding NoResults

No result

0.0%

No change vs previous 7d0 product outcomes

Calls / turn

4.0

+22% vs previous 7d89.7% 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

Latency regression

query_database_data p95 slowed 191%

3.6 s now vs 1.2 s previously across 473 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

89.7% now vs 75.4% previously (105 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
136 calls on 2026-10-0146 calls on 2026-10-028 calls on 2026-10-0326 calls on 2026-10-0482 calls on 2026-10-0532 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
query_database_data473+134% vs prior267 msNo change vs prior3.6 s+191% vs prior8.2%-5.1 pts vs prior0.0%No change vs prior

Failure codes

Operational failures only; NoResults is excluded.

InvalidArguments39

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
query_database_dataHJC127 msOct 6, 8:05 PM UTC

Outcome

Success

Thread

ed7becf5…

Tool call

call_dci…

Turn sequence

8 of 29

Turn state

Completed

query_database_dataHJC169 msOct 6, 7:48 PM UTC

Outcome

InvalidArguments

Thread

ed7becf5…

Tool call

chatcmpl…

Turn sequence

1 of 6

Turn state

Completed

query_database_dataHJC207 msOct 6, 7:48 PM UTC

Outcome

Success

Thread

ed7becf5…

Tool call

chatcmpl…

Turn sequence

2 of 6

Turn state

Completed

query_database_dataHJC401 msOct 6, 7:48 PM UTC

Outcome

Success

Thread

ed7becf5…

Tool call

chatcmpl…

Turn sequence

4 of 6

Turn state

Completed

query_database_dataHJC184 msOct 6, 7:36 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_5vs…

Turn sequence

30 of 41

Turn state

Completed

query_database_dataHJC243 msOct 6, 7:22 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_ZMH…

Turn sequence

13 of 24

Turn state

Completed

query_database_dataHJC282 msOct 6, 7:22 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_tKc…

Turn sequence

14 of 24

Turn state

Completed

query_database_dataHJC955 msOct 6, 7:22 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_b0Z…

Turn sequence

15 of 24

Turn state

Completed

query_database_dataHJC182 msOct 6, 7:17 PM UTC

Outcome

InvalidArguments

Thread

1af0e222…

Tool call

chatcmpl…

Turn sequence

1 of 1

Turn state

Completed

query_database_dataHJC181 msOct 6, 7:14 PM UTC

Outcome

InvalidArguments

Thread

3d7ad6cb…

Tool call

chatcmpl…

Turn sequence

1 of 9

Turn state

Completed

query_database_dataHJC180 msOct 6, 7:14 PM UTC

Outcome

InvalidArguments

Thread

3d7ad6cb…

Tool call

chatcmpl…

Turn sequence

2 of 9

Turn state

Completed

query_database_dataHJC152 msOct 6, 7:14 PM UTC

Outcome

InvalidArguments

Thread

3d7ad6cb…

Tool call

chatcmpl…

Turn sequence

3 of 9

Turn state

Completed

query_database_dataHJC184 msOct 6, 7:14 PM UTC

Outcome

InvalidArguments

Thread

3d7ad6cb…

Tool call

chatcmpl…

Turn sequence

4 of 9

Turn state

Completed

query_database_dataHJC358 msOct 6, 7:14 PM UTC

Outcome

Success

Thread

3d7ad6cb…

Tool call

chatcmpl…

Turn sequence

5 of 9

Turn state

Completed

query_database_dataHJC474 msOct 6, 7:14 PM UTC

Outcome

Success

Thread

3d7ad6cb…

Tool call

chatcmpl…

Turn sequence

6 of 9

Turn state

Completed

query_database_dataHJC3.5 sOct 6, 7:14 PM UTC

Outcome

Success

Thread

3d7ad6cb…

Tool call

chatcmpl…

Turn sequence

7 of 9

Turn state

Completed

query_database_dataHJC226 msOct 6, 7:06 PM UTC

Outcome

Success

Thread

dae0a154…

Tool call

chatcmpl…

Turn sequence

2 of 3

Turn state

Completed

query_database_dataHJC208 msOct 6, 7:02 PM UTC

Outcome

Success

Thread

033cbc16…

Tool call

chatcmpl…

Turn sequence

4 of 5

Turn state

Completed

query_database_dataHJC174 msOct 6, 6:12 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_zVX…

Turn sequence

7 of 21

Turn state

Completed

query_database_dataHJC339 msOct 6, 6:12 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_JzA…

Turn sequence

9 of 21

Turn state

Completed

query_database_dataHJC159 msOct 6, 6:12 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_GQg…

Turn sequence

13 of 21

Turn state

Completed

query_database_dataHJC232 msOct 6, 6:13 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_2is…

Turn sequence

21 of 21

Turn state

Completed

query_database_dataHJC198 msOct 6, 6:04 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_83e…

Turn sequence

6 of 13

Turn state

Completed

query_database_dataHJC254 msOct 6, 5:58 PM UTC

Outcome

Success

Thread

7839e632…

Tool call

call_FQj…

Turn sequence

7 of 15

Turn state

Completed

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