mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-11-02 03:27:54 +00:00
backport of commit a53e78699f (#22397)
Co-authored-by: Peter Wilson <peter.wilson@hashicorp.com>
This commit is contained in:
committed by
GitHub
parent
d9343ea9d1
commit
72a44d0ceb
@@ -162,9 +162,12 @@ parameters found in the template configuration section in the consul-template
|
||||
[documentation
|
||||
page](https://github.com/hashicorp/consul-template/blob/main/docs/configuration.md#templates)
|
||||
can be used here:
|
||||
|
||||
<Tip>
|
||||
|
||||
The parameters marked with `Δ` below are only applicable to file templates and
|
||||
cannot be used with `env_template` entries in process supervisor mode.
|
||||
|
||||
</Tip>
|
||||
|
||||
- `source` `(string: "")` - Path on disk to use as the input template. This
|
||||
|
||||
@@ -57,29 +57,29 @@ telemetry {
|
||||
num_lease_metrics_buckets = 168
|
||||
add_lease_metrics_namespace_labels = false
|
||||
filter_default = true
|
||||
|
||||
|
||||
statsite_address = "mycompany.statsite:8125"
|
||||
}
|
||||
```
|
||||
|
||||
<Tip heading="Use a prefix filter to reduce the volume of metrics you receive">
|
||||
<Tip>
|
||||
|
||||
Many metrics solutions charge by the metric. You can set `filter_default` to
|
||||
false and use the `prefix_filter` parameter to include and exclude specific
|
||||
values based on metric name to avoid paying for irrelevant information.
|
||||
|
||||
For example, to limit your telemetry to the core token metrics plus the number
|
||||
of leases set to expire:
|
||||
|
||||
```hcl
|
||||
telemetry {
|
||||
filter_default = false
|
||||
prefix_filter = ["+vault.token", "-vault.expire", "+vault.expire.num_leases"]
|
||||
}
|
||||
```
|
||||
|
||||
</Tip>
|
||||
|
||||
For example, to limit your telemetry to the core token metrics plus the number
|
||||
of leases set to expire:
|
||||
|
||||
```hcl
|
||||
telemetry {
|
||||
filter_default = false
|
||||
prefix_filter = ["+vault.token", "-vault.expire", "+vault.expire.num_leases"]
|
||||
}
|
||||
```
|
||||
|
||||
## Step 4: Choose a reporting solution
|
||||
|
||||
You need to save or forward your telemetry data to a separate storage solution
|
||||
@@ -107,4 +107,4 @@ Popular reporting solutions compatible with Vault:
|
||||
Vault telemetry for Splunk using Telegraf and Fluentd.
|
||||
- Review the
|
||||
[Monitor telemetry with Prometheus and Grafana](/vault/tutorials/monitoring/monitor-telemetry-grafana-prometheus)
|
||||
tutorial to configure your Vault telemetry for Prometheus and Grafana.
|
||||
tutorial to configure your Vault telemetry for Prometheus and Grafana.
|
||||
|
||||
Reference in New Issue
Block a user