Metrics configuration optionsedit

dedot_custom_metrics ( [1.22.0] Added in 1.22.0. )edit

Replaces dots with underscores in the metric names for custom metrics, such as Micrometer metrics.

Setting this to false can lead to mapping conflicts as dots indicate nesting in Elasticsearch. An example of when a conflict happens is two metrics with the name foo and foo.bar. The first metric maps foo to a number and the second metric maps foo as an object.

dynamic config

Default Type Dynamic

true

Boolean

true

Java System Properties Property file Environment

elastic.apm.dedot_custom_metrics

dedot_custom_metrics

ELASTIC_APM_DEDOT_CUSTOM_METRICS

metric_set_limit ( [1.33.0] Added in 1.33.0. )edit

Limits the number of active metric sets. The metrics sets have associated labels, and the metrics sets are held internally in a map using the labels as keys. The map is limited in size by this option to prevent unbounded growth. If you hit the limit, you’ll receive a warning in the agent log. The recommended option to workaround the limit is to try to limit the cardinality of the labels, eg naming your transactions so that there are fewer distinct transaction names. But if you must, you can use this option to increase the limit.

Default Type Dynamic

1000

Integer

false

Java System Properties Property file Environment

elastic.apm.metric_set_limit

metric_set_limit

ELASTIC_APM_METRIC_SET_LIMIT