Skip to main content
Version: latest

trace_fsslower

The trace fsslower gadget streams file operations (open, read, write and fsync) that are slower than a threshold.

Getting started​

Running the gadget:

$ kubectl gadget run ghcr.io/inspektor-gadget/gadget/trace_fsslower:latest [flags]

Flags​

--min​

Minimum latency in ms to trace

Default value: "10"

--pid​

Show only bind events generated by this particular PID

Default value: ""

--filesystem​

Filesystem to trace. Possible values are: btrfs, ext4, fuse, nfs, nfts3 or xfs.

Default value: "ext4"

Guide​

In this guide you'll deploy an example workload that performs some open(), read() write() and sync() calls and will trace which ones are slower than 1 ms.

Let's start the gadget before running our workload:

TODO

Launch a container that will perform input/output operations:

TODO

The tool will list the I/O operations that were slower than 1ms:

TODO