Item with key "jmx[...] already exists on ...

[jpomorski]

Hi,

I have on the server two instances of JVM and two different ports for JMX. I've added two JMX interfaces in host definition and I want to check the same parameters in the two JVM instances. It is no problem to add items for the first instance, but if I want to add them to the second instances (the same key, but different name and host interface), I get information that Item with key "jmx[...] already exists on ...

Is it possibility to add two items with the same key in the same host or I need second host for second instance?

zabbix 2.0.6

Jarek

[joseperes]

Hi,

I have on the server two instances of JVM and two different ports for JMX. I've added two JMX interfaces in host definition and I want to check the same parameters in the two JVM instances. It is no problem to add items for the first instance, but if I want to add them to the second instances (the same key, but different name and host interface), I get information that Item with key "jmx[...] already exists on ...

Is it possibility to add two items with the same key in the same host or I need second host for second instance?

zabbix 2.0.6

Jarek

I have the same issue, did you find a solution?

[markfree]

So you have 2 different JMX interfaces for your host.
You need to monitor both interfaces parameters and for that you are using the same item key, right?

According to items documentation, "the key must be unique within a single host".
If you try to repeat the key, Zabbix will give you that error.

The documentation also states that the "jmx[]" item key contains three parameters, and one of them is:

unique short description - a unique description that allows multiple JMX items with the same object name and attribute name on the host (optional)

So, if you can change some parameters for you item, I think it would be possible to use the same key.
I mean, you would have one item with jmx[parm1] and another with key jmx[parm2].

Something like this:

item for interface 1

jmx[object_name,attribute_name,<unique short description FOR INTERFACE 1>]

item for interface 2

jmx[object_name,attribute_name,<unique short description FOR INTERFACE 2>]

[markfree]

This is new to 5.4, so anything before that and you are out of luck...

That's true
I didn't notice the server was version 2.

Maybe it's possible to use Macros, one for each interface.

Or you could try upgrading the server.

[Semiadmin]

Before v5.4 was a workaround - to add a backspace (one or many) to the end of jmx key. Sometimes was up to 5 backspaces...