ZBXNEXT-1757 might be about the same original issue

check also ZBX-7569

Considering that I have 7 JMX instances that are running on a single host, this limitation is huge.

The problem applies for an huge number of cases: monitoring multiple HTTP ports on the same machine, multiple JMX instances, ....

This limitation kills the JMX use case for hadoop clusters, which typically have many jvms per node.

While we're thinking about JMX on multiple interfaces, it is typical for one set of keys to be common to all JVMs (heap size, etc), while others are application-specific counters that exist only in some interfaces.

Hopefully a solution will include an answer for how to either select which interfaces to query, or a way to gracefully ignore when the keys are absent.

Finally, the killer feature for the hadoop use case would be the ability to define such an item within a template. I have dozens of mapreduce nodes that all run jvms..

phs, the assigning could be easily done with ZBXNEXT-735#comment-83047.
In case item key uniqueness criteria is additionally made up of host interface (resp. alias on template level), then one might possibly do something like this:

Templates
A common JVM template is linked into application specific templates:
Template 'Common JVM' is linked into template 'Java App Foo'
Template 'Common JVM' is linked into template 'Java App Bar'

Items in template 'Common JVM' have no host interface alias/hint/label set.
All items (incl. linked/templated) in template 'Java App Foo' have a host interface alias 'FooApp' set.
All items (incl. linked/templated) in template 'Java App Bar' have a host interface alias 'BarApp' set.

Host
A host jboss.example.com has two JVM host interfaces:
JMX host interface 1 has an interface alias/hint/label 'FooApp' set.
JMX host interface 2 has an interface alias/hint/label 'BarApp' set.

Since uniqueness criteria takes host interface or host interface alias into account, one may link both application specific templates into the same host.
Proper host interfaces for items are selected based on interface aliases/labels/hints.

ZBXNEXT-1049 is remotely similar

general item-interface linkage covered in ZBXNEXT-735 , this issue seems to be specifically about snmp traps - suggested to update the summary

ZBXNEXT-3872 may help a bit here.

Hi, I guess the problem is because the "KEY of the element" is a "primary key" in the zabbix database.
My question is ... Why is the "primary key" in the database a "KEY in an element", and not a simple and unique identifier? For example, an autoincremental.

I'm sorry if my question is stupid or something else.

Hi everyone.

I think that's an excellent question...

I also need to monitor more than one IP per host...