Merge branch 'master' into webhook-sink-json-formatting

Author: arikalon1

docs/conf.py

@@ -71,7 +71,11 @@
     "developer-guide/actions/findings-api.html": "/master/playbook-reference/actions/develop-actions/findings-api.html",
     "tutorials/my-first-custom-action.html": "/master/playbook-reference/actions/develop-actions/index.html",
     "user-guide/self-hosting.html": "/master/how-it-works/oss-vs-saas.html",
-    "getting-started/installation.html": "/master/setup-robusta/installation/all-in-one-installation.html",
+    "getting-started/installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/all-in-one-installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/standalone-installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/dev-setup.html": "/master/help.html",
+    "setup-robusta/supported-clusters.html": "/master/setup-robusta/installation/index.html",
     "tutorials/java-troubleshooting.html": "/master/tutorials/application-troubleshooting-java.html",
     "catalog/sinks/index.html": "/master/configuration/sinks/index.html",
     "tutorials/prometheus-enrichment.html": "/master/tutorials/alert-custom-enrichment.html",
@@ -97,7 +101,8 @@
     "configuration/defining-playbooks/playbook-basics.html": "/master/playbook-reference/index.html",
     "configuration/defining-playbooks/trigger-action-binding.html": "/master/playbook-reference/index.html#matching-actions-to-triggers",
     "playbook-reference/defining-playbooks/trigger-action-binding.html": "/master/playbook-reference/index.html#matching-actions-to-triggers",
-    "configuration/additional-settings.html": "/master/setup-robusta/additional-settings.html",
+    "configuration/additional-settings.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/additional-settings.html": "/master/setup-robusta/installation/index.html",
     "developer-guide/writing-playbooks.html": "/master/playbook-reference/defining-playbooks/index.html",
     "user-guide/slack.html": "/master/configuration/sinks/slack.html",
     "user-guide/elasticsearch.html": "/master/playbook-reference/triggers/elasticsearch.html",
@@ -130,8 +135,11 @@
     "tutorials/alert-custom-prometheus.html": "/master/configuration/alertmanager-integration/alert-custom-prometheus.html",
     "catalog/triggers/prometheus.html": "/master/configuration/alertmanager-integration/index.html",
     "playbook-reference/prometheus-examples/alert-remediation.html": "/master/playbook-reference/automatic-remediation-examples/index.html",
-    "configuration/ai-analysis.html": "/master/configuration/holmesgpt/main-features.html",
-    "configuration/holmesgpt/index.html": "/master/configuration/holmesgpt/main-features.html",
+    "configuration/ai-analysis.html": "https://robusta.dev/",
+    "configuration/holmesgpt/index.html": "https://robusta.dev/",
+    "configuration/holmesgpt/main-features.html": "https://robusta.dev/",
+    "configuration/holmesgpt/getting-started.html": "https://robusta.dev/",
+    "configuration/holmesgpt/holmesgpt-docs.html": "https://robusta.dev/",
     # AI Analysis pages redirects to holmesgpt.dev (docs have moved there)
     "configuration/holmesgpt/builtin_toolsets.html": "https://holmesgpt.dev/data-sources/builtin-toolsets/?tab=robusta-helm-chart",
     "configuration/holmesgpt/permissions.html": "https://holmesgpt.dev/data-sources/permissions/?tab=robusta-helm-chart",
@@ -164,12 +172,12 @@
     "tutorials/more-tutorials.html": "/master/help.html",
     "common-errors.html": "/master/help.html#common-errors",
     "user-guide/defining-playbooks.html": "/master/playbook-reference/defining-playbooks/index.html",
-    "user-guide/global-config.html": "/master/setup-robusta/additional-settings.html#global-config",
+    "user-guide/global-config.html": "/master/setup-robusta/installation/index.html",
     "user-guide/configuration-secrets.html": "master/setup-robusta/configuration-secrets.html",
     "user-guide/additional-playbooks.html": "/master/playbook-reference/defining-playbooks/external-playbook-repositories.html",
     "user-guide/embedded-prometheus.html": "/master/configuration/alertmanager-integration/embedded-prometheus.html#enabling-the-embedded-prometheus",
     "user-guide/node-selector.html": "/master/setup-robusta/node-selector.html",
-    "user-guide/interactivity.html": "/master/setup-robusta/additional-settings.html#two-way-interactivity",
+    "user-guide/interactivity.html": "/master/setup-robusta/installation/index.html",
     "user-guide/flow-control.html": "/master/playbook-reference/index.html#using-filters-to-restrict-triggers",
     "catalog/triggers/index.html": "/master/playbook-reference/triggers/index.html",
     "catalog/triggers/kubernetes.html": "/master/playbook-reference/triggers/kubernetes.html",
@@ -216,7 +224,7 @@
     "playbook-reference/overview.html": "/master/playbook-reference/index.html",
     "playbook-reference/defining-playbooks/playbook-basics.html": "/master/playbook-reference/index.html",
     "how-it-works/alert-builtin-enrichment.html": "/master/playbook-reference/builtin-alert-enrichment.html",
-    "setup-robusta/installation/extend-prometheus-installation.html": "/master/setup-robusta/installation/standalone-installation.html",
+    "setup-robusta/installation/extend-prometheus-installation.html": "/master/setup-robusta/installation/index.html",
     "playbook-reference/defining-playbooks/index.html": "/master/playbook-reference/index.html",
     "configuration/alertmanager-integration/alert-custom-prometheus.html": "/master/configuration/alertmanager-integration/embedded-prometheus.html#creating-custom-prometheus-alerts",
     "configuration/alertmanager-integration/index.html": "/master/configuration/index.html",

docs/configuration/alertmanager-integration/_testing_integration.rst

@@ -56,4 +56,4 @@ If everything is setup properly, this alert will reach Robusta. It will show up
 
     Robusta enriches alerts with Kubernetes and log data using Prometheus labels for mapping.
     Standard label names are used by default. If your setup differs, you can
-    `customize this mapping </setup-robusta/additional-settings.html#alert-label-mapping>`_ to fit your environment.
+    `customize this mapping </configuration/alertmanager-integration/customize-labels-priorities.html>`_ to fit your environment.

docs/configuration/exporting/robusta-pro-features.rst

@@ -19,9 +19,7 @@ Data Export and Reporting
 * :doc:`Alert Reporting API <alert-statistics-api>`: Get aggregated statistics and counts for different alert types
 * :doc:`Send Alerts API <send-alerts-api>`: Send alerts programmatically from external systems
 * :doc:`Configuration Changes API <configuration-changes-api>`: Track configuration changes in your environment
-* :doc:`Namespace Resources API <namespace-resources-api>`: Query namespace-level resource information
 * :doc:`RBAC Configuration API <rbac-api>`: Programmatically manage role-based access control configurations
-* :doc:`Prometheus Query API <prometheus-query-api>`: Run PromQL queries against Prometheus in your connected clusters
 
 Getting Started
 ---------------

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

@@ -1,24 +1,12 @@
 Send Alerts API
 ===============
 
-Why Send Your Alerts to Robusta?
----------------------------------
-
-Benefits include:
-
-* Persistent alert history on a filterable timeline
-* Centralized view of alerts from all your monitoring systems (multiple Prometheus instances, cloud services, custom tools)
-* AI investigation of alerts
-* Correlations between alerts and Kubernetes deploys
-* and more!
-
-.. image:: /images/robusta-ui-timeline.png
-   :alt: Prometheus Alert History
+Send alerts to Robusta to have HolmesGPT automatically run an AI-powered root cause analysis on each one. HolmesGPT investigates the alert against your live cluster state, logs, metrics, and connected data sources, then attaches its findings to help accelerate triage.
 
 Integration Methods
 -------------------
 
-There are two main ways to send alerts to Robusta:
+There are two main ways to send alerts to Robusta for HolmesGPT to investigate:
 
 1. **Pre-built Integrations**: Use our existing integrations for AlertManager, Nagios, SolarWinds, and other monitoring systems. See :doc:`Send Alerts <../index>`.
 
@@ -27,9 +15,6 @@ There are two main ways to send alerts to Robusta:
 Send Alerts API
 ---------------
 
-.. note::
-    This API is available with the Robusta SaaS platform and self-hosted commercial plans. It is not available in the open-source version.
-
 Use this endpoint to send alert data to Robusta. You can send up to 1000 alerts in a single request.
 
 .. _send-alerts-api:
@@ -261,7 +246,7 @@ Troubleshooting
 
         **Alerts arriving but missing Kubernetes context?**
 
-        Check :doc:`Alert Label Mapping </setup-robusta/additional-settings>` to customize how Prometheus labels map to Kubernetes resources.
+        Check :doc:`Customize Labels and Priorities </configuration/alertmanager-integration/customize-labels-priorities>` to customize how Prometheus labels map to Kubernetes resources.
 
 Testing Your Integration
 ------------------------

docs/configuration/github-actions/holmes-pr-review.rst

@@ -0,0 +1,137 @@
+HolmesGPT PR Review
+===================
+
+.. note::
+    This integration is available with the Robusta SaaS platform and self-hosted commercial plans. It is not available in the open-source version.
+
+Use HolmesGPT as a GitHub Action to automatically review pull requests. On every PR open, reopen, or push, the action asks HolmesGPT to review the change and post its review as a comment on the pull request. You control what Holmes checks by editing the prompt — it can flag risky changes, check code against runbooks, cross-reference logs or metrics, or run any investigation available via its :doc:`data sources <../holmesgpt/main-features>`.
+
+Example review posted by HolmesGPT on a pull request:
+
+.. image:: /images/holmes-pr-review-example.png
+  :width: 700
+  :align: center
+
+How It Works
+------------
+
+1. A pull request event triggers the GitHub Action.
+2. The action calls the :ref:`Holmes Chat API <holmes-chat-api>` with your review prompt and the PR URL.
+3. HolmesGPT uses the GitHub toolset to read the pull request, reason about it using the data sources you have configured, and post its review as a comment on the PR.
+
+Prerequisites
+-------------
+
+Before setting up the action, you must enable the Holmes GitHub integration so HolmesGPT can read pull requests and post comments. Follow the `HolmesGPT GitHub toolset guide <https://holmesgpt.dev/latest/data-sources/builtin-toolsets/github-mcp/>`_.
+
+Setup
+-----
+
+Step 1: Create a Robusta API Key
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In the Robusta Platform, navigate to **Settings** → **API Keys** and click **New API Key**.
+
+Give the key a descriptive name (for example, ``HolmesGPT github action``) and check the **Robusta AI Write** capability. Click **Generate API Key** and copy the key — you will not be able to view it again.
+
+.. image:: /images/new-api-key.png
+  :width: 600
+  :align: center
+
+Step 2: Get Your Account ID and Cluster ID
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In the Robusta Platform, navigate to **Settings** → **Workspace** and copy your **Account ID**.
+
+Then pick the cluster HolmesGPT should run the investigation on and copy its **Cluster ID**. Any cluster connected to your account can be used — HolmesGPT will use its data sources (logs, metrics, Kubernetes state, etc.) from that cluster when reviewing the PR.
+
+Step 3: Add GitHub Secrets
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In your GitHub repository, go to **Settings** → **Secrets and variables** → **Actions** and add the following repository secrets:
+
+.. list-table::
+   :widths: 25 75
+   :header-rows: 1
+   :width: 100%
+
+   * - Secret
+     - Value
+   * - ``ROBUSTA_API_KEY``
+     - The API key you generated in Step 1.
+   * - ``ROBUSTA_ACCOUNT_ID``
+     - The account ID from Step 2.
+   * - ``ROBUSTA_CLUSTER_ID``
+     - The cluster ID from Step 2.
+
+Step 4: Add the Workflow File
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Create a new file in your repository at ``.github/workflows/holmes-pr-review.yaml`` with the following contents:
+
+.. code-block:: yaml
+
+    name: Holmes PR review
+    on:
+      pull_request:
+        types: [opened, synchronize, reopened]
+    jobs:
+      review:
+        runs-on: ubuntu-latest
+        env:
+          RELAY_BASE_URL: https://api.robusta.dev
+          ACCOUNT_ID: ${{ secrets.ROBUSTA_ACCOUNT_ID }}
+          API_KEY: ${{ secrets.ROBUSTA_API_KEY }}
+          CLUSTER_ID: ${{ secrets.ROBUSTA_CLUSTER_ID }}
+          PR_URL: ${{ github.event.pull_request.html_url }}
+          PROMPT: |
+            Review the pull request at the URL below. Flag risky, unclear, or
+            incomplete changes. You MUST post your review as a single PR comment
+            on that pull request using your GitHub toolset. Do not reply with the
+            review in chat only — posting the comment is required.
+        steps:
+          - name: Ask Holmes (Holmes posts the comment)
+            run: |
+              set -euo pipefail
+              jq -n \
+                --arg ask "$PROMPT"$'\n\nPull request: '"$PR_URL" \
+                --arg cluster "$CLUSTER_ID" \
+                '{ask: $ask, cluster_id: $cluster, stream: false}' > body.json
+              curl -fsS --retry 2 \
+                -H "Authorization: Bearer $API_KEY" \
+                -H "Content-Type: application/json" \
+                --data-binary @body.json \
+                "$RELAY_BASE_URL/api/holmes/$ACCOUNT_ID/chat" > response.json
+              # Log analysis for debugging; Holmes is expected to have posted the comment.
+              jq -r '.analysis // "(no analysis text returned)"' response.json
+
+Commit and push the workflow file. The next pull request opened against the repository will trigger the action, and HolmesGPT will post its review as a PR comment.
+
+Customizing the Review Prompt
+-----------------------------
+
+The ``PROMPT`` environment variable controls what HolmesGPT checks. Edit it to match your team's review policy. For example:
+
+* Enforce coding standards or architecture rules.
+* Cross-reference the change against runbooks, incident history, or documentation in Confluence/Notion.
+* Validate that related Kubernetes manifests, Helm values, or Prometheus alert rules are consistent with the code changes.
+* Require that PRs changing specific paths include tests.
+
+Whatever you put in the prompt, keep the instruction to post the review as a PR comment — otherwise Holmes will return the review only in the API response.
+
+Configuration Reference
+-----------------------
+
+The action calls the :ref:`Holmes Chat API <holmes-chat-api>`. Any parameter supported by that endpoint (for example, ``model`` or ``additional_system_prompt``) can be added to the JSON body in the workflow.
+
+Troubleshooting
+---------------
+
+No comment appears on the PR
+    Check the action logs. The final step prints the ``analysis`` field returned by the API — if it contains a review but no comment was posted, the GitHub integration is not enabled for HolmesGPT. Re-check the `GitHub toolset guide <https://holmesgpt.dev/latest/data-sources/builtin-toolsets/github-mcp/>`_.
+
+``401 Unauthorized``
+    The ``ROBUSTA_API_KEY`` secret is missing, invalid, or lacks the **Robusta AI Write** capability. Regenerate the key in the Robusta Platform.
+
+``404 Not Found`` or cluster errors
+    The ``ROBUSTA_CLUSTER_ID`` secret does not match a cluster connected to your account. Copy the cluster ID from the Robusta Platform again.

docs/configuration/github-actions/index.rst

@@ -0,0 +1,12 @@
+GitHub Actions
+==============
+
+.. note::
+    These integrations are available with the Robusta SaaS platform and self-hosted commercial plans. They are not available in the open-source version.
+
+Run HolmesGPT inside your GitHub workflows to automate code review and investigation directly from GitHub events.
+
+Available Actions
+-----------------
+
+* :doc:`HolmesGPT PR Review <holmes-pr-review>`: Automatically review pull requests with HolmesGPT and post the review as a PR comment.

docs/configuration/holmesgpt/getting-started.rst

@@ -185,5 +185,5 @@ Next Steps
 ----------
 
 - Configure :doc:`alert routing </notification-routing/index>`
-- Set up :doc:`AI-powered insights </configuration/holmesgpt/getting-started>`
+- `Set up AI-powered insights <https://platform.robusta.dev/signup>`_
 - Learn about :doc:`common configuration options <metric-providers>`