In Nagios Core, there's a pretty finite number of things that would spike httpd specifically, and it's usually the CGIs or pnp4nagios. Are you running any sort of reporting behind-the-scenes?
In Nagios XI, there's several things that could spike httpd specifically.
The JSON Query Generator might be of interest: https://labs.nagios.com/2014/06/19/exploring-the-new-json-cgis-in-nagios-core-4-0-7-part-1/ Should be included in Nagios Core by default at this point -- no need to install anything additional, just navigate to: http://<nagios server>/nagios/jsonquery.h...
Correct, you could also submit the check results passively. https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/passivechecks.html If NCPA is your weapon of choice: https://www.nagios.org/ncpa/help/2.2/passive.html Or if you're still hip to the cron idea, you could pipe those check r...
This is not possible. If it's a check being executed via a Nagios command definition, it must honor the service_check_timeout or host_check_timeout. You may consider having a separate process, orchestrated by something like cron, which is responsible for caching this data to disk somewhere periodica...
The page referenced by that plugin no longer exists, as far as I can tell. Using the WayBackMachine the last snapshot I can find was on July 9th . I suspect the plugin would need to be modified to pull either from the RSS feed , or this JSON history of incidents: https://www.google.com/appsstatus/d...
Are you sure you're using the right plugin to communicate with the right agent? 12489 is typically the NSClient++ default port. NCPA listens on 5693 by default.
There's a few checks on exchange Could you link some of them? Or better yet, the specific one you're using that recently stopped working? I get 0 results when searching "Google Workspace status dashboard" on the Nagios Exchange. It'd also be useful to see the verbose/debug output for the ...