SREInsights documentation
SREInsights watches the systems you run and tells the right people when something breaks. You set up monitors (checks on a schedule), jobs (data collection on a schedule), alert rules and notification routes in one console. The checks themselves run on runners: small programs in your own network, a function in your own AWS account, or hosted runners for public endpoints.
The hosted product is at console.sreinsights.com. You can also run your own instance.
Start here
Section titled “Start here”- Quickstart: sign up, create a monitor and get your first alert in about 10 minutes.
- How SREInsights works: the path of one run, from the schedule to a message in Slack.
What you can do
Section titled “What you can do”| You want to | Read |
|---|---|
| Know when a website is down or its certificate is about to expire | Monitor a website and its certificate |
| Check databases, queues or services inside your network | Install a Docker runner, then Check types |
| Run checks or jobs without a server of your own | Set up a Lambda runner in your AWS account |
| Replace a cron job, a launchd agent or an EventBridge schedule | Move a scheduled job into SREInsights |
| Collect Search Console, GA4 or Shopify data every day | Collect data with a job |
| Copy a Google Sheet into an API or a Postgres table | Sync a Google Sheet |
| Send alerts to Telegram, Slack, email, SNS or PagerDuty | Send alerts to your team |
| Test a whole user journey: sign in, call an API, compare values | Build a flow |
| Show customers or clients how their services are doing | Share a status page |
| Keep several clients apart in one organization | Set up clients for an agency |
The main ideas
Section titled “The main ideas”- Checks run on runners, never on SREInsights. A runner connects out to SREInsights over HTTPS, takes work, runs it and reports back. Nothing connects into your network. See Runners.
- Monitors check; rules decide; routes deliver. A monitor runs a check on a schedule. Alert rules turn its results into alerts. Routes send alerts to channels.
- Secrets stay protected. Connection secrets are encrypted per organization and never returned by the API. A runner receives them sealed to its own key, for one run only. See Connections and secrets.
- Jobs are configuration, not code. A job picks a built-in job type, its connections and its settings. The job type’s code ships in the runner image.
For developers
Section titled “For developers”- REST API: everything the web app does, over HTTP.
- Runner protocol and job type contract: how runners and job commands talk to SREInsights.
- Environment variables and runner settings.