Hopefully someone can help here cause I'm racking my brain over this.
We have a simple agent.ping configured as an Active Item and set to trigger after nodata(30m).
In the agent log I'm seeing "active check data upload to [XXX] started to fail" and then 30 minutes later "active check data upload to [XXX] is working again". I think this is just caused by an internet issue. Doesn't seem to be server side issue as only one host has the issue at a time.
The problem is once the active checks are "working again" it seems to send some of the data from the last 30 minutes causing the problem to resolve with a negative duration.
I tried to set the recovery expression to "{template:agent.ping.sum(10m)}>17" but this still evaluates on the agent time rather than the server time.
I know I can switch to non-active checks but I'd rather not do that due to potential IP changes.
Is it normal for the agent to queue the item checks when the active connections fail? Can I change this functionality somehow?
We have a simple agent.ping configured as an Active Item and set to trigger after nodata(30m).
In the agent log I'm seeing "active check data upload to [XXX] started to fail" and then 30 minutes later "active check data upload to [XXX] is working again". I think this is just caused by an internet issue. Doesn't seem to be server side issue as only one host has the issue at a time.
The problem is once the active checks are "working again" it seems to send some of the data from the last 30 minutes causing the problem to resolve with a negative duration.
I tried to set the recovery expression to "{template:agent.ping.sum(10m)}>17" but this still evaluates on the agent time rather than the server time.
I know I can switch to non-active checks but I'd rather not do that due to potential IP changes.
Is it normal for the agent to queue the item checks when the active connections fail? Can I change this functionality somehow?