Thank you very much for the quick fix 🥇

It's not merged yet ;)

Sorry, I was too euphoric 🙈 We are using the fix already

Hello again!

Out user also whish for a way to remove downtimes for individulal services. The usage of /icingaweb2/icingadb/downtimes/delete?host.name=<hostname> to remove them all is in some cases too much on an sledgehammer approach, where users need to remove only individual downtimes one after another.

Could you expand the functionality? Something like /icingaweb2/icingadb/downtimes/delete?service.name=<hostname>!<servicename> whould be helpful.

If I'm not mistaken, the linked pull request allows to pass any filter the comment/downtime list also accepts. If you search there for the downtimes you want to remove and use the same filter for the automation endpoint, it should affect only those you saw in the list as well.

This approach works, but unfortunately you need to know the individual guid of every single service downtime, which is hidden knowledge outside of icinga. Also I expect the guid to be ever changing.

/icingaweb2/icingadb/downtimes/delete?name=<host_name>%21<service_name>%21<individual_guid>
{"status":"success","data":[{"type":"success","message":"Removed downtime successfully"}]}

The users only know their host- and the service-names. With knowledge of the known facts alone I am unable to delete a service downtime:

/icingaweb2/icingadb/downtimes/delete?name=<host_name>%21<service_name>
{"status":"error","message":"No command targets found"}

Am I maybe doing things wrong?

Try /icingaweb2/icingadb/downtimes/delete?host.name=<host-name>&service.name=<service_name>. With any filter, I meant any filter ;)

Thank you so much for clarification!