From 2002115637e18b30d45701fdba4d002b7620c990 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Mon, 16 Apr 2018 08:43:46 +0200 Subject: [PATCH] Add doc ref for hierarchical name mapping --- .../src/main/asciidoc/production-ready-features.adoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc index dbbb824b68..1a4dd9cda7 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc @@ -1436,7 +1436,8 @@ to use can be provided using: ---- Micrometer provides a default `HierarchicalNameMapper` that governs how a dimensional -meter id is mapped to flat hierarchical names. +meter id is {micrometer-registry-documentation}/graphite#_hierarchical_name_mapping[mapped +to flat hierarchical names]. TIP: To take control over this behaviour, define your `GraphiteMeterRegistry` and supply your own `HierarchicalNameMapper`. An auto-configured `GraphiteConfig` and `Clock` beans @@ -1470,7 +1471,9 @@ server] to use can be provided using: Micrometer provides a hierarchical mapping to {micrometer-registry-documentation}/jmx[JMX], primarily as a cheap and portable way to view metrics locally. Micrometer provides a default `HierarchicalNameMapper` that governs -how a dimensional meter id is mapped to flat hierarchical names. +how a dimensional meter id is +{micrometer-registry-documentation}/jmx#_hierarchical_name_mapping[mapped to flat +hierarchical names]. TIP: To take control over this behaviour, define your `JmxMeterRegistry` and supply your own `HierarchicalNameMapper`. An auto-configured `JmxConfig` and `Clock` beans are