Dependencies

Most outages a growing team sees are not in their own code. A payment provider degrades, a CDN has a regional incident, an email API starts timing out - and your monitors go red for a reason outside your control. Dependency monitoring puts those upstream providers next to your own checks, so you can tell at a glance whether a failure is yours to fix or someone else's to resolve.

You tell NoDisrupt which third-party services you depend on. NoDisrupt watches each provider's official status page and shows its current status - and any open incident - right where you already look: on the monitor, and optionally on your public status page.

Dependency monitoring is available on the Pro and Elite plans. See Plans.

How it works

  • NoDisrupt keeps a catalog of thousands of providers that publish a status page in the common Statuspage format (Stripe, AWS, Cloudflare, GitHub, Twilio, SendGrid, OpenAI, Anthropic and many more).
  • When you add a dependency, NoDisrupt reads that provider's status and reports it back as one of Operational, Degraded, or Outage (or Unknown when the provider is not reporting). If the provider has an open incident, NoDisrupt shows its title, impact and a link to the provider's own status page.
  • A provider can publish several components - for example Stripe splits out "API", "Dashboard" and "Webhooks". You can depend on the whole provider or on just the components you actually use, so you are not alerted about a part of their service you never touch.

Adding a dependency

Open the service you want to attach the dependency to (see Where you can add dependencies below) and use Add dependency:

  1. Search for the provider by name.
  2. Optionally pick one or more components, or keep All components to depend on the whole provider.
  3. Choose how it should affect your alerts - Alert or Suppress (see Alert behaviour).

The provider's current status is fetched as you select it, so you can confirm you have the right service before you save.

Where you can add dependencies

You can attach dependencies at three levels, depending on how widely the provider is used:

  • Monitor - the dependency applies to a single monitor. Use this when only one endpoint relies on the provider.
  • Project - the dependency applies to the whole project and is inherited, read-only, by every monitor in it. Edit it at the project level. Use this when a provider (say, your payment processor) underpins everything in a project.
  • Organisation - a standalone list of the providers your whole organisation depends on, managed from your organisation settings. These are not attached to individual monitors; they are an at-a-glance view of your overall supplier status.

Alert behaviour

Each dependency has a mode that controls what happens to your alerts while the upstream provider is having an outage:

  • Alert (the default) - nothing changes about your paging. If your monitor fails, the incident opens as normal and is annotated with the upstream cause, so whoever responds can see the provider is down.
  • Suppress - NoDisrupt does not page you while the provider reports an outage. The incident still opens and is still annotated - you keep the record
    • but your on-call is not woken for a failure they cannot fix. Paging resumes as normal once the provider recovers.

Suppress is best for dependencies you can do nothing about at 3am; Alert is the safe default for everything else. See Managing incidents for how incidents and alerts work generally.

Seeing upstream status on a monitor

On the monitor view, dependencies stay quiet while everything is healthy - a single line confirming the services you depend on are operational. If a provider degrades or goes down, that line expands to show which dependency is affected, the provider's open incident, and a link to their status page. When your monitor's own checks are still passing, NoDisrupt says so too, so you can tell an upstream wobble from a real failure on your side.

Showing dependencies on your status page

You can surface your dependencies to your own users. In the status page editor, the Dependencies tab lets you choose which providers to list publicly and in what order. Visitors to your status page then see each provider's live status alongside your own components - useful when an upstream incident is the reason your service is affected, so your users understand the cause without opening a ticket.

A provider is missing

The catalog covers thousands of providers that publish a Statuspage-format status page, but not every service does. If the provider you need is not in the list, get in touch and we will look at adding it.