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
Updated by mfriedrich on 2016-12-09 10:31:07 +00:00
History views and sla reports should take the "was_cancelled" column into account. That one is updated too. The actual_end_time is updated in Icinga 1.x and so does Icinga 2 to behave the same. Icinga Web 2 doesn't take "was_cancelled" into account currently as far as I can see.
In terms of sending a downtimeend notification - this has been sitting there by design, since the downtime is removed. There's no such different notification flag for cancelled downtimes (yet). Probably we should change that, but I'd like to discuss this with Eric and Gunnar first (which means not something for 2.6).
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13489
Created by mfrosch on 2016-12-08 15:50:53 +00:00
Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-12-09 10:31:07 +00:00 (in Redmine)
In addition to #12549
When I cancel a downtime that starts in the future, a DOWNTIMEEND notification is send.
Also not sure if the actual dates should be filled for a downtime that never started:
Relations:
The text was updated successfully, but these errors were encountered: