From e8e084fc6cfc512ccc9bf8af8d3fae4fe5b026fc Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Wed, 10 Jul 2024 09:48:36 -0700 Subject: [PATCH] Backport of Fix broken link in wal-logstore/index.mdx into release/1.19.x (#21291) backport of commit 9d4e98b4cb5202c09eb751fbf7c55fed002d8d89 Co-authored-by: Will Jordan --- website/content/docs/agent/wal-logstore/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/agent/wal-logstore/index.mdx b/website/content/docs/agent/wal-logstore/index.mdx index 77dc1dd05846..b215db158c8b 100644 --- a/website/content/docs/agent/wal-logstore/index.mdx +++ b/website/content/docs/agent/wal-logstore/index.mdx @@ -32,7 +32,7 @@ To mitigate risks associated with sudden bursts of log data, Consul tries to lim But the larger the file, the more likely it is to have a large freelist or suddenly form one after a burst of writes. For this reason, the many of Consul's default options associated with snapshots, truncating logs, and keeping the log history aggressively keep BoltDT small rather than using disk IO more efficiently. -Other reliability issues, such as [raft replication capacity issues](/consul/docs/agent/telemetry#raft-replication-capacity-issues), are much simpler to solve without the performance concerns caused by storing more logs in BoltDB. +Other reliability issues, such as [raft replication capacity issues](/consul/docs/agent/monitor/telemetry#raft-replication-capacity-issues), are much simpler to solve without the performance concerns caused by storing more logs in BoltDB. ### WAL approaches storage issues differently