Hi,
I've read through the Prometheus Recording Rules document, and I find
myself in a situation where I'm not sure what the accepted naming
convention is for some instances. Does it make sense to have an empty
"level" such that a metric reads `:metrc:operations`? If I'm aggregating
across multiple levels like what are some standard practices on keeping the
level meaningful without growing out of control?
For example, my recording rule is summing multiple gauges from a legacy
application to form a more useful metric. I then roll that up into
pop-level metrics, and I'd rather not use "pop_city_region_platform" for
the level. The same holds for the initial aggregation. How do you guys
balance making the aggregation level informative without it being unwieldy?
- record: server_pop_city_region_platform_service:proxy_err_500
expr: |
sum by (server, pop, city, region, platform, service)
(
Error_Gauge1 +
Error_Gauge2 +
...
Error_Gauge3
)
- record: pop_city_region_platform:proxy_err_500:sum_rate5m
expr: sum by (pop, city, region, platform) (proxy_err_500)
Thanks,
-Juan
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/de3c978f-e6dd-4a78-8af9-3c60c3dd0291n%40googlegroups.com.
