Impact
Reliability Signals
Impact views consume observed reliability and telemetry signals only. Quiet sources stay quiet.
What counts as a signal
A reliability signal is an observed fact from monitoring or telemetry that can attach to a catalog service or incident window — for example a failed HTTP check, an open alert, error log volume on a known trace_id, or browser errors on a known session.
Sources
- Monitoring — HTTP / SSL / DNS check results
- Incidents & alerts
- Browser, Logs, Tracing — when correlation IDs exist
How to read empty
No signals means none were observed in scope — not that impact is zero or that the service is proven healthy.
Limitations
- Coming-soon monitor catalog kinds never contribute signals.
- Analysis rules: Impact Analysis.