search

NagiosEnterprises / ncpa

Nagios Cross-Platform Agent
Other
177 stars 95 forks source link

NCPA 2.4.0:: Memory usage performance graphic doesn't work in NCPA version 2.4.0 #845

Open FTackEUR opened 2 years ago

FTackEUR commented 2 years ago

Hi all,

Since the update of NCPA version 2.4.0 the memory usage service check performance graphic isn't working anymore on NCPA version 2.4.0 on our RHEL8 clients. This worked on the previous version 2.3.1. See also screenshot of the performance graphic of a memory usage on our clients. Selection_083

Kind Regards,

Fabiuseur

MrPippin66 commented 2 years ago

Can you expand on the issue you're seeing?

dan-m-joh commented 2 years ago

Have you seen that there is one more measurement (percent) in the performance data output in 2.4.0 in comparison to 2.3.x?

2.3.x: | 'available'=0.89GiB;;; 'total'=1.80GiB;;;  'free'=0.17GiB;;; 'used'=0.65GiB;;;
2.4.0: | 'available'=0.89GiB;;; 'total'=1.80GiB;;; 'percent'=50.50%;80;90; 'free'=0.17GiB;;; 'used'=0.65GiB;;;

Could it bee that your graphing-tool chokes on this?

FTackEUR commented 2 years ago

Yeah, I see the comparison between NCPA version 2.3.x and 2.4.0. And that the graphing-tool of Nagios XI is choking on the percent measurement in the recent release of NCPA.

I've fixed this issue to cleanup the memory usage performance data in /usr/local/nagios/share/perfdata//Memory_Usage.rrd and Memory.Usage.xml

But it will erase all historical performance data of the memory usage service check.

shodgson11 commented 2 years ago

You can fix this by running the rrd_ds_fix tool here: https://support.nagios.com/kb/article/nagios-xi-icmp-and-ping-checks-stopped-graphing-149.html However, if you've already started collecting new data and want to keep old and new data, you'll need to copy the old rrd file with the new xml file somewhere else, run the fix tool above, and then run a combining tool on the fixed old rrd and the new rrd (https://gist.github.com/yalinhuang/9a8d35421c1feb148bd0).

This is really something that should have been automatically handled. It's a bad look when Nagios's own server monitoring client breaks data collection.

Relevant Nagios support forum post: https://support.nagios.com/forum/viewtopic.php?f=16&t=64622