You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 11, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+17-12Lines changed: 17 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,15 +20,22 @@ difficult to find the root cause of the issue.
20
20
21
21
True story; after this was deployed, a recurring OOM-kill in Fluentd was
22
22
quickly discovered on one of the nodes. It turns out that the resource limits
23
-
were set too low, and this particular node was logging a lot more. Logs were
23
+
were set too low to process logs on that node. Logs were
24
24
not being forwarded because the Fluentd worker process kept being OOM-kill and
25
-
then restarted by the main process. A fix was then deployed 10 minute later.
25
+
then restarted by the main process. A fix was then deployed 10 minutes later.
26
+
27
+
##Supported Container Runtimes
28
+
* Docker
29
+
* Containerd
30
+
31
+
Kubernetes 1.20 has deprecated Docker container runtime, so we have added support for Containerd since the version`0.21.0` of`missing-container-metrics`.
32
+
Both options should cover most of common use cases (EKS, GKE, K3S, Digital Ocean Kubernetes, ...).
26
33
27
34
##Deployment
28
35
29
36
###Kubernetes
30
37
31
-
The easiest way of installing`missing-container-metrics` in yourk8s cluster is using our[helm chart](https://artifacthub.io/packages/helm/missing-container-metrics/missing-container-metrics).
38
+
The easiest way of installing`missing-container-metrics` in yourkubernetes cluster is using our[helm chart](https://artifacthub.io/packages/helm/missing-container-metrics/missing-container-metrics).
Exposes metrics about Docker containers from Docker events.
49
+
Exposes metrics about Docker/Containerd containers.
43
50
Every metric contains following labels:
44
51
##Exposed Metrics
45
52
@@ -51,8 +58,7 @@ Number of restarts of the container.
51
58
52
59
###`container_ooms` (counter)
53
60
54
-
Number of OOM kills for the container. This covers OOM kill of any process in
55
-
the container cgroup.
61
+
Number of OOM kills for the container. This covers OOM kill of any process in the container cgroup.
56
62
57
63
###`container_last_exit_code` (gauge)
58
64
@@ -62,23 +68,23 @@ Last exit code of the container.
62
68
63
69
###`docker_container_id`
64
70
65
-
Full id of theDockercontainer.
71
+
Full id of the container.
66
72
67
73
###`container_short_id`
68
74
69
75
First 6 bytes of the Docker container id.
70
76
71
77
###`container_id`
72
78
73
-
Container id represented in the same format as in metrics ofk8s pods - prefixed with`docker://`. This enables easy joins in Prometheus to kube_pod_container_info metric.
79
+
Container id represented in the same format as in metrics ofkubernetes pods - prefixed with`docker://` and`containerd://` depending on the container runtime. This enables easy joins in Prometheus to`kube_pod_container_info` metric.
74
80
75
81
###`name`
76
82
77
83
Name of the container.
78
84
79
85
###`image_id`
80
86
81
-
Image id represented in the same format as in metrics of k8spods - prefixed with`docker-pullable://`. This enables easy joins in Prometheus to kube_pod_container_info metric.
87
+
Image id represented in the same format as in metrics of k8spod. This enables easy joins in Prometheus to`kube_pod_container_info` metric.
82
88
83
89
###`pod`
84
90
@@ -90,9 +96,8 @@ will be set as the `pod` label in the metric
90
96
If`io.kubernetes.pod.namespace` label is set on the container, it's value
91
97
will be set as the`namespace` label of the metric.
92
98
93
-
This label, together with`pod` is useful in the context of Kubernetes deployments, to determine namespace/pod to which the container is part of,
94
-
instead of having to join with`kube_pod_container_info` metric to determine
95
-
those values.
99
+
Together with`pod`, this label is useful in the context of Kubernetes deployments, to determine namespace/pod to which the container is part of.
100
+
One can see it as a shortcut to joining with the`kube_pod_container_info` metric to determine those values.