I started using Zabbix to test monitoring a moderately large application over JMX. My idea is to first set it up against a test environment, and then clone that to production if all seems well, however I'm wondering about two things.
- Zabbix allows attaching multiple JMX interfaces to a single host, however it does not allow using the same key for different interfaces, so if you have multiple java instances on one host you can't monitor heap size (for example) or other generic items for the separate JVM's. Do I actually have to create multiple hosts that have the same IP to achieve this?
- My plan is to create a template with the test environment, and then copy that to production environments (there can be tens of them). It seems (without testing yet) that if I want to use a separate jmx user and password in different environments, it will require either doing manual database updates to the item table or hundreds of clicks?
Is there a reason the authentication information is stored on the item level instead of the interface level, since it would probably always be the same for any JMX items under the interface? Now instead of just setting a different password for an interface I have to do it for hundreds of items...
- Zabbix allows attaching multiple JMX interfaces to a single host, however it does not allow using the same key for different interfaces, so if you have multiple java instances on one host you can't monitor heap size (for example) or other generic items for the separate JVM's. Do I actually have to create multiple hosts that have the same IP to achieve this?
Code:
UNIQUE KEY `items_1` (`hostid`,`key_`),
Is there a reason the authentication information is stored on the item level instead of the interface level, since it would probably always be the same for any JMX items under the interface? Now instead of just setting a different password for an interface I have to do it for hundreds of items...
Comment