@@ -28,8 +28,13 @@ to only send events for new or modified files.
2828
2929The operating system features that power this feature are as follows.
3030
31- * Linux - `inotify` is used, and therefore the kernel must have inotify support.
31+ * Linux - Multiple backends are supported: `auto`, `fsnotify`, `kprobes`, `ebpf`.
32+ By default, `fsnotify` is used, and therefore the kernel must have inotify support.
3233Inotify was initially merged into the 2.6.13 Linux kernel.
34+ The eBPF backend uses modern eBPF features and supports 5.10.16+ kernels.
35+ FSNotify doesn't have the ability to associate user data to file events.
36+ The preferred backend can be selected by specifying the `backend` config option.
37+ Since eBPF and Kprobes are in technical preview, `auto` will default to `fsnotify`.
3338* macOS (Darwin) - Uses the `FSEvents` API, present since macOS 10.5. This API
3439coalesces multiple changes to a file into a single event. {beatname_uc} translates
3540this coalesced changes into a meaningful sequence of actions. However,
@@ -144,6 +149,9 @@ of this directories are watched. If `recursive` is set to `true`, the
144149`file_integrity` module will watch for changes on this directories and all
145150their subdirectories.
146151
152+ *`backend`*:: (*Linux only*) Select the backend which will be used to
153+ source events. Valid values: `auto`, `fsnotify`, `kprobes`, `ebpf`. Default: `fsnotify`.
154+
147155include::{docdir}/auditbeat-options.asciidoc[]
148156
149157
0 commit comments