Hi there,
Just wondering how people have set up their JMX monitoring? Currently we just zabbix-jmx-gateway to connect to the mbeans and return the information. If there is any kind of error though it seems to just error out and stop processing all JMX on that particular server for 15secs. Is there some way you can disable it from stopping processing?
I have come up with another method of JMX monitoring that seems a lot more stable and was comsidering implenting it - essentially I confgure an item to run an external script which sends the bean and parameter to a commandline java rmi client then returns the value directly to zabbix (bypassing the JMX gateway). Is anybody else doing something similar? Anyone see any reason not to do this?
Thanks,
Belinda
Just wondering how people have set up their JMX monitoring? Currently we just zabbix-jmx-gateway to connect to the mbeans and return the information. If there is any kind of error though it seems to just error out and stop processing all JMX on that particular server for 15secs. Is there some way you can disable it from stopping processing?
I have come up with another method of JMX monitoring that seems a lot more stable and was comsidering implenting it - essentially I confgure an item to run an external script which sends the bean and parameter to a commandline java rmi client then returns the value directly to zabbix (bypassing the JMX gateway). Is anybody else doing something similar? Anyone see any reason not to do this?
Thanks,
Belinda