Grafana Shows Wrong Core_Frequency Value, But Data is Right

[alastorid]

The system is a DL560G8 with 4x4657LV2. Here's what the Grafana looks like:

The metric 7.86e-7 for CPU frequency seems incorrect, as I expect the CPUs to run between 1 to 2.9 GHz, or possibly at 0.8 GHz. I've monitored the dashboard for a while and noticed that the frequency never reaches 2.x GHz, even when the target system is fully loaded.

I checked the data from back-end and the result seems good:

Attached are some metric files from the system, along with the prometheus.json dashboard file. Not all data on Grafana are incorrect: for example, DDR read/write and cache hit rates appear correct. I've checked the dashboard file and can't find an obvious reason for the unexpected Core_Frequency value. Any pointers would be appreciated!
Dashbaord

• prometheus.json
• prometheus-default.json

Metrics

• metrics1.txt
• metrics2.txt
• metrics3.txt
• metrics4.txt
• metrics5.txt
• metrics6.txt
• metrics7.txt

P.S. The Grafana instance is running in Docker on a freshly installed Red Hat Enterprise Linux 9.4, launched using the script ./start-prometheus.sh target.txt

[rdementi]

thanks for the report. This looks like a bug to me..

[rdementi]

this seems to be specific to the way how this pcm data is exposed in prometheus format. The PCM start.sh grafana script (telegraf/inflixdb/grafana stack) shows these metrics correctly.

[rdementi]

I think I have root-caused the issue.

[alastorid]

Glad to hear it’s been figured out! Looking forward to the update.