倒排索引/搜索引擎>> zfs_exporter>> 返回
项目作者： pdf

项目描述 ：
Prometheus ZFS exporter
高级语言： Go
项目地址: git://github.com/pdf/zfs_exporter.git
创建时间： 2018-11-08T11:14:35Z
项目社区：https://github.com/pdf/zfs_exporter
开源协议：MIT License
下载


ZFS Exporter

Test
Release
Go Report Card
License

Prometheus exporter for ZFS (pools, filesystems, snapshots and volumes). Other implementations exist, however performance can be quite variable, producing occasional timeouts (and associated alerts). This exporter was built with a few features aimed at allowing users to avoid collecting more than they need to, and to ensure timeouts cannot occur, but that we eventually return useful data:

  • Pool selection - allow the user to select which pools are collected
  • Multiple collectors - allow the user to select which data types are collected (pools, filesystems, snapshots and volumes)
  • Property selection - allow the user to select which properties are collected per data type (enabling only required properties will increase collector performance, by reducing metadata queries)
  • Collection deadline and caching - if the collection duration exceeds the configured deadline, cached data from the last run will be returned for any metrics that have not yet been collected, and the current collection run will continue in the background. Collections will not run concurrently, so that when a system is running slowly, we don’t compound the problem - if an existing collection is still running, cached data will be returned.

Installation

Download the latest release for your platform, and unpack it somewhere on your filesystem.

You may also build the latest version using Go v1.11 - 1.17 via go get:

  1. go get -u github.com/pdf/zfs_exporter

Installation can also be accomplished using go install:

  1. version=latest # or a specific version tag
  2. go install github.com/pdf/zfs_exporter@$version

Usage

  1. usage: zfs_exporter [<flags>]
  4. Flags:
  5.   -h, --[no-]help                Show context-sensitive help (also try --help-long and --help-man).
  6.       --[no-]collector.dataset-filesystem  
  7.                                  Enable the dataset-filesystem collector (default: enabled)
  8.       --properties.dataset-filesystem="available,logicalused,quota,referenced,used,usedbydataset,written"  
  9.                                  Properties to include for the dataset-filesystem collector, comma-separated.
  10.       --[no-]collector.dataset-snapshot  
  11.                                  Enable the dataset-snapshot collector (default: disabled)
  12.       --properties.dataset-snapshot="logicalused,referenced,used,written"  
  13.                                  Properties to include for the dataset-snapshot collector, comma-separated.
  14.       --[no-]collector.dataset-volume  
  15.                                  Enable the dataset-volume collector (default: enabled)
  16.       --properties.dataset-volume="available,logicalused,referenced,used,usedbydataset,volsize,written"  
  17.                                  Properties to include for the dataset-volume collector, comma-separated.
  18.       --[no-]collector.pool      Enable the pool collector (default: enabled)
  19.       --properties.pool="allocated,dedupratio,fragmentation,free,freeing,health,leaked,readonly,size"  
  20.                                  Properties to include for the pool collector, comma-separated.
  21.       --web.telemetry-path="/metrics"  
  22.                                  Path under which to expose metrics.
  23.       --[no-]web.disable-exporter-metrics  
  24.                                  Exclude metrics about the exporter itself (promhttp_*, process_*, go_*).
  25.       --deadline=8s              Maximum duration that a collection should run before returning cached data. Should be set to a value shorter than your scrape timeout duration. The current collection run will continue and update the cache when
  26.                                  complete (default: 8s)
  27.       --pool=POOL ...            Name of the pool(s) to collect, repeat for multiple pools (default: all pools).
  28.       --exclude=EXCLUDE ...      Exclude datasets/snapshots/volumes that match the provided regex (e.g. '^rpool/docker/'), may be specified multiple times.
  29.       --[no-]web.systemd-socket  Use systemd socket activation listeners instead of port listeners (Linux only).
  30.       --web.listen-address=:9134 ...  
  31.                                  Addresses on which to expose metrics and web interface. Repeatable for multiple addresses. Examples: `:9100` or `[::1]:9100` for http, `vsock://:9100` for vsock
  32.       --web.config.file=""       Path to configuration file that can enable TLS or authentication. See: https://github.com/prometheus/exporter-toolkit/blob/master/docs/web-configuration.md
  33.       --log.level=info           Only log messages with the given severity or above. One of: [debug, info, warn, error]
  34.       --log.format=logfmt        Output format of log messages. One of: [logfmt, json]
  35.       --[no-]version             Show application version.

Collectors that are enabled by default can be negated by prefixing the flag with --no-*, ie:

  1. zfs_exporter --no-collector.dataset-filesystem

TLS endpoint

EXPERIMENTAL

The exporter supports TLS via a new web configuration file.

  1. ./zfs_exporter --web.config.file=web-config.yml

See the exporter-toolkit https package for more details.

Caveats

The collector may need to be run as root on some platforms (ie - Linux prior to ZFS v0.7.0).

Whilst inspiration was taken from some of the alternative ZFS collectors, metric names may not be compatible.

Alternatives

In no particular order, here are some alternative implementations: