Hi
My scenario I am trying to monitor
linux boxes with multiple java process. all with rmi ports open
and I have a standard template for java process, which mean i get key clash . official way to work around ..... spaces ... sigh argh yuck
Dear maintainers of zabbix
remove the port from interface and add it to the key - this will make it unique, will also make it much easier to roll this out for lots of java apps
Also ...... java gateway ... it sucks
So if one of my java apps blocks or is done java gateway says all jmx on that ip is down... thats stupid ....
I was thinking a better approach is rewrite java gateway to a jmx proxy ... so the process would keep tcp connection open
you make a request to the proxy with the key - [ port , username, password, key , interval ]
if this is the first time its seen then it setups up in its cache grabs the value and set time to get it again
second time it comes in it can feed the value back from the cache value (remember it grabs it at interval !) - maybe have a cache life value so you don't get to old value
cache - leave that up to you - thinking like the snmp bulk, better to grab lots of values at a time instead of 1 at a time
But definitely leave the connation open save time from opening connection and logging in and setting up state
Sorry haven't fleshed it out to much but should be enough to build somehting off
My scenario I am trying to monitor
linux boxes with multiple java process. all with rmi ports open
and I have a standard template for java process, which mean i get key clash . official way to work around ..... spaces ... sigh argh yuck
Dear maintainers of zabbix
remove the port from interface and add it to the key - this will make it unique, will also make it much easier to roll this out for lots of java apps
Also ...... java gateway ... it sucks
So if one of my java apps blocks or is done java gateway says all jmx on that ip is down... thats stupid ....
I was thinking a better approach is rewrite java gateway to a jmx proxy ... so the process would keep tcp connection open
you make a request to the proxy with the key - [ port , username, password, key , interval ]
if this is the first time its seen then it setups up in its cache grabs the value and set time to get it again
second time it comes in it can feed the value back from the cache value (remember it grabs it at interval !) - maybe have a cache life value so you don't get to old value
cache - leave that up to you - thinking like the snmp bulk, better to grab lots of values at a time instead of 1 at a time
But definitely leave the connation open save time from opening connection and logging in and setting up state
Sorry haven't fleshed it out to much but should be enough to build somehting off