registry/vendor/github.com/prometheus/procfs
Sebastiaan van Stijn 6e8dd268a8
update to go 1.18 (continue testing against 1.17)
Go 1.16 reached end of life, so update to the current version of Go, but also
run CI on the previous version (which is still supported).

We should probably also decide wether or not we want the Dockerfiles to pin to
a specific minor version; this makes the releases more deterministic.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-05-05 10:36:28 +02:00
..
internal/fs vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
.gitignore vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
.golangci.yml vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
buddyinfo.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
CONTRIBUTING.md migrate to go modules from vndr 2019-06-19 12:24:07 -07:00
doc.go Add Prometheus Metrics 2018-02-09 14:27:51 -08:00
fixtures.ttar vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
fs.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
ipvs.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
LICENSE Add Prometheus Metrics 2018-02-09 14:27:51 -08:00
MAINTAINERS.md vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
Makefile vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
Makefile.common vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
mdstat.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
mountinfo.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
mountstats.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
net_dev.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
net_unix.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
NOTICE Add Prometheus Metrics 2018-02-09 14:27:51 -08:00
proc.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
proc_environ.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
proc_io.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
proc_limits.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
proc_ns.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
proc_psi.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
proc_stat.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
proc_status.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
README.md vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
stat.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
ttar vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00
xfrm.go vendor: update docker/go-metrics v0.0.1 2020-03-02 20:14:15 +01:00

procfs

This procfs package provides functions to retrieve system, kernel and process metrics from the pseudo-filesystems /proc and /sys.

WARNING: This package is a work in progress. Its API may still break in backwards-incompatible ways without warnings. Use it at your own risk.

GoDoc Build Status Go Report Card

Usage

The procfs library is organized by packages based on whether the gathered data is coming from /proc, /sys, or both. Each package contains an FS type which represents the path to either /proc, /sys, or both. For example, current cpu statistics are gathered from /proc/stat and are available via the root procfs package. First, the proc filesystem mount point is initialized, and then the stat information is read.

fs, err := procfs.NewFS("/proc")
stats, err := fs.Stat()

Some sub-packages such as blockdevice, require access to both the proc and sys filesystems.

    fs, err := blockdevice.NewFS("/proc", "/sys")
    stats, err := fs.ProcDiskstats()

Building and Testing

The procfs library is normally built as part of another application. However, when making changes to the library, the make test command can be used to run the API test suite.

Updating Test Fixtures

The procfs library includes a set of test fixtures which include many example files from the /proc and /sys filesystems. These fixtures are included as a ttar file which is extracted automatically during testing. To add/update the test fixtures, first ensure the fixtures directory is up to date by removing the existing directory and then extracting the ttar file using make fixtures/.unpacked or just make test.

rm -rf fixtures
make test

Next, make the required changes to the extracted files in the fixtures directory. When the changes are complete, run make update_fixtures to create a new fixtures.ttar file based on the updated fixtures directory. And finally, verify the changes using git diff fixtures.ttar.