开源软件名称：

开源软件地址：

开源软件介绍：

Node exporter

Prometheus exporter for hardware and OS metrics exposed by *NIX kernels, writtenin Go with pluggable metric collectors.

The WMI exporter is recommended for Windows users.

Collectors

There is varying support for collectors on each operating system. The tablesbelow list all existing collectors and the supported systems.

Collectors are enabled by providing a --collector.<name> flag.Collectors that are enabled by default can be disabled by providing a --no-collector.<name> flag.

Enabled by default

Disabled by default

Textfile Collector

The textfile collector is similar to the Pushgateway,in that it allows exporting of statistics from batch jobs. It can also be usedto export static metrics, such as what role a machine has. The Pushgatewayshould be used for service-level metrics. The textfile module is for metricsthat are tied to a machine.

To use it, set the --collector.textfile.directory flag on the Node exporter. Thecollector will parse all files in that directory matching the glob *.promusing the textformat.

To atomically push completion time for a cron job:

echo my_batch_job_completion_time $(date +%s) > /path/to/directory/my_batch_job.prom.$$mv /path/to/directory/my_batch_job.prom.$$ /path/to/directory/my_batch_job.prom

To statically set roles for a machine using labels:

echo 'role{role="application_server"} 1' > /path/to/directory/role.prom.$$mv /path/to/directory/role.prom.$$ /path/to/directory/role.prom

Filtering enabled collectors

The node_exporter will expose all metrics from enabled collectors by default. This is the recommended way to collect metrics to avoid errors when comparing metrics of different families.

For advanced use the node_exporter can be passed an optional list of collectors to filter metrics. The collect[] parameter may be used multiple times. In Prometheus configuration you can use this syntax under the scrape config.

  params:    collect[]:      - foo      - bar

This can be useful for having different Prometheus servers collect specific metrics from nodes.

Building and running

Prerequisites:

• Go compiler
• RHEL/CentOS: glibc-static package.

Building:

go get github.com/prometheus/node_exportercd ${GOPATH-$HOME/go}/src/github.com/prometheus/node_exportermake./node_exporter <flags>

To see all available configuration flags:

./node_exporter -h

Running tests

make test

Using Docker

The node_exporter is designed to monitor the host system. It's not recommendedto deploy it as a Docker container because it requires access to the host system.Be aware that any non-root mount points you want to monitor will need to be bind-mountedinto the container.If you start container for host monitoring, specify path.rootfs argument.This argument must match path in bind-mount of host root. The node_exporter will usepath.rootfs as prefix to access host filesystem.

docker run -d \  --net="host" \  --pid="host" \  -v "/:/host:ro,rslave" \  quay.io/prometheus/node-exporter \  --path.rootfs /host

On some systems, the timex collector requires an additional Docker flag,--cap-add=SYS_TIME, in order to access the required syscalls.

Using a third-party repository for RHEL/CentOS/Fedora

There is a community-supplied COPR repository which closely follows upstream releases.