[ZBX-16298] JMX, Solution for problem with same KEY in the same host, is optimal? Created: 2019 Jun 25 Updated: 2019 Jun 26 Resolved: 2019 Jun 26 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Java gateway (J), Server (S) |
Affects Version/s: | 4.0.9 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Minor |
Reporter: | Sistemes | Assignee: | Aleksandrs Petrovs-Gavrilovs |
Resolution: | Duplicate | Votes: | 0 |
Labels: | items, usability | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Linux zabbixeqt 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16) x86_64 GNU/Linux description: Space-saving Computer |
Issue Links: |
|
Description |
Hello, I'm sorry but I do not know how to categorize this ... We need to know that the solution is safe in the short and medium time, thank you. (we resume below) In summary, we have many Java services in the same virtual machine, and each of these Java services has independent endpoints to monitor with JMX, but we need to monitor the same KEYS ... The problem is that Zabbix does not accept more than one KEY on the same host, and we found a solution for this, but ... Of course, I do not understand exactly why this works, but my fears are that in the future, zabbix will be updated and ... Is posible this will stop working. Thank you |
Comments |
Comment by richlv [ 2019 Jun 25 ] |
ZBXNEXT-1490 asks for a proper solution. |
Comment by Aleksandrs Petrovs-Gavrilovs [ 2019 Jun 26 ] |
Hello sistemes, The ZBXNEXT's mentioned by richlv are indeed either similar or either connected to your issue, so i would strongly recommend voting for at least ZBXNEXT-1490, as it very close and asks for a proper solution. Others two could be quite useful while seeking for available solutions, so i would recommend also following them. At the moment I will be closing the issue as a duplicate of ZBXNEXT-1490. Best Regards, |