-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[libbeat] translate_sid should skip empty target fields #18990
Labels
bug
libbeat
:Processors
Team:Services
(Deprecated) Label for the former Integrations-Services team
:Windows
Comments
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Jun 5, 2020
4 tasks
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jun 5, 2020
The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes elastic#18990
andresrc
added
the
Team:Services
(Deprecated) Label for the former Integrations-Services team
label
Jun 5, 2020
Pinging @elastic/integrations-services (Team:Services) |
botelastic
bot
removed
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Jun 5, 2020
andrewkroh
added a commit
that referenced
this issue
Jun 9, 2020
The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes #18990
4 tasks
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jun 9, 2020
The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes elastic#18990 (cherry picked from commit baccaad)
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jun 9, 2020
The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes elastic#18990 (cherry picked from commit baccaad)
4 tasks
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jun 9, 2020
The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes elastic#18990 (cherry picked from commit baccaad)
4 tasks
andrewkroh
added a commit
that referenced
this issue
Jun 10, 2020
The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes #18990 (cherry picked from commit baccaad)
andrewkroh
added a commit
that referenced
this issue
Jun 10, 2020
…dling (#19084) The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes #18990 (cherry picked from commit baccaad)
andrewkroh
added a commit
that referenced
this issue
Jun 10, 2020
…dling (#19085) The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes #18990 (cherry picked from commit baccaad)
Fixed in #18991 targeting v7.7.2, v7.8.0, and v7.9.0. |
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this issue
Oct 14, 2020
The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes elastic#18990
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
…eld handling (elastic#19085) The translate_sid processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g. "": "Group"). Closes elastic#18990 (cherry picked from commit 4b19f09)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
libbeat
:Processors
Team:Services
(Deprecated) Label for the former Integrations-Services team
:Windows
The
translate_sid
processor only requires one of the three target fields to be configured. It should work properly when some of the targets are not set, but it doesn't check if the are empty strings. So it ends up adding target fields that are empty strings to the event (e.g."": "Group"
).The text was updated successfully, but these errors were encountered: