Skip to content

[auditbeat] fim: implement ebpf backend#37223

Merged
mmat11 merged 2 commits intomainfrom
matt/fim-ebpf
Feb 13, 2024
Merged

[auditbeat] fim: implement ebpf backend#37223
mmat11 merged 2 commits intomainfrom
matt/fim-ebpf

Conversation

@mmat11
Copy link
Copy Markdown
Contributor

@mmat11 mmat11 commented Nov 28, 2023

Proposed commit message

This PR adds an additional opt-in eBPF backend to the file_integrity module. See related issues for more context.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

How to test this PR locally

Enable the eBPF backend in the file_integrity module config by specifying force_backend: ebpf and observe file events after running auditbeat.

Related issues

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 28, 2023
@mmat11 mmat11 added Team:Security-Linux Platform Linux Platform Team in Security Solution and removed needs_team Indicates that the issue/PR needs a Team:* label labels Nov 28, 2023
@mergify mergify bot assigned mmat11 Nov 28, 2023
@mmat11 mmat11 force-pushed the matt/fim-ebpf branch 12 times, most recently from 8204ed0 to 9c9cac4 Compare December 4, 2023 16:18
@elastic elastic deleted a comment from mergify bot Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from elasticmachine Dec 7, 2023
@elastic elastic deleted a comment from mergify bot Dec 7, 2023
@elasticmachine
Copy link
Copy Markdown
Contributor

❕ Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

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

Expand to view the summary

Build stats

  • Start Time: 2024-02-02T20:25:10.367+0000

  • Duration: 21 min 53 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

Steps errors 16

Expand to view the steps failures

Show only the first 10 steps failures

auditbeat-rhel-9-rhel-9 - mage build unitTest
  • Took 1 min 6 sec . View more details here
  • Description: mage build unitTest
auditbeat-rhel-9-rhel-9 - mage build unitTest
  • Took 0 min 2 sec . View more details here
  • Description: mage build unitTest
auditbeat-rhel-9-rhel-9 - mage build unitTest
  • Took 0 min 2 sec . View more details here
  • Description: mage build unitTest
x-pack/auditbeat-build - mage update build test
  • Took 1 min 16 sec . View more details here
  • Description: mage update build test
x-pack/auditbeat-build - mage update build test
  • Took 0 min 5 sec . View more details here
  • Description: mage update build test
x-pack/auditbeat-build - mage update build test
  • Took 0 min 5 sec . View more details here
  • Description: mage update build test
x-pack/auditbeat-rhel-9-rhel-9 - mage build unitTest
  • Took 1 min 11 sec . View more details here
  • Description: mage build unitTest
x-pack/auditbeat-rhel-9-rhel-9 - mage build unitTest
  • Took 0 min 2 sec . View more details here
  • Description: mage build unitTest
x-pack/auditbeat-rhel-9-rhel-9 - mage build unitTest
  • Took 0 min 2 sec . View more details here
  • Description: mage build unitTest
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 1'

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

@elasticmachine
Copy link
Copy Markdown
Contributor

❕ Build Aborted

Either there was a build timeout or someone aborted the build.

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

Expand to view the summary

Build stats

  • Duration: 16 min 10 sec

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

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Feb 2, 2024

💚 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

  • Duration: 178 min 13 sec

❕ Flaky test report

No test was executed to be analysed.

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

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Feb 5, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mmat11? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@mmat11
Copy link
Copy Markdown
Contributor Author

mmat11 commented Feb 5, 2024

/test auditbeat integTest

@mmat11
Copy link
Copy Markdown
Contributor Author

mmat11 commented Feb 5, 2024

/test auditbeat integTest arm

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Feb 6, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b matt/fim-ebpf upstream/matt/fim-ebpf
git merge upstream/main
git push upstream matt/fim-ebpf

@mmat11 mmat11 force-pushed the matt/fim-ebpf branch 3 times, most recently from 136b45c to 3e7db0b Compare February 8, 2024 16:53
@mmat11
Copy link
Copy Markdown
Contributor Author

mmat11 commented Feb 8, 2024

/test auditbeat integTest arm

@mmat11
Copy link
Copy Markdown
Contributor Author

mmat11 commented Feb 8, 2024

/test auditbeat integTest arm

Copy link
Copy Markdown
Member

@andrewkroh andrewkroh left a comment

Choose a reason for hiding this comment

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

Just a few minor comments, I don't think anything that requires another look.

For future reference, in these larger changesets I would prefer if we didn't force push after the first peer review comments come in. Being able to view the changes since you last reviewed is valuable. At least in this repo, you are required to squash at merge so you still have an opportunity to clean up the commit message.

@mmat11 mmat11 requested a review from a team as a code owner February 9, 2024 17:23
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

History

cc @mmat11

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

History

cc @mmat11

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

History

cc @mmat11

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

History

cc @mmat11

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

History

cc @mmat11

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

History

cc @mmat11

Copy link
Copy Markdown
Contributor

@pkoutsovasilis pkoutsovasilis left a comment

Choose a reason for hiding this comment

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

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Auditbeat enhancement Team:Security-Linux Platform Linux Platform Team in Security Solution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants