root
/
spring-boot
mirror of https://github.com/spring-projects/spring-boot.git
1
0
Fork 0
Code Issues Actions 12 Packages Projects Releases Wiki Activity

Polish "Remove HierarchicalNameMapper as a configured @Bean" 

Closes gh-12683
This commit is contained in:
Stephane Nicoll 2018-04-03 11:18:49 +02:00
parent 8572a091b8
commit 7dbeaaa932
3 changed files with 13 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/metrics/export/ganglia/GangliaMetricsExportAutoConfiguration.java
View File

@ -62,4 +62,5 @@ public class GangliaMetricsExportAutoConfiguration {
Clock clock) { Clock clock) {
return new GangliaMeterRegistry(gangliaConfig, clock); return new GangliaMeterRegistry(gangliaConfig, clock);
} }
} }

1
spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/metrics/export/jmx/JmxMetricsExportAutoConfiguration.java
View File

@ -61,4 +61,5 @@ public class JmxMetricsExportAutoConfiguration {
public JmxMeterRegistry jmxMeterRegistry(JmxConfig config, Clock clock) { public JmxMeterRegistry jmxMeterRegistry(JmxConfig config, Clock clock) {
return new JmxMeterRegistry(config, clock); return new JmxMeterRegistry(config, clock);
} }
} }

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

@ -1435,11 +1435,12 @@ to use can be provided using:
management.metrics.export.graphite.port=9004 management.metrics.export.graphite.port=9004
---- ----
Micrometer provides a default `HierarchicalNameMapper` that governs Micrometer provides a default `HierarchicalNameMapper` that governs how a dimensional
how a dimensional meter id is mapped to flat hierarchical names. meter id is mapped to flat hierarchical names.
TIP: To take control over this behaviour, define your `GraphiteMeterRegistry` and supply your TIP: To take control over this behaviour, define your `GraphiteMeterRegistry` and supply
own `HierarchicalNameMapper`. your own `HierarchicalNameMapper`. An auto-configured `GraphiteConfig` and `Clock` beans
are provided unless you define your own:
[source,java] [source,java]
---- ----
@ -1449,6 +1450,8 @@ public GraphiteMeterRegistry graphiteMeterRegistry(GraphiteConfig config, Clock
} }
---- ----
[[production-ready-metrics-export-influx]] [[production-ready-metrics-export-influx]]
==== Influx ==== Influx
By default, metrics are exported to {micrometer-registry-documentation}/influx[Influx] By default, metrics are exported to {micrometer-registry-documentation}/influx[Influx]
@ -1470,7 +1473,8 @@ view metrics locally. Micrometer provides a default `HierarchicalNameMapper` tha
how a dimensional meter id is mapped to flat hierarchical names. how a dimensional meter id is mapped to flat hierarchical names.
TIP: To take control over this behaviour, define your `JmxMeterRegistry` and supply your TIP: To take control over this behaviour, define your `JmxMeterRegistry` and supply your
own `HierarchicalNameMapper`. own `HierarchicalNameMapper`. An auto-configured `JmxConfig` and `Clock` beans are
provided unless you define your own:
[source,java] [source,java]
---- ----
@ -1480,6 +1484,8 @@ public JmxMeterRegistry jmxMeterRegistry(JmxConfig config, Clock clock) {
} }
---- ----
[[production-ready-metrics-export-newrelic]] [[production-ready-metrics-export-newrelic]]
==== New Relic ==== New Relic
New Relic registry pushes metrics to {micrometer-registry-documentation}/new-relic[New New Relic registry pushes metrics to {micrometer-registry-documentation}/new-relic[New