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.Documentation Index
Fetch the complete documentation index at: https://docs.devhelm.io/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Prerequisites
- DevHelm CLI installed or an API token
- At least one alert channel — see First alert
Add your first dependency
Browse the catalog
Configure alert sensitivity
Control which events trigger alerts: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:| Level | Behavior |
|---|---|
AWARENESS | Default. Tracks real vendor incidents on the dashboard but never pages |
INCIDENTS_ONLY | Pages on real vendor incidents (any severity) |
ALL | Pages on any status change, including synthetic degradations |
MAJOR_ONLY | Pages only on major outages |
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:Manage dependencies
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.