feat: Configurable list of json fields to mine patterns #14528
+94
−56
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.
What this PR does / why we need it:
This PR makes the hardcoded list of json fields to mine patterns for configurable. This would allow us to:
This list is now configurable via the
pattern_ingester_tokenizable_json_fields
field orlimits.pattern-ingester-tokenizable-json-fields
cmd arg. It takes a comma-separated list of fields. By default we set it to the currently hardcoded list:log,message,msg,msg_,_msg,content
.The docs are hidden.
Special notes for your reviewer:
pattern.stream
via theinstanceID
of thepattern.instance
which in turns comes from thepattern.Ingester
atGetOrCreateInstance
where theinstanceID
comes from the tenantID in the ctx.Checklist
CONTRIBUTING.md
guide (required)feat
PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.md
deprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR