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

161

+19% vs previous 7d44 saved production turns

p50 latency

398 ms

-30% vs previous 7d161 timed calls

p95 latency

1.9 s

+139% vs previous 7d161 timed calls

Tool failures

0.0%

No change vs previous 7d0 excluding NoResults

No result

0.0%

No change vs previous 7d0 product outcomes

Calls / turn

3.7

+38% vs previous 7d100.0% 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

app_run_data_request p95 slowed 139%

1.9 s now vs 801 ms previously across 161 calls.

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

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
2 calls on 2026-10-017 calls on 2026-10-0227 calls on 2026-10-0415 calls on 2026-10-0541 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
app_run_data_request161+19% vs prior398 ms-30% vs prior1.9 s+139% vs prior0.0%No change vs prior0.0%No change vs prior

Failure codes

Operational failures only; NoResults is excluded.

No operational failures

in the selected view

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
app_run_data_requestHJC428 msOct 6, 8:10 PM UTC

Outcome

Success

Thread

ed7becf5…

Tool call

call_sDA…

Turn sequence

16 of 29

Turn state

Completed

app_run_data_requestHJC500 msOct 6, 8:12 PM UTC

Outcome

Success

Thread

ed7becf5…

Tool call

call_bMT…

Turn sequence

29 of 29

Turn state

Completed

app_run_data_requestHJC2 msOct 6, 8:01 PM UTC

Outcome

Success

Thread

ed7becf5…

Tool call

call_gtV…

Turn sequence

5 of 27

Turn state

Completed

app_run_data_requestHJC359 msOct 6, 8:02 PM UTC

Outcome

Success

Thread

ed7becf5…

Tool call

call_QPF…

Turn sequence

11 of 27

Turn state

Completed

app_run_data_requestHJC389 msOct 6, 7:36 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_AoV…

Turn sequence

29 of 41

Turn state

Completed

app_run_data_requestHJC1 msOct 6, 7:22 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_djW…

Turn sequence

16 of 24

Turn state

Completed

app_run_data_requestHJC1 msOct 6, 7:22 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_9GP…

Turn sequence

17 of 24

Turn state

Completed

app_run_data_requestHJC0 msOct 6, 7:22 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_5vN…

Turn sequence

18 of 24

Turn state

Completed

app_run_data_requestHJC482 msOct 6, 7:23 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_0PO…

Turn sequence

22 of 24

Turn state

Completed

app_run_data_requestHJC491 msOct 6, 7:23 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_9HW…

Turn sequence

23 of 24

Turn state

Completed

app_run_data_requestHJC500 msOct 6, 7:23 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_zYg…

Turn sequence

24 of 24

Turn state

Completed

app_run_data_requestHJC1 msOct 6, 7:07 PM UTC

Outcome

Success

Thread

dae0a154…

Tool call

call_Mzh…

Turn sequence

4 of 36

Turn state

Completed

app_run_data_requestHJC417 msOct 6, 7:07 PM UTC

Outcome

Success

Thread

dae0a154…

Tool call

call_bM3…

Turn sequence

13 of 36

Turn state

Completed

app_run_data_requestHJC406 msOct 6, 7:07 PM UTC

Outcome

Success

Thread

dae0a154…

Tool call

call_1hy…

Turn sequence

14 of 36

Turn state

Completed

app_run_data_requestHJC1.4 sOct 6, 7:07 PM UTC

Outcome

Success

Thread

dae0a154…

Tool call

call_KdV…

Turn sequence

15 of 36

Turn state

Completed

app_run_data_requestHJC173 msOct 6, 7:07 PM UTC

Outcome

Success

Thread

dae0a154…

Tool call

call_9Mi…

Turn sequence

16 of 36

Turn state

Completed

app_run_data_requestHJC376 msOct 6, 7:08 PM UTC

Outcome

Success

Thread

dae0a154…

Tool call

call_0Qw…

Turn sequence

24 of 36

Turn state

Completed

app_run_data_requestHJC430 msOct 6, 7:10 PM UTC

Outcome

Success

Thread

dae0a154…

Tool call

call_nBU…

Turn sequence

30 of 36

Turn state

Completed

app_run_data_requestHJC490 msOct 6, 6:44 PM UTC

Outcome

Success

Thread

d41e378a…

Tool call

call_qoc…

Turn sequence

11 of 29

Turn state

Completed

app_run_data_requestHJC519 msOct 6, 6:44 PM UTC

Outcome

Success

Thread

d41e378a…

Tool call

call_mbs…

Turn sequence

12 of 29

Turn state

Completed

app_run_data_requestHJC144 msOct 6, 6:44 PM UTC

Outcome

Success

Thread

d41e378a…

Tool call

call_VQU…

Turn sequence

15 of 29

Turn state

Completed

app_run_data_requestHJC155 msOct 6, 6:44 PM UTC

Outcome

Success

Thread

d41e378a…

Tool call

call_Gmb…

Turn sequence

16 of 29

Turn state

Completed

app_run_data_requestHJC457 msOct 6, 6:46 PM UTC

Outcome

Success

Thread

d41e378a…

Tool call

call_GjD…

Turn sequence

28 of 29

Turn state

Completed

app_run_data_requestHJC476 msOct 6, 6:46 PM UTC

Outcome

Success

Thread

d41e378a…

Tool call

call_ZdK…

Turn sequence

29 of 29

Turn state

Completed

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