Rootly
Connect Rootly so Sazabi can route issues to your Rootly alerting targets.
About
Connecting Rootly lets Sazabi route issues to Rootly so they enter your Rootly alerting and on-call. Rootly is a shared notification channel.
When you route to Rootly, you can target a default destination, a specific service, a team, or an escalation policy. Sazabi triggers and resolves Rootly alerts as an issue opens and closes.
Prerequisites
- A Rootly account and an API key.
- Organization admin access in Sazabi.
Set up in the dashboard
Create a Rootly API key
In Rootly, create an API key. Copy it.
Open the Rootly integration
In the dashboard, go to Settings > Integrations > Rootly.
Enter the API key
Paste the key and connect. Sazabi uses it to discover your Rootly services, teams, and escalation policies so you can pick a routing target.
Add a delivery rule
On the project Settings > Notifications page, add a delivery rule that routes an event type to a Rootly destination. See Route notifications.
Set up with the CLI
You can also connect Rootly with the Sazabi CLI (installed and authenticated — see CLI reference).
Rootly is an API-key provider, so pass its API key as the apiKey credential. Read the key from an environment variable rather than pasting it inline:
export ROOTLY_API_KEY=... # your Rootly API key
sazabi integrations connect rootly \
--credentials "{\"apiKey\":\"$ROOTLY_API_KEY\"}"Then add a delivery rule so issues reach Rootly — from the project Settings > Notifications page, or with the CLI (sazabi notifications delivery-rules create; see Route notifications). Run sazabi integrations list to confirm the connection, or sazabi integrations providers --json to see each provider's credential fields.
Notifications
Use Rootly as a delivery destination for issue and system events: on the project Settings > Notifications page, add a delivery rule that routes an event type to a Rootly destination. See Route notifications.
Verify
With a delivery rule pointing at a Rootly destination, trigger a test issue and confirm an alert appears in Rootly within a minute. Resolve the issue and confirm the Rootly alert resolves.
Troubleshooting
No alert in Rootly — Confirm the delivery rule names both the event type and the Rootly destination, and that no condition excludes the issue.
Connection shows needs attention — The API key may have been revoked. Create a new key in Rootly and reconnect.