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

[8.6](backport #33699) [Filebeat] aws.vpcflow - use parse_aws_vpc_flow_log processor #33710

Merged
merged 1 commit into from
Nov 17, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 17, 2022

This is an automatic backport of pull request #33699 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

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)
@mergify mergify bot requested review from a team as code owners November 17, 2022 01:01
@mergify mergify bot requested review from faec and leehinman and removed request for a team November 17, 2022 01:01
@mergify mergify bot added the backport label Nov 17, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 17, 2022
@botelastic
Copy link

botelastic bot commented Nov 17, 2022

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-11-17T01:01:38.911+0000

  • Duration: 69 min 9 sec

Test stats 🧪

Test Results
Failed 2
Passed 3528
Skipped 174
Total 3704

Test errors 2

Expand to view the tests failures

Extended / x-pack/filebeat-cloudAWS / TestServerPool/inconsistent_tls_config – github.com/elastic/beats/v7/x-pack/filebeat/input/http_endpoint
    Expand to view the error details

     Failed 
    

    Expand to view the stacktrace

     === RUN   TestServerPool/inconsistent_tls_config
        input_test.go:245: unexpected error calling serve: got=`inconsistent TLS configuration on 127.0.0.1:9001: configuration options do not agree: old={"ca_sha256":[],"certificate":"","certificate_authorities":[],"cipher_suites":[],"client_authentication":0,"curve_types":[],"key":"","key_passphrase":"","supported_protocols":[],"verification_mode":3} new={"ca_sha256":[],"certificate":"","certificate_authorities":[],"cipher_suites":[],"client_authentication":0,"curve_types":[],"key":"","key_passphrase":"","supported_protocols":[],"verification_mode":1}`, want=`inconsistent TLS configuration on 127.0.0.1:9001: configuration options do not agree: old={"ca_sha256":[],"certificate":"","certificate_authorities":[],"cipher_suites":[],"client_authentication":0,"curve_types":[],"key":"","key_passphrase":"","supported_protocols":[],"verification_mode":1} new={"ca_sha256":[],"certificate":"","certificate_authorities":[],"cipher_suites":[],"client_authentication":0,"curve_types":[],"key":"","key_passphrase":"","supported_protocols":[],"verification_mode":3}`
        --- FAIL: TestServerPool/inconsistent_tls_config (1.00s)
     
    

Extended / x-pack/filebeat-cloudAWS / TestServerPool – github.com/elastic/beats/v7/x-pack/filebeat/input/http_endpoint
    Expand to view the error details

     Failed 
    

    Expand to view the stacktrace

     === RUN   TestServerPool
    --- FAIL: TestServerPool (5.06s)
     
    

Steps errors 2

Expand to view the steps failures

x-pack/filebeat-cloudAWS - mage build test goIntegTest
  • Took 5 min 41 sec . View more details here
  • Description: mage build test goIntegTest
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 1'

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors 2

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

  • Name: Extended / x-pack/filebeat-cloudAWS / TestServerPool/inconsistent_tls_config – github.com/elastic/beats/v7/x-pack/filebeat/input/http_endpoint
  • Name: Extended / x-pack/filebeat-cloudAWS / TestServerPool – github.com/elastic/beats/v7/x-pack/filebeat/input/http_endpoint

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants