Skip to main content
Create your first HTTP monitor in under 5 minutes. Pick the approach that fits your workflow.

Prerequisites

Set your token as an environment variable:
export DEVHELM_API_TOKEN=dh_live_xxxxxxxx
Each API token is scoped to a single organization and workspace, so the examples below work without any org/workspace flag. If your token grants access to multiple orgs or workspaces, set DEVHELM_ORG_ID and DEVHELM_WORKSPACE_ID as well — see CLI authentication for switching contexts in the CLI.
The examples below use a 60-second check frequency, which requires a paid plan (the Free plan minimum is 300 seconds). Omit the frequency entirely to default to your plan’s minimum.

Create a monitor

Install the CLI globally:
npm install -g devhelm
Create a monitor:
devhelm monitors create \
  --name "My API" \
  --type HTTP \
  --url https://api.example.com/health \
  --frequency 60 \
  --regions us-east
Check your monitor status:
devhelm monitors list

What happens next

Once your monitor is running, DevHelm will:
  1. Check your endpoint from the selected probe regions at the configured frequency
  2. Create an incident automatically if the endpoint fails or violates assertions
  3. Alert your team through connected alert channels (Slack, PagerDuty, email, etc.)
  4. Resolve the incident automatically when the endpoint recovers

Next steps

Monitoring overview

Learn about all six monitor types, assertions, and regions.

Alerting guide

Set up alert channels, notification policies, and escalation rules.

Monitoring as Code

Manage your monitoring stack in YAML or Terraform and deploy from CI/CD.

CLI overview

Full command reference for all CLI operations.