Alerts and webhooks
Suta checks your devices about every 20 seconds. When a problem starts, it opens an alert. When the problem clears, it resolves the alert on its own.
See alerts
Section titled “See alerts”Go to Alerts in the sidebar. The sidebar shows how many alerts are open.
- Open lists devices that need attention now, and how long each alert has been open. Select one to go to the device.
- History lists past and current alerts. Search, or filter by status and condition.
Open alerts also appear on the Devices page and on each device’s page.
Choose conditions
Section titled “Choose conditions”Go to Alerts > Conditions. Turn each condition on or off and set its limit, then select Save changes. Only admins can change conditions.
| Condition | Default | Range | Resolves when |
|---|---|---|---|
| Device offline | 10 minutes | 2–1440 minutes | The device is back online |
| High memory use | 90% | 50–99% | Use drops 5 points below the limit |
| Storage almost full | 90% | 50–99% | Use drops 5 points below the limit |
| High temperature | 80 °C | 50–95 °C | Temperature drops 5 °C below the limit |
| Agent update failed | On | On or off | A newer update is requested or succeeds |
Conditions apply to every device in the workspace. Turning a condition off resolves its open alerts. Alerts use only fresh readings from online devices; missing or old readings never open or resolve an alert.
Send alerts to Slack
Section titled “Send alerts to Slack”-
In Slack, create an incoming webhook for the channel you want, and copy its URL.
-
In Suta, go to Alerts > Notifications and select Add webhook.
-
Enter a Name, such as
#ops-alerts, and paste the URL into Webhook URL. -
Under Notify when an alert, choose Opens, Resolves or both. Under For these conditions, keep All conditions or choose Only some.
-
Select Add webhook, then Done.
-
Select Send test to check that a message arrives.
Slack shows the message text directly. You don’t need anything in between. Only admins can manage notifications, and a workspace can have up to 10 webhooks.
Send alerts to your own service
Section titled “Send alerts to your own service”Add a webhook the same way, using your own HTTPS URL. Suta sends a JSON POST
for each alert that matches the webhook’s events and conditions.
When you add the webhook, select Copy secret and store the signing secret safely. Suta shows it only once. Your service should:
- Verify the signature on every request.
- Respond with any
2xxstatus within 10 seconds. - Handle the same alert more than once. Delivery is at least once.
If delivery fails, Suta retries after 1, 2, 4, 8 and 16 minutes.
See Webhook reference for the payload and a signature checker you can try in your browser.
Manage a webhook
Section titled “Manage a webhook”Each webhook shows its status (Active, Paused, Failing or Retrying), its last delivery and its counts for the last 24 hours. Select Deliveries to see recent deliveries.
From the … menu you can:
- Edit the name, URL, events or conditions.
- Pause deliveries, and Resume them later.
- Rotate signing secret. The new secret is shown once, and it signs every delivery from then on, so update your service straight away.
- Delete the webhook.