Commit 3774b8a0 authored by Ben Bodenmiller's avatar Ben Bodenmiller Committed by Evan Read

Clarify RPC concurrency limit details

parent cedb39e9
...@@ -800,6 +800,12 @@ You can observe the behavior of this queue using the Gitaly logs and Prometheus: ...@@ -800,6 +800,12 @@ You can observe the behavior of this queue using the Gitaly logs and Prometheus:
- `gitaly_rate_limiting_queued`. - `gitaly_rate_limiting_queued`.
- `gitaly_rate_limiting_seconds`. - `gitaly_rate_limiting_seconds`.
The metric definitions are available:
- Directly from Prometheus `/metrics` endpoint configured for Gitaly.
- Using [Grafana Explore](https://grafana.com/docs/grafana/latest/explore/) on a
Grafana instance configured against Prometheus.
NOTE: NOTE:
Although the name of the Prometheus metric contains `rate_limiting`, it's a concurrency limiter, not Although the name of the Prometheus metric contains `rate_limiting`, it's a concurrency limiter, not
a rate limiter. If a Gitaly client makes 1,000 requests in a row very quickly, concurrency doesn't a rate limiter. If a Gitaly client makes 1,000 requests in a row very quickly, concurrency doesn't
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment