Hello,

I have an idea because I’m frequently facing the same issue. Some templates have common items, so if you want to use two such templates on a host, you can’t, because of the error “item key already exists”. This is a problem because both templates can be useful for a host, but the error forces you to duplicate a template and remove the common item. This has happened to me several times.

Maybe in this case Zabbix could detect the duplicate item keys and disable one of them by default. Then, if we try to enable a duplicate item key on a host, a message would appear, such as “Duplicate item key: this item can’t be enabled”. That way, the templates could always be linked to the host, and the conflict would be handled at the enable/disable action instead of at link time.

This is a proposal. I don’t know all the technical implications it could have , so it may not be feasible as described. I’m open to any other solution that would solve the problem.

 

Thanks!