metric name
The name that identifies what a metric measures, such as http_request_duration_seconds.
In more detail
Names are the interface other people build on, so Prometheus conventions matter: base units such as seconds and bytes, _total at the end of a counter, and no values encoded in the name. Put variations such as status or route in labels, because you can add across a label but not across different names.
Example
Good: http_requests_total{status="500"}. Bad: checkout_requests_from_mobile.Related terms
- metric label — A name and value attached to a metric, such as status="200", that splits one metric into separate series you can compare.
- base unit — The plain unit a metric should be recorded in, such as seconds rather than milliseconds and bytes rather than kilobytes.
- counter — A metric that only ever goes up, such as the total number of requests or errors, from which rates are calculated.
Taught in
- Metric Types: Counters And Gauges — Full-Stack Observability: Metrics, Tracing & Logging
- Cardinality And How It Bankrupts You — Full-Stack Observability: Metrics, Tracing & Logging
- The Prometheus Exposition Format — Full-Stack Observability: Metrics, Tracing & Logging
- PromQL Basics And Selectors — Full-Stack Observability: Metrics, Tracing & Logging
- Cart Versus cart: The Data Model And What A Scrape Returns — Prometheus Certified Associate (PCA) Exam Prep
- Fundamentals Sprint: Nine Calls On The Server — Prometheus Certified Associate (PCA) Exam Prep
- The Server That Would Not Die: Selecting Data — Prometheus Certified Associate (PCA) Exam Prep
- Milliseconds Versus Seconds: Naming Metrics And Labels — Prometheus Certified Associate (PCA) Exam Prep
- Instrumentation Sprint: Sixteen Calls On Code And Exporters — Prometheus Certified Associate (PCA) Exam Prep
- Seventy Seven Percent, Book Now? The Full Mock — Prometheus Certified Associate (PCA) Exam Prep