-
Notifications
You must be signed in to change notification settings - Fork 5k
[auditbeat][fim] Update Auditbeat file_integrity module to default to auto backend with intelligent fallback #47498
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
Open
marc-gr
wants to merge
3
commits into
elastic:main
Choose a base branch
from
marc-gr:feat/fim-auto-backend
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or 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
…o backend with intelligent fallback
|
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
🤖 GitHub commentsJust comment with:
|
🔍 Preview links for changed docs |
…file integrity module
| func newEBPFReader(c Config, l *logp.Logger) (EventProducer, error) { | ||
| // Test if eBPF is available by trying to get the watcher | ||
| // This validates early that eBPF can actually be used, allowing fallback to work | ||
| _, err := ebpf.GetWatcher() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that newFSNotifyReader and newKProbesReader, get watchers and then close them.
The ebpf watcher doesn't need to be closed?
… test configuration for backend fallback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Auditbeat
backport-skip
Skip notification from the automated backport with mergify
docs
enhancement
Team:Security-Linux Platform
Linux Platform Team in Security Solution
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.
Proposed commit message
The auto backend option now tries the backends in order until the best available option is found
Checklist
stresstest.shscript to run them under stress conditions and race detector to verify their stability../changelog/fragmentsusing the changelog tool.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs