|
|
@ -1470,10 +1470,17 @@ server] to use can be provided using:
|
|
|
|
==== JMX
|
|
|
|
==== JMX
|
|
|
|
Micrometer provides a hierarchical mapping to
|
|
|
|
Micrometer provides a hierarchical mapping to
|
|
|
|
{micrometer-registry-documentation}/jmx[JMX], primarily as a cheap and portable way to
|
|
|
|
{micrometer-registry-documentation}/jmx[JMX], primarily as a cheap and portable way to
|
|
|
|
view metrics locally. Micrometer provides a default `HierarchicalNameMapper` that governs
|
|
|
|
view metrics locally.By default, metrics are exported to the `metrics` JMX domain. The
|
|
|
|
how a dimensional meter id is
|
|
|
|
domain to use can be provided provided using:
|
|
|
|
{micrometer-registry-documentation}/jmx#_hierarchical_name_mapping[mapped to flat
|
|
|
|
|
|
|
|
hierarchical names].
|
|
|
|
[source,properties,indent=0]
|
|
|
|
|
|
|
|
----
|
|
|
|
|
|
|
|
management.metrics.export.jmx.domain=com.example.app.metrics
|
|
|
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Micrometer provides a default `HierarchicalNameMapper` that governs 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
|
|
|
|
TIP: To take control over this behaviour, define your `JmxMeterRegistry` and supply your
|
|
|
|
own `HierarchicalNameMapper`. An auto-configured `JmxConfig` and `Clock` beans are
|
|
|
|
own `HierarchicalNameMapper`. An auto-configured `JmxConfig` and `Clock` beans are
|
|
|
|