Glossary
Dependency Monitoring
Continuous third-party API observation with quorum-confirmed incidents.
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 to one region. RELIASTRA’s multi-region checks disagree - one origin fails, two succeed - distinguishing a regional path problem from a vendor-wide outage.
How RELIASTRA approaches it
One scheduler dispatches one task per dependency per region through a message broker to workers. Every result carries its region. Recovery requires consecutive successes, so flapping does not page your team twice.
Know when your dependencies fail. Prove what happened.
Monitor the external APIs your product relies on, correlate their failures with your incidents, and generate verifiable evidence when a vendor causes downtime.