{"id":60,"date":"2017-06-23T19:49:23","date_gmt":"2017-06-23T19:49:23","guid":{"rendered":"http:\/\/www.matez.de\/?p=60"},"modified":"2017-07-02T21:34:35","modified_gmt":"2017-07-02T21:34:35","slug":"jax-rs-codahaledropwizard-metrics-cdi-prometheus","status":"publish","type":"post","link":"https:\/\/www.matez.de\/index.php\/2017\/06\/23\/jax-rs-codahaledropwizard-metrics-cdi-prometheus\/","title":{"rendered":"Jax-RS + Codahale\/dropwizard metrics + CDI + Prometheus"},"content":{"rendered":"

I used to use dropwizard built-in metrics annotations and graphite, but now I wanted to integrate these into my javaee project exposing prometheus metrics format. The main difference between graphite and prometheus is the push or pull mentality. So instead of pushing the metrics data to the sink, they are provided via http servlet and the prometheus server is scraping them from there.<\/p>\n

There are two registry classes which we have to bring together. One is the\u00a0com.codahale.metrics.MetricRegistry which holds all codahale metrics and the other one is the\u00a0io.prometheus.client.CollectorRegistry which holds all metrics being published in the prometheus. So in our case, we will receive all metrics from our Jax-RS resource classes annotated with\u00a0com.codahale.metrics.annotation.Timed or\u00a0com.codahale.metrics.annotation.ExceptionMetered.<\/p>\n

The prometheus library contains some default Jvm metrics (DefaultExports), but I could not use them because of some sun jdk classes which do not exist in OpenJDK for example. But it is good to add these in addition to the metrics coming from our annotated Jax-RS resource classes. So this is the class<\/p>\n

\n
\n
\n \n
\n
\n \n
\n\n \n
\n\n