From 954e99b1a8a272bc77ed923e46b8b2e288f11cf8 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 28 May 2026 10:52:40 +0000 Subject: [PATCH 1/2] Document Rootly alert webhook integration Adds send-events/rootly.rst with setup steps for the Rootly outgoing webhook and wires it into the Send Events API toctree and the Incident Management grid. Pairs with the relay rootly origin parser. https://claude.ai/code/session_01WUQzXDiD8RUrpvmmdonPAZ --- .../exporting/send-events-api.rst | 6 +++ .../exporting/send-events/rootly.rst | 43 +++++++++++++++++++ 2 files changed, 49 insertions(+) create mode 100644 docs/configuration/exporting/send-events/rootly.rst diff --git a/docs/configuration/exporting/send-events-api.rst b/docs/configuration/exporting/send-events-api.rst index fe940c8ec..0d3e64c3a 100644 --- a/docs/configuration/exporting/send-events-api.rst +++ b/docs/configuration/exporting/send-events-api.rst @@ -20,6 +20,7 @@ This is the recommended ingestion path for new integrations. The legacy :doc:`Se send-events/newrelic send-events/opsgenie send-events/pagerduty + send-events/rootly send-events/sentry send-events/solarwinds send-events/splunk @@ -174,6 +175,11 @@ Incident Management :link: send-events/opsgenie :link-type: doc + .. grid-item-card:: :octicon:`pulse;1em;` Rootly + :class-card: sd-bg-light sd-bg-text-light + :link: send-events/rootly + :link-type: doc + Other ~~~~~~ diff --git a/docs/configuration/exporting/send-events/rootly.rst b/docs/configuration/exporting/send-events/rootly.rst new file mode 100644 index 000000000..0e50a9578 --- /dev/null +++ b/docs/configuration/exporting/send-events/rootly.rst @@ -0,0 +1,43 @@ +Rootly +======= + +Forward Rootly alert lifecycle events to Robusta via a Rootly outgoing webhook. + +Prerequisites +------------- + +* A Robusta account with API access. +* Your Robusta ``account_id``, found in ``generated_values.yaml``. +* A Robusta API key with ``Read/Write`` access to alerts, generated under **Settings → API Keys → New API Key**. +* A Rootly admin able to create outgoing webhooks. + +Webhook URL +----------- + +.. robusta-code:: + + https://api.robusta.dev/webhooks?type=alert&origin=rootly&account_id= + +Configure Rootly +---------------- + +1. In Rootly, go to **Integrations → Webhooks → New Webhook**. +2. Set the **URL** to the webhook URL above. +3. Add a custom header: + + .. code-block:: + + Authorization: Bearer + +4. Subscribe the webhook to the alert events you want forwarded — at minimum ``alert.created`` and ``alert.resolved``. ``alert.acknowledged`` is also supported and is treated as a still-firing alert. +5. Save. Rootly will start delivering alerts immediately. + +Payload +------- + +Rootly sends a fixed JSON envelope; no body template is required. The relay extracts the alert summary, status, source system, labels, and timestamps. Severity is read from ``data.labels[]`` (Rootly's ``[{key, value}]`` array) or from the freeform ``data.data`` object if the upstream system propagated it there. The ``data.external_id`` field is used as the deduplication fingerprint so retransmissions of the same upstream alert fold into a single Robusta timeline entry. + +Verify +------ + +Trigger a test alert in Rootly (or wait for the next real alert). The event should appear in **Settings → Delivery Log** and on the Robusta timeline. From f8a118bebff95c0a92b0041e7bbd1db990259260 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 28 May 2026 11:18:52 +0000 Subject: [PATCH 2/2] Drop speculative Rootly event-name references in user docs Rootly's public docs only confirm alert.created as a webhook event type. The previous wording told customers to subscribe to alert.resolved and alert.acknowledged as if those were documented; rework the step to recommend alert.created plus whatever the Rootly UI exposes, and clarify that resolution is driven by the alert object's ended_at field. https://claude.ai/code/session_01WUQzXDiD8RUrpvmmdonPAZ --- docs/configuration/exporting/send-events/rootly.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/exporting/send-events/rootly.rst b/docs/configuration/exporting/send-events/rootly.rst index 0e50a9578..fbe6498e4 100644 --- a/docs/configuration/exporting/send-events/rootly.rst +++ b/docs/configuration/exporting/send-events/rootly.rst @@ -29,7 +29,7 @@ Configure Rootly Authorization: Bearer -4. Subscribe the webhook to the alert events you want forwarded — at minimum ``alert.created`` and ``alert.resolved``. ``alert.acknowledged`` is also supported and is treated as a still-firing alert. +4. Subscribe the webhook to the alert events you want forwarded — at minimum ``alert.created``. If the Rootly UI offers other ``alert.*`` events (for example to notify on resolution), subscribe to those as well; Robusta accepts the whole ``alert.*`` family and uses the alert object's ``ended_at`` field to tell firing from resolved, so the parser stays correct regardless of which specific event names Rootly emits. 5. Save. Rootly will start delivering alerts immediately. Payload