Skip to content

Commit 9933eb6

Browse files
committed
feat(k8s): update docs
1 parent 7a21933 commit 9933eb6

File tree

1 file changed

+11
-8
lines changed

1 file changed

+11
-8
lines changed

pages/kubernetes/how-to/monitor-data-plane-with-cockpit.mdx

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
meta:
3-
title: How to monitor your Kubernetes Kapsule data plane with Cockpit
3+
title: How to monitor your Kubernetes Kapsule cluster with Cockpit using Promtail
44
description: This page explains how to integrate Kubernetes container logs with Scaleway Cockpit using Promtail
55
content:
6-
h1: How to monitor your Kubernetes Kapsule data plane with Cockpit
6+
h1: How to monitor your Kubernetes Kapsule cluster with Cockpit using Promtail
77
paragraph: This page explains how to integrate Kubernetes container logs with Scaleway Cockpit using Promtail
88
categories:
99
- iot-hub
@@ -53,8 +53,9 @@ The system leverages **Promtail** (a lightweight log collector) running on your
5353
1. **Promtail** can collect logs from:
5454
- **Container stdout/stderr** (pods)
5555
- **systemd journal** (e.g., `kubelet.service`)
56-
2. **Log data** is transmitted to **Cockpit** (Loki).
57-
3. **Cockpit** stores and indexes these logs.
56+
2. The app automatically creates a custom datasource called `kubernetes-logs` and a Cockpit token with push logs permission.
57+
3. **Log data** is transmitted to **Cockpit** (Loki).
58+
4. **Cockpit** stores and indexes these logs.
5859

5960
## Step-by-step: Enabling container logs in Cockpit
6061

@@ -74,7 +75,7 @@ You can use Scaleway’s **[Easy Deploy](/kubernetes/how-to/enable-easy-deploy/)
7475
cockpit_promtail_scrape_config_journal: "kubelet.service,kube-proxy.service"
7576
```
7677
</Message>
77-
78+
7879
### Example Promtail configuration
7980
Below is a simplified snippet of the configuration that Easy Deploy generates by default:
8081
```yaml
@@ -104,13 +105,15 @@ extraVolumes:
104105

105106
Once Promtail is running:
106107

107-
1. Go to **Cockpit**, then **Kubernetes Cluster Pod Logs** (or open your own Grafana connected to Cockpit).
108-
2. **Filter** by:
108+
1. Go to the **Cockpit** section of the Scaleway console, then click **Open dashboards**.
109+
2. Log into Grafana using your [Cockpit credentials](/cockpit/how-to/retrieve-grafana-credentials/).
110+
3. In Grafana's menu, go to dashboards and select **Kubernetes Cluster Pod Log**.
111+
4. **Filter** by:
109112
- `Datasource` which is automatically created upon deployment, and visible in the Cockpit console
110113
- `Cluster Name` ( e.g. `my-kapsule-cluster`)
111114
- `namespace`, `pod`, or `container` labels to isolate specific workloads
112115
- **Time range** to limit how far back in history you want to query
113-
3. **Analyze** logs in real-time or historical mode to troubleshoot issues, watch for errors, or track performance.
116+
5. **Analyze** logs in real-time or historical mode to troubleshoot issues, watch for errors, or track performance.
114117

115118
## Usage and pricing
116119

0 commit comments

Comments
 (0)