From 0fe36dd247f1a61e64681f275b6bda2a408a7726 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Tue, 28 Feb 2023 10:05:09 -0800 Subject: [PATCH] backport of commit e2f570f13f6e61cad78f91970b2439381ff841f2 (#16403) Co-authored-by: Poonam Jadhav Co-authored-by: Tu Nguyen --- website/content/docs/agent/limits/init-rate-limits.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/agent/limits/init-rate-limits.mdx b/website/content/docs/agent/limits/init-rate-limits.mdx index cb85d052a762..320571845309 100644 --- a/website/content/docs/agent/limits/init-rate-limits.mdx +++ b/website/content/docs/agent/limits/init-rate-limits.mdx @@ -26,7 +26,7 @@ In order to set limits for traffic, you must first understand regular and peak l 1. Observe the logs and metrics for your application's typical cycle, such as a 24 hour period. Refer to [`log_file`](/consul/docs/agent/config/config-files#log_file) for information about where to retrieve logs. Call the [`/agent/metrics`](/consul/api-docs/agent#view-metrics) HTTP API endpoint and check the data for the following metrics: - - `rpc.rate_limit.exceeded.read` - - `rpc.rate_limit.exceeded.write` + - `rpc.rate_limit.exceeded` with value `global/read` for label `limit_type` + - `rpc.rate_limit.exceeded` with value `global/write` for label `limit_type` 1. If the limits are not reached, set the `mode` configuration to `enforcing`. Otherwise adjust and iterate limits. \ No newline at end of file