Skip to content

fix: throttle repeated same-reason degrade telemetry to one row per minute - #11

Merged
AskTheWay merged 1 commit into
AskTheWay:mainfrom
JadeLab8:jl8/fix-degrade-throttle
Oct 7, 2026
Merged

AskTheWay merged 1 commit into
AskTheWay:mainfrom
JadeLab8:jl8/fix-degrade-throttle

Conversation

@JadeLab8

@JadeLab8 JadeLab8 commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Fixes #6.

A keyless (or cooldown-open) session wrote one identical degraded telemetry row per tool call — thousands of no-key lines per busy session, drowning useful rows and burning toward the 20 MiB rotation bound. The throttle records a repeated same-reason degrade at most once per minute (heartbeat) plus on every reason change; degradation behavior itself is unchanged (still null, still fail-closed).

  • state field + one guard in the degrade path; injectable clock keeps the test offline
  • 78 tests green locally

…inute

With no key (or an open cooldown) every non-read-only tool call degrades
and writes an identical telemetry row — a busy keyless session produced
thousands of no-key lines drowning the useful rows. A repeated
same-reason degrade now records at most once per minute (heartbeat) and
on every reason change; the information content is the state transition,
not the repetition.

Test: five same-minute no-key calls -> one row; clock jump -> heartbeat.

Fixes AskTheWay#6
@AskTheWay
AskTheWay merged commit 70ce6f0 into AskTheWay:main Oct 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Telemetry log floods with identical 'degraded' rows when no API key is set

2 participants