You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow library users to specify custom labels for CacheMetricsCollector.
Please upvote this issue if you would like this feature to be merged.
Let's say we are having k8s cluster with 10 different apps. Each of it uses caffeine as a cache. But single prometheus scrapper.
Currently, the only way to distinguish cache metrics provided by this library between apps is to modify somehow cacheName parameter (either we can prefix it with domain, e.g. users_the_cache_name, dashboards_the_cache_name, etc. or with postfix). This makes creating Grafana dashboards pretty difficult as we have to rely on regexes of cache label.
In order to create cache dashboard for users service we have to write something like
sum(rate(caffeine_cache_miss_total{cache~="users_.*"}[5m])) by (cache)
I think would be easier for users to specify their own labels and create Grafana dashboard like this:
Allow library users to specify custom labels for
CacheMetricsCollector
.Please upvote this issue if you would like this feature to be merged.
Let's say we are having k8s cluster with 10 different apps. Each of it uses caffeine as a cache. But single prometheus scrapper.
Currently, the only way to distinguish cache metrics provided by this library between apps is to modify somehow
cacheName
parameter (either we can prefix it with domain, e.g.users_the_cache_name
,dashboards_the_cache_name
, etc. or with postfix). This makes creating Grafana dashboards pretty difficult as we have to rely on regexes ofcache
label.In order to create cache dashboard for
users
service we have to write something likeI think would be easier for users to specify their own labels and create Grafana dashboard like this:
NOTE:
Implemented in scope of #602 but has some drawbacks (see PR comments).
The text was updated successfully, but these errors were encountered: