On Tue, Jul 15, 2014 at 9:11 AM, Garrett Barton <[EMAIL PROTECTED]>
My vote is to look them up via thrift (and cache as needed).  The config
value is "blur.http.status.running.port" and can be retrieved by calling
getConfiguration() on the given process.  We could likely build a nice
little java object that would cache things as needed and make the results
available via a thrift admin call.


NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB