How to avoid unnecessary service structure in status.dat
Posted: Thu Mar 28, 2013 12:14 am
Hello all! I installed nagios and check_nrpe to monitor the hosts and services associated with them in my cluster with 3 nodes. I have considered one of them as the monitoring server. Now, I want to monitor two of the services in one remotehost once in 2hrs and keep all others have the default check interval. I referred the documentation and found that I can change the pooling interval (normal_check_interval) to attain this. In the templates.cfg I can see that service named local-service sets the normal_check_interval to 5. With this, I can make the associated plugin execute once in 2hrs by adding a line normal_check_interval=2h in the corresponding service definition (Please correct me if I am wrong).
But with this, I can just make the service be checked once in 2hrs but cannot reduce the size of status.dat file. Even if the service is not being checked every 5 mins, the status.dat file always contains the entry for that service structure with old 'status information', 'perfdata' and other values. My intention is to reduce the unnecessary data transfer between the remote host and the server. But here, I think the old data is transfered for 2hrs every 5 mins. How to avoid this?
But with this, I can just make the service be checked once in 2hrs but cannot reduce the size of status.dat file. Even if the service is not being checked every 5 mins, the status.dat file always contains the entry for that service structure with old 'status information', 'perfdata' and other values. My intention is to reduce the unnecessary data transfer between the remote host and the server. But here, I think the old data is transfered for 2hrs every 5 mins. How to avoid this?