No TH values

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
seaward1983
Posts: 69
Joined: Wed Jul 17, 2019 2:09 pm

No TH values

Post by seaward1983 »

I suspect the answer is "no", but was wondering if "monitoring" can be set up with no threshold values set. "Why would you want to do that". We have MSSQL environment, but are just wanting performance metrics, without having threshold values set. Yes, I have notifications disabled, but still shows up in the Service Status Summary as "Critical".... which confuses the team. #PanicEnsues

I've tried just removing the values - but it errors out

check_xi_ncpa!-t 'XXXXX' -P 5693 -M memory/swap -u Gi -w 95 -c 99!!!!!!

Asking for a friend :lol:
dchurch
Posts: 858
Joined: Wed Oct 07, 2020 12:46 pm
Location: Yo mama

Re: No TH values

Post by dchurch »

Most checks accept "critical" and "warning" thresholds with lower and upper bounds in the form of [LOWER]:[UPPER]. That is, if critical=1:5, then if it's outside the range of 1-5 inclusive (for example 0 or 7), it'll consider it "critical." When UPPER is empty, it assumed it's Infinity. Likewise, if LOWER is empty, it's assumed to be 0.

Most of the time, you can disable the critical and warning by simply not specifying them. But if you're dealing with a check script that has a default critical or warning threshold if not specified, you can use the value critical=0: to disable the check from going critical.

So, to disable the critical and warning checks, just making this check informational only:

Code: Select all

check_xi_ncpa!-t 'XXXXX' -P 5693 -M memory/swap -u Gi -w 0: -c 0:!!!!!!
If you didn't get an 8% raise over the course of the pandemic, you took a pay cut.

Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
Locked