Glossary
Dependency Monitoring
Continuous third-party observation with deterministic fault confirmation.
Definition
Dependency monitoring is the continuous probing of external endpoints your product relies on - APIs, auth providers, payment gateways, cloud services - to detect degradation before your users report it.
The problem
Vendor status pages are written by humans, after the fact, and scoped to incidents the vendor chose to declare. Timing is approximate and the record belongs to the counterparty.
Why it matters
A dependency that fails silently breaks your product while every internal dashboard stays green. Direct measurement closes that blind spot.
Practical example
Your auth provider starts returning 500s intermittently. Scheduled checks record exactly which probes failed, with timestamps and latencies, separating a single lost request from a fault window that two consecutive checks confirm.
How RELIASTRA approaches it
One scheduler dispatches one check task per dependency through a message broker to a worker. Every result carries the region label of the worker that ran it, and a detection policy parameterised by observation topology decides the confirmation rule. Recovery requires consecutive successes, so flapping does not page you twice.
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.