OpenID Connect (OIDC) identity and OAuth 2.0 provider with pluggable connectors
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Mark Sagi-Kazar 0f1927a1ba
Vendor dependencies
6 years ago
..
internal Vendor dependencies 6 years ago
.gitignore run 'go get -u; make revendor' 7 years ago
.golangci.yml Vendor dependencies 6 years ago
CONTRIBUTING.md Vendor dependencies 6 years ago
LICENSE vendor: Add metrics packages 8 years ago
MAINTAINERS.md run 'go get -u; make revendor' 7 years ago
Makefile run 'go get -u; make revendor' 7 years ago
Makefile.common run 'go get -u; make revendor' 7 years ago
NOTICE vendor: Add metrics packages 8 years ago
README.md Vendor dependencies 6 years ago
arp.go Vendor dependencies 6 years ago
buddyinfo.go Vendor dependencies 6 years ago
cpuinfo.go Vendor dependencies 6 years ago
crypto.go Vendor dependencies 6 years ago
doc.go vendor: Add metrics packages 8 years ago
fixtures.ttar Vendor dependencies 6 years ago
fs.go run 'go get -u; make revendor' 7 years ago
go.mod Vendor dependencies 6 years ago
go.sum Vendor dependencies 6 years ago
ipvs.go Vendor dependencies 6 years ago
mdstat.go run 'go get -u; make revendor' 7 years ago
meminfo.go Vendor dependencies 6 years ago
mountinfo.go Vendor dependencies 6 years ago
mountstats.go run 'go get -u; make revendor' 7 years ago
net_dev.go Vendor dependencies 6 years ago
net_sockstat.go Vendor dependencies 6 years ago
net_softnet.go Vendor dependencies 6 years ago
net_unix.go Vendor dependencies 6 years ago
proc.go Vendor dependencies 6 years ago
proc_environ.go Vendor dependencies 6 years ago
proc_fdinfo.go Vendor dependencies 6 years ago
proc_io.go Vendor dependencies 6 years ago
proc_limits.go run 'go get -u; make revendor' 7 years ago
proc_ns.go run 'go get -u; make revendor' 7 years ago
proc_psi.go Vendor dependencies 6 years ago
proc_stat.go Vendor dependencies 6 years ago
proc_status.go Vendor dependencies 6 years ago
schedstat.go Vendor dependencies 6 years ago
stat.go Vendor dependencies 6 years ago
ttar run 'go get -u; make revendor' 7 years ago
vm.go Vendor dependencies 6 years ago
xfrm.go run 'go get -u; make revendor' 7 years ago
zoneinfo.go Vendor dependencies 6 years ago

README.md

procfs

This 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, 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()

Package Organization

The packages in this project are organized according to (1) whether the data comes from the /proc or /sys filesystem and (2) the type of information being retrieved. For example, most process information can be gathered from the functions in the root procfs package. Information about block devices such as disk drives is available in the blockdevices sub-package.

Building and Testing

The procfs library is intended to be built as part of another application, so there are no distributable binaries.
However, most of the API includes unit tests which can be run with make test.

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.