We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12395
Created by mfriedrich on 2016-08-10 14:05:31 +00:00
Assignee: mfriedrich Status: Resolved (closed on 2016-08-10 15:20:05 +00:00) Target Version: 2.5.0 Last Update: 2016-08-10 15:20:05 +00:00 (in Redmine)
Icinga Version: 2.4.10 Backport?: Not yet backported Include in Changelog: 1
Currently all downtimes are removed once end_time is reached. If trigger_time+duration < end_time then the downtime will not be deleted
Changesets
2016-08-10 15:15:27 +00:00 by mfriedrich 8389d01
Fix flexible downtimes expiry time and removal fixes #12395
The text was updated successfully, but these errors were encountered:
Updated by mfriedrich on 2016-08-10 15:13:58 +00:00
In addition, OnDowntimeRemoved must check the following before sending a notification:
Sorry, something went wrong.
Updated by mfriedrich on 2016-08-10 15:20:05 +00:00
Applied in changeset 8389d01.
No branches or pull requests
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12395
Created by mfriedrich on 2016-08-10 14:05:31 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-08-10 15:20:05 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-10 15:20:05 +00:00 (in Redmine)
Currently all downtimes are removed once end_time is reached. If trigger_time+duration < end_time then the downtime will not be deleted
Changesets
2016-08-10 15:15:27 +00:00 by mfriedrich 8389d01
The text was updated successfully, but these errors were encountered: