I'm asking that the human readable names of Pipelines, Pipeline Rules, and Caches be included in the prometheus labels. Given this is requesting a "breaking change" for how prometheus will treat these (since the set of labels changing will cause the metric to no longer be the same as the historical metric) i think its a good idea to make this configurable (either in the graylog UX or via server.conf)
Why?
Some of the metrics are very difficult to work with because they do not resolve to human readable names. Resolving these by hands, at best, involves understanding which graylog web page to use and then paste the value into the address bar. At worst, these values are unresolvable.
Your Environment
Graylog Version: 6.0.3
OpenSearch Version: 2.12.0
MongoDB Version: 6.0.15
Operating System: Ubuntu Server 22.04 LTS
Browser version: Google Chrome Version 126.0.6478.115 (Official Build) (arm64)
What?
Graylog provides an incredibly useful metrics exporter.
I'm asking that the human readable names of Pipelines, Pipeline Rules, and Caches be included in the prometheus labels. Given this is requesting a "breaking change" for how prometheus will treat these (since the set of labels changing will cause the metric to no longer be the same as the historical metric) i think its a good idea to make this configurable (either in the graylog UX or via
server.conf)Why?
Some of the metrics are very difficult to work with because they do not resolve to human readable names. Resolving these by hands, at best, involves understanding which graylog web page to use and then paste the value into the address bar. At worst, these values are unresolvable.
Your Environment
Please let me know if there are any questions.