New more configurable version of JMX exporter, using simpleclient.

It supports:
- Scraping the local jvm
- Scraping a remote jvm
- The existing output format by default (mostly, escaping is a bit safer, and it doesn't assume 'type' is the first beanProperty)
- Customising the name, help and labels as needed
- Exporting only what you want (only whitelist right now, blacklist would be easy to add)
- The java simpleclient

A config of 
  { "hostpost": "localhost:1234",
    "rules": [
      {"^java"}
    ]}
would export everything under java, with the default (i.e. existing) format.



I haven't written tests or the servlet bit yet, but wanted to get initial feedback on the approach.
It also puts out a metric per sample too rather than combining metrics with the same name, which isn't correct.
On 15 December 2014 at 10:46, Björn Rabenstein <notifications@github.com>
wrote:

> In pom.xml
> <https://github.com/prometheus/jmx_exporter/pull/4#discussion-diff-21816440>
> :
>
> > @@ -5,7 +5,7 @@
> >    <groupId>com.prometheus.jmx4prometheus</groupId>
> >    <artifactId>jmx4prometheus</artifactId>
> >    <packaging>jar</packaging>
> > -  <version>0.2</version>
> > +  <version>0.3</version>
> >    <name>jmx4prometheus</name>
>
> Hmmm, so far, as far as I have seen, in Prometheus lingo, an "exporter" is
> a stand-alone binary that exports something as Prometheus metrics, while a
> "collector" is an interface within a client library to collect metrics. I
> would like to avoid mixing those two up. node_exporter exports node
> attributes, haproxy_exporter exports haproxy metrics, so jmx_exporter
> exporting JMX metrics as Prometheus metrics doesn't sound terribly off...
>
What would you call something that exports metrics to JMX?

Brian



> —
> Reply to this email directly or view it on GitHub
> <https://github.com/prometheus/jmx_exporter/pull/4/files#r21816440>.
>