Support: Use logstash prune high cardinality fields #1838
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We have guids in some of our field names As of the time of writing we have over 4k fields in our index in elasticsearch, which makes kibana hard to use Signed-off-by: Toby Lorne <toby.lornewelch-richards@digital.cabinet-office.gov.uk>
|
Having received a verbal thumbs up from 👑 in Slack, I will apply this to Dev |
tlwr
commented
Apr 11, 2019
| @@ -1022,4 +1022,11 @@ filter { | |||
| "[@source][director]" | |||
| ] | |||
| } | |||
|
|
|||
| prune { | |||
| blacklist_names = [ | |||
There was a problem hiding this comment.
Suggested change
| blacklist_names = [ | |
| blacklist_names => [ |
|
This is not necessary if we clear out the fields in Kibana (when old things expire the GUIDs will go away), logging stacks with low retention do not have the GUID fields. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I haven't tested this at all, it is a PoC to start a discussion
What
We have guids in some of our field names
As of the time of writing we have over 4k fields in our index in
elasticsearch, which makes kibana hard to use
How to review
Code review
Test in the dev stack in logit
Who can review
Not @tlwr