I see it as blank. What is "it"? The Powershell script's output when executed from the Windows host? The results received by check_nt or check_nrpe interacting with the Powershell script? Your Nagios graphs? The performance RRDs? Here's the specification for performance data in Nagios plu...

Your format looks correct; Here are some sample disk checks, a few of which use the official nagios-plugins check_disk plugin: https://support.nagios.com/kb/article/disk-space-checks-770.html#disk_free_percentage In the server checked I have in the file nrpe command [check_disk] = / usr / lib64 / na...

You can try adding the -v flag to get more verbose output for what exactly check_http is doing: -v, --verbose Show details for command-line debugging (Nagios may truncate output) You can also use -e flag to instead look for that "Unrecognized username or password" message in the response b...

Nagios Core doesn't really have an authentication layer. It has some light authorization, but the actual authentication is pawned-off onto httpd. https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/cgiauth.html So if you can integrate Okta with nginx/httpd/etc, then yes it's possible...

Your NRPE user doesn't have permissions to read any of the Docker overlayfs mounts. Which is a good thing usually. If you don't want to monitor these overlayfs mounts, check_disk offers many arguments to do include/exclude logic: -p, --path=PATH, --partition=PARTITION Mount point or block device as ...

You can also ask check_http to follow 3xx redirects, give that a try if you're expecting either a 200 or 401: -f, --onredirect=<ok|warning|critical|follow|sticky|stickyport> How to handle redirected pages. sticky is like follow but stick to the specified IP address. stickyport also ensures port stay...

It depends on the form's behavior. If there's something like a POST request that is being submit to /login as the login form's action, check_http supports setting the request method and providing request data: -P, --post=STRING URL encoded http POST data -j, --method=STRING (for example: HEAD, OPTIO...

There was a recent change with MS Teams webhooks: https://office365itpros.com/2021/02/03/new-format-webhook-url/ Connectors were supposed to be updated by April 11th. Is that around the time you started noticing this problem? If so you may just need to re-generate your webhook and update your Nagios...

Here's the official documentation:
https://assets.nagios.com/downloads/nag ... ading.html

Certainly let us know if you run into any problems. Note that the process is different for packaged-based installations.

I would suggest you give the check_by_ssh plugin a try, and see if you get different results: https://nagios-plugins.org/doc/man/check_by_ssh.html That plugin is included with the standard nagios-plugins suite, and may already be sitting on your Nagios Core machine: https://github.com/nagios-plugins...