sartar help
sartar watches your websites and APIs from several regions, and tells you when one of them stops answering as it should. Everything you can do in the web dashboard can also be done from a terminal or from code. These pages explain how.
The tools
- The sartar CLI. A single binary named
sartar. List and edit monitors, run a scenario from a CI pipeline, read results, manage users and notification channels. - The Terraform provider. Describe folders, monitors, scenarios and notification channels as code, with Terraform or OpenTofu.
- Private probes. Install a probe inside your own network, to monitor what the public probes cannot reach.
Which one should I use?
| You want to | Use |
|---|---|
| Look something up, or make a quick change | the CLI |
| Run a scenario as a gate in a CI pipeline | the CLI |
| Script against your account | the CLI, with --json |
| Keep your monitoring configuration in a repository, reviewed like code | the Terraform provider |
| Move an existing account under Terraform | both: the provider, and the CLI to generate the import blocks |
| Monitor a service that is not reachable from the internet | a private probe |
The CLI and the provider use the same API and the same API keys, so they can be used side by side.
Before you start: an API key
The CLI and the provider authenticate with an API key of your account. A private probe does not: it uses the token of its region.
- Sign in at sartar.app.
- Open the account menu, then API keys.
- Choose Create key, give it a label, and pick a scope: Read-only to look, Read / write to change things.
- Copy the key right away. It is shown only once.
Only an administrator of the account can create or revoke keys.
A read-only key is enough to list, to read results, and to run
terraform plan. Give a read / write key only to what really needs to change
your account.