Prometheus middleware for actix-web

Build Status docs.rs crates.io

Prometheus instrumentation for actix-web. This middleware is heavily influenced by the work in sd2k/rocket_prometheus. We track the same default metrics and allow for adding user defined metrics.

By default two metrics are tracked (this assumes the namespace actix_web_prom):

Usage

First add actix_web_prom to your Cargo.toml:

toml [dependencies] actix_web_prom = "0.1"

You then instantiate the prometheus middleware and pass it to .wrap():

```rust use actixweb::{web, App, HttpResponse, HttpServer}; use actixweb_prom::PrometheusMetrics;

fn health() -> HttpResponse { HttpResponse::Ok().finish() }

fn main() -> std::io::Result<()> { let prometheus = PrometheusMetrics::new("api", "/metrics"); HttpServer::new(move || { App::new() .wrap(prometheus.clone()) .service(web::resource("/health").to(health)) }) .bind("127.0.0.1:8080")? .run(); Ok(()) } ```

Using the above as an example, a few things are worth mentioning: - api is the metrics namespace - /metrics will be auto exposed (GET requests only)

A call to the /metrics endpoint will expose your metrics:

```shell $ curl http://localhost:8080/metrics

HELP apihttprequestsdurationseconds HTTP request duration in seconds for all requests

TYPE apihttprequestsdurationseconds histogram

apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="0.005"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="0.01"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="0.025"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="0.05"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="0.1"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="0.25"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="0.5"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="1"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="2.5"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="5"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="10"} 1 apihttprequestsdurationsecondsbucket{endpoint="/metrics",method="GET",status="200",le="+Inf"} 1 apihttprequestsdurationsecondssum{endpoint="/metrics",method="GET",status="200"} 0.00003 apihttprequestsdurationsecondscount{endpoint="/metrics",method="GET",status="200"} 1

HELP apihttprequests_total Total number of HTTP requests

TYPE apihttprequests_total counter

apihttprequests_total{endpoint="/metrics",method="GET",status="200"} 1 ```

Custom metrics

You instantiate PrometheusMetrics and then use its .registry to register your custom metric (in this case, we use a IntCounterVec.

Then you can pass this counter through .data() to have it available within the resource responder.

```rust use actixweb::{web, App, HttpResponse, HttpServer}; use actixweb_prom::PrometheusMetrics; use prometheus::IntCounterVec;

fn health(counter: web::Data) -> HttpResponse { counter.withlabelvalues(&["endpoint", "method", "status"]).inc(); HttpResponse::Ok().finish() }

fn main() -> std::io::Result<()> { let prometheus = PrometheusMetrics::new("api", "/metrics");

let counter_opts = opts!("counter", "some random counter").namespace("api");
let counter = IntCounterVec::new(counter_opts, &["endpoint", "method", "status"]).unwrap();
prometheus
    .registry
    .register(Box::new(counter.clone()))
    .unwrap();

HttpServer::new(move || {
    App::new()
        .wrap(prometheus.clone())
        .data(counter.clone())
        .service(web::resource("/health").to(health))
})
.bind("127.0.0.1:8080")?
.run();
Ok(())

} ```