Commit aedda184 authored by Julius Volz's avatar Julius Volz

Make relevant metric parts bold in naming conventions.

parent 83f3ae57
...@@ -15,14 +15,14 @@ conventions differently. ...@@ -15,14 +15,14 @@ conventions differently.
A metric name: A metric name:
* should have a (single-word) application prefix relevant to the containing Prometheus domain * should have a (single-word) application prefix relevant to the containing Prometheus domain
* `prometheus_notifications_total` * <code><b>prometheus</b>\_notifications\_total</code>
* `indexer_requests_latencies_milliseconds` * <code><b>indexer</b>\_requests\_latencies\_milliseconds</code>
* `processor_requests_total` * <code><b>processor</b>\_requests\_total</code>
* must have a single unit (i.e. don't mix seconds with milliseconds) * must have a single unit (i.e. don't mix seconds with milliseconds)
* should have a units suffix * should have a units suffix
* `api_http_request_latency_milliseconds` * <code>api\_http\_request\_latency\_<b>milliseconds</b></code>
* `node_memory_usage_bytes` * <code>node\_memory\_usage\_<b>bytes</b></code>
* `api_http_requests_total` (for an accumulating count) * <code>api\_http\_requests\_<b>total</b></code> (for an accumulating count)
* should represent the same logical thing-being-measured * should represent the same logical thing-being-measured
* request duration * request duration
* bytes of data transfer * bytes of data transfer
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment