package prometheus
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=e2894de14ab9f9a095b1359581d84094123a1214f76e1563f7ce5a16c69c6ac5
sha512=6a4d81fef6514400ecf7e16a9871db0aba83a8cd52deaaaa3d07517ecbb460a638684326fc1087c4a57dfd830a609ae7486b69a9f77d07ab5e0eada663191228
Description
To run services reliably, it is useful if they can report various metrics (for example, heap size, queue lengths, number of warnings logged, etc).
A monitoring service can be configured to collect this data regularly. The data can be graphed to help understand the performance of the service over time, or to help debug problems quickly. It can also be used to send alerts if a service is down or behaving poorly.
Published: 03 Mar 2020
README
OCaml client library for Prometheus monitoring
To run services reliably, it is useful if they can report various metrics (for example, heap size, queue lengths, number of warnings logged, etc).
A monitoring service can be configured to collect this data regularly. The data can be graphed to help understand the performance of the service over time, or to help debug problems quickly. It can also be used to send alerts if a service is down or behaving poorly.
This repository contains code to report metrics to a Prometheus monitoring server.
Use by libraries
Library authors should define a set of metrics that may be useful. For example, the DataKitCI cache module defines several metrics like this:
module Metrics = struct
open Prometheus
let namespace = "DataKitCI"
let subsystem = "cache"
let builds_started_total =
let help = "Total number of builds started" in
Counter.v_label ~help ~label_name:"name" ~namespace ~subsystem "builds_started_total"
let builds_succeeded_total =
let help = "Total number of builds that succeeded" in
Counter.v_label ~help ~label_name:"name" ~namespace ~subsystem "builds_succeeded_total"
let builds_failed_total =
let help = "Total number of builds that failed" in
Counter.v_label ~help ~label_name:"name" ~namespace ~subsystem "builds_failed_total"
[...]
end
Each of these metrics has a name
label, which allows the reports to be further broken down by the type of thing being built.
When (for example) a build succeeds, the CI does:
Prometheus.Counter.inc_one (Metrics.builds_succeeded_total build_type)
Use by applications
Applications can enable metric reporting using the prometheus-app
opam package. This depends on cohttp and can serve the metrics collected above over HTTP.
The prometheus-app.unix
ocamlfind library provides the Prometheus_unix
module, which includes a cmdliner option and pre-configured web-server. See the examples/example.ml
program for an example, which can be run as:
$ dune exec -- examples/example.exe --listen-prometheus=9090
If run with the option --listen-prometheus=9090, this program serves metrics at
http://localhost:9090/metrics
Tick!
Tick!
...
Unikernels can use Prometheus_app
instead of Prometheus_unix
to avoid the Unix
dependency.
API docs
Generated API documentation is available at https://mirage.github.io/prometheus/.
Licensing
This code is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.
Dev Dependencies (1)
-
alcotest
with-test
Used by (15)
- capnp-rpc-net
- current
-
current_examples
>= "0.4"
-
current_github
>= "0.4"
- current_gitlab
-
current_ocluster
< "0.2"
-
current_web
>= "0.4"
-
datakit-server
>= "0.10.0" & < "0.11.0"
-
ocluster
!= "0.2"
-
prometheus-app
= "0.7"
-
protocol-9p-unix
>= "0.11.0"
-
qcow
>= "0.10.0"
-
tezos-p2p
= "13.0"
-
tezos-shell
= "13.0"
-
tezos-store
= "13.0"
Conflicts
None