I think the -l parameter of the USEDDISKSPACE module for check_nt is what you need. From the help info: http://nagios-plugins.org/doc/man/check_nt.html USEDDISKSPACE = Size and percentage of disk use. Request a -l parameter containing the drive letter only. Warning and critical thresholds can be spe...

Nagios Core does not have a dependency on MySQL/MariaDB. Nagios XI does, but you mentioned using Nagios Core here. If you're using something like NagiosQL /NConf/Lilac or another configuration management utility, which may have a dependencies on MySQL/MariaDB, it'd probably be best to inquire with t...

What is the source of truth for the dynamic value? Nagios Core offers some "standard" and "custom" macros you can use in your object definitions, but they may not be a good fit for your use case: https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/macrolist.html h...

I get a 404 on the documentation you linked, so it's hard to offer insight there. Best I can do is speculate at this point. I assume 192.168.1.120 is the WIndows Server 2012 R2 host? What sort of NRPE server is provided on the Windows host? I assume you're using NSClient++, in which case the NSClien...

Could you describe how you went about configuring Nagios Core to accept SNMP traps? The specifics are relevant to the answer. Presumably you're doing some translation of those traps into Nagios Core check results. Most people are using NSTI for this. I suspect this is your problem: Passive check res...

I read this as an exclusive or : Please either specify specify system type (-T) OR base SNMP OIDs for name (-N) and data (-D) tables OR exact list of sensor names (-n) and data OIDs (-d) ! And the code verifies this behavior: https://github.com/willixix/WL-NagiosPlugins/blob/master/check_snmp_temper...

I configured an host alert to check host alive each 2 minutes Check Interval 2 min Retry Check 1 min Max Check Attempts 3 I think this would have Nagios dispatch an alert no greater than 4 minutes from initially detecting the problem, assuming the problem didn't start until immediately after the la...

The check_http plugin works with HTTPS: http://nagios-plugins.org/doc/man/check_http.html -S, --ssl=VERSION[+] Connect via SSL. Port defaults to 443. VERSION is optional, and prevents auto-negotiation (2 = SSLv2, 3 = SSLv3, 1 = TLSv1, 1.1 = TLSv1.1, 1.2 = TLSv1.2). With a '+' suffix, newer versions ...

Anyone know if this is a bug or of a workaround? I gather you're running NRPE on this CentOS 7 server, and executing the check from your Nagios Core machine (on the Debian 10 server) by leveraging the check_nrpe plugin? Or are you executing the check_tcp plugin directly from the Nagios Core server ...

I don't know much about EyesOfNetwork, and how it handles Nagios Plugin outputs. A lot of what is below assumes you're configuring checks in Nagios Core. The first thing to understand is the difference between service checks and host checks: https://assets.nagios.com/downloads/nagioscore/docs/nagios...