Monitor IDs are UUIDs (e.g.
6e09775a-1b2c-4d5e-9f0a-1b2c3d4e5f6a). The CLI validates the format locally and rejects non-UUID values before calling the API. Get IDs from devhelm monitors list.Commands
monitors list
List all monitors in your organization.monitors get
Get detailed information about a single monitor.monitors create
Create a new monitor.Probe-driven types (
HTTP, TCP, DNS, ICMP) require at least one region. If you omit --regions, the CLI defaults to us-east and prints a note to stderr.Examples by type
Heartbeat monitors
monitors create --type HEARTBEAT creates a heartbeat with a fixed default config (expectedInterval: 60, gracePeriod: 60 seconds) — the CLI flags don’t expose these fields yet. To control the expected ping interval and grace period, define the monitor in YAML and deploy it:
Config-as-code
monitors update
Update an existing monitor’s configuration.monitors delete
Delete a monitor. This also removes all associated check results. Prompts for confirmation; pass--yes (-y) in scripts and CI — non-interactive runs without it are refused.
monitors pause
Temporarily stop a monitor from running checks. The monitor retains its configuration and can be resumed at any time.monitors resume
Resume a paused monitor.monitors test
Run an on-demand check immediately, without waiting for the next scheduled interval.-o json for structured output:
CreateMonitorRequest payload) without persisting anything — pass --config instead of an ID:
--config, not both.
monitors set-channels
Replace the full set of alert channels linked to a monitor. Pass an empty string to clear all channels.monitors results
Show recent check results for a monitor.monitors versions list
List configuration versions for a monitor. Each update to a monitor creates a new version.monitors versions get
Get a specific configuration version.Next steps
Monitoring overview
Understanding monitor types, regions, and assertions.
Config as Code
Deploy monitors from YAML configuration files.