Bidlo Status Frontend

Chat tool telemetry

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

Detailed production timing active

495 of 570 saved tool calls include execution duration.

86.8% timing coverage

Tool calls

13

+333% vs previous 7d8 saved production turns

p50 latency

219 ms

Timing not instrumented11 timed calls

p95 latency

2.4 s

Timing not instrumented11 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

1.6

-46% vs previous 7d87.5% 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

Stable against baseline

No material tool regressions detected

Tools with enough activity were checked for higher failure rates, available p95 latency regressions, more no-results, and increased loop pressure.

Review the tool comparison for absolute hotspots that may still need a product threshold.

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
8 calls on 2026-08-065 calls on 2026-08-07
Aug 1Aug 4Aug 7

Payload pressure

How often results exceed the 20 KB inline cap.

Unavailable

handle rows / all calls

The handle store could not be read with the current credentials.

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_shell13+333% vs prior219 msNo prior timing2.4 sNo prior timing0.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_shellHJC2.4 sAug 7, 3:41 PM UTC

Outcome

Success

Thread

1047785c…

Tool call

call_Ic1…

Turn sequence

1 of 14

Turn state

Completed

app_shellHJC219 msAug 7, 3:41 PM UTC

Outcome

Success

Thread

1047785c…

Tool call

call_hZF…

Turn sequence

4 of 14

Turn state

Completed

app_shellHJC89 msAug 7, 3:42 PM UTC

Outcome

Success

Thread

1047785c…

Tool call

call_cUr…

Turn sequence

9 of 14

Turn state

Completed

app_shellHJC98 msAug 7, 3:42 PM UTC

Outcome

Success

Thread

1047785c…

Tool call

call_cYa…

Turn sequence

11 of 14

Turn state

Completed

app_shellHJC470 msAug 7, 3:38 PM UTC

Outcome

Success

Thread

1047785c…

Tool call

call_8G3…

Turn sequence

9 of 11

Turn state

Completed

app_shellBidlo132 msAug 6, 9:15 PM UTC

Outcome

Success

Thread

1ab2ebd7…

Tool call

call_Hab…

Turn sequence

13 of 19

Turn state

Completed

app_shellHJC1.5 sAug 6, 6:04 PM UTC

Outcome

Success

Thread

cca85bae…

Tool call

call_Mqc…

Turn sequence

1 of 1

Turn state

Completed

app_shellHJCNot timedAug 6, 5:59 PM UTC

Outcome

Success

Thread

cca85bae…

Tool call

call_Mqc…

Turn sequence

14 of 14

Turn state

Completed

app_shellHJCNot timedAug 6, 5:50 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_YLz…

Turn sequence

17 of 21

Turn state

Completed

app_shellHJC901 msAug 6, 5:46 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_XKM…

Turn sequence

4 of 13

Turn state

Completed

app_shellHJC77 msAug 6, 5:46 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_jUp…

Turn sequence

7 of 13

Turn state

Completed

app_shellHJC265 msAug 6, 5:47 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_ftf…

Turn sequence

8 of 13

Turn state

Completed

app_shellHJC113 msAug 6, 5:43 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_Y1o…

Turn sequence

20 of 39

Turn state

Completed

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