[ZBXNEXT-4510] allow 3rd parameter in Java gateway item keys Created: 2018 Apr 17  Updated: 2019 Oct 28  Resolved: 2018 Apr 18

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Java gateway (J)
Affects Version/s: None
Fix Version/s: None

Type: Change Request Priority: Major
Reporter: Oleksii Zagorskyi Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: flexibility, javagateway, key, validation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate

 Description   

Java gateway item key validation currently accepts strictly 2 item key parameters.

Zabbix 3.4 added JMX discovery, which is a great feature - but currently it is not possible to use this feature to discover multiple JVMs on a host.
Consider a solution that knows about the JMX ports and can send a JSON to a Zabbix LLD rule. While a different port can be used in the JMX endpoint field, it all breaks in the item prototypes - an item cannot be created for multiple JVMs as the item key would be the same.

There is a very simple solution - accept 2 or 3 item key parameters. With a one-line change, Zabbix JMX functionality becomes much more powerful.

While we have it hacked in our gateway already and it is working great, it would be a useful feature for other users, and having it upstream would remove the need for us to patch that one line.

 Comments   
Comment by Alexander Vladishev [ 2018 Apr 18 ]

It looks like a hack and will cause potential problems if in the future there will be a real 2nd or 3rd parameter for these keys - the upgrade patch will be very complicated because item keys can be used in macros {host.key.func()}.

Comment by richlv [ 2019 Oct 28 ]

ZBXNEXT-1983 might be a more universal solution.

Generated at Sat Apr 20 06:09:06 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.