Thanks log1c, I did not, no. I didn’t find too much info on what this really does but from what I understand there are already implicit dependencies, ie if a host is down and in downtime, then the services will not all be down as they have that dependency ‘link’ to the host. Thought that would be enough so would not have to use ‘All Services’. Hitting ‘All services’ means that the services are not checked (like the host?), if it’s unticked, there will not be notifications BUT the checks carry on being checked, or attempted to be checked. Not sure about that last part but that’s how I understood it.
As a side note, selecting ‘All Services’ also puts all of the services in the overview-downtime and if you want to cancel a host being down you have to go to every single service check in the downtimes and hit the red cross for that host. It’s an ok price to pay for having all this working though, but people ‘on the floor’ had better not make mistakes as it’s a click-fest after that.
TLDR: Is the common practice to use ‘All Services’ more often than not when creating a downtime? I’m not really bothered about individual services when doing this, the use will typically be to take down a host and all of its elements in monitoring so no notifications.