eBPF DCstat

eBPF DCstat

Plugin: ebpf-go.plugin Module: dcstat

Overview

Monitor directory cache events given an overall vision about files on memory or storage device. Setting dcstat = yes enables collection and the host-wide charts only; the per-application and per-cgroup charts additionally require apps = yes and/or cgroups = yes in the [global] section. reference, slow and miss are independent kernel counters and are reported independently: an interval with no fast-path lookups can still report slow-path lookups or misses. The C implementation of this collector suppressed slow and miss whenever reference did not move in the same interval.

Attach a kprobe to lookup_fast and a kretprobe to d_lookup, using the object flavor selected for the running 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 permission during installation time.

eBPF DCstat can be monitored further using the following other integrations:

• {% relatedResource id=“apps.plugin-apps-Applications” %}Applications{% /relatedResource %}
• {% relatedResource id=“cgroups.plugin-/sys/fs/cgroup-Containers” %}Containers{% /relatedResource %}

Default Behavior

Auto-Detection

The plugin checks kernel compilation flags (CONFIG_KPROBES, CONFIG_BPF, CONFIG_BPF_SYSCALL, CONFIG_BPF_JIT), presence of BTF files, and the configured object flavor to decide which eBPF program will be attached. Because lookup_fast is a static kernel function, the collector resolves its real symbol name from /proc/kallsyms before attaching.

Limits

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

Performance Impact

This thread will add overhead every time that an internal kernel function monitored by this thread is called.

Setup

Prerequisites

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 according to the 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 defined 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

Configuration

Options

The dcstat option in section [ebpf programs] controls whether the module is loaded. The options listed below are [global] overrides.

via File

The configuration file name for this integration is ebpf.d.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.conf

Examples

There are no configuration examples.

Metrics

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 eBPF DCstat instance

These metrics show how often file lookups were resolved by the kernel directory cache, host-wide.

This scope has no labels.

Metrics:

Alerts

There are no alerts configured by default for this integration.