Incident Impact
Impact answers what measurable telemetry was affected during an incident window — not a subjective severity score.
What impact answers#
For an open or resolved incident, impact aggregates reliability signals and telemetry linked by exact correlation IDs (trace, session, request). There is no Impact Score and no estimated user count.
Open from the incident detail impact view in /app/incidents.
Correlation#
Joins require direct ID equality only. Timestamp-only or “probably related” heuristics are not used. When IDs are missing, dimensions report unavailable with a reason.
User impact honesty#
Missing user-identity evidence is shown as unavailable — never as 0 users affected. Session counts are not relabeled as users.
Limitations
- Computed at request time — not a persisted snapshot table.
- Time window is clamped (hard cap) around the incident interval.