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

Set source.bytes/packets for uni-directional netflow #14111

Merged

Conversation

andrewkroh
Copy link
Member

This populates the source.bytes and source.packets fields for uni-directional netflow events. Previously only network.bytes/network.packets would be set. The input would already populate the source fields for bi-directional flows.

This also fixes an issue where the totals in network.bytes and network.packets were incorrectly calculated for bi-directional flows.

@@ -67,11 +67,12 @@
"bytes": 132,
"ip": "172.16.32.201",
"locality": "private",
"packets": 200,
"packets": 2,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was being populated with the revBytes.

This populates the `source.bytes` and `source.packets` fields for uni-directional netflow events. Previously only `network.bytes`/`network.packets` would be set. The input would already populate the source fields for bi-directional flows.

This also fixes an issue where the totals in `network.bytes` and `network.packets` were incorrectly calculated for bi-directional flows.
@andrewkroh andrewkroh force-pushed the feature/filebeat-netflow-source-bytes branch from 878613f to dabd9f5 Compare October 17, 2019 14:16
@andrewkroh andrewkroh added needs_backport PR is waiting to be backported to other branches. and removed backport labels Oct 17, 2019
@andrewkroh
Copy link
Member Author

This should help with the rendering of uni-directional netflow events on the SIEM network page.

@adriansr
Copy link
Contributor

I guess this closes #11473

@andrewkroh
Copy link
Member Author

Yeah, this will address that issue. I forgot I had that open. Thanks.

@andrewkroh andrewkroh merged commit cbc040a into elastic:master Oct 17, 2019
@andrewkroh andrewkroh added v7.5.0 and removed needs_backport PR is waiting to be backported to other branches. labels Oct 21, 2019
andrewkroh added a commit to andrewkroh/beats that referenced this pull request Oct 21, 2019
This populates the `source.bytes` and `source.packets` fields for uni-directional netflow events. Previously only `network.bytes`/`network.packets` would be set. The input would already populate the source fields for bi-directional flows.

This also fixes an issue where the totals in `network.bytes` and `network.packets` were incorrectly calculated for bi-directional flows.

Closes elastic#11473

(cherry picked from commit cbc040a)
andrewkroh added a commit that referenced this pull request Oct 21, 2019
This populates the `source.bytes` and `source.packets` fields for uni-directional netflow events. Previously only `network.bytes`/`network.packets` would be set. The input would already populate the source fields for bi-directional flows.

This also fixes an issue where the totals in `network.bytes` and `network.packets` were incorrectly calculated for bi-directional flows.

Closes #11473

(cherry picked from commit cbc040a)
jorgemarey pushed a commit to jorgemarey/beats that referenced this pull request Jun 8, 2020
This populates the `source.bytes` and `source.packets` fields for uni-directional netflow events. Previously only `network.bytes`/`network.packets` would be set. The input would already populate the source fields for bi-directional flows.

This also fixes an issue where the totals in `network.bytes` and `network.packets` were incorrectly calculated for bi-directional flows.

Closes elastic#11473
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…lastic#14161)

This populates the `source.bytes` and `source.packets` fields for uni-directional netflow events. Previously only `network.bytes`/`network.packets` would be set. The input would already populate the source fields for bi-directional flows.

This also fixes an issue where the totals in `network.bytes` and `network.packets` were incorrectly calculated for bi-directional flows.

Closes elastic#11473

(cherry picked from commit 9e801c2)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants