http://hg.omfa.de/prosody-hg/ en-us util/openmetrics.lua revision history http://hg.omfa.de/prosody-hg/log/d10957394a3c/util/openmetrics.lua Kim Alvefur <zash@zash.se> Fri, 17 Mar 2023 16:23:16 +0100 http://hg.omfa.de/prosody-hg/log/176fd3ea505c/util/openmetrics.lua
See bd9e006a7a74 for more context]]> Kim Alvefur <zash@zash.se> Mon, 19 Dec 2022 23:11:42 +0100 http://hg.omfa.de/prosody-hg/log/5eaf77114fdb/util/openmetrics.lua
Added in d278a770eddc avoid having to deal with its absence in Lua 5.1.
No longer needed when Lua 5.1 support is dropped.]]> Kim Alvefur <zash@zash.se> Mon, 11 Jul 2022 19:15:24 +0200 http://hg.omfa.de/prosody-hg/log/39ae08180c81/util/openmetrics.lua Kim Alvefur <zash@zash.se> Mon, 11 Jul 2022 19:07:38 +0200 http://hg.omfa.de/prosody-hg/log/7ef7abb72cdd/util/openmetrics.lua
Don't think we cause any such errors right now, but you never know!]]> Kim Alvefur <zash@zash.se> Mon, 30 May 2022 17:37:25 +0200 http://hg.omfa.de/prosody-hg/log/3caff1f93520/util/openmetrics.lua
Silences luacheck warning about the metatable being unused.]]> Kim Alvefur <zash@zash.se> Mon, 30 May 2022 17:34:58 +0200 http://hg.omfa.de/prosody-hg/log/05c250fa335a/util/openmetrics.lua
Words, sometimes I wonder how they even work

Maybe I missed something.]]> Kim Alvefur <zash@zash.se> Mon, 07 Mar 2022 00:13:56 +0100 http://hg.omfa.de/prosody-hg/log/85d51bfcf56b/util/openmetrics.lua
This version has several changes from the earlier mod_prometheus:

- Conversion of metrics into the text-based OpenMetrics format is moved to
util.openmetrics
- Support for IP-based access control
- Compatibility with earlier Prosody versions removed]]> Matthew Wild <mwild1@gmail.com> Wed, 24 Nov 2021 16:03:05 +0000 http://hg.omfa.de/prosody-hg/log/a02c277eb97a/util/openmetrics.lua Matthew Wild <mwild1@gmail.com> Mon, 14 Jun 2021 11:19:42 +0100 http://hg.omfa.de/prosody-hg/log/0db763f3f3be/util/openmetrics.lua
"%g" turns 1GB into 1.07374e+09, which is a bit awkward for the bytes
measurements IMO. Turning up the precision, at "%.17g" turns 0.1 into
0.10000000000000001 while "%0.16" gives 0.1, hiding most of those pesky
floating point artefacts. Lua version 5.2 uses "%.14g" ( see
LUA_NUMBER_FMT in luaconf.h.html ) so it seems like a sensible choice
here.]]> Kim Alvefur <zash@zash.se> Tue, 08 Jun 2021 00:58:27 +0200 http://hg.omfa.de/prosody-hg/log/5f15ab7c6ae5/util/openmetrics.lua
The metric subsystem of Prosody has had some shortcomings from
the perspective of the current state-of-the-art in metric
observability.

The OpenMetrics standard [0] is a formalization of the data
model (and serialization format) of the well-known and
widely-used Prometheus [1] software stack.

The previous stats subsystem of Prosody did not map well to that
format (see e.g. [2] and [3]); the key reason is that it was
trying to do too much math on its own ([2]) while lacking
first-class support for "families" of metrics ([3]) and
structured metric metadata (despite the `extra` argument to
metrics, there was no standard way of representing common things
like "tags" or "labels").

Even though OpenMetrics has grown from the Prometheus world of
monitoring, it maps well to other popular monitoring stacks
such as:

- InfluxDB (labels can be mapped to tags and fields as necessary)
- Carbon/Graphite (labels can be attached to the metric name with
dot-separation)
- StatsD (see graphite when assuming that graphite is used as
backend, which is the default)

The util.statsd module has been ported to use the OpenMetrics
model as a proof of concept. An implementation which exposes
the util.statistics backend data as Prometheus metrics is
ready for publishing in prosody-modules (most likely as
mod_openmetrics_prometheus to avoid breaking existing 0.11
deployments).

At the same time, the previous measure()-based API had one major
advantage: It is really simple and easy to use without requiring
lots of knowledge about OpenMetrics or similar concepts. For that
reason as well as compatibility with existing code, it is preserved
and may even be extended in the future.

However, code relying on the `stats-updated` event as well as
`get_stats` from `statsmanager` will break because the data
model has changed completely; in case of `stats-updated`, the
code will simply not run (as the event was renamed in order
to avoid conflicts); the `get_stats` function has been removed
completely (so it will cause a traceback when it is attempted
to be used).

Note that the measure_*_event methods have been removed from
the module API. I was unable to find any uses or documentation
and thus deemed they should not be ported. Re-implementation is
possible when necessary.

[0]: https://openmetrics.io/
[1]: https://prometheus.io/
[2]: #959
[3]: #960]]> Jonas Schäfer <jonas@wielicki.name> Sun, 18 Apr 2021 11:47:41 +0200