Replies: 2 comments 4 replies
-
that is just a representation of the internal data structure and our lack of understanding of Prometheus; we're open to suggestions for improvement indeed |
Beta Was this translation helpful? Give feedback.
0 replies
-
2.4.15.1rc0 e14de9e reformats the Prometheus output into e.g.:
and also addresses #1161 perhaps you could give this a try |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The metrics exposed in Prometheus format look similar to the following:
From what I understand, the metric name (e.g.
example_com_provider_metadata_bucket
) should only cover the semantics of what the metric actually is. Any context can then be added through labels.Naming the metrics as described would likely make it easier to aggregate the metrics across multiple VirtualHosts or Servers with different ServerNames.
Is there a reason why the ServerName is added to the name of the metric instead of a label?
Beta Was this translation helpful? Give feedback.
All reactions