From 67e28c94ed3286e44640380c069d41a460744e4e Mon Sep 17 00:00:00 2001 From: Kevin Sheldrake Date: Thu, 11 Jan 2024 11:49:19 +0000 Subject: [PATCH] Docs: improve rate limit documentation The documentation describes the rateLimit action flag. This applies per thread. Improve the documentation to make that clear. Signed-off-by: Kevin Sheldrake --- docs/content/en/docs/concepts/tracing-policy/selectors.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/content/en/docs/concepts/tracing-policy/selectors.md b/docs/content/en/docs/concepts/tracing-policy/selectors.md index 91804ea55e..56b8a34cc8 100644 --- a/docs/content/en/docs/concepts/tracing-policy/selectors.md +++ b/docs/content/en/docs/concepts/tracing-policy/selectors.md @@ -811,9 +811,10 @@ This action allows you to specify parameters for the `Post` action. `Post` takes the `rateLimit` parameter with a time value. This value defaults to seconds, but post-fixing 'm' or 'h' will cause the value to be interpreted in minutes or hours. When this parameter is specified for an action, that -action will check if the same action has fired within the time window, with the -same inspected arguments. (Only the first 16 bytes of each inspected argument -is used in the matching. Only supported on kernels v5.3 onwards.) +action will check if the same action has fired, for the same thread, within +the time window, with the same inspected arguments. (Only the first 40 bytes +of each inspected argument is used in the matching. Only supported on kernels +v5.3 onwards.) For example, you can specify a selector to only generate an event every 5 minutes with adding the following action and its paramater: