Based on https://www.robustperception.io/on-the-naming-of-things/ and https://prometheus.io/docs/practices/rules/#naming-and-aggregation naming should normally be level:metric:operations. This implies that colons are "reserved" for use in aggregation rules, so metrics with colons are a bit confusing and breaks with Prometheus conventions.
Also thanks for creating this, was rather sad to see that there wasn't any simple way to get Prometheus + Python UWSGI with the official client, but this looks very promising :-)
Based on https://www.robustperception.io/on-the-naming-of-things/ and https://prometheus.io/docs/practices/rules/#naming-and-aggregation naming should normally be
level:metric:operations. This implies that colons are "reserved" for use in aggregation rules, so metrics with colons are a bit confusing and breaks with Prometheus conventions.Also thanks for creating this, was rather sad to see that there wasn't any simple way to get Prometheus + Python UWSGI with the official client, but this looks very promising :-)