docs(cpt): add images + fix dates

menu/navigation.json

@@ -3558,6 +3558,14 @@
                     "label": "Send metrics to Cockpit using Grafana Alloy",
                     "slug": "send-metrics-with-grafana-alloy"
                   },
+                  {
+                    "label": "Send metrics from your Kubernetes cluster to Cockpit",
+                    "slug": "send-metrics-from-k8s-to-cockpit"
+                  },
+                  {
+                    "label": "Send logs from your Kubernetes cluster to Cockpit",
+                    "slug": "send-logs-from-k8s-to-cockpit"
+                  },
                   {
                     "label": "Send metrics and logs to your Cockpit",
                     "slug": "send-metrics-logs-to-cockpit"

observability/cockpit/how-to/send-log-from-k8s-to-cockpit.mdx

@@ -9,8 +9,8 @@ tags: kubernetes cockpit logs observability monitoring cluster
 categories:
   - observability
 dates:
-  validation: 2025/01/20
-  posted: 2025/01/20
+  validation: 2025-01-20
+  posted: 2025-01-20
 ---
 
 In this page, we will show you how to send application logs from your Kubernetes cluster to your Cockpit using either a Helm chart or deploying a Helm chart with [Terraform](https://www.terraform.io/).
@@ -43,14 +43,14 @@ destinations:
   - name: "my-cockpit-logs"
     type: "loki"
     protocol: "http"
-    logs: 
+    logs:
       enabled: true
     url: "$COCKPIT_CUSTOM_LOGS_DATASOURCE_URL/loki/api/v1/push" ##You can find your logs URL in the **Data sources** tab of the Scaleway console under the "API URL" section of the relevant data source
     tenantId: "$COCKPIT_TOKEN"
-    
-    metrics: 
+
+    metrics:
       enabled: false
-    traces: 
+    traces:
       enabled: false
 clusterEvents:
   enabled: true
@@ -91,7 +91,6 @@ Once you have configured your `values.yml` file, you can use Helm to deploy the
   helm install -f /your-path/to/values.yml name-of-your-choice-for-your-log-ingester k8s-monitoring --version 1.6.16
   ```
     The `-f` flag specifies the path to your `values.yml` file, which contains the configuration for the Helm chart. Make sure that you replace `/your-path/to/values.yml` with the correct path where your `values.yml` file is stored. Make sure that you also replace `name-of-your-choice-for-your-log-ingester` with a clear name (ex. `alloy-logs-ingester`). In our configuration, we are using `alloy-lm-ingester`.
-
     Helm installs the `k8s-monitoring` chart, which includes the Alloy DaemonSet configured to collect logs from your Kubernetes cluster.
     The DaemonSet ensures that a pod is running on each node in your cluster, which collects logs and forwards them to the specified Loki endpoint in your Cockpit.
 

observability/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx

@@ -9,8 +9,8 @@ tags: kubernetes cockpit metrics observability monitoring cluster
 categories:
   - observability
 dates:
-  validation: 2025/01/20
-  posted: 2025/01/20
+  validation: 2025-01-20
+  posted: 2025-01-20
 ---
 
 
@@ -45,14 +45,14 @@ destinations:
   - name: "my-cockpit-metrics"
     type: "prometheus"
     protocol: "http"
-    metrics: 
+    metrics:
       enabled: true
     url: "$COCKPIT_CUSTOM_METRICS_DATASOURCE_URL/api/v1/push"
     tenantId: "$COCKPIT_TOKEN"
-    
-    logs: 
+
+    logs:
       enabled: false
-    traces: 
+    traces:
       enabled: false
 
 annotationAutodiscovery:
@@ -151,9 +151,8 @@ Once you have configured your `values.yml` file, you can use Helm to deploy the
   helm install -f /your-path/to/values.yml name-of-your-choice-for-your-metric-ingester k8s-monitoring --version 1.6.16
   ```
     The `-f` flag specifies the path to your `values.yml` file, which contains the configuration for the Helm chart. Make sure that you replace `/your-path/to/values.yml` with the correct path where your `values.yml` file is stored. Make sure that you also replace `name-of-your-choice-for-your-metric-ingester` with a clear name (ex. `alloy-metrics-ingester`). In our configuration, we are using `alloy-lm-ingester`.
-        
-        Helm installs the `k8s-monitoring` chart, which includes the Alloy DaemonSet configured to collect metrics from your Kubernetes cluster.
-        The DaemonSet ensures that a pod is running on each node in your cluster, which collects metrics and forwards them to the specified Prometheus endpoint in your Cockpit.
+    Helm installs the `k8s-monitoring` chart, which includes the Alloy DaemonSet configured to collect metrics from your Kubernetes cluster.
+    The DaemonSet ensures that a pod is running on each node in your cluster, which collects metrics and forwards them to the specified Prometheus endpoint in your Cockpit.
 
 3. Optionally, check the status of the release to ensure it was installed: