Skip to main content

​
Overview

Rootly’s Nobl9 integration turns SLO alert policy violations into Rootly alerts. When Nobl9 detects that a service’s error budget has been exhausted or an SLO objective has been breached, it fires a webhook to Rootly which creates an alert automatically. Alerts created from Nobl9 include contextual labels pulled directly from the payload — service, project, severity, SLO name, alert policy, and organization — making it easy to route and filter alerts in Rootly.

SLO-Driven Alerting

Alerts fire automatically when error budgets are breached or SLO objectives are violated.

Rich Labels

Each alert carries service, project, severity, SLO, alert policy, and organization labels from Nobl9.

Alert Routing

Route Nobl9 alerts to services, escalation policies, or teams based on label values.

Incident Escalation

Escalate Nobl9 alerts into full incidents when SLO violations require immediate response.

​
Before You Begin

  • You must be a Rootly admin to set up the integration
  • You must have access to Nobl9 with permissions to create Alert Methods and Alert Policies

​
Installation

1

Add the integration in Rootly

In Rootly, go to Configuration → Integrations and find Nobl9. Click Connect.
Nobl9 integration in Rootly integrations page
Rootly will generate a unique webhook URL tied to your team. Copy this URL — you’ll need it in the next step.
Nobl9 webhook URL in Rootly
2

Create an Alert Method in Nobl9

In Nobl9, navigate to Integrations → Alert Methods and click + Add Alert Method.
Nobl9 Integrations page
Click Alert Methods and create a new alert method.
Creating a new alert method in Nobl9
3

Configure as Webhook type

Select Webhook as the alert method type.
Selecting webhook type in Nobl9
Paste the webhook URL from Rootly into the URL field and save.
Pasting Rootly webhook URL into Nobl9
4

Attach to an Alert Policy

In Nobl9, open or create an Alert Policy and attach the Rootly alert method to it. Any SLO that uses this alert policy will now send alerts to Rootly when violated.

​
Alert Labels

When Nobl9 fires an alert, Rootly automatically extracts the following labels from the payload:
LabelSource
serviceNobl9 service name
projectNobl9 project name
severityAlert severity
sloSLO name
alert_policyAlert policy name
organizationNobl9 organization
These labels can be used in Rootly to route alerts, set urgency, and filter in dashboards.

​
Uninstall

To remove the Nobl9 integration:
  1. Go to Configuration → Integrations and find Nobl9
  2. Click Connected to reveal the disconnect option
  3. Click Disconnect
Click Connected to reveal the Disconnect option
After disconnecting, update or remove any Nobl9 alert methods that reference the Rootly webhook URL. Nobl9 will continue attempting to deliver webhooks to a disconnected endpoint.

​
Frequently Asked Questions

No. Nobl9 webhooks are fire-and-forget — they don’t send a resolve signal when the SLO recovers. Alerts created from Nobl9 must be resolved manually in Rootly or via a separate automation.
Yes. Use Rootly’s alert routing rules to match on labels like service, project, or alert_policy and route to the appropriate team or escalation policy.
Yes. The same webhook URL can be attached to multiple alert methods and policies in Nobl9. All alerts will flow into the same Rootly integration.
The alert summary is set from the message field in the Nobl9 payload, which typically describes the SLO violation (e.g., “Error budget exhausted for checkout-latency SLO”).