From d7e000da53b14782674fda26b932cfb4b12b7f49 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Wed, 21 Feb 2018 10:19:41 +0100 Subject: [PATCH] Add missing JMX section --- .../src/main/asciidoc/production-ready-features.adoc | 12 ++++++++++++ 1 file changed, 12 insertions(+) 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 e6712a8b56..449e4463f3 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 @@ -1126,6 +1126,7 @@ monitoring systems, including: - <> - <> - <> +- <> - <> - <> - <> @@ -1279,6 +1280,17 @@ server] to use can be provided using: +[[production-ready-metrics-export-jmx]] +==== JMX +Micrometer provides a hierarchical mapping to +{micrometer-registry-documentation}/jmx[JMX], primarily as a cheap and portable way to +view metrics locally. Spring Boot provides a default `HierarchicalNameMapper` that governs +how a dimensional meter id is mapped to flat hierarchical names. + +TIP: To take control over this behaviour, define your own `HierarchicalNameMapper` bean. + + + [[production-ready-metrics-export-simple]] ==== Simple Micrometer ships with a simple, in-memory backend that is automatically used as a fallback