It would be helpful if nc_net would accept warning and critical thresholds while running the following command:
./check_nt -s nagiospasswd -H [HOST] -v PROCSTATE -l "[Process Name]"
that would alarm if more or less than the desired process are running. I know this can be extrapolated by using the ENUMPROCESS option but currently the warn and crit options are not used with PROCSTATE checks.
What do you think?
Kyle
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good point! How should the output be? the same just with a different Return code? (then the Output message may mismatch the return code?)
Since the Service and Process Commands check can check for more than one service/process at a time, I assume the best approch should be the threshold values against the Total number of matching items?
what would example of this be,
SHould it be similar to Counters that one can check either direction by specifying C>w or w>c should it check for Less than or Greater than if only one threshold is specified?
Tony
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Instead of checking the warning and critical thresholds against the total number of processes running, I would recommend accepting comma separated thresholds for each process. To check more than one process:
Maybe the thresholds could be similar to the way the unix check_procs plugin does it.
Allow each threshold to be a range (i.e. 1:5 - there must be at least one process running by that name but not more than 5). If only one number is entered that number would be the Max (with no Minimum) allowed.
What do you think?
Kyle
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tony,
It would be helpful if nc_net would accept warning and critical thresholds while running the following command:
./check_nt -s nagiospasswd -H [HOST] -v PROCSTATE -l "[Process Name]"
that would alarm if more or less than the desired process are running. I know this can be extrapolated by using the ENUMPROCESS option but currently the warn and crit options are not used with PROCSTATE checks.
What do you think?
Kyle
Hi Kyle,
Good point! How should the output be? the same just with a different Return code? (then the Output message may mismatch the return code?)
Since the Service and Process Commands check can check for more than one service/process at a time, I assume the best approch should be the threshold values against the Total number of matching items?
what would example of this be,
SHould it be similar to Counters that one can check either direction by specifying C>w or w>c should it check for Less than or Greater than if only one threshold is specified?
Tony
Tony,
Instead of checking the warning and critical thresholds against the total number of processes running, I would recommend accepting comma separated thresholds for each process. To check more than one process:
./check_nt -s nagiospasswd -H [HOST] -v PROCSTATE -l [process1],[process2],[process3] -w [warn_process1],[warn_process2],[warn_process3] -c [crit_process1],[crit_process2],[crit_process3]
Maybe the thresholds could be similar to the way the unix check_procs plugin does it.
Allow each threshold to be a range (i.e. 1:5 - there must be at least one process running by that name but not more than 5). If only one number is entered that number would be the Max (with no Minimum) allowed.
What do you think?
Kyle