Don't dynamically add mappings for Kibana meta to avoid field explosion #47890
+46
−1
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.
Fixes #45255
Proposed commit message
The
metafield in Kibana logs contains additional metadata that might be useful for understanding a log entry. This often means meta is a deeply nested object, mapping every field in this object causes a mapping explosion and slows down the Kibana UI. Users should not have to filter or search on the meta field.Checklist
stresstest.shscript to run them under stress conditions and race detector to verify their stability../changelog/fragmentsusing the changelog tool.Disruptive User Impact
Users should not be relying on the meta field or any keys therein.
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs