-
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] add_network_direction creates field name that contains a dot #29747
Labels
Comments
andrewkroh
added
bug
libbeat
:Processors
good first issue
Indicates a good issue for first-time contributors
labels
Jan 7, 2022
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Jan 7, 2022
legoguy1000
added a commit
to legoguy1000/beats
that referenced
this issue
Jan 9, 2022
6 tasks
botelastic
bot
removed
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Jan 17, 2022
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
andrewkroh
added a commit
that referenced
this issue
Feb 1, 2022
Fix Add Network Direction processor field with dot in name. Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
andrewkroh
added a commit
that referenced
this issue
Mar 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The
add_network_direction
processor creates field names that contain dots. By default it will create a document that containsWhat is does:
What is SHOULD do:
The problem is this line that directly uses the target key without considering that it could contain dots.
beats/libbeat/processors/actions/add_network_direction.go
Lines 103 to 105 in ce73772
It looks to me like it should use:
event.PutValue(m.Target, networkDirection(internalSource, internalDestination))
The text was updated successfully, but these errors were encountered: