mirror of https://github.com/hashicorp/consul
backport of commit e2f570f13f
(#16403)
Co-authored-by: Poonam Jadhav <poonam.jadhav@hashicorp.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>pull/16463/head
parent
d4f51f70fc
commit
0fe36dd247
|
@ -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.
|
Loading…
Reference in New Issue