Grafana Shows Wrong Core_Frequency Value, But Data is Right
- Dominant language
- C++
- Stars
- 3.3k
- Forks
- 528
- Avg merge
- 1h 40m
- Merged PRs (30d)
- 2
Description
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](https://github.com/user-attachments/files/16248206/prometheus.json)
- [prometheus-default.json](https://github.com/user-attachments/files/16248207/prometheus-default.json)
**Metrics**
- [metrics1.txt](https://github.com/user-attachments/files/16248208/metrics1.txt)
- [metrics2.txt](https://github.com/user-attachments/files/16248209/metrics2.txt)
- [metrics3.txt](https://github.com/user-attachments/files/16248210/metrics3.txt)
- [metrics4.txt](https://github.com/user-attachments/files/16248211/metrics4.txt)
- [metrics5.txt](https://github.com/user-attachments/files/16248203/metrics5.txt)
- [metrics6.txt](https://github.com/user-attachments/files/16248204/metrics6.txt)
- [metrics7.txt](https://github.com/user-attachments/files/16248205/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`
Contributor guide
Assessment
This issue has not been assessed yet.