pulse CLI is PulseGuard’s official command-line tool. It brings your monitoring configuration into the same workflow as your code — so you can create, update, and inspect monitors without opening a browser, automate uptime checks as part of your CI/CD pipeline, and stream live events directly in your terminal.
What you can do
Every capability of thepulse CLI maps to a concrete workflow:
- Authenticate using an API key you generate in the PulseGuard dashboard. Your credentials are stored locally by the OS-native config store, never in plain text.
- Manage monitors via YAML by writing a
pulseguard.yamlfile and runningpulse monitors apply. This is Monitoring as Code — your monitor definitions live alongside your application code and are applied idempotently. - Trigger on-demand checks with
pulse triggerto run an immediate health check against any monitor without waiting for its next scheduled interval. - Tail live event logs using
pulse logs tailto stream check results to your terminal in real time — useful when debugging a degraded service. - Gate CI/CD deployments with
pulse wait, which blocks a pipeline step until a monitor reports UP or a configurable timeout is reached.
Top-level help
Runpulse --help at any time to see all available commands:
--help for detailed flag documentation. For example, pulse monitors --help lists all monitor subcommands.
Where to go next
Installation
Install the pulse CLI via npm, bun, or pnpm and verify your setup.
Authentication
Generate an API key and log in to start managing monitors.
Monitors
List, inspect, apply, and export monitors using YAML files.
CI/CD Integration
Gate deployments on monitor health with pulse wait.