From d189b667605a8973d5e6d899db8ac0544b2c6599 Mon Sep 17 00:00:00 2001 From: Eguzki Astiz Lezaun Date: Tue, 8 Oct 2024 11:07:01 +0200 Subject: [PATCH] doc: fix limits example Signed-off-by: Eguzki Astiz Lezaun --- doc/server/configuration.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/doc/server/configuration.md b/doc/server/configuration.md index 7ec1f166..b3374a06 100644 --- a/doc/server/configuration.md +++ b/doc/server/configuration.md @@ -29,10 +29,10 @@ Options: The port to listen on for HTTP [default: 8080] -l, --limit-name-in-labels Include the Limit Name in prometheus label + --tracing-endpoint + The host for the tracing service [default: ] -v... Sets the level of verbosity - --tracing-endpoint - The endpoint for the tracing service --validate Validates the LIMITS_FILE and exits -H, --rate-limit-headers @@ -90,13 +90,13 @@ required: Here is an example of such a limit definition: ```yaml -namespace: example.org -max_value: 10 -seconds: 60 -conditions: - - "req.method == 'GET'" -variables: - - user_id +- namespace: example.org + max_value: 10 + seconds: 60 + conditions: + - "req.method == 'GET'" + variables: + - user_id ``` - `namespace` namespaces the limit, will generally be the domain, [see here](../how-it-works.md)