Skip to main content
By the end of this guide, you’ll have services from the Status Data catalog added as dependencies, with alerts configured to notify you when they have outages.
  • DevHelm CLI installed or an API token
  • At least one alert channel — see First alert
For conceptual background, see Dependencies.

​
Add your first dependency

1

Browse the catalog

devhelm services list
devhelm services list --search stripe
devhelm services list --category cloud-infrastructure

curl "https://api.devhelm.io/api/v1/services?limit=20"
curl "https://api.devhelm.io/api/v1/services?search=stripe"
Find the services your application depends on — GitHub, Stripe, AWS, Vercel, etc.
2

Add a dependency

devhelm dependencies track github
devhelm dependencies track stripe
devhelm dependencies track aws

curl -X POST https://api.devhelm.io/api/v1/service-subscriptions/github \
  -H "Authorization: Bearer $DEVHELM_API_TOKEN"

curl -X POST https://api.devhelm.io/api/v1/service-subscriptions/stripe \
  -H "Authorization: Bearer $DEVHELM_API_TOKEN"
3

Configure alert sensitivity

Control which events trigger alerts:
devhelm dependencies update <subscription-id> \
  --alert-sensitivity INCIDENTS_ONLY
New dependencies start in AWARENESS (silent tracking — the incident is recorded on the dashboard but no alert channels fire). Switch to one of the paging modes when you’re ready to be alerted:
LevelBehavior
AWARENESSDefault. Tracks real vendor incidents on the dashboard but never pages
INCIDENTS_ONLYPages on real vendor incidents (any severity)
ALLPages on any status change, including synthetic degradations
MAJOR_ONLYPages only on major outages
4

Verify routing

Dependency alerts route through the same notification policies as monitor alerts. Verify with a catch-all policy or create a targeted one:
{
  "name": "Dependency alerts to Slack",
  "matchRules": [
    { "type": "service_id_in", "values": ["<github-service-id>", "<stripe-service-id>"] }
  ],
  "escalation": {
    "steps": [{
      "delayMinutes": 0,
      "channelIds": ["<slack-channel-id>"]
    }]
  }
}

​
Track specific components

If you only depend on part of a service (e.g., GitHub API but not GitHub Pages), add a component-level dependency: 
devhelm dependencies track github --component <component-id>

curl -X POST "https://api.devhelm.io/api/v1/service-subscriptions/github" \
  -H "Authorization: Bearer $DEVHELM_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "componentId": "<component-id>" }'
Find component IDs by listing a service’s components: 
devhelm services components github

​
Manage dependencies

devhelm dependencies list
devhelm dependencies delete <subscription-id>
Free plans support up to 10 dependencies. Starter and above have unlimited.

​
Next steps

Dependencies reference

Alert sensitivity, component tracking, and plan limits.

Service incidents

View incidents from your tracked services.

Uptime reporting

Query historical uptime for your dependencies.