sni / Thruk

Thruk is a multibackend monitoring webinterface for Naemon, Nagios, Icinga and Shinken using the Livestatus API.
http://www.thruk.org
Other
406 stars 147 forks source link

Recurring Downtime for Host and all Services #1377

Open elitretti opened 2 months ago

elitretti commented 2 months ago

Describe the bug When i try to generate a recurrent Downtime for a Host and all Services it works with some workarounds(for ex. setting a own recurrent Downtime for all Services and the Host) but when a new Service is added to that host, then this Service is not part of that Recurrent Downtime.

So as of now there is no simple or pretty solution, to set a recurrent Downtime for a Host and all Services

Thruk Version Current

To Reproduce Steps to reproduce the behavior:

  1. Go to Hosts and select Wanted host
  2. Click on hostname for Quick Commands Dialog
  3. Select "Add Downtime"
  4. Comment / Start / Enddate...
  5. Select Services: Schedule downtime for all Services
  6. Check Recurring -> Yes
  7. Then you are on the Regular Recurring Downtime dialog. With no possibility to set a Downtime for a Host and all Services with a longterm Solution.

Expected behavior A Button/API Endpoint to Set a Recurrent Downtime for Host and all Services. <3

Screenshots /

Desktop (please complete the following information):

Additional context So as of now there is no simple or pretty solution, to set a recurrent Downtime for a Host and all Services

ccztux commented 2 months ago

I agree with that. It would be nice to set recurring downtimes for a host and all its services as the gui suggests:

image

But after clicking the "submit command for x host" button, it is not possible to set a recurring downtime for the host and all of its services:

image

sni commented 2 months ago

it is usually not required to set a downtime for a host and the services since the hostdowntime includes all services already. What is the use case for this?

ccztux commented 2 months ago

Honestly speaking due to a past issue in an old nagios version, where a host downtime has not prevented service problems to be notified, our users are used to set the downtime for the host and all its services. Another more cosmetical issue with the host downtimes for me is, that i can not see this info in the extinfo.cgi?type=2&host=zet&service=ICMP with ARGS&backend=328c5 view.