Cherry-pick #25113 to 7.x: [Metricbeat] Remove elasticsearc.index.created from the SM code #25172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #25113 to 7.x branch. Original message:
What does this PR do?
SM
index
metricset does an API HTTP call to elasticsearch to retrieve index metadata information. This information is required to populate fieldelasticsearch.index.created
or (index_stats.created
ifxpack.enabled: true
when configuring the module).The code removes the API call to
/_cluster/state/metadata
.Why is it important?
The HTTP call to
/_cluster/state/metadata
can be VERY expensive. The reason for this is that it returns the entire mapping of all indices on a cluster. If a user has many indices and / or each index has many fields, this could lead to very heavy responses from elasticsearchr (20 Mb in big clusters measured with curl).Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
elasticsearch.index.created
orindex_stats.created
and they will be removed.