You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With NSClient++ you could create internal schedulers.
This seems to currently be missing from snclient.
When running a passive setup where the agent has an internal schedule and pushes the results to a naemon/nagios that uses freshness on the configured checks/services support for some internal scheduler would be amazing!
Extra points if it works with the current nsclient++ config 👍
The text was updated successfully, but these errors were encountered:
I was able to script around this and create an active/passive environment that used a single active command to execute an external script and receive the passive data via NRDP more akin to an echo than a scheduled broadcast of a passive signal.
Pulling the Powershell from the wrapper you can see it's creating a payload and then forwarding the data to NRDP. With this scenario you can still enable and configure freshness checks on your deployed passive services as they function no different in NagiosXI than before.
One added benefit is that you gain the ability to set the requesting service as the parent of all the passive services deployed so when you have an issue or situational outage your monitoring engine can help absorb some of the alert storm without putting added pressure on your upstream notification systems.
With NSClient++ you could create internal schedulers.
This seems to currently be missing from snclient.
When running a passive setup where the agent has an internal schedule and pushes the results to a naemon/nagios that uses freshness on the configured checks/services support for some internal scheduler would be amazing!
Extra points if it works with the current nsclient++ config 👍
The text was updated successfully, but these errors were encountered: