[infinispan-issues] [JBoss JIRA] (ISPN-10012) Observability: Qualify metrics using Prometheus naming

[Nistor Adrian (Jira)]

    [ https://issues.redhat.com/browse/ISPN-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992706#comment-13992706 ] 

Nistor Adrian commented on ISPN-10012:
--------------------------------------

[~NadirX] The metrics are currently using snake case naming. All parts of the name are lowercased. Except the included cache manager name and cache name, which are left as they are, no lowercasing, no snake casing. But non-complying characters are still replaced with '_'.  I believe this is pretty much what Prometheus conventions are.  

The actual metric name is formed like: `cache_manager_MyCacheManager_cache_MyCache_statistics_stores` by default.

An additional `prefix` attribute in the <metrics> element allow us to specify a prefix, just in case we need to avoid some conflict. Default prefix is empty.

The boolean attribute `namesAsTags` allows us to switch to using fixed metric names, that do not contain variable parts like the cache manager name / cache name. Instead these are added as tags when namesAsTags=true. So the metric name would be simply `statistics_stores` with tags [cache_manager="MyCacheManager", cache="MyCache"]


> Observability: Qualify metrics using Prometheus naming
> ------------------------------------------------------
>
>                 Key: ISPN-10012
>                 URL: https://issues.redhat.com/browse/ISPN-10012
>             Project: Infinispan
>          Issue Type: Sub-task
>          Components: JMX, reporting and management
>            Reporter: Tristan Tarrant
>            Assignee: Nistor Adrian
>            Priority: Major
>             Fix For: 10.1.3.Final, 11.0.0.Alpha2
>
>
> We currently annotate metrics using conventions derived from RHQ. We should update the convention to that used by Prometheus (Counters, Gauges, etc)



--
This message was sent by Atlassian Jira
(v7.13.8#713008)