telegraf/plugins/inputs/vault
Sven Rebhan 8e23402305
chore: remove deprecated io/ioutils (#11678)
2022-09-20 09:37:14 -06:00
..
testdata feat: add Vault input plugin (#10198) 2021-12-10 13:10:26 -07:00
README.md chore: Fix readme linter errors for input plugins M-Z (#11274) 2022-06-08 15:22:56 -06:00
sample.conf chore(inputs_m-z): migrate sample configs into separate files (#11133) 2022-05-18 11:31:34 -05:00
vault.go docs: Remove warning not to remove go:embed (#11797) 2022-09-13 12:47:58 -05:00
vault_metrics.go feat: add Vault input plugin (#10198) 2021-12-10 13:10:26 -07:00
vault_test.go chore: remove deprecated io/ioutils (#11678) 2022-09-20 09:37:14 -06:00

README.md

Hashicorp Vault Input Plugin

The Vault plugin could grab metrics from every Vault agent of the cluster. Telegraf may be present in every node and connect to the agent locally. In this case should be something like http://127.0.0.1:8200.

Tested on vault 1.8.5

Configuration

# Read metrics from the Vault API
[[inputs.vault]]
  ## URL for the Vault agent
  # url = "http://127.0.0.1:8200"

  ## Use Vault token for authorization.
  ## Vault token configuration is mandatory.
  ## If both are empty or both are set, an error is thrown.
  # token_file = "/path/to/auth/token"
  ## OR
  token = "s.CDDrgg5zPv5ssI0Z2P4qxJj2"

  ## Set response_timeout (default 5 seconds)
  # response_timeout = "5s"

  ## Optional TLS Config
  # tls_ca = /path/to/cafile
  # tls_cert = /path/to/certfile
  # tls_key = /path/to/keyfile

Metrics

For a more deep understanding of Vault monitoring, please have a look at the following Vault documentation: