Merge branch 'master' into rob-1267_unified_logging_docs_update

Author: pavangudiwada

docs/configuration/holmesgpt/builtin_toolsets.rst

@@ -18,6 +18,7 @@ Builtin Toolsets
    toolsets/internet
    toolsets/kafka
    toolsets/kubernetes
+   toolsets/notion
    toolsets/opensearch_logs
    toolsets/opensearch_status
    toolsets/prometheus
@@ -99,6 +100,11 @@ by the user by providing credentials or API keys to external systems.
         :class-card: sd-bg-light sd-bg-text-light
         :link: toolsets/kubernetes
         :link-type: doc
+    
+    .. grid-item-card:: :octicon:`cpu;1em;` Notion
+        :class-card: sd-bg-light sd-bg-text-light
+        :link: toolsets/notion
+        :link-type: doc
 
     .. grid-item-card:: :octicon:`cpu;1em;` OpenSearch logs
         :class-card: sd-bg-light sd-bg-text-light

docs/configuration/holmesgpt/index.rst

@@ -10,12 +10,15 @@ AI Analysis
    builtin_toolsets
    permissions
    custom_toolsets
+   remote_mcp_servers
 
 Why use HolmesGPT?
 ^^^^^^^^^^^^^^^^^^^
 
 Robusta can integrate with `Holmes GPT <https://github.com/robusta-dev/holmesgpt>`_ to analyze health issues on your cluster, and to run AI based root cause analysis for alerts.
 
+This requires a Robusta SaaS account, and for the Robusta UI sink to be enabled. (We have plans to support HolmesGPT in a pure OSS mode in the near future. Stay tuned!)
+
 When available, AI based investigations can be launched in one of two ways:
 
 1. Click the ``Ask HolmesGPT`` button in Slack. The AI investigation will be sent back as a new message.
@@ -35,7 +38,7 @@ Add ``enableHolmesGPT: true`` to the Robusta Helm values, and then follow these
 
 1. Choose an AI model - we highly recommend using GPT-4o to get the most accurate results! Other models may work, but are not officially supported.
 2. :ref:`Configure your AI provider with the chosen model <Choosing and configuring an AI provider>`.
-3. :ref:`Optional: Configure HolmesGPT Access to SaaS Data <Configuring HolmesGPT Access to SaaS Data>`.
+3. :ref:`Configure HolmesGPT Access to SaaS Data <Configuring HolmesGPT Access to SaaS Data>`.
 
 Choosing and configuring an AI provider
 ----------------------------------------
@@ -371,3 +374,14 @@ Custom toolsets
 
 Custom toolsets are created through your Helm values file and you can find instructions
 to :doc:`write your own toolsets here <builtin_toolsets>`.
+
+Remote MCP servers 
+---------------------
+
+.. warning::
+
+    Remote MCP servers are in **Tech Preview** stage.
+
+Remote MCP server connections are configured through your Helm values file.
+For detailed instructions, refer to the :doc:`Connecting to Remote MCP Servers <remote_mcp_servers>` guide.
+

docs/configuration/holmesgpt/remote_mcp_servers.rst

@@ -0,0 +1,46 @@
+Remote MCP Servers 
+====================
+
+.. warning::
+
+    Remote MCP servers are in **Tech Preview** stage.
+
+
+HolmesGPT can integrate with remote MCP servers using SSE mode.
+This capability enables HolmesGPT to access external data sources and tools in real time.
+This guide provides step-by-step instructions for configuring HolmesGPT to connect with remote MCP servers over SSE.
+
+Example : MCP server configuration
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. md-tab-set::
+
+  .. md-tab-item:: Robusta Helm Chart
+
+    **Helm Values:**
+
+    .. code-block:: yaml
+
+      holmes:
+        mcp_servers:
+          mcp_server_1:
+            # human-readable description of the mcp server (this is not seen by the AI model - its just for users)
+            description: "Remote mcp server"
+            url: "http://example.com:8000/sse"
+          
+          mcp_server_2:
+            description: "MCP server that runs in my cluster"
+            url: "http://<service-name>.<namespace>.svc.cluster.local:<service-port>"
+            config:
+              headers:
+                key: "{{ env.my_mcp_server_key }}" # You can use holmes environment variables as headers for the MCP server requests.
+        
+    Update your Helm values with the provided YAML configuration, then apply the changes with Helm upgrade:
+
+    .. code-block:: bash
+
+        helm upgrade robusta robusta/robusta --values=generated_values.yaml --set clusterName=<YOUR_CLUSTER_NAME>
+
+    
+
+

helm/robusta/values.yaml

@@ -578,7 +578,7 @@ image:
 # parameters for the robusta forwarder deployment
 kubewatch:
   image: ~ # image can be used to override image.registry/imageName
-  imageName: kubewatch:v2.9.0
+  imageName: kubewatch:v2.11.0
   imagePullPolicy: IfNotPresent
   pprof: True
   resources:

src/robusta/integrations/jira/client.py

@@ -150,7 +150,7 @@ def _get_issue_for_labels(self, labels):
 
         issue = issues.get("issues")[0]
         if issues.get("total", 0) > 1:
-            logging.warn(f"More than one issue found for query: '{query}', picking most recent one")
+            logging.warning(f"More than one issue found for query: '{query}', picking most recent one")
             logging.debug(f"Picked issue '{issue}'")
 
         return issue