Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify docs on disable_metrics behaviour for micrometer #3320

Merged
merged 1 commit into from
Sep 13, 2023
Merged

Clarify docs on disable_metrics behaviour for micrometer #3320

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/metrics.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -580,6 +580,10 @@ Although there is no upper limit, note that a high number of distinct values per
higher index sizes, and slower queries.
Also, make sure the number of distinct tag keys is limited to avoid {ref}/mapping.html#mapping-limit-settings[mapping explosions].

Depending on the meter type, some meters might be exported as multiple metrics to elasticsearch. The resulting fields are shown below for each meter type.
Note that the <<config-disable-metrics, `disable_metrics`>> option operates on the original name of the metric, not on the generated fields.
For that reason it is only possible to disable all fields of a given metric, not individual ones.

*`Timer`*::
+
--
Expand Down
Loading