5.1 Tasks: kube-prometheus metrics

Mon, 01 Jan 0001 00:00:00 +0000

Task 5.1.1: Memory usage of Prometheus

Task description:

Display the memory usage of both Prometheus pods
Use a filter to just display metrics from your prometheus containers

Use the [Thanos Querier web UI](https://thanos-query.app.lernvirt.ch to execute the queries.

Note

Search for a metric with memory_working_set in its name

Hints

container_memory_working_set_bytes{pod=~"prometheus-prometheus-0", container="prometheus",namespace=~"<user>.*"}

Task 5.1.2: Kubernetes pod count

Task description:

Display how many pods are currently running on your Kubernetes platform

Hints

There are different ways to archive this. You can for example query all running containers and group them by pod and namespace.

count(sum(kube_pod_container_status_running == 1) by (pod,namespace,cluster))

You may also sum() all running pods on your Kubernetes nodes

sum(kubelet_running_pods)

5.2 Tasks: Prometheus Operator

Mon, 01 Jan 0001 00:00:00 +0000

5.2.1: Prometheus storage

By default, the Prometheus operator stack does not persist the data of the deployed monitoring stack. Therefore, any pod restart would result in a reset of all data. Let’s learn about persistence for Prometheus.

Task description:

See this example of how to configure storage for Prometheus

To get the current values, either look at the file in git or use kubectl -n $USER-monitoring get prometheus prometheus -oyaml.

Hints

To enable storage for our Prometheus we would simply add the following section to our Prometheus definition.

...
spec:
  ...
  securityContext:
    fsGroup: 65534
  storage:
    disableMountSubPath: true
    volumeClaimTemplate:
      spec:
        resources:
          requests:
            storage: 10Gi
  ...

5. Prometheus in Kubernetes on IT-CNE Cloud-Native Core

5.1 Tasks: kube-prometheus metrics

Task 5.1.1: Memory usage of Prometheus

Task 5.1.2: Kubernetes pod count

5.2 Tasks: Prometheus Operator

5.2.1: Prometheus storage