What happens in the kernel

Packet drops, OOM, memory stalls and hardware drops grouped by cause.

Host kernelDiting
NIC
Stack
Scheduler
Memory
From NIC to application, which layer lost something.

View by cause

Network drops separate stack, queue, driver and hardware. Memory separates OOM, direct reclaim and stalls. Any probe that fails says why.

Grouped by cause

01

Network drops

Stack, queue, driver and hardware counted separately.

02

Memory

OOM, direct reclaim and stalls, aligned to the timeline.

03

Host hotspots

CPU, locks and syscalls, down to function and process.

04

Probe status

Which capability works on which host, and why not.

How it works

CaptureeBPF and kernel probes, enabled per host
CompatibilityFrom 3.10; kernels without BTF use compatibility objects
DegradationA failed probe does not stop the agent; the reason is reported
OverheadSampling and switches configured per host

Fits

  • Teams tracing host-level performance problems
  • Old kernels and domestic distributions

Doesn't fit

  • Kernel security policies that forbid loading eBPF programs
  • Shared hosts with no root access

Bring your system in

Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.