prom-client
prom-client copied to clipboard
Prometheus client for node.js
> The `eventLoopUtilization()` method returns an object that contains the cumulative duration of time the event loop has been both **idle** and **active** as a high-resolution milliseconds timer. With the...
const { collectDefaultMetrics } = client; collectDefaultMetrics(); Warning: Possible perf_hooks memory leak detected. There are 1947 entries in the Performance Timeline. Use the clear methods to remove entries that are...
As requested in issue #470, here is a PR New functions: getClusterMetricsAsJSON() getClusterMetricsAsArray()
At the moment it seems the cluster metrics are only available in the string format and not the JSON format. I seems like it would be trivial to also add...
With exemplar support coming to Prometheus version 2.26.0 I thought I could start on this. Also addresses [#410](https://github.com/siimon/prom-client/issues/410). Looking for some direction to see if this the right approach to...
Hello, Thank you for all the work with this library! We are using our own implementation of the event loop lag metric because the [default metric](https://github.com/siimon/prom-client/blob/master/lib/metrics/eventLoopLag.js) did not work well...
Hi, as stated in the title, I believe the event loop lag metric should be a summary, not a gauge. The reason is that event loop lag can fluctuate quite...
In README, `gauge.labels({label1: value1, label2: value2}).set(1)` is supposed to be valid (as 2nd version), but it is rejected in util.js `getLabels()` because it expects args to be an array. Same...
The /examples folder has examples for the other metrics but an example of using Summary is missing