Back to Netdata

eBPF Cachestat

src/collectors/ebpf.plugin/ebpfgo.plugin/integrations/ebpf_cachestat.md

2.11.06.6 KB
Original Source
<!--startmeta custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/collectors/ebpf.plugin/ebpfgo.plugin/integrations/ebpf_cachestat.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/ebpf.plugin/ebpfgo.plugin/metadata.yaml" sidebar_label: "eBPF Cachestat" learn_status: "Published" learn_rel_path: "Collecting Metrics/Collectors/Operating Systems" keywords: ['Page cache', 'Hit ratio', 'eBPF'] message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" endmeta-->

eBPF Cachestat

Plugin: ebpf-go.plugin Module: cachestat

Overview

Monitor Linux page cache events giving users a general vision about how the kernel is manipulating files.

Attach tracing (kprobe, 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 permission during installation time.

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

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.

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. The estimated additional period of time is between 90-200ns per call on kernels that do not have BTF technology.

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

All options are defined inside section [global].

<details open><summary>Config options</summary>
OptionDescriptionDefaultRequired
update everyData collection frequency. This configuration value takes precedence over the runtime interval passed by pluginsd.10no
ebpf load modeLegacy compatibility option. eBPFGo accepts entry; return is not supported and is ignored with a warning.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 object flavorSelect the cachestat object flavor to load. Available values are arena, buffer ring (also accepted as buffer), and legacy (also accepted as tracing). The default is buffer, and the collector falls back when the requested flavor is not available on the system.bufferno
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
btf pathOverride the default BTF source directory. The collector checks this path for a vmlinux BTF file used by CO-RE loading./sys/kernel/btfno
collect pidControls which PIDs are stored in the BPF hash tables. real parent stores only the real parent PID (lowest overhead); parent stores the immediate parent PID; all stores every PID used by the process (highest overhead).real parentno
lifetimeSet default lifetime for thread when enabled by cloud.300no
</details>

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.

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

There are no configuration examples.

Alerts

There are no alerts configured by default for this integration.

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 Cachestat instance

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

This scope has no labels.

Metrics:

MetricDescriptionDimensionsUnit
mem.cachestat_ratioHit ratioratio%
mem.cachestat_dirtiesNumber of dirty pagesdirtypage/s
mem.cachestat_hitsNumber of accessed fileshithits/s
mem.cachestat_missesFiles out of page cachemissmisses/s