backport of commit b2580d4 (#26604)

Co-authored-by: CJ <105300705+cjobermaier@users.noreply.github.com>
hashicorp · Apr 23, 2024 · 66e3e94 · 66e3e94
1 parent dba2312
commit 66e3e94
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 1 deletion.
diff --git a/website/content/docs/internals/telemetry/key-metrics.mdx b/website/content/docs/internals/telemetry/key-metrics.mdx
@@ -23,7 +23,7 @@ This document consists of five metrics sections: core, usage, storage backend, a
 
 #### Background:
 
-![Recommended architecture](/img/vault/vault-integrated-storage-reference-architecture.svg)
+![Recommended architecture](/img/vault-integrated-storage-reference-architecture.svg)
 
 The diagram illustrates a highly available Vault cluster with five nodes distributed between three availability zones. Vault's Integrated Storage uses a consensus protocol to provide consistency across the cluster nodes. The leader (active) node is responsible for ingesting new log entries, replicating them to the follower (standby) nodes, and managing when to commit an entry. Integrated Storage uses consensus protocol to provide consistency; therefore, if the leader is lost, the voting nodes will elect a new leader. Refer to the [Integrated storage](/vault/docs/internals/integrated-storage) documentation for more details.
 

diff --git a/website/public/img/vault-integrated-storage-reference-architecture.svg b/website/public/img/vault-integrated-storage-reference-architecture.svg