Nagios Support Forum

Hi Team,

Can you please let us know if you have any standard templates for configuring for below basic services?

1. windows
2. linux
3. active directory
4.exchange
5. SQL
6. IIS
7. Switches
8. firewall
9. routers
10. nimble storage
11. cohesity storage
12. Oracle

All time periods were before set to 00:00-00:00 but the alert was still fired on the 25th of Dec. So I though this could be an issue with the time period configurations and added the 00:00-24:00 interval. But what is noteworthy is that we did not have this issue last year when it was set to 00:00-00...

Hi Team,

Is there a way we can extract the critical and warning thresholds for all services for each server in Nagios?

Hi Benjamin,

Yes, this was added to the exclusion.

Will PM you the profile.

Hi Team, We want to understand why the check_cpu_stats.sh plugin only has thresholds set for iowait and not cpuuser. Can you please help us to modify this so that we can set the thresholds for cpuuser as well? Attached is the plugin we are using. [root@hostname etc]# /usr/local/nagios/libexec/check_...

Hi Team, We are receiving FATAL: Could not load state! error on all DB services. This was previously discussed on case #770790 where the issue was likely recorded as related to the NDO3. However, even after we have downgraded to NDO2 DB this has reoccurred. Please suggest what we can do to fix this.

Have PM you a copy of the profile.

Hi Team, We have received false alerts over the holidays as Nagios was not excluding the public holidays. I have added this in the exclusion for time periods but it still did the check on those days. Please let me know if anything is incorrect with the timeperiod set. Timeperiod for the public holid...

Thanks for that. We did have other issues with Nagios that day. However, the output still shows incorrect even after the repair. We do not see the database repair error anymore but the load output is still incorrect. Please let me know how we can fix this. When I check for top on the server output i...

You can close this case.

This has not re occurred. Will raise a new case if this happens again.