Split labels from naming.md into a new labels.md

Signed-off-by: Conall O'Brien <conall@conall.net>

Author: conallob

docs/practices/labels.md

@@ -0,0 +1,43 @@
+---
+title: Label Best Practices
+sort_rank: 1
+---
+
+The label conventions presented in this document are not required
+for using Prometheus, but can serve as both a style-guide and a collection of
+best practices. Individual organizations may want to approach some of these
+practices, e.g. naming conventions, differently.
+
+## Labels
+
+Prometheus labels can come from both the target and from
+[relabeling in discovery](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config) as well as from the target itself.
+
+By default Prometheus configures two primary discovery target labels.
+
+* `job`
+   * The `job` label is one of the few ubiquitious labels, set at scrape time, and is
+     used to identify metrics scraped from the same target/exporter.
+   * If not specified in PromQL expressions, they will match unrelated metrics with the same name. This is especially true in a multi system or multi tenant installation
+
+WARNING: When using `without`, be careful not to strip out the `job` label accidentally.
+
+* `instance`
+   * The `instance` label will include the `ip:port` what was scraped, providing a
+     crucial breadcrumb for debugging scrape time issues
+
+### General Labelling Advice
+
+Use labels to differentiate the characteristics of the thing that is being measured:
+
+ * `api_http_requests_total` - differentiate request types: `operation="create|update|delete"`
+ * `api_request_duration_seconds` - differentiate request stages: `stage="extract|transform|load"`
+
+Do not put the label names in the metric name, as this introduces redundancy
+and will cause confusion if the respective labels are aggregated away.
+
+CAUTION: Remember that every unique combination of key-value label
+pairs represents a new time series, which can dramatically increase the amount
+of data stored. Do not use labels to store dimensions with high cardinality
+(many different label values), such as user IDs, email addresses, or other
+unbounded sets of values.

docs/practices/naming.md

@@ -1,9 +1,9 @@
 ---
-title: Metric and label naming
+title: Metric naming
 sort_rank: 1
 ---
 
-The metric and label conventions presented in this document are not required
+The metric conventions presented in this document are not required
 for using Prometheus, but can serve as both a style-guide and a collection of
 best practices. Individual organizations may want to approach some of these
 practices, e.g. naming conventions, differently.
@@ -80,37 +80,6 @@ the underlying metric type and unit you work with.
 * **Metric collisions**: With growing adoption and metric changes over time, there are cases where lack
 of unit and type information in the metric name will cause certain series to collide (e.g. `process_cpu` for seconds and milliseconds).
 
-## Labels
-
-Prometheus labels can come from both the target and from [relabeling in discovery](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config) as well as from the target itself.
-
-By default Prometheus configures two primary discovery target labels.
-
-* `job`
-   * The `job` label is one of the few ubiquitious labels, set at scrape time, and is used to identify metrics scraped from the same target/exporter.
-   * If not specified in PromQL expressions, they will match unrelated metrics with the same name. This is especially true in a multi system or multi tenant installation
-
-WARNING: When using `without`, be careful not to strip out the `job` label accidentally.
-
-* `instance`
-   * The `instance` label will include the `ip:port` what was scraped, providing a crucial breadcrumb for debugging scrape time issues
-
-### General Labelling Advice
-
-Use labels to differentiate the characteristics of the thing that is being measured:
-
- * `api_http_requests_total` - differentiate request types: `operation="create|update|delete"`
- * `api_request_duration_seconds` - differentiate request stages: `stage="extract|transform|load"`
-
-Do not put the label names in the metric name, as this introduces redundancy
-and will cause confusion if the respective labels are aggregated away.
-
-CAUTION: Remember that every unique combination of key-value label
-pairs represents a new time series, which can dramatically increase the amount
-of data stored. Do not use labels to store dimensions with high cardinality
-(many different label values), such as user IDs, email addresses, or other
-unbounded sets of values.
-
 ## Base Units
 
 Prometheus does not have any units hard coded. For better compatibility, base