Doug Hoard
Doug Hoard
@fstab The code change was introduced as part of metric name collision work. Do you remember the specifics? Is it necessary?
@secureaniruddha there is no per-metric configuration to convert the metric name to lowercase. Typically `lowercaseOutputName: true` is used for metric name consistency. Can you elaborate on what you mean by...
@secureaniruddha This sounds like an issue with the CCRC tool, since the exporter only exposed metrics via HTTP(S).
@fstab @iagotomas I will need to investigate the change after the pending release. The `MatchedRule` is used before any of the snapshot builds. @doxsch Your issue is similar, but not...
@fstab @zeitlinger Looking at the OpenMetrics specification... ``` Exposers SHOULD avoid names that could be confused with the suffixes that text format sample metric names use. Suffixes for the respective...
@doxsch can you create a new issue around the `_created`?
@offermannu We are discussing possible changes. For your rules, what metric names and types (`GAUGE`, `COUNTER` or `UNTYPED`) are you using that are having issues?
This is a function of suffix requirements for Prometheus/OpenMetrics formats. There is ongoing work on an OpenMetrics 2.0 proposal that will remove any suffix requirements.
Removal of metric name restrictions will be resolved with: https://github.com/prometheus/client_java/issues/1361#issuecomment-2890801832 https://github.com/prometheus/OpenMetrics/issues/286
Currently, there is no linter. An out-of-band linting tool is hard to implement since the rules are based on the dynamically scraped MBeans.