Open iam333 opened 5 years ago
Hi @iam333, thanks for taking the time to make a suggestion!
I see where you're coming from. It's certainly intuitive to me that a servicegroup might have a contactgroup assigned to it for notification.
However, there are a lot of things that get configured per-service that could also be assigned per-group: check_interval/attempts, flapping/volatility, and retain_status_information also all sound like they could be reasonably configured for whole servicegroups at a time. The current solution for each of these (as well as for contacts/contactgroups) is to use service templates.
I'm not saying we won't add it, though. I'll make sure to discuss this with the team
This goes to #639 as well. Once the arbitrary separation between object types is eliminated, then anything can be set on anything and inheritance follows normal object/class inheritance rules.
Maybe my request would be a sub-case of this one: link servicegroups to hostgroups. Why should we keep linking every single service of a servicegroup to a hostgroup?
Thanks in advance!
I think it would be useful to be able to put the directive contacts/contact_groups in servicegroup/hostgroup definitions, since, being a grouping, it allows to centralize some directives like that and they should not be configured individually.
In the same way it could be done with other directives that are usually done by template or individually.
Thank you so much!