scottk/vault
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/vault.git synced 2025-11-02 19:47:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs updates about redirection and metrics (#24445)

Browse Source 
* docs updates

* remove comma
This commit is contained in:
miagilepner
2023-12-11 15:49:38 +01:00
committed by GitHub
parent 1dfce2a271
commit 2db1941fd8
2 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
website/content/docs/configuration/telemetry.mdx
View File

@@ -187,6 +187,11 @@ These `telemetry` parameters apply to
The `/v1/sys/metrics` endpoint is only accessible on active nodes The `/v1/sys/metrics` endpoint is only accessible on active nodes
and automatically disabled on standby nodes. You can enable the `/v1/sys/metrics` and automatically disabled on standby nodes. You can enable the `/v1/sys/metrics`
endpoint on standby nodes by [enabling unauthenticated metrics access][telemetry-tcp]. endpoint on standby nodes by [enabling unauthenticated metrics access][telemetry-tcp].
Standby nodes will never forward a request to `/v1/sys/metrics` to the active
node. If unauthenticated metrics access is enabled, the standby node will
respond with its own metrics. If unauthenticated metrics access is not enabled,
then a standby node will attempt to service the request but fail and then
redirect the request to the active node.
Querying `/v1/sys/metrics` with one of the following headers: Querying `/v1/sys/metrics` with one of the following headers:

2
website/content/docs/enterprise/performance-standby.mdx
View File

@@ -21,6 +21,8 @@ that do not modify Vault's storage.
Performance Standbys require the request forwarding method described in the [HA Performance Standbys require the request forwarding method described in the [HA
Server-to-Server](/vault/docs/concepts/ha#server-to-server-communication) docs. Server-to-Server](/vault/docs/concepts/ha#server-to-server-communication) docs.
Unlike regular standby nodes, performance standbys will **not** respect the
`X-Vault-No-Request-Forwarding` header.
A performance standby will connect to the active node over the existing request A performance standby will connect to the active node over the existing request
forwarding connection. If selected by the active node to be promoted to a forwarding connection. If selected by the active node to be promoted to a