Ben Kochie

That's not a bad idea. Would we want one setting for metric names and one for label values? ``` label_cardinality_limit ```

Yes, definitely looks like a quoting issue to me. Docker is very likely passing in the path as literal `"/var/lib/node_exporter/textfile_collector"` @discordianfish We've been putting those flag parsing lines in as...

@discordianfish Oh, hmm, I'm not sure adding `--path.rootfs` makes sense. Users may have the textfile dir not directly on the rootfs and have something like a `-v /some_path:/textfile_colector` in their...

Any progress on this?

The metric is correct as-is, in this case `node_processes_pids` is already "Number of Processes". The documentation in the help string is just a bit misleading/confusing.

This does not seem like an issue with the exporter. The exporter exposes what data the kernel provides.

It doesn't seem like this feature works on modern systems: ```console $ grep CONFIG_CPU_FREQ_STAT /boot/config-$(uname -r) CONFIG_CPU_FREQ_STAT=y $ ls -l /sys/devices/system/cpu/*/cpufreq/stats ls: cannot access '/sys/devices/system/cpu/*/cpufreq/stats': No such file or directory...

IIRC the ignoring of missing files was intentional, as the cpufreq drivers have inconsistent implementations.

Figuring out ephemeral port usage is tricky, because it's not just the local port range. But it is multiplied by the 4-tuple of source and destination IP:port combinations. Just because...

How about making this a textfile collector tool first as a PoC?