Back to features
CLI
Monitoring from your terminal.
Install the OnlineOrNot CLI to authenticate from your terminal, query status, and script common monitoring tasks without opening the dashboard.
- Feature
- Log in from your terminal
- Feature
- Query checks and status
- Feature
- Use OnlineOrNot in scripts and CI
- Feature
- Pair with the API for custom workflows
Example
onlineornot login
onlineornot checks list- Built for operators and developers.
- Use the CLI when you want a quick answer from the place you are already working, without clicking through the dashboard.
- Terminal workflows
- Scripts
- CI jobs
- Pairs well with the API.
- The CLI is the fastest path for human operators; the API is there when you need full automation.
- API tokens
- Automation
- Docs-first workflows
- Useful during deploys and debugging.
- Check status from a terminal while you deploy, investigate an incident, or verify that a new monitor exists after provisioning.
- Release checks
- Incident investigation
- Provisioning scripts
- Keep simple tasks simple.
- Not every workflow needs a custom client. The CLI gives you a practical interface for the commands humans run repeatedly.
- List checks
- Inspect status
- Script repeatable tasks
Frequently asked questions
The short version. The docs have the details when you need them.
- Where do I start?
- Install the CLI, log in, and query your checks from the terminal.
- Can I use it in CI?
- Yes. Pair CLI usage with API tokens and scripts for your own workflows.
- Does the CLI replace the dashboard?
- No. Use the dashboard for visual setup and investigation. Use the CLI for terminal workflows and repeatable checks.
- Where does the CLI fit with the API?
- Use the CLI when a person wants a command-line interface. Use the API when your own application or automation needs to control OnlineOrNot directly.
Start with the CLI.
Install the CLI for quick terminal access, then reach for the API when the workflow belongs in code.