Feature request/proposal: Downtime until OK/UP

[log1-c]

I'd like to propose a new feature for downtimes (or a new type of downtime):
The possibility to define a downtime that stays as long the host/service is in a problem state and automatically gets removed when it switches to UP/OK.

Our use case for this would be the following:
Currently we have hundreds of virtual desktop servers (terminal servers) that automatically scale (get shut down/booted up) based on the number of sessions needed.
As they always stay in the monitoring, we need to set downtimes when they shut down. This is done via a shutdown script on the host against the Icinga 2 API.
On boot the inverse happens. The downtimes need to be removed. This is another script, getting the downtimes (only those created by the shutdown script), triggering all checks (to get them into an OK state to prevent false-positive notifications on old states) and then remove the downtime objects.

With this feature the startup script and its API calls would become obsolete. And I could imagine that there are other use cases as well :)

[oxzi]

Thanks for proposing this. Thus, you want a more Acknowledgement-like behavior for Downtimes?

[log1-c]

Thus, you want a more Acknowledgement-like behavior for Downtimes?

Yes, that's a good way to put it 👍

[Al2Klimov]

What about allowing ack-ing before the problem happens instead?

[log1-c]

Acknowledging a not yet existing problem seems strange to me.

I would want something like a "check box" (similar to the "All services" one) with
⟦ ⟧"Remove downtime on recovery" ℹ️ This downtime will be removed once the host or service it relates to has recovered to an UP/OK state

This (imo) would also mean to not remove service downtimes created via "All services" switch on host recovery but only when the service itself recovered.