Skip to content

Instantly share code, notes, and snippets.

@zircote
Created May 24, 2017 22:22
Show Gist options
  • Save zircote/9ab0bcff37c43a01bc5bc0c96bfff7b3 to your computer and use it in GitHub Desktop.
Save zircote/9ab0bcff37c43a01bc5bc0c96bfff7b3 to your computer and use it in GitHub Desktop.
A InfluxDB/StatsD configuration for Hashicorp Vault
# Statsd Server
[[inputs.statsd]]
## Address and port to host UDP listener on
service_address = "127.0.0.1:8126"
## The following configuration options control when telegraf clears it's cache
## of previous values. If set to false, then telegraf will only clear it's
## cache when the daemon is restarted.
## Reset gauges every interval (default=true)
delete_gauges = true
## Reset counters every interval (default=true)
delete_counters = true
## Reset sets every interval (default=true)
delete_sets = true
## Reset timings & histograms every interval (default=true)
delete_timings = true
## Percentiles to calculate for timing & histogram stats
percentiles = [90]
## separator to use between elements of a statsd metric
metric_separator = ":"
## Parses tags in the datadog statsd format
## http://docs.datadoghq.com/guides/dogstatsd/
parse_data_dog_tags = false
## Statsd data translation templates, more info can be read here:
## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md#graphite
templates = [
"vault.barrier.* measurement.measurement.field*",
"vault.core.* measurement.measurement.field*",
"vault.*.expire.* measurement.host.measurement.field*",
"vault.*.runtime.* measurement.host.measurement.field*",
"vault.policy.* measurement.measurement.field*",
"vault.rollback.* measurement.measurement.measurement.mount.field*",
"vault.route.rollback.* measurement.measurement.measurement.mount.field*",
"vault.runtime.* measurement.measurement.field*",
"vault.zookeeper.* measurement.measurement.field*"
]
## Number of UDP messages allowed to queue up, once filled,
## the statsd server will start dropping packets
allowed_pending_messages = 10000
## Number of timing/histogram values to track per-measurement in the
## calculation of percentiles. Raising this limit increases the accuracy
## of percentiles but also increases the memory usage and cpu time.
percentile_limit = 1000
@zircote
Copy link
Author

zircote commented May 24, 2017

I also suspect it can be simplified a bit but I haven't time yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment