From 3095e937eb110470ee3c5f18f1f321e1ecb4c2de Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sandor=20Sz=C3=BCcs?= Date: Fri, 5 Jan 2024 14:57:09 +0100 Subject: [PATCH] explain the chunked logging and the prefix MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Sandor Szücs --- docs/reference/filters.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/docs/reference/filters.md b/docs/reference/filters.md index fddb581e5a..e9b1900b7b 100644 --- a/docs/reference/filters.md +++ b/docs/reference/filters.md @@ -732,12 +732,16 @@ Example: ### logBody -The `logBody` filter logs the request or response body while -streaming. Note that this filter should be used only in diagnostics -setup and with care, since the request and response body may contain -sensitive data, and they also can explode the amount of logs. You can -log request or response bodies. This filter has close to no overhead -other than the I/O created by the logger. +The `logBody` filter logs the request or response body in chunks while +streaming. Chunks start with `logBody("request") $flowid: `, such that +you can find all chunks belonging to a given flow. See also +[flowId()](#flowid) filter. + +Note that this filter should be used only in diagnostics setup and +with care, since the request and response body may contain sensitive +data, and they also can explode the amount of logs. You can log +request or response bodies. This filter has close to no overhead other +than the I/O created by the logger. Parameters: