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

60

+200% vs previous 7d38 saved production turns

p50 latency

215 ms

-42% vs previous 7d60 timed calls

p95 latency

1.2 s

+23% vs previous 7d60 timed calls

Tool failures

8.3%

+8.3 pts vs previous 7d5 excluding NoResults

No result

0.0%

No change vs previous 7d0 product outcomes

Calls / turn

1.6

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

resolve_documents_by_name failures increased

8.3% now vs 0.0% previously across 60 calls; InvalidArguments is the leading code.

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

Investigate

Latency regression

resolve_documents_by_name p95 slowed 23%

1.2 s now vs 974 ms previously across 60 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.5% previously (37 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
11 calls on 2026-10-019 calls on 2026-10-023 calls on 2026-10-0414 calls on 2026-10-056 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
resolve_documents_by_name60+200% vs prior215 ms-42% vs prior1.2 s+23% vs prior8.3%+8.3 pts vs prior0.0%No change vs prior

Failure codes

Operational failures only; NoResults is excluded.

InvalidArguments5

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

Outcome

Success

Thread

ed7becf5…

Tool call

call_Jz2…

Turn sequence

6 of 29

Turn state

Completed

resolve_documents_by_nameHJC603 msOct 6, 7:22 PM UTC

Outcome

Success

Thread

b612fa70…

Tool call

call_e9A…

Turn sequence

10 of 24

Turn state

Completed

resolve_documents_by_nameHJC159 msOct 6, 6:12 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_f4m…

Turn sequence

5 of 21

Turn state

Completed

resolve_documents_by_nameHJC169 msOct 6, 6:12 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_x6w…

Turn sequence

6 of 21

Turn state

Completed

resolve_documents_by_nameHJC280 msOct 6, 6:12 PM UTC

Outcome

Success

Thread

50ac87df…

Tool call

call_apa…

Turn sequence

8 of 21

Turn state

Completed

resolve_documents_by_nameBidlo315 msOct 6, 3:47 PM UTC

Outcome

Success

Thread

20a1bcaf…

Tool call

call_BmM…

Turn sequence

6 of 48

Turn state

Completed

resolve_documents_by_nameHJC2.1 sOct 5, 11:34 PM UTC

Outcome

Success

Thread

8baa70ed…

Tool call

call_gO4…

Turn sequence

12 of 34

Turn state

Completed

resolve_documents_by_nameHJC2.0 sOct 5, 11:19 PM UTC

Outcome

Success

Thread

8baa70ed…

Tool call

call_9W9…

Turn sequence

13 of 23

Turn state

Completed

resolve_documents_by_nameHJC562 msOct 5, 10:52 PM UTC

Outcome

Success

Thread

8baa70ed…

Tool call

call_BGZ…

Turn sequence

3 of 14

Turn state

Completed

resolve_documents_by_nameHJC291 msOct 5, 9:14 PM UTC

Outcome

Success

Thread

8baa70ed…

Tool call

call_nUz…

Turn sequence

3 of 5

Turn state

Completed

resolve_documents_by_nameHJC564 msOct 5, 9:14 PM UTC

Outcome

Success

Thread

8baa70ed…

Tool call

call_OIQ…

Turn sequence

4 of 5

Turn state

Completed

resolve_documents_by_nameHJC132 msOct 5, 8:39 PM UTC

Outcome

Success

Thread

bf677805…

Tool call

chatcmpl…

Turn sequence

18 of 20

Turn state

Completed

resolve_documents_by_nameHJC1.2 sOct 5, 8:18 PM UTC

Outcome

Success

Thread

8baa70ed…

Tool call

call_nmQ…

Turn sequence

7 of 33

Turn state

Completed

resolve_documents_by_nameHJC2 msOct 5, 8:16 PM UTC

Outcome

InvalidArguments

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

3 of 25

Turn state

Completed

resolve_documents_by_nameHJC0 msOct 5, 8:16 PM UTC

Outcome

InvalidArguments

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

4 of 25

Turn state

Completed

resolve_documents_by_nameHJC123 msOct 5, 8:16 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

5 of 25

Turn state

Completed

resolve_documents_by_nameHJC249 msOct 5, 8:16 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

6 of 25

Turn state

Completed

resolve_documents_by_nameHJC206 msOct 5, 8:16 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

7 of 25

Turn state

Completed

resolve_documents_by_nameHJC268 msOct 5, 8:16 PM UTC

Outcome

Success

Thread

215345f3…

Tool call

chatcmpl…

Turn sequence

8 of 25

Turn state

Completed

resolve_documents_by_nameTexas Materials242 msOct 5, 8:01 PM UTC

Outcome

Success

Thread

464fa3c3…

Tool call

call_zwY…

Turn sequence

4 of 18

Turn state

Completed

resolve_documents_by_nameHJC65 msOct 4, 6:36 PM UTC

Outcome

Success

Thread

913d4f54…

Tool call

chatcmpl…

Turn sequence

3 of 10

Turn state

Completed

resolve_documents_by_nameHJC77 msOct 4, 4:54 PM UTC

Outcome

Success

Thread

e1179f50…

Tool call

call_dRH…

Turn sequence

6 of 16

Turn state

Completed

resolve_documents_by_nameHJC559 msOct 4, 4:35 PM UTC

Outcome

Success

Thread

e1179f50…

Tool call

call_mMq…

Turn sequence

34 of 54

Turn state

Completed

resolve_documents_by_nameHJC192 msOct 2, 7:56 PM UTC

Outcome

Success

Thread

c1a79eab…

Tool call

chatcmpl…

Turn sequence

12 of 28

Turn state

Completed

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