Yes, I try to build it more in a way similar to this with multiple service sets:
- Apache Default - assigned to all Apache Systems - containing default checks like service status, port 80 check, …
- Apache SSL - assigned to All Apache Systems with SSL - checks like port 443, certificate, …
- Apache FeatureA - additionally assigned to all where Feature A is used
- Apache FeatureB - additionally assigned to all where Feature B is used
- Apache ApplicationX - additionally assigned to all where Application X is used
- Apache ApplicationY - additionally assigned to all where Application Y is used
- Apache Port### - assigned where Apache runs on an additional port without a specific application
This should show the logic and is of course not a real world example, but I hope it is understandable. In some cases it is more complicated to build this logic then simply having an array and an apply for rule. But using the Director my goal is typically not the most simple but the most readable configuration.
And having a Serviceset, which has all the parts in its name a colleague or in my case a customer will likely search for, will result in him finding the set when he needs to add a service to it instead of creating a new one.