lei...@gmail.com
unread,Dec 5, 2024, 4:57:16 PM12/5/24Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Bartłomiej Płotka, Josh Suereth, arve.k...@gmail.com, OpenMetrics, que...@google.com
In which way do you want these proposals to go? I'm an old IETF geek,
I sort of prefer mail lists, other options for discussions are fine -
whatever you do. I'm unlikely to come to the WG meeting except
virtually.
Ihve long history with network engineering, software dev, monitoring,
linux and open source. Probably best known for nagios monitoring
contributions but I mostly do cloud apps now. Open-metrics is a
de-facto standard for model app monitoring though there are a lot of
proprietary solutions. The existing standard is SNMP and it doesn't
fit the modern app model.
I'm not proposing major changes or something that would require query
support I think. Severity thresholds are useful and would allow to
re-map existing data. They would only work with some data types like
gauge. Could be open to discussing how to do it, but that is what I
had in mind for it. There is an existing _info string defined in
open-metrics 1.0 but it is defined as "SHOULD NOT CHANGE". I'm
proposing an information only status message that can be displayed to
the user about current status, but not necessarily queried and
searched for separately from existing metrics. In my opinion these are
not major changes and would allow to remap other monitoring data to
open-metrics and potentially for use by prometheus with some
extensions.