Skip to main content

eBPF Filedescriptor

Plugin: ebpf.plugin Module: filedescriptor


Monitor calls for functions responsible to open or close a file descriptor and possible errors.

Attach tracing (kprobe and trampoline) to internal kernel functions according options used to compile kernel.

This collector is only supported on the following platforms:

  • Linux

This collector supports collecting metrics from multiple instances of this integration, including remote instances.

The plugin needs setuid because it loads data inside kernel. Netdata sets necessary permissions during installation time.

Default Behavior


The plugin checks kernel compilation flags (CONFIG_KPROBES, CONFIG_BPF, CONFIG_BPF_SYSCALL, CONFIG_BPF_JIT) and presence of BTF files to decide which eBPF program will be attached.


The default configuration for this integration does not impose any limits on data collection.

Performance Impact

Depending of kernel version and frequency that files are open and close, this thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.


Metrics grouped by scope.

The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.

Per cgroup

These Metrics show grouped information per cgroup/service.

This scope has no labels.


services.file_opena dimension per systemd servicecalls/s
services.file_open_errora dimension per systemd servicecalls/s
services.file_closeda dimension per systemd servicecalls/s
services.file_close_errora dimension per systemd servicecalls/s

Per eBPF Filedescriptor instance

These metrics show total number of calls to functions inside kernel.

This scope has no labels.


filesystem.file_descriptoropen, closecalls/s
filesystem.file_erroropen, closecalls/s

Per apps

These Metrics show grouped information per apps group.


app_groupThe name of the group defined in the configuration.




There are no alerts configured by default for this integration.



Compile kernel

Check if your kernel was compiled with necessary options (CONFIG_KPROBES, CONFIG_BPF, CONFIG_BPF_SYSCALL, CONFIG_BPF_JIT) in /proc/config.gz or inside /boot/config file. Some cited names can be different accoring preferences of Linux distributions. When you do not have options set, it is necessary to get the kernel source code from or a kernel package from your distribution, this last is preferred. The kernel compilation has a well definedd pattern, but distributions can deliver their configuration files with different names.

Now follow steps:

  1. Copy the configuration file to /usr/src/linux/.config.
  2. Select the necessary options: make oldconfig
  3. Compile your kernel image: make bzImage
  4. Compile your modules: make modules
  5. Copy your new kernel image for boot loader directory
  6. Install the new modules: make modules_install
  7. Generate an initial ramdisk image (initrd) if it is necessary.
  8. Update your boot loader



The configuration file name for this integration is ebpf.d/fd.conf.

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config ebpf.d/fd.conf


All options are defined inside section [global].

Config options
update everyData collection frequency.5no
ebpf load modeDefine whether plugin will monitor the call (entry) for the functions or it will also monitor the return (return).entryno
appsEnable or disable integration with apps.pluginnono
cgroupsEnable or disable integration with cgroup.pluginnono
pid table sizeNumber of elements stored inside hash tables used to monitor calls per PID.32768no
ebpf type formatDefine the file type to load an eBPF program. Three options are available: legacy (Attach only kprobe), co-re (Plugin tries to use trampoline when available), and auto (plugin check OS configuration before to load).autono
ebpf co-re tracingSelect the attach method used by plugin when co-re is defined in previous option. Two options are available: trampoline (Option with lowest overhead), and probe (the same of legacy code).trampolineno
maps per coreDefine how plugin will load their hash maps. When enabled (yes) plugin will load one hash table per core, instead to have centralized information.yesno
lifetimeSet default lifetime for thread when enabled by cloud.300no


There are no configuration examples.

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.