Since i have upgraded to version 4.0 i have encountered two issues;
First one is that we have a trigger to notify us when a host is offline;
Windows OS:agent.ping.nodata(2m)}=1
This worked perfectly fine in 3.4, however whe have some hosts that go into maintenance during the night until 10:15 am. Once they come out of maintenance this trigger fires and notifies us that they are all down, then within a min or so they all report in and show as online.
In the previous version, they would come out of maintenance then report into the server fine before the trigger fired.
Am i missing something?
The second issue we have is that now two hosts will not report in correctly, they are online but showing as down.
When i look in the queue the hosts are there showing a time delay which just keeps increasing. I cannot see any performance issues and all pollers etc are working as expected.
Anyone else come across this before?
First one is that we have a trigger to notify us when a host is offline;
Windows OS:agent.ping.nodata(2m)}=1
This worked perfectly fine in 3.4, however whe have some hosts that go into maintenance during the night until 10:15 am. Once they come out of maintenance this trigger fires and notifies us that they are all down, then within a min or so they all report in and show as online.
In the previous version, they would come out of maintenance then report into the server fine before the trigger fired.
Am i missing something?
The second issue we have is that now two hosts will not report in correctly, they are online but showing as down.
When i look in the queue the hosts are there showing a time delay which just keeps increasing. I cannot see any performance issues and all pollers etc are working as expected.
Anyone else come across this before?