Plugin: ebpf.plugin Module: mdflush
Monitor when flush events happen between disks.
Attach tracing (kprobe, trampoline) to internal kernel functions according options used to compile kernel.
This collector is only supported on the following platforms:
This collector supports collecting metrics from multiple instances of this integration, including remote instances.
The plugin needs setuid because it loads data inside kernel. Netada sets necessary permission during installation time.
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.
This thread will add overhead every time that
md_flush_request is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
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 https://kernel.org 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:
initrd) if it is necessary.
The configuration file name for this integration is
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/mdflush.conf
All options are defined inside section
|update every||Data collection frequency.||5||False|
|ebpf load mode||Define whether plugin will monitor the call (
|lifetime||Set default lifetime for thread when enabled by cloud.||300||False|
There are no configuration examples.
Metrics grouped by scope.
The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
Number of times md_flush_request was called since last time.
This scope has no labels.
There are no alerts configured by default for this integration.