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

-33% vs previous 7d16 saved production turns

p50 latency

0 ms

Timing not instrumented14 timed calls

p95 latency

1 ms

Timing not instrumented14 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.0

No change 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
1 calls on 2026-08-023 calls on 2026-08-031 calls on 2026-08-043 calls on 2026-08-056 calls on 2026-08-062 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
get_team_collections16-33% vs prior0 msNo prior timing1 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
get_team_collectionsBidlo0 msAug 7, 4:59 PM UTC

Outcome

Success

Thread

c9d2c295…

Tool call

call_V1O…

Turn sequence

1 of 1

Turn state

Completed

get_team_collectionsBidlo - dev1 msAug 7, 3:25 PM UTC

Outcome

Success

Thread

c4d541df…

Tool call

call_EsR…

Turn sequence

1 of 1

Turn state

Completed

get_team_collectionsBidlo0 msAug 6, 9:20 PM UTC

Outcome

Success

Thread

5a4e8ad2…

Tool call

call_x6A…

Turn sequence

2 of 9

Turn state

Completed

get_team_collectionsBidlo1 msAug 6, 9:15 PM UTC

Outcome

Success

Thread

1ab2ebd7…

Tool call

call_fSL…

Turn sequence

7 of 19

Turn state

Completed

get_team_collectionsBidlo0 msAug 6, 8:53 PM UTC

Outcome

Success

Thread

21602129…

Tool call

call_a2r…

Turn sequence

3 of 19

Turn state

Completed

get_team_collectionsHJCNot timedAug 6, 5:59 PM UTC

Outcome

Success

Thread

cca85bae…

Tool call

call_ldn…

Turn sequence

1 of 14

Turn state

Completed

get_team_collectionsBidlo0 msAug 6, 1:15 PM UTC

Outcome

Success

Thread

a4c6b869…

Tool call

call_8ET…

Turn sequence

4 of 18

Turn state

Completed

get_team_collectionsBidlo1 msAug 6, 1:04 PM UTC

Outcome

Success

Thread

66970855…

Tool call

call_D8y…

Turn sequence

7 of 15

Turn state

Completed

get_team_collectionsRagle0 msAug 5, 9:40 PM UTC

Outcome

Success

Thread

057b75a0…

Tool call

toolu_01…

Turn sequence

7 of 12

Turn state

Completed

get_team_collectionsHJCNot timedAug 5, 8:26 PM UTC

Outcome

Success

Thread

d02bb273…

Tool call

call_OZk…

Turn sequence

1 of 20

Turn state

Completed

get_team_collectionsHJC1 msAug 5, 2:09 PM UTC

Outcome

Success

Thread

4c56afbc…

Tool call

call_ZJS…

Turn sequence

3 of 11

Turn state

Completed

get_team_collectionsHJC0 msAug 4, 4:52 PM UTC

Outcome

Success

Thread

c1ea98f7…

Tool call

call_BC9…

Turn sequence

5 of 30

Turn state

Completed

get_team_collectionsTexas Materials0 msAug 3, 5:33 PM UTC

Outcome

Success

Thread

1765bb64…

Tool call

call_rW1…

Turn sequence

4 of 20

Turn state

Completed

get_team_collectionsHJC0 msAug 3, 3:59 PM UTC

Outcome

Success

Thread

562421d5…

Tool call

call_tlR…

Turn sequence

11 of 17

Turn state

Completed

get_team_collectionsHJC0 msAug 3, 3:45 PM UTC

Outcome

Success

Thread

f5d38ce1…

Tool call

call_mZl…

Turn sequence

2 of 28

Turn state

Completed

get_team_collectionsBidlo0 msAug 2, 9:14 PM UTC

Outcome

Success

Thread

8ae68fe4…

Tool call

call_js5…

Turn sequence

3 of 18

Turn state

Completed

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