[Filebeat] aws.vpcflow - use parse_aws_vpc_flow_log processor #33699
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
botelastic
bot
added
the
needs_team
|
This pull request doesn't have a |
Update the aws.vpcflow dataset in the AWS module to use the parse_aws_vpc_flow_log processor. I also updated the module to be aligned with ECS. It was not using valid event.category and event.type values. It will now produce `event.category: [network]`. And `event.type: [connection]` or `[connection, allowed]` or `[connection, denied]`.
andrewkroh
force-pushed
the
feature/fb/aws-vpcflow-module-update
branch
from
492c9ef to
74f9a4d
Compare
This comment was marked as outdated.
This comment was marked as outdated.
andrewkroh
requested review from
belimawr and
cmacknz
and removed request for
a team
belimawr
approved these changes
Nov 16, 2022
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
kaiyan-sheng
approved these changes
Nov 16, 2022
|
@Mergifyio backport 8.6 |
mergify bot
pushed a commit
that referenced
this pull request
Nov 17, 2022
Update the aws.vpcflow dataset in the AWS module to use the parse_aws_vpc_flow_log processor. I also updated the module to be aligned with ECS. It was not using valid event.category and event.type values. It will now produce `event.category: [network]`. And `event.type: [connection]` or `[connection, allowed]` or `[connection, denied]`. (cherry picked from commit 703d529)
✅ Backports have been created
|
andrewkroh
added a commit
that referenced
this pull request
Nov 17, 2022
Update the aws.vpcflow dataset in the AWS module to use the parse_aws_vpc_flow_log processor. I also updated the module to be aligned with ECS. It was not using valid event.category and event.type values. It will now produce `event.category: [network]`. And `event.type: [connection]` or `[connection, allowed]` or `[connection, denied]`. (cherry picked from commit 703d529) Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
chrisberkhout
pushed a commit
that referenced
this pull request
Jun 1, 2023
Update the aws.vpcflow dataset in the AWS module to use the parse_aws_vpc_flow_log processor. I also updated the module to be aligned with ECS. It was not using valid event.category and event.type values. It will now produce `event.category: [network]`. And `event.type: [connection]` or `[connection, allowed]` or `[connection, denied]`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Update the
aws.vpcflowdataset in the AWS module to use theparse_aws_vpc_flow_log processor. I also updated the module to be aligned with ECS. It was not using validevent.categoryandevent.typevalues. It will now produceevent.category: [network]. Andevent.type: [connection]or[connection, allowed]or[connection, denied].Why is it important?
This aligns the output to ECS and optimizes processing by using a dedicated processor.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues