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
When I acknowledge a service in a warning or critical state with an expire time via the webinterface, the acknowledged status is not removed after the expire time. Although the history tab of the service in the webinterface says “ACKNOWLEDGEMENT REMOVED”, the service is still acknowledged.
To Reproduce
Acknowledge a service check in warning or ciritcal state and enable "Use Expire Time"
Acknowledgement is not removed after the timestamp has expired
Expected behavior
In my opinion the acknowledgement should be removed and displayed as a critical service state, but this is not happening. Is this a bug?
Screenshots
Your Environment
Include as many relevant details about the environment you experienced the problem in
How does your service configuration look like? Do you have a huge check_interval configured or are active checks enabled at all for that service? The acknowledgement gets removed with the next check, but that may never happen if the service is not actively checked.
hi @yhabteab, thanks for your quick response. This issues applies to all services and hosts check, so I dont think it is a service specific issue. The check interval for this specific check is 60 minutes. But even when I do a manual recheck, the acknowledgement is not removed from the check. Only when the service state recovers to an OK state, the acknowledgement is removed.
Result after manual recheck and configuration overview:
When I acknowledge a service in a warning or critical state with an expire time via the webinterface, the acknowledged status is not removed after the expire time. Although the history tab of the service in the webinterface says “ACKNOWLEDGEMENT REMOVED”, the service is still acknowledged.
To Reproduce
Expected behavior
In my opinion the acknowledgement should be removed and displayed as a critical service state, but this is not happening. Is this a bug?
Screenshots
Your Environment
Include as many relevant details about the environment you experienced the problem in
Additional context
A scheduled downtime with an expire time works as expected. The dowtime state is removed from the service when the expire time expires
The text was updated successfully, but these errors were encountered: