Add support for configuring common tags declaratively

Closes gh-12933

spring-boot-project/spring-boot-docs/src/main/asciidoc/appendix-application-properties.adoc

@@ -1432,6 +1432,7 @@ content into your application. Rather, pick only the properties that you need.
 	management.metrics.export.wavefront.step=10s # Step size (i.e. reporting frequency) to use.
 	management.metrics.export.wavefront.uri=https://longboard.wavefront.com # URI to ship metrics to.
 	management.metrics.use-global-registry=true # Whether auto-configured MeterRegistry implementations should be bound to the global static registry on Metrics.
+	management.metrics.tags.*= # Common tags that are applied to every meter.
 	management.metrics.web.client.max-uri-tags=100 # Maximum number of unique URI tag values allowed. After the max number of tag values is reached, metrics with additional tag values are denied by filter.
 	management.metrics.web.client.requests-metric-name=http.client.requests # Name of the metric for sent requests.
 	management.metrics.web.server.auto-time-requests=true # Whether requests handled by Spring MVC or WebFlux should be automatically timed.

spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

@@ -1846,6 +1846,21 @@ all meter IDs beginning with `com.example`, you can do the following:
 include::{code-examples}/actuate/metrics/MetricsFilterBeanExample.java[tag=configuration]
 ----
 
+[[production-ready-metrics-common-tags]]
+==== Common tags
+Common tag are generally used for dimensional drill-down on the operating environment like
+host, instance, region, stack, etc. Commons tags applied to all meters and can be
+configured as shown in the following example:
+
+[source,properties,indent=0]
+----
+	management.metrics.tags.region=us-east-1
+	management.metrics.tags.stack=prod
+----
+
+The example above adds a `region` and `stack` tags to all meters with a value of
+`us-east-1` and `prod` respectively.
+
 
 
 ==== Per-meter properties