just to clarify - templates are not assigned to host groups, they are linked to hosts.
not sure how would this look like - but this is basically a request to implement host group->template association

The reasoning behind this is because the hostgroups view is a little mis-leading to those that are new to the product. If I add a host to a host group, "Hosts (0)" increments. If I add a Template, then "Templates (0)" increments...however it doesn't link. When I first started using zabbix, I created host groups and added templates to them thinking that that action itself did the linking since it showed up in the hostgroup view. As I read and worked with the product more, I learned how it worked. Maybe a solution would be to not show Hosts and Templates together in Host groups but have a drop down like with user/user groups in the configuration showing the associations.

+1 for getting this feature.

I've just started using Zabbix and at present the logic is rather confusing - I would normally assume that associating a template with a host group would apply the template to all members.

In HP Operation Manager you can link template to node group (host group in Zabbix). With this feature template are automatically linked to new hosts.

+1 for getting this feature.

Sorry posted this on a duped ticket:

I don't think this is trivial. When working with large amounts of hosts it's actually a pretty big deal. It makes sense to have apache servers in the apache group linked to the apache monitoring template at the group level.

This is something I've actually been waiting for for about 5 years now. I hope you guys implement it someday soon. I love all the improvements and bug fixes but yea, this is a big one for me.

A Big Huge +1 from me! We monitor thousands of servers and services and have a nicely organized infrastructure. Assigning templates at a group level just makes sense!

As Airone already mentioned, this is how HPOM works. It through me off in the beginning as well. As far as implementation goes, the ability to designate a host group that "template assignment" group type to change it's behavior would be great. In other words, users should have the option to use a host group as either a normal "container" (as they are now) or as an auto/dynamic template-assignment group type. Being able to deal with and/or warn about loosing item history/trends data would be necessary as well.

Agreed on this.

I have about 60 hosts, which are divided into various groups. The groups match templates, as certain sets of checks are only relevant to that group.

If I could apply the template to the group it would save me (a small amount of) effort when creating a host, but also reduce the risk of user error.

I also would like to see this. Could someone address whether there is any intention on implementing this?

This is not a trivial feature.

This is pretty important to workflow and setup. I can't imagine it'd be too difficult to add a DB table for hostgroup_templates_linked (Dunno your naming convention, just an example).

Then all you need is to add a checkbox for something like:

Automatically link templates to hosts in this group, and a function call when adding a host to a group to check if that group contains linked templates to apply.

Here is nice page http://www.zabbix.com/development_services.php where on the bottom of this page is possibility to Contribute on specific feature. I think that it can be way how to promote some feature requests and to do something like crowdfunding on specific feature. Zabbix dev setup price and we can contribute on this feature I think it can be good way how to pay for each feature and to to pay whole development by one customer.

I'm new at zabbix and I know it's going to take some time for me to be able to help improving and delivering features.
But I'm pretty sure this is a show-stopper for bigger environments. It might have some workaround using automation.

I have more than 30.000 servers, and I'm studying a way to use Zabbix instead of proprietary tools...
Applying monitor templates against group of hosts is vital for our Ops.

I'll update this thread if I find any way to automate this.

You don't have to do it manually or create workaround. Zabbix already has `Auto registration` rules (https://www.zabbix.com/documentation/3.4/manual/discovery/auto_registration)

Zabbix 6.2 separated host and template groups, any objections against closing this?