From 4135c00d33c9788df8c451bf99af37b218fae1e6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20Vorburger=20=E2=9B=91=EF=B8=8F?= Date: Fri, 27 Mar 2020 20:59:47 +0100 Subject: [PATCH] minor README doc fix re. collector.perf.cpus Signed-off-by: Michael Vorburger --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3a1546e695..bed3a908d8 100644 --- a/README.md +++ b/README.md @@ -89,11 +89,11 @@ By default, the perf collector will only collect metrics of the CPUs that `node_exporter` is running on (ie [`runtime.NumCPU`](https://golang.org/pkg/runtime/#NumCPU). If this is insufficient (e.g. if you run `node_exporter` with its CPU affinity set to -specific CPUs) You can specify a list of alternate CPUs by using the +specific CPUs), you can specify a list of alternate CPUs by using the `--collector.perf.cpus` flag. For example, to collect metrics on CPUs 2-6, you would specify: `--collector.perf --collector.perf.cpus=2-6`. The CPU -configuration is zero indexed and can also take a stride value -`--collector.perf --collector.perf.cpus=1-10:5`, would collect on CPUs +configuration is zero indexed and can also take a stride value; e.g. +`--collector.perf --collector.perf.cpus=1-10:5` would collect on CPUs 1, 5, and 10.