Glossary
Dependency Telemetry
The raw observations behind every reliability claim: checks, outcomes, timestamps.
Definition
Dependency telemetry is the retained record of every probe against a dependency - timestamp, the region label of the worker that issued it, latency, status code and outcome - from which availability, latency and incident figures are derived.
The problem
An uptime percentage without its underlying observations cannot be audited. You cannot distinguish “vendor down” from “we never ran the probe”.
Why it matters
Telemetry is what makes a reliability claim inspectable. It separates target failures (the vendor failed) from infrastructure failures (the probe could not run) and transitional states (never checked, queued, executing).
Practical example
A gap in the chart is labeled explicitly: policy-blocked target, dispatch failure, or dead scheduler - three different causes with three different owners, never collapsed into “no data”.
How RELIASTRA approaches it
Each stored result records the region label, outcome, status code, latency and execution time. Missed probes are never backfilled: a gap stays a gap. Retention is 90 days on the Developer plan, and 24 hours once a trial ends without a subscription.
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.