Retry-amplified alerts need identity spread and error classes

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.