[ZBXNEXT-1338] JMXMP support Created: 2012 Jul 29 Updated: 2012 Jul 30 Resolved: 2012 Jul 30 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Java gateway (J) |
Affects Version/s: | 2.0.1 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Major |
Reporter: | Tim McCune | Assignee: | Alexei Vladishev |
Resolution: | Duplicate | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | diff jdmkrt-1.0-b02.jar jmxremote_optional-1.0.1_04.jar | ||||||||
Issue Links: |
|
Description |
Just upgraded from Zabbix 1.8 to 2.0 and was pleased to find that Java support has finally been added! However, the Java Gateway is currently hard-coded to access JMX over RMI, which is awful for firewalls and tunneling, and requires you to open up your entire RMI registry to the outside world, which isn't the most secure thing to do. I set up a JMXMP agent on my server, and patched Zabbix's Java Gateway to speak JMXMP, which is newer and better way to do remote JMX monitoring. In my patched version, I've simply replaced the RMI implementation with the JMX implementation, but a more flexible way of implementing this might be to have the Zabbix GUI let the user input the entire JMX URL. |
Comments |
Comment by richlv [ 2012 Jul 30 ] |
this does see like a dupe of |