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

16

+167% vs previous 7d13 saved production turns

p50 latency

129 ms

Timing not instrumented12 timed calls

p95 latency

400 ms

Timing not instrumented12 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.2

+23% 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

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
1 calls on 2026-08-0311 calls on 2026-08-064 calls on 2026-08-07
Aug 2Aug 5Aug 8

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_typecheck16+167% vs prior129 msNo prior timing400 msNo 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_typecheckHJC137 msAug 7, 4:02 PM UTC

Outcome

Success

Thread

de203492…

Tool call

call_KiR…

Turn sequence

6 of 6

Turn state

Completed

app_typecheckHJC106 msAug 7, 3:58 PM UTC

Outcome

Success

Thread

582bd8f4…

Tool call

call_1Fx…

Turn sequence

9 of 9

Turn state

Completed

app_typecheckHJC128 msAug 7, 3:55 PM UTC

Outcome

Success

Thread

28ab5468…

Tool call

call_APX…

Turn sequence

10 of 11

Turn state

Completed

app_typecheckHJC119 msAug 7, 3:38 PM UTC

Outcome

Success

Thread

1047785c…

Tool call

call_QSN…

Turn sequence

11 of 11

Turn state

Completed

app_typecheckBidlo129 msAug 6, 9:16 PM UTC

Outcome

Success

Thread

1ab2ebd7…

Tool call

call_ERT…

Turn sequence

18 of 19

Turn state

Completed

app_typecheckHJCNot timedAug 6, 5:59 PM UTC

Outcome

Success

Thread

cca85bae…

Tool call

call_IDg…

Turn sequence

12 of 14

Turn state

Completed

app_typecheckHJCNot timedAug 6, 5:50 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_BAX…

Turn sequence

13 of 21

Turn state

Completed

app_typecheckHJCNot timedAug 6, 5:50 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_UMl…

Turn sequence

16 of 21

Turn state

Completed

app_typecheckHJCNot timedAug 6, 5:50 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_Q3V…

Turn sequence

20 of 21

Turn state

Completed

app_typecheckHJC103 msAug 6, 5:47 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_yI0…

Turn sequence

12 of 13

Turn state

Completed

app_typecheckHJC400 msAug 6, 5:45 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_vBc…

Turn sequence

26 of 39

Turn state

Completed

app_typecheckHJC141 msAug 6, 5:45 PM UTC

Outcome

Success

Thread

1c6b6c3e…

Tool call

call_EiF…

Turn sequence

38 of 39

Turn state

Completed

app_typecheckHJC124 msAug 6, 5:40 PM UTC

Outcome

Success

Thread

2d1997bc…

Tool call

call_HSx…

Turn sequence

5 of 6

Turn state

Completed

app_typecheckHJC142 msAug 6, 5:37 PM UTC

Outcome

Success

Thread

2d1997bc…

Tool call

call_GWO…

Turn sequence

26 of 27

Turn state

Completed

app_typecheckBidlo354 msAug 6, 1:05 PM UTC

Outcome

Success

Thread

66970855…

Tool call

call_tyr…

Turn sequence

15 of 15

Turn state

Completed

app_typecheckBidlo141 msAug 3, 2:21 PM UTC

Outcome

Success

Thread

fb5e59c8…

Tool call

call_GGC…

Turn sequence

11 of 11

Turn state

Completed

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