Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Retry-amplified alerts need identity spread and error classes
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Client-event counts can overstate incident breadth when one user repeatedly retries a deterministic failure. Normalize by a stable flow or session identity, require a minimum distinct-identity spread for widespread paging, and separate expected validation rejection from client/network and server/dependency errors. Report raw failures, distinct affected identities, and retries per identity. Correlate the window with deployment version and the responsible guard or error path. Page broadly only when rate or volume and identity spread are both high; route concentrated loops separately. This applies when retries re-emit the same terminal event. It does not replace raw-event ratios for independent requests or persisted-state checks for user impact.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review