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.0](backport #29435) [Winlogbeat] Switch to ingest node processing #29685

Merged
merged 1 commit into from
Jan 4, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 4, 2022

This is an automatic backport of pull request #29435 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

What does this PR do?

Switches to ingest node processing instead of local javascript
processing for modules.

Why is it important?

For Agent we are using ingest node processing. This keeps the
Winlogbeat and Agent processing in sync and allows bug fixes to be
shared between them.

Changes

- remove JS processing
- remove testing of JS processing
- add ingest node pipelines from agent
- use routing pipeline to direct to correct module pipeline
- embed pipelines in winlogbeat executable
- add `export pipeline` command
- add loading of pipelines to setup command
- add loading of pipelines to every ES connection if the pipelines
  don't exist
- exports several functions from filebeat/fileset to avoid code
  duplication
- update docs
- update default config
- update reference config

Closes #29184

(cherry picked from commit a3c2208)
@mergify mergify bot requested a review from a team as a code owner January 4, 2022 17:20
@mergify mergify bot added the backport label Jan 4, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 4, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 4, 2022
@andrewkroh andrewkroh assigned andrewkroh and unassigned leehinman Jan 4, 2022
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jan 4, 2022

💚 Build Succeeded

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-01-04T17:59:32.585+0000

  • Duration: 122 min 55 sec

  • Commit: 725dd03

Test stats 🧪

Test Results
Failed 0
Passed 47556
Skipped 4278
Total 51834

💚 Flaky test report

Tests succeeded.

🤖 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!)

@andrewkroh
Copy link
Member

/test

@andrewkroh andrewkroh merged commit de857a6 into 8.0 Jan 4, 2022
@mergify mergify bot deleted the mergify/bp/8.0/pr-29435 branch January 4, 2022 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants