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.
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.
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
Followup to 12606 #18316
Followup to 12606 #18316
Changes from all commits
a60f5fb
f2f3b65
cc9c097
ff11264
611c877
5ef7bd9
8914d75
4d0259a
fcda77d
5eb058e
583b42e
50f3ee5
8551c2c
8b1f6ea
49acde0
9b0debc
16a9eaa
1f4fd5d
5c02b87
0a7e6b5
440e8c9
85c6e54
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, now I'm curious. Why is the
@metadata.op_type
a string? Do we read it from the log file as is?In case the field is set internally we should prefer it to be an enum always. In case it can indeed be both let's use:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, I'm not thinking about this correctly 😠.
@metadata.op_type
is expected to be set by developers in code. So there's no reason it shouldn't always be an enum. The only time we should use it as a string is if we need to serialize it for printing in log messages or sending in in JSON, etc. Will fix.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still think it makes sense to support it as 'string' input. E.g. in setups like
Beat -> json file -> Filebeat -> Elasticsearch
orBeat-> Kafka -> Filebeat -> Elasticsearch
we want it to continue to work (JSON unfortunately hasn't that many types).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, in those setups we would need to read
op_type
from the metadata as well (in the Filebeat step). Will add the string input support.