remove fluff

Author: aantn

docs/configuration/holmesgpt/holmesgpt-docs.rst

@@ -3,25 +3,4 @@ HolmesGPT Documentation
 
 For comprehensive HolmesGPT documentation, please visit the official HolmesGPT documentation site at `holmesgpt.dev <https://holmesgpt.dev>`_.
 
-Configuring HolmesGPT with Robusta
------------------------------------
-
-When configuring HolmesGPT with Robusta, follow the **Robusta Helm Chart configuration method** described in the HolmesGPT documentation rather than standalone CLI installation.
-
-Key points:
-
-* Use the ``enableHolmesGPT: true`` setting in your Robusta Helm values
-* Configure data sources and advanced settings using the Helm chart configuration examples provided in the HolmesGPT docs
-* Refer to the `Helm Configuration Reference <https://holmesgpt.dev/reference/helm-configuration/>`_ for advanced HolmesGPT settings specific to Robusta deployments
-
-Quick Links
------------
-
-* `HolmesGPT Main Documentation <https://holmesgpt.dev>`_
-* `Data Sources Configuration <https://holmesgpt.dev/data-sources/builtin-toolsets/>`_
-* `Helm Chart Configuration Reference <https://holmesgpt.dev/reference/helm-configuration/>`_
-
-For Robusta-specific HolmesGPT setup instructions, see:
-
-* :doc:`getting-started` - Quick setup guide for HolmesGPT with Robusta
-* :doc:`main-features` - Overview of AI analysis features
+For Robusta-specific setup instructions, see :doc:`getting-started`.

docs/configuration/holmesgpt/main-features.rst

@@ -3,27 +3,38 @@ Main Features
 
 Robusta integrates `HolmesGPT <https://github.com/robusta-dev/holmesgpt>`_ to provide AI-powered root cause analysis for Kubernetes alerts and issues.
 
-What HolmesGPT Does
--------------------
-
-**Automatic Investigation**
-   When alerts fire, HolmesGPT automatically:
-   
-   * Analyzes pod logs and events
-   * Examines resource metrics and limits
-   * Checks recent deployments and changes
-   * Investigates related resources and dependencies
-   * Provides actionable recommendations
-
-**Multi-Source Analysis**
-   HolmesGPT pulls data from:
-   
-   * Kubernetes API (pods, nodes, events, logs)
-   * Prometheus metrics
-   * Cloud provider APIs (AWS, Azure, GCP)
-   * Application monitoring (Datadog, New Relic)
-   * Log aggregation systems (Loki, OpenSearch, Coralogix)
-   * And more via `extensible toolsets <https://holmesgpt.dev/data-sources/builtin-toolsets/>`_
+See HolmesGPT in Action
+-----------------------
+
+.. tab-set::
+
+   .. tab-item:: AWS Troubleshooting
+
+      .. raw:: html
+
+         <div style="position: relative; padding-bottom: 56.25%; height: 0;">
+            <iframe src="https://www.loom.com/embed/2e5e3a259a5c41018914c9abd8429f00"
+                    frameborder="0"
+                    webkitallowfullscreen
+                    mozallowfullscreen
+                    allowfullscreen
+                    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;">
+            </iframe>
+         </div>
+
+   .. tab-item:: CPU Spike Investigation
+
+      .. raw:: html
+
+         <div style="position: relative; padding-bottom: 56.25%; height: 0;">
+            <iframe src="https://www.loom.com/embed/b63f0eba0fd74750929f37c16b3fca3b"
+                    frameborder="0"
+                    webkitallowfullscreen
+                    mozallowfullscreen
+                    allowfullscreen
+                    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;">
+            </iframe>
+         </div>
 
 How to Use It
 -------------
@@ -36,40 +47,11 @@ How to Use It
 
 **Via @holmes in Slack**
    Ask natural language questions about your clusters:
-   
+
    * ``@holmes what apps are crashing in prod-cluster?``
    * ``@holmes why is my alert firing on staging?``
    * ``@holmes investigate high memory usage in dev-cluster``
 
-Example Investigation
----------------------
-
-Here's what HolmesGPT found for a CrashLoopBackOff alert:
-
-.. image:: /images/AI_Analysis_demo2.png
-    :width: 1000px
-
-The AI identified:
-- The exact error from pod logs
-- The root cause (missing environment variable)
-- Recommended fix with example YAML
-- Related configuration issues
-
-Why Use HolmesGPT?
-------------------
-
-**Save Time**
-   Stop manually checking logs, metrics, and events across multiple tools. HolmesGPT does it in seconds.
-
-**Reduce MTTR**
-   Get to root cause faster with AI that understands Kubernetes patterns and common issues.
-
-**Learn as You Go**
-   Each investigation explains what was checked and why, helping your team learn Kubernetes troubleshooting.
-
-**24/7 Coverage**
-   AI investigations run automatically on every alert, even at 3 AM.
-
 Next Steps
 ----------