lookfirst/jmxtrans — Issue #17: issues running with >200 jmx targets
Author: kmcminn
Created: 2012-03-06 19:43:18+00:00
State: open

Have 205 json config files with identical layouts based using common queries such as heap, memory and threads. Noticing jmxtrans is using 263 threads to get the job done (ps -eLo, ps -p -T) and send the metrics to graphite. Using one host per json file. Is there a more efficient way to query or setup the config for more efficiency?