Then, i do want to get notifications only if both of the Hosts are down. check_multi, or BPI, are your free options: https://support.nagios.com/forum/viewtopic.php?f=7&t=63083&p=333311 You'd create a check_multi definition for your 2 host's check commands (probably check_ping as it stands?)...

Which version of Nagios XI? Might be related to #582 / #484.

For the standard Nagios Core event handlers, I think you'd need to create separate "email" and "sms" contact (or contactgroup ) definitions and selectively assign them to the service/host objects you wish to receive either email/sms notifications on. You could also have separate ...

Depending on your NSClient++ version, the CheckEventLog module may be an option:
https://docs.nsclient.org/reference/win ... kEventLog/
https://support.nagios.com/kb/article/l ... s-787.html

Depending on the firewall in-use on the 172.18.1.91 machine, telnet may not be enough to test that the port is truly open and that the check_jmx traffic is not being filtered out by the firewall. Might try nmap or netcat instead. Both are great tools to have on your Nagios server for troubleshooting...

NDO uses MyISAM for the storage engine. Looks like this table (and potentially others) got flipped to InnoDB, when it should be using MyISAM. ALTER TABLE my_table ENGINE = MyISAM; Definitely don't alter the database tables while Nagios XI / NDOUtils is "doing stuff". The configured service...

check_multi is one option. Else something like BPI but the community edition is pretty long-in-the-tooth.

With check_multi I think you'd just disable notifications for all of your services under the host, except for the check_multi service check.

You could try using NCPA instead: https://www.nagios.org/ncpa/help.php#api-modules-logs The last NSClient++ release was over 3 years ago. IIRC not all the operators were supported for check_eventlog but I haven't looked at the code in ages. There may be other supported filters you can use to address...

NSClient offers you a few options with your expressions: https://docs.nsclient.org/checks/#expressions I think it'd be as simple as: check_eventlog "filter=id not in (24)" Or something like this if you're OK dealing with double/tripple-escaping reserved characters like ! check_eventlog &qu...

Think you're going to need to write a script for this. There's nothing native to Nagios that would do this to my knowledge. Is there alternative way to have each unique login logged in the nagios.log when a service is disabled or anything done with the service? log_external_commands can be set withi...