snapshot of 2026-09-15 · Named ways a run stumbled, as a rate against the work done. · read-only
This is a frozen snapshot, not a live page. It shows one day and does not update. The live version runs on the operator's own machine and is not public. Figures are read from the engine's own stores for 2026-09-15; the snapshot was taken on 2026-09-15.
74.1friction events per 1k requeststhe rate that matters
1,482friction eventsraw count that day
What the friction was
signal
events
share
tool:malformed
645
43.5%
tool:guardrail
288
19.4%
llm:network
219
14.8%
tool:error
183
12.3%
llm:invalid_request
81
5.5%
tool:security
33
2.2%
tool:budget
24
1.6%
tool:retriable
7
0.5%
finish:error
1
0.1%
finish:length
1
0.1%
llm:other
0
0.0%
llm:rate_limit
0
0.0%
tool:other
0
0.0%
A friction signal is a named way a run stumbled - an error at finish, a retry, a malformed reply. The list is the engine's own vocabulary, not a severity ranking.
Day by day
day
events
per 1k requests
2026-09-15
1,482
74.1
2026-09-14
2,749
58.2
2026-09-13
1,484
39.0
2026-09-12
2,147
47.3
2026-09-11
2,641
36.1
2026-09-10
1,767
31.0
2026-09-09
2,635
47.2
2026-09-08
1,302
36.6
2026-09-07
1,425
37.8
2026-09-06
1,207
29.7
2026-09-05
1,317
23.4
2026-09-04
418
30.6
2026-09-03
845
26.4
2026-09-02
616
26.4
Counts, rates and ratios only. This page reports what the work was, never what it was billed at.