Ben Kochie
Ben Kochie
Yes, I never liked the dumping of random proc contents with no filtering. This leads to random breakage.
The other question is can this be obtained without root privileges.
Parsing `/sys/block/*/stat` might be a good idea. But some users do want partition-level stats. We use the regexp method to provide the most generic way to filter exactly what the...
It's also possible to scan `/sys/block/$DEV/$DEV*/stat` for partition data. But either way, this would require completely re-designing the flag layout for this collector. It also changes the consistency of the...
I guess we could mark the existing metric deprecated.
This seems like a duplicate of https://github.com/prometheus/node_exporter/issues/1241, but possibly a new bug. Can you run the node_exporter with --log.level=debug and get the output for the cpufreq collector?
It might also be worth trying out the latest 1.0 release candidate.
This looks like an issue with the procfs parsing of the cpufreq data.
It would be useful to include the text output of this script: ``` for f in $(find /sys/devices/system/cpu/cpu*/cpufreq/ -type f) ; do echo "$f: $(< $f)" ; done ```
That's strange, I don't see `` in any of that output. Are you sure this is the same system?