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
Copy file name to clipboardExpand all lines: docs/ops.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,8 +82,8 @@ There are a few settings that are important for ops.
82
82
The first setting is the `oom_score`. Because containerd will be managing multiple containers, we need to ensure that containers are killed before the containerd daemon gets into an out of memory condition.
83
83
We also do not want to make containerd unkillable, but we want to lower its score to the level of other system daemons.
84
84
85
-
containerd also exports its own metrics as well as container level metrics via the prometheus metrics format.
86
-
Currently, prometheus only supports TCP endpoints, therefore, the metrics address should be a TCP address that your prometheus infrastructure can scrape metrics from.
85
+
containerd also exports its own metrics as well as container level metrics via the Prometheus metrics format under `/v1/metrics`.
86
+
Currently, Prometheus only supports TCP endpoints, therefore, the metrics address should be a TCP address that your Prometheus infrastructure can scrape metrics from.
87
87
88
88
containerd also has two different storage locations on a host system.
89
89
One is for persistent data and the other is for runtime state.
0 commit comments