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

Cherry-pick #14111 to 7.5: Set source.bytes/packets for uni-directional netflow #14161

Merged
merged 1 commit into from
Oct 21, 2019

Conversation

andrewkroh
Copy link
Member

Cherry-pick of PR #14111 to 7.5 branch. Original message:

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.

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)
Copy link
Contributor

@adriansr adriansr left a comment

Choose a reason for hiding this comment

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

LGTM

@andrewkroh andrewkroh merged commit 62d4ae0 into elastic:7.5 Oct 21, 2019
@andrewkroh andrewkroh deleted the backport_14111_7.5 branch January 14, 2022 14:09
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