fix(cockpit): added extraDiscoveryRules

Author: fleblay

pages/cockpit/how-to/send-logs-from-k8s-to-cockpit.mdx

@@ -63,7 +63,13 @@ podLogs:
   destinations: ["my-cockpit-logs"]
   volumeGatherSettings:
     onlyGatherNewLogLines: true
-
+  # Prevent collecting the collector own logs
+  extraDiscoveryRules: |
+    rule {
+      source_labels = ["__meta_kubernetes_pod_name"]
+      action = "drop"
+      regex = ".*alloy-logs.*"
+    }
 # An Alloy instance for collecting log data.
 alloy-logs:
   enabled: true
@@ -73,6 +79,10 @@ alloy-logs:
 alloy-singleton:
   enabled: true
 ```
+<Message type="tip">
+  The `PodLogs` feature will do the autodiscovery to collect logs from all pods. In the above configuration, we have dropped all the logs of the pod in charge of collecting the logs.
+  If you want to exlude other pods, you can add an extra drop rule in the extraDiscoveryRules section.
+</Message>
 
 <Message type="note">
  The template above is for sending logs to your Cockpit. You can also configure it to send metrics to Cockpit using this Helm chart.
@@ -146,4 +156,4 @@ You can also use Terraform/OpenTofu to manage and deploy Helm charts, providing
 7. Optionally, click the **Clock** icon on the top right corner of your screen and filter by time range.
 8. Click **Run query** to see your logs. An output similar to the following should display.
 
-<Lightbox image={image} alt="" />
+<Lightbox image={image} alt="" />