luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

Add upgrade note for #9553. (#9563) 

* Add upgrade note for #9553.
* Note that these are metrics introduced in 1.5.0.
* Added link to docs.
This commit is contained in:
Mark Gritter 2020-07-22 14:47:48 -05:00 committed by GitHub
parent f3587c341b
commit 5d9a1caba1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
website/pages/docs/upgrading/upgrade-to-1.5.0.mdx
View File

@ -10,7 +10,7 @@ description: |-
# Overview
This page contains the list of deprecations and important or breaking changes
for Vault 1.4.x compared to 1.5.0. Please read it carefully.
for Vault 1.5.0 compared to 1.4.1. Please read it carefully.
## Raft Configuration
@ -24,3 +24,18 @@ In addition, a new metric has been introduced, `vault.raft-storage.entry_size`,
that allows for operators to sample the entry size, view the average, and adjust
the configuration value as necessary. For additional details, please see
[Raft configuration](docs/configuration/storage/raft).
## Known Issues
Enabling telemetry on 32-bit systems will cause Vault to crash. A workaround for this
issue is to disable collection of usage gauges in the [telemetry](docs/configuration/telemetry) stanza of the configuration.
```
telemetry {
...
usage_gauge_period = "none"
}
```
This will suppress the metrics `vault.identity.entity.count`, `vault.identity.entity.alias.count`, `vault.token.count`, `vault.token.count.by_auth`, `vault.token.count.by_policy`, `vault.token.count.by_ttl` and `vault.secret.kv.count` that were introduced in version 1.5.0, but all other Vault telemetry will remain available.