Close obsolete Icinga Notifications incidents

[nilmerg]

Icinga DB currently does not close incidents if the associated object is no longer available. It is already possible to retrieve open incidents via the API. When establishing a connection, Icinga DB must use this endpoint to close obsolete incidents. If possible, the incident statuses should be synchronized with the corresponding object statuses at the same time.

[bmtwl]

Hello, is there a timeline for this fix? Its critical for our adoption of the notifications module.
I see it on the backlog as To-do under "Iteration 5", but I'm not sure what that means.

[nilmerg]

Hi, there is no timeline. Icinga Notifications is currently reworked a lot and this is just a single to do on the list.

Iteration 5 means it will be implemented in the coming 2-6 weeks. The release is not scheduled.

[yhabteab]

I've created an issue in Icinga 2 to include the missing host and service names in the runtime deletion events as it currently sends only the object ID, which is not enough to map it to the respective incident in Icinga Notifications. This is a reminder for future me or someone else working on this issue!