You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, first of all, thank you very much for your work in keeping naemon up to date.
I am contacting you today because I wanted to report a problem that I am encountering, we have installed pnp4nagios in its latest version provided in your repository (https://github.com/ConSol-Monitoring/omd/tree/labs/packages/pnp4nagios), when we want to view the graphs generated by the hosts, it works because data is reported. Unfortunately, this is not the case for services, they seem to be lost, when the perfdata are generated, they are changed folder but neither xml or RRD files are generetad/populated for the service(s).
I will reproduce the problem to provide you the screenshots to visualize the problem encountered.
I could also see that in an old open incident from 2018, this data loss had already appeared before.
Incident link: #273
Thank you in advance for any response you can give us.
The text was updated successfully, but these errors were encountered:
Finnaly, we found the solution for this issue, it was a mistake in the config file. In this file, i didn't specify the variable of datas that we need to get, i think it was when i tried to copy and paste this file.
Hello, first of all, thank you very much for your work in keeping naemon up to date.
I am contacting you today because I wanted to report a problem that I am encountering, we have installed pnp4nagios in its latest version provided in your repository (https://github.com/ConSol-Monitoring/omd/tree/labs/packages/pnp4nagios), when we want to view the graphs generated by the hosts, it works because data is reported. Unfortunately, this is not the case for services, they seem to be lost, when the perfdata are generated, they are changed folder but neither xml or RRD files are generetad/populated for the service(s).
I will reproduce the problem to provide you the screenshots to visualize the problem encountered.
I could also see that in an old open incident from 2018, this data loss had already appeared before.
Incident link: #273
Thank you in advance for any response you can give us.
The text was updated successfully, but these errors were encountered: