Restrict Send Events API docs to alerts only

Only the alert type is supported today. Remove origins that only
produce incidents (Rootly, Incident.io) or changes (Argo CD,
GitHub, LaunchDarkly), drop the Incident Management → Rootly/
Incident.io and Changes & Deployments cards, simplify the type
parameter to require 'alert', and rewrite PagerDuty for the
AIOps alert flow only.

Author: claude

docs/configuration/exporting/send-events-api.rst

@@ -1,7 +1,7 @@
 Send Events API
 ================
 
-Send alerts, incidents, and changes from any monitoring system to Robusta through a single webhook endpoint. HolmesGPT investigates each event against your live cluster state, logs, metrics, and connected data sources, and attaches its findings to help accelerate triage.
+Send alerts from any monitoring system to Robusta through a single webhook endpoint. HolmesGPT investigates each alert against your live cluster state, logs, metrics, and connected data sources, and attaches its findings to help accelerate triage.
 
 This is the recommended ingestion path for new integrations. The legacy :doc:`Send Alerts API </configuration/exporting/send-alerts-api>` remains available for existing customers.
 
@@ -19,12 +19,7 @@ This is the recommended ingestion path for new integrations. The legacy :doc:`Se
    send-events/azure-monitor
    send-events/splunk
    send-events/sentry
-   send-events/launchdarkly
-   send-events/argocd
-   send-events/github
    send-events/opsgenie
-   send-events/rootly
-   send-events/incidentio
    send-events/nagios
    send-events/solarwinds
    send-events/aws-cloudwatch
@@ -36,7 +31,7 @@ The endpoint accepts the default payload structure of the supported origins. The
 
 .. code-block::
 
-    POST https://api.robusta.dev/webhooks?type=<TYPE>&origin=<ORIGIN>&account_id=<ACCOUNT_ID>
+    POST https://api.robusta.dev/webhooks?type=alert&origin=<ORIGIN>&account_id=<ACCOUNT_ID>
 
 Query Parameters
 ----------------
@@ -51,7 +46,7 @@ Query Parameters
      - Required
    * - ``type``
      - string
-     - One of ``alert``, ``incident``, or ``change``.
+     - Must be ``alert``.
      - Yes
    * - ``origin``
      - string
@@ -189,37 +184,6 @@ 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
-
-    .. grid-item-card:: :octicon:`pulse;1em;` Incident.io
-        :class-card: sd-bg-light sd-bg-text-light
-        :link: send-events/incidentio
-        :link-type: doc
-
-Changes & Deployments
-~~~~~~~~~~~~~~~~~~~~~~
-
-.. grid:: 1 1 2 3
-    :gutter: 3
-
-    .. grid-item-card:: :octicon:`package;1em;` Argo CD
-        :class-card: sd-bg-light sd-bg-text-light
-        :link: send-events/argocd
-        :link-type: doc
-
-    .. grid-item-card:: :octicon:`mark-github;1em;` GitHub
-        :class-card: sd-bg-light sd-bg-text-light
-        :link: send-events/github
-        :link-type: doc
-
-    .. grid-item-card:: :octicon:`plug;1em;` LaunchDarkly
-        :class-card: sd-bg-light sd-bg-text-light
-        :link: send-events/launchdarkly
-        :link-type: doc
-
 Other
 ~~~~~~
 

docs/configuration/exporting/send-events/argocd.rst

@@ -1,47 +1,38 @@
 PagerDuty
 ==========
 
-Forward PagerDuty incidents (and AIOps alerts) to Robusta via Generic Webhooks v3.
+Forward PagerDuty alerts to Robusta via PagerDuty AIOps Event Orchestration.
 
 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 PagerDuty admin able to create webhooks. AIOps Event Orchestration is required to forward full alert-level data.
+* An AIOps-enabled PagerDuty plan with admin access to Event Orchestration.
 
 Webhook URL
 -----------
 
-For incidents:
-
-.. code-block::
-
-    https://api.robusta.dev/webhooks?type=incident&origin=pagerduty&account_id=<ACCOUNT_ID>
-
-For AIOps-forwarded alerts:
-
 .. code-block::
 
     https://api.robusta.dev/webhooks?type=alert&origin=pagerduty&account_id=<ACCOUNT_ID>
 
 Configure PagerDuty
 -------------------
 
-1. In PagerDuty, go to **Integrations → Generic Webhooks v3** and click **New Webhook**.
-2. Set the **Webhook URL** to the URL above.
-3. Add a custom header:
+1. In PagerDuty, go to **AIOps → Event Orchestration** and open the orchestration that handles the alerts you want forwarded.
+2. Under **Automation → Webhook Actions**, add a new webhook.
+3. Set the **Webhook URL** to the URL above.
+4. Add a custom header:
 
    .. code-block::
 
        Authorization: Bearer <ROBUSTA_API_KEY>
 
-4. Save. PagerDuty will sign the payload, but Robusta authenticates on the API key alone — the signature is ignored.
-
-For AIOps event-level forwarding, repeat the same steps inside **AIOps → Event Orchestration → Webhook Action** and target the ``type=alert`` URL.
+5. Save. PagerDuty will sign the payload, but Robusta authenticates on the API key alone — the signature is ignored.
 
 Verify
 ------
 
-Trigger a test incident in PagerDuty. It should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Trigger a test alert in PagerDuty. It should appear in **Settings → Delivery Log** and on the Robusta timeline.