Glossary
External Dependency Fault Report
The artifact that attributes a failure window to a specific dependency.
Definition
An External Dependency Fault Report is the compiled artifact for one failure window: which dependency failed, over what interval, observed from where, with what severity, what customer impact correlated, and what the record’s checksum is.
The problem
Incident threads contain fragments - graphs, pasted curl output, status-page screenshots. Nobody can later reconstruct exactly what was observed and when.
Why it matters
A single compiled report replaces a scattered thread. It is what gets attached to vendor tickets, postmortems and SLA claims.
Practical example
Contents: dependency, window (UTC), the detection record with the rule id that applied, every observation in the window, severity, correlated incidents, the attribution result, methodology version, payload and document checksums, verification link.
How RELIASTRA approaches it
Records are generated from retained observations when an incident resolves or on demand, carry the account binding and the checksums, and expose an unauthenticated verification endpoint that confirms existence and integrity - never private configuration.
Related
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.