Trim Send Events API docs to setup-only content

- Drop HMAC/signature-ignored note on PagerDuty page.
- Replace Delivery Log mentions in every Verify section with a
  simple 'alert should appear on the Robusta timeline' line.
- Trim the main page: remove HolmesGPT marketing sentence, the
  Response/Errors sections, rate-limit numbers, and the
  401-on-mismatch note.
- Collapse the Query Parameters table from four columns to two.
- Shorten the Nagios resource.cfg security explanation.
- Drop the 'token is an alternative to Authorization' meta note
  from the GCP page.

Author: claude

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

@@ -1,7 +1,7 @@
 Send Events API
 ================
 
-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.
+Send alerts from your monitoring system to Robusta through a single webhook endpoint.
 
 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.
 
@@ -24,11 +24,9 @@ This is the recommended ingestion path for new integrations. The legacy :doc:`Se
    send-events/solarwinds
    send-events/splunk
 
-Overview
+Endpoint
 --------
 
-The endpoint accepts the default payload structure of the supported origins. The request is parameterized by query string:
-
 .. code-block::
 
     POST https://api.robusta.dev/webhooks?type=alert&origin=<ORIGIN>&account_id=<ACCOUNT_ID>
@@ -37,25 +35,17 @@ Query Parameters
 ----------------
 
 .. list-table::
-   :widths: 20 10 60 10
+   :widths: 20 70
    :header-rows: 1
 
    * - Parameter
-     - Type
      - Description
-     - Required
    * - ``type``
-     - string
      - Must be ``alert``.
-     - Yes
    * - ``origin``
-     - string
      - Identifies the monitoring product. Must be one of the supported origins listed under `Integrations`_ below.
-     - Yes
    * - ``account_id``
-     - string
      - Your Robusta account ID, found in ``generated_values.yaml``.
-     - Yes
 
 Authentication
 --------------
@@ -66,8 +56,6 @@ Send your Robusta API key as a Bearer token. Generate keys in the Robusta UI und
 
     Authorization: Bearer <API_KEY>
 
-The key must be scoped to the ``account_id`` query parameter. Mismatches return ``401``.
-
 Example Request
 ---------------
 
@@ -79,22 +67,6 @@ Example Request
       --header 'Content-Type: application/json' \
       --data-raw '{ "title": "High error rate", "severity": "high" }'
 
-Response
---------
-
-A successful request returns ``200`` with the ID of the stored event:
-
-.. code-block:: json
-
-    { "id": "8f1b...e21" }
-
-Errors:
-
-* ``400`` — missing or empty ``account_id``, ``origin``, or ``type``; invalid ``type`` value.
-* ``401`` — invalid or out-of-scope API key.
-* ``429`` — rate limit exceeded (300 requests per 5-minute window per account).
-* ``503`` — transient storage failure; vendors should retry.
-
 Integrations
 ------------
 
@@ -199,4 +171,3 @@ Other
         :class-card: sd-bg-light sd-bg-text-light
         :link: send-events/solarwinds
         :link-type: doc
-

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

@@ -43,4 +43,4 @@ Set ``continue: true`` if Robusta is not your only receiver, so alerts also reac
 Verify
 ------
 
-Open **Settings → Delivery Log** in the Robusta UI to see the request arrive, then check the timeline for the parsed alert.
+The alert should appear on the Robusta timeline.

docs/configuration/exporting/send-events/aws-cloudwatch.rst

@@ -61,4 +61,4 @@ Alternatively, if you already use **Amazon EventBridge → API destination**, po
 Verify
 ------
 
-Use the **Test alarm** action in CloudWatch. The event should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Use the **Test alarm** action in CloudWatch. The alert should appear on the Robusta timeline.

docs/configuration/exporting/send-events/azure-monitor.rst

@@ -35,4 +35,4 @@ Action Group webhook receivers do not allow custom headers, so authenticate via
 Verify
 ------
 
-Use the action group's **Test** option. The event should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Use the action group's **Test** option. The alert should appear on the Robusta timeline.

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

@@ -35,4 +35,4 @@ Configure Datadog
 Verify
 ------
 
-Trigger a test alert from a Datadog monitor. The event should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Trigger a test alert from a Datadog monitor. The alert should appear on the Robusta timeline.

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

@@ -35,4 +35,4 @@ Configure Dynatrace
 Verify
 ------
 
-Use the **Send test notification** button. The event should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Use the **Send test notification** button. The alert should appear on the Robusta timeline.

docs/configuration/exporting/send-events/gcp-monitoring.rst

@@ -27,8 +27,6 @@ GCP webhook notification channels do not support custom headers in the console,
 
     https://api.robusta.dev/webhooks?type=alert&origin=gcp&account_id=<ACCOUNT_ID>&token=<ROBUSTA_API_KEY>
 
-The ``token`` query parameter is accepted as an alternative to the ``Authorization`` header.
-
 1. In the GCP Console, go to **Monitoring → Alerting → Edit Notification Channels**.
 2. Click **Add new** under **Webhooks**.
 3. Set the **Endpoint URL** to the URL above and name it ``Robusta``.
@@ -37,4 +35,4 @@ The ``token`` query parameter is accepted as an alternative to the ``Authorizati
 Verify
 ------
 
-Use **Send test notification** on the channel. The event should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Use **Send test notification** on the channel. The alert should appear on the Robusta timeline.

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

@@ -35,4 +35,4 @@ Configure Grafana
 Verify
 ------
 
-Use Grafana's **Test** button on the contact point. The event should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Use Grafana's **Test** button on the contact point. The alert should appear on the Robusta timeline.

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

@@ -21,23 +21,21 @@ Webhook URL
 Configure Nagios
 ----------------
 
-Nagios delivers notifications by running shell commands. Define a command that POSTs the alert as JSON.
-
-Store the API key in ``resource.cfg`` rather than inlining it in ``commands.cfg`` so that it does not appear in command definitions, command-line process listings, or backups of the main configuration:
+Store the API key in ``resource.cfg`` so it does not appear in command definitions or process listings:
 
 .. code-block::
 
     # /etc/nagios/resource.cfg
     $USER20$=<ROBUSTA_API_KEY>
 
-Nagios resource macros are intentionally not exposed to the CGIs and can hold secrets. Tighten the file permissions so only the Nagios user can read it, and exclude ``resource.cfg`` from any unprotected backup or config-management bundle:
+Restrict the file to the Nagios user:
 
 .. code-block:: bash
 
     chown root:nagios /etc/nagios/resource.cfg
     chmod 640 /etc/nagios/resource.cfg
 
-Then reference ``$USER20$`` from the notification command:
+Define a notification command that references ``$USER20$``:
 
 .. code-block::
 
@@ -73,4 +71,4 @@ Add ``robusta`` to the ``contact_groups`` you want to forward.
 Verify
 ------
 
-Acknowledge a test problem to fire a notification. The event should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Acknowledge a test problem to fire a notification. The alert should appear on the Robusta timeline.

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

@@ -35,4 +35,4 @@ Configure New Relic
 Verify
 ------
 
-Trigger a test incident in New Relic. The event should appear in **Settings → Delivery Log** and on the Robusta timeline.
+Trigger a test incident in New Relic. The alert should appear on the Robusta timeline.