From b25d10218adc809ee70c8a06fe662c2f451761b3 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 4 Aug 2026 10:46:57 +0000 Subject: [PATCH] Add F5 Distributed Cloud page to Send Events API docs Companion to robusta-dev/relay#691 (origin=f5 webhook alert parser) and robusta-dev/robusta-frontend#3483 (source entry). Documents the webhook URL, the F5 XC console setup (webhook alert receiver with Token auth + alert policy routing), Send Test Alert verification, the severity mapping, and the &cluster= override for tying alerts to a cluster. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01NhfExtHG9haNaK6Ls9dmLg --- .../exporting/send-events-api.rst | 6 +++ .../exporting/send-events/f5.rst | 43 +++++++++++++++++++ 2 files changed, 49 insertions(+) create mode 100644 docs/configuration/exporting/send-events/f5.rst diff --git a/docs/configuration/exporting/send-events-api.rst b/docs/configuration/exporting/send-events-api.rst index 06ea255dc..6c184dc7e 100644 --- a/docs/configuration/exporting/send-events-api.rst +++ b/docs/configuration/exporting/send-events-api.rst @@ -14,6 +14,7 @@ This is the recommended ingestion path for new integrations. The legacy :doc:`Se send-events/azure-monitor send-events/datadog send-events/dynatrace + send-events/f5 send-events/gcp-monitoring send-events/grafana send-events/jsm @@ -194,6 +195,11 @@ Other .. grid:: 1 1 2 3 :gutter: 3 + .. grid-item-card:: :octicon:`pulse;1em;` F5 Distributed Cloud + :class-card: sd-bg-light sd-bg-text-light + :link: send-events/f5 + :link-type: doc + .. grid-item-card:: :octicon:`pulse;1em;` Nagios :class-card: sd-bg-light sd-bg-text-light :link: send-events/nagios diff --git a/docs/configuration/exporting/send-events/f5.rst b/docs/configuration/exporting/send-events/f5.rst new file mode 100644 index 000000000..2835f7b30 --- /dev/null +++ b/docs/configuration/exporting/send-events/f5.rst @@ -0,0 +1,43 @@ +F5 Distributed Cloud +===================== + +Forward alerts from F5 Distributed Cloud (XC) to Robusta via a webhook alert receiver. + +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. +* An F5 Distributed Cloud tenant with permission to manage alert receivers and alert policies. + +Webhook URL +----------- + +.. robusta-code:: + + https://api.robusta.dev/webhooks?type=alert&origin=f5&account_id= + +Configure F5 Distributed Cloud +------------------------------ + +1. In the F5 Distributed Cloud Console, go to **Multi-Cloud App Connect → Alerts Management → Alert Receivers** (under Shared Configuration in some tenants) and select **Add Alert Receiver**. +2. Set **Receiver** to ``Webhook`` and name it ``robusta``. +3. Set the **URL** to the webhook URL above. +4. Under **Authentication**, choose **Token** and set the token value to your Robusta API key. F5 sends it as ``Authorization: Bearer ``. +5. Save the receiver. +6. Go to **Alert Policies → Add Alert Policy**, name it ``robusta``, and add the receiver you just created under **Alert Receivers**. +7. Under **Policy Rules**, select which alerts to route — choose **Select All Alerts** to forward everything, or filter by alert group/severity. +8. Save the policy. Only alerts matched by an active alert policy are forwarded. + +Verify +------ + +Use **Send Test Alert** on the alert receiver (available from the receiver's action menu). The event should appear in **Settings → Delivery Log** and on the Robusta timeline. + +Notes +----- + +* F5 severities map to Robusta priorities as follows: ``critical`` and ``major`` → ``HIGH``, ``minor`` → ``LOW``, ``info`` → ``INFO``. +* The ``namespace`` on an F5 alert is a Distributed Cloud namespace, not a Kubernetes one; it is kept as an alert label along with ``tenant``, ``site``, and ``group``. +* F5 alerts are not tied to a Kubernetes cluster. To associate them with one of your clusters anyway, append ``&cluster=`` to the webhook URL.