From 93eaeca65686d7fa9f36d531b10ff07a4fb773cc Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 1 Jun 2026 09:41:41 +0000 Subject: [PATCH 1/2] docs: use &token= URL param for Rootly webhook auth Rootly outgoing webhooks don't support custom HTTP headers, so the Robusta API key must be passed via the &token= query parameter instead of an Authorization header, matching the Sentry/Splunk/etc. docs. --- .../exporting/send-events/rootly.rst | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/configuration/exporting/send-events/rootly.rst b/docs/configuration/exporting/send-events/rootly.rst index fbe6498e4..9b5b2616c 100644 --- a/docs/configuration/exporting/send-events/rootly.rst +++ b/docs/configuration/exporting/send-events/rootly.rst @@ -16,21 +16,21 @@ Webhook URL .. robusta-code:: - https://api.robusta.dev/webhooks?type=alert&origin=rootly&account_id= + https://api.robusta.dev/webhooks?type=alert&origin=rootly&account_id=&token= + +Replace ```` with your Robusta account id and ```` with the API key you generated. + +.. note:: + + Rootly outgoing webhooks **do not let you add custom outgoing HTTP headers**, so the Robusta API key goes in the ``&token=`` URL parameter rather than an ``Authorization`` header. 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``. 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. +3. 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. +4. Save. Rootly will start delivering alerts immediately. Payload ------- From 71f0cca6385ba51a033ec6f2393182ab60ab5ac8 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 1 Jun 2026 11:40:10 +0000 Subject: [PATCH 2/2] docs: remove unhelpful note from Rootly webhook page --- docs/configuration/exporting/send-events/rootly.rst | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/configuration/exporting/send-events/rootly.rst b/docs/configuration/exporting/send-events/rootly.rst index 9b5b2616c..4c788b5c2 100644 --- a/docs/configuration/exporting/send-events/rootly.rst +++ b/docs/configuration/exporting/send-events/rootly.rst @@ -20,10 +20,6 @@ Webhook URL Replace ```` with your Robusta account id and ```` with the API key you generated. -.. note:: - - Rootly outgoing webhooks **do not let you add custom outgoing HTTP headers**, so the Robusta API key goes in the ``&token=`` URL parameter rather than an ``Authorization`` header. - Configure Rootly ----------------