Error in Elasticsearch discovery rule

[VN1977]

The error is

Cannot create item: item with the same key "elasticsearch.node_stats.jvm.buffer_polls.count.[{#JVMBUFFERSPOOLS}]" already exists

How to correct it?

[VN1977]

[akitsul]

Hi,

please check the items of this host, is there any discovery items found there?

[VN1977]

Yes, there are some items.
But my items have type Zabbix aggregate and yours are Zabbix trapper. Why?

[akitsul]

Hello,
this is normal.

What does not work?

[VN1977]

Hi!
Everything works OK. But my question was about only error in discovery rule. What's wrong with it? Why do we have such an error?
As I can see this rule tries to create an item with key elasticsearch.node_stats.jvm.buffer_polls.count[{#JVMBUFFERSPOOLS}] but the item with the same key already exist.
I used zabbix_get to check the discovery rule.
zabbix_get -s IP -k elasticsearch.discovery[Elasticsearch_cluster_1]
The answer is
{"data":[{"{#GROUPNAME}":"Elasticsearch_cluster_1"},{"{#JVMGCCOLLECTORS}":"old"},{"{#JVMGCCOLLECTORS}":"young"},{"{#JVMBUFFERSPOOLS}":"direct"},{"{#JVMBUFFERSPOOLS}":"mapped"},.........
So this discovery rule works as expected but why Zabbix tries to create new items and only for prototype Template App Elasticsearch Service: JVM buffer pools {#JVMBUFFERSPOOLS} count again and again?
I don't like if something works with errors so I try to get rid of any of them.

[dmitry-sobol]

I have the same error:

[akitsul]

@dmitry-sobol
Hello, this is normal.

What does not work?

[breisig]

It's not working me either.

[aguzmans]

I have the same problem with a customized mysql Discovery:

root@ubuntu-bionic:/home/zabbix# zabbix_agentd -t docker.container.service[con_nc_test_abel_mysql7,mysqld] -c /etc/zabbix/instances/con_nc_test_abel_mysql7/zabbix_agentd.conf docker.container.service[con_nc_test_abel_mysql7,mysqld] [t|{ "data":[ { "{#SERVICENAME}":"mysqld" } ] }] root@ubuntu-bionic:/home/zabbix#

That is the discovery working from the agent perspective. I have my agent in Active mode. The web interface of zabbix says on this discovery template item:
Cannot create item: item with the same key "docker.container.mysql_realtime[{HOST.HOST},innodb_buffer_pool_pages_dirty]" already exists. Cannot create item: item with the same key "docker.container.mysql_realtime[{HOST.HOST},innodb_buffer_pool_pages_total]" already exists. (...)
Then the items are not added to my discovery mysql. Where do those items already exist? I do not understand.

[Pakbon]

Same problem here with a custom LLD script. With the exception that it still adds those keys and successfully monitors the values of the keys .
Cannot create item: item with the same key "solr.online[{#SOLRPORT6}]" already exists.
Cannot create item: item with the same key "solr.online[{#SOLRPORT}]" already exists.

[Olodain]

When I try to make , I have an error. Could you please help me for this? Im newbie.

cd /root/zabbix-agent-extension-elasticsearch/.gopath/src/zabbix-agent-extension-elasticsearch;
GOPATH=/root/zabbix-agent-extension-elasticsearch/.gopath
dep ensure -v
/bin/sh: 2: dep: not found
Makefile:40: recipe for target 'deps' failed
make: *** [deps] Error 127

[geryjuhasz]

When I try to make , I have an error. Could you please help me for this? Im newbie.

cd /root/zabbix-agent-extension-elasticsearch/.gopath/src/zabbix-agent-extension-elasticsearch;
GOPATH=/root/zabbix-agent-extension-elasticsearch/.gopath
dep ensure -v
/bin/sh: 2: dep: not found
Makefile:40: recipe for target 'deps' failed
make: *** [deps] Error 127

will be fixed with:

apt install go-dep