From 6f46f6396dd7250902cb8146df044fece1fbdf6e Mon Sep 17 00:00:00 2001 From: Tu Nguyen Date: Mon, 27 Feb 2023 09:21:34 -0800 Subject: [PATCH] Add missing link --- .../docs/agent/limits/set-global-traffic-rate-limits.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/agent/limits/set-global-traffic-rate-limits.mdx b/website/content/docs/agent/limits/set-global-traffic-rate-limits.mdx index 466e0a25b0..5d4fc43df0 100644 --- a/website/content/docs/agent/limits/set-global-traffic-rate-limits.mdx +++ b/website/content/docs/agent/limits/set-global-traffic-rate-limits.mdx @@ -14,7 +14,7 @@ Rate limits apply to each Consul server separately and limit the number of read Because all requests coming to a Consul server eventually perform an RPC or an internal gRPC request, global rate limits apply to Consul's user interfaces, such as the HTTP API interface, the CLI, and the external gRPC endpoint for services in the service mesh. -Refer to [Initialize Rate Limit Settings]() for additional information about right-sizing your gRPC request configurations. +Refer to [Initialize Rate Limit Settings](/consul/docs/agent/limits/init-rate-limits) for additional information about right-sizing your gRPC request configurations. ## Set a global rate limit for a Consul server