Kinda depends on the setup, but you're usually re-deploying or re-configuring the particular agent. With a less secure setup you might be able to just hit it with check_nrpe / check_ncpa (if the token is known) without any additional reconfiguration. and how many can you do per day? If you're using ...

You might try ^(a-).* instead.

Simply put: https://docs.oracle.com/javase/7/docs/api/javax/management/InstanceNotFoundException.html The specified MBean does not exist in the repository. You're asking for an MBean VisServerManager872 that doesn't exist in the repository located at service:jmx:rmi:///jndi/rmi://ch00sa120:1099/jmxr...

Tough to provide much insight without a detailed understanding of the VisServerManager872 object structure. This plugin does have a -v argument which should provide you with better debugging output: -v[vvv] verbatim level controlled as a number of v (optional) Might try -vvvv and see if it provides ...

Looks like this plugin has an exclude argument baked-in: https://bitbucket.org/jetole/mssql-job-history/src/2c4fcd2d1571dfb779427c8f05c52a76dae7dcdc/check_mssql_job_history.py#lines-67 parser.add_argument("-x", "--exclude", action="store", help="A comma seperated l...

Where did you get this plugin from? Can you provide a URL or the raw script itself?

InfluxDB 2.0+ has a default username+password I believe: https://docs.influxdata.com/influxdb/v2.0/reference/release-notes/influxdb/#bug-fixes-4 Require user to set password during initial user onboarding. https://docs.influxdata.com/influxdb/v2.0/users/change-password/ If you're set on using Influx...

You're using the script provided by the vendor I assume?
https://www.hw-group.com/support/how-to ... wg-sms-gw3

Try passing -v for verbose instead of -q for quiet, that might provide some hints.

I know nothing about this plugin or the hardware it's meant for, but I think --blacklist is the way to do this. See the "Blacklisting" section of the documentation:
https://labs.consol.de/nagios/check_hpasm/index.html

Perhaps something like this:

Code: Select all

--blacklist daacb

Nagios XI has a concept of scheduled reports, but I don't know of anything like this that would exist in the Nagios Core ecosystem.

I'm sure with some clever scripting you could hit avail.cgi with some parameters on a cron job and pipe the output into an email.