Passive Host Check

[onegative]

G 'Day Nagios Support,

So I need help trying to create a workaround for an environment in which I have absolutely no access to due to a major overlap of a private subnet. The hosts in that subnet can successfully direct passive checks to our F5 vip which is the front-end to our Nagios XI environment. The problem I have is trying to utilize custom check where I query the Last Check value to determine if my __HOST__ host check is updating the host within Nagios. Seems like when the host check exceeds the time differential for whatever reason (most likely freshness) fires the dummy command (xiwizard_passive_host) and updates the Last Check value and of course clears the event.

I am open to any ideas...trying to get a tool server in that environment is an option but not immediately and I would really like a way to really make a Passive Host Check work...maybe I am just missing something and just need a nudge.

Any and all help greatly appreciated.
Thanks,
Danny
@onegative

[ssax]

The problem I have is trying to utilize custom check where I query the Last Check value to determine if my __HOST__ host check is updating the host within Nagios

How specifically are you doing this?

If the freshness threshold is exceeded there's no way to stop it from doing that without disabling/or increasing the freshness thresholds or creating your own check command that freshness will run that does/checks for something else.

[onegative]

So after chasing other rabbit holes...I finally figured out that our problem...basically we used the API to pull the hoststatus and needed to read the last_check parameter but the person who wrote the python code used status_update_timeinstead which after the service alert would update the value thus clearing the alert. So once I determined this wrong parameter query and pointed to last_check parameter it started working as expected.

You can close this thread and thanks,
Danny

[scottwilkerson]

So after chasing other rabbit holes...I finally figured out that our problem...basically we used the API to pull the hoststatus and needed to read the last_check parameter but the person who wrote the python code used status_update_timeinstead which after the service alert would update the value thus clearing the alert. So once I determined this wrong parameter query and pointed to last_check parameter it started working as expected.

You can close this thread and thanks,
Danny

Locking thread