Glossary
Incident Attribution
Determining whether an incident originated inside your stack or with a vendor.
Definition
Incident attribution is the process of assigning an observed failure to its most likely origin - your infrastructure or a specific external dependency - using correlated timelines rather than inference.
The problem
An outage you caused and an outage your vendor caused look identical from inside your own monitoring. Both present as your service failing.
Why it matters
Correct attribution decides where engineers look first, what gets rolled back, what gets escalated to a vendor, and what evidence supports an SLA claim.
Practical example
Your incident window (14:02–14:19) overlaps a period in which the dependency was independently observed failing from RELIASTRA’s own infrastructure. That overlap is a fact about two measured timelines - not a finding about cause.
How RELIASTRA approaches it
RELIASTRA keeps your incident history and the dependency’s observation history on the same timeline, applies a deterministic correlation engine with confidence levels, and refuses to claim causation - only correlated, timestamped evidence.
Add one dependency you already own.
RELIASTRA probes the external services your software relies on, confirms a fault deterministically, and keeps a record you can verify later. One plan, $9/month, and a 14-day trial that needs no card.