@swolf, I think I've resolved. I overlooked that in /usr/local/nagios/etc/pnp/process_perfdata.cfg, I had changed the RRDPATH. Upon reverting to /usr/local/nagios/share/perfdata, rrd and xml files are now being generated there, AND, graphs are populating.
#RRDPATH = /var/log/nagios/perfdata
RRDPATH = /usr/local/nagios/share/perfdata
Clarification, please, on something you wrote: " . . . so if someone updates their check to, say, track an additional hard drive, that can break the graph. Many users find that deleting the existing RRD is easier than migrating the schema."
Which RRD should be deleted? Wouldn't a new hard drive check create a new RRD?
Now IF I delete an RRD, am I not loosing historical performance data and starting all over?
RESOLVED - No Performance graphs, data is being processed
-
- Posts: 172
- Joined: Fri Sep 11, 2020 2:13 pm
-
- Posts: 336
- Joined: Wed Aug 23, 2023 1:02 pm
Re: No Performance graphs, data is being processed
First of all, its great you got the problem resolved!
As for your questions, If you had 7 drives previously and added an 8th, that's correct that a new RRD file would be generated. What we mean by "breaking the graphs" is that depending on how your specific services are named and indexed, adding a new drive could reorder the drive names or indexes, particularly after a reboot when everything gets rescanned by the system. In that case the data from different drives could get conflated into the same graph, before and after the device name change. Correcting those files is what is meant by changing the schema, and as noted, some customers find it preferable in those cases to just start from scratch.
To your last question, yes if you delete the rrd you'll lose the historical data contained within it.
As for your questions, If you had 7 drives previously and added an 8th, that's correct that a new RRD file would be generated. What we mean by "breaking the graphs" is that depending on how your specific services are named and indexed, adding a new drive could reorder the drive names or indexes, particularly after a reboot when everything gets rescanned by the system. In that case the data from different drives could get conflated into the same graph, before and after the device name change. Correcting those files is what is meant by changing the schema, and as noted, some customers find it preferable in those cases to just start from scratch.
To your last question, yes if you delete the rrd you'll lose the historical data contained within it.
Please let us know if you have any other questions or concerns.
-Jason
-Jason
-
- Posts: 172
- Joined: Fri Sep 11, 2020 2:13 pm
Re: RESOLVED - No Performance graphs, data is being processed
Thanks for the clarification on those points, @jmichaelson.
I created a new service, using the folder watch configuration wizard, to monitor /usr/local/nagios/var/spool/xidpe. Files backing up in that folder indicate a problem (and have caused my / to fill in the past)
On the service check settings I clicked process perf data. Although the new service is showing up and checking in the services list, there is no icon indicating a chart is available, and no chart. Also, looking in /usr/local/nagios/share/perfdata/<nagios hostname> I see no new .xml or rrd created for that monitor. I've cycled npcd. Is there anything else I need to do to get RRDs and charts generated for a new monitor? I would have thought not.
Thanks,
I created a new service, using the folder watch configuration wizard, to monitor /usr/local/nagios/var/spool/xidpe. Files backing up in that folder indicate a problem (and have caused my / to fill in the past)
On the service check settings I clicked process perf data. Although the new service is showing up and checking in the services list, there is no icon indicating a chart is available, and no chart. Also, looking in /usr/local/nagios/share/perfdata/<nagios hostname> I see no new .xml or rrd created for that monitor. I've cycled npcd. Is there anything else I need to do to get RRDs and charts generated for a new monitor? I would have thought not.
Thanks,