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 449e4463f3b..2a9e995f28b 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 @@ -1127,10 +1127,10 @@ monitoring systems, including: - <> - <> - <> -- <> - <> - <> - <> +- <> - <> - <> @@ -1291,22 +1291,6 @@ TIP: To take control over this behaviour, define your own `HierarchicalNameMappe -[[production-ready-metrics-export-simple]] -==== Simple -Micrometer ships with a simple, in-memory backend that is automatically used as a fallback -if no other registry is configured. This allows you to see what metrics are collected in -the <>. - -The in-memory backend disables itself as soon as you're using any of the other available -backend. You can also disable it explicitly: - -[source,properties,indent=0] ----- - management.metrics.export.simple.enabled=false ----- - - - [[production-ready-metrics-export-newrelic]] ==== New Relic New Relic registry pushes metrics to {micrometer-registry-documentation}/newrelic[New @@ -1371,6 +1355,22 @@ You can also change the interval at which metrics are sent to SignalFx: +[[production-ready-metrics-export-simple]] +==== Simple +Micrometer ships with a simple, in-memory backend that is automatically used as a fallback +if no other registry is configured. This allows you to see what metrics are collected in +the <>. + +The in-memory backend disables itself as soon as you're using any of the other available +backend. You can also disable it explicitly: + +[source,properties,indent=0] +---- + management.metrics.export.simple.enabled=false +---- + + + [[production-ready-metrics-export-statsd]] ==== StatsD The StatsD registry pushes metrics over UDP to a StatsD agent eagerly. By default, metrics