Skip to content
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

[Packetbeat] flow dataset should have "network" in event.category #20364

Closed
leehinman opened this issue Jul 30, 2020 · 1 comment · Fixed by #20392
Closed

[Packetbeat] flow dataset should have "network" in event.category #20364

leehinman opened this issue Jul 30, 2020 · 1 comment · Fixed by #20392

Comments

@leehinman
Copy link
Contributor

  1. packetbeat flow dataset events with event.category:network_traffic as the only value.
@leehinman leehinman added bug needs_backport PR is waiting to be backported to other branches. Team:SIEM labels Jul 30, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

leehinman added a commit to leehinman/beats that referenced this issue Jul 31, 2020
andrewkroh pushed a commit that referenced this issue Aug 11, 2020
Add "network" to event.category value.

Closes #20364
andrewkroh pushed a commit to andrewkroh/beats that referenced this issue Aug 11, 2020
Add "network" to event.category value.

Closes elastic#20364


(cherry picked from commit 7b47f1f)
andrewkroh added a commit that referenced this issue Aug 14, 2020
Add "network" to event.category value.

Closes #20364


(cherry picked from commit 7b47f1f)

Co-authored-by: Lee Hinman <[email protected]>
melchiormoulin pushed a commit to melchiormoulin/beats that referenced this issue Oct 14, 2020
@andrewkroh andrewkroh removed the needs_backport PR is waiting to be backported to other branches. label Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants