From 2d6a2a76d60715ad484aa3208404388f293f96b0 Mon Sep 17 00:00:00 2001 From: Twisha Bansal <58483338+twishabansal@users.noreply.github.com> Date: Mon, 9 Feb 2026 11:55:18 +0530 Subject: [PATCH] Update docs/en/samples/pre_post_processing/_index.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- docs/en/samples/pre_post_processing/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/samples/pre_post_processing/_index.md b/docs/en/samples/pre_post_processing/_index.md index e7f758acd5..7b4ffd22ff 100644 --- a/docs/en/samples/pre_post_processing/_index.md +++ b/docs/en/samples/pre_post_processing/_index.md @@ -61,7 +61,7 @@ It is helpful to understand how tool-level processing differs from other scopes: ### Observability & Debugging - **Structured Logging**: Instead of simple print statements, use structured JSON logging with correlation IDs. This allows you to trace a single user request through multiple agent turns and tool calls. -- **Redundant Logging for Testability**: LLM responses are non-deterministic and may summarize away key details. +- **Logging for Testability**: LLM responses are non-deterministic and may summarize away key details. - **Pattern**: Add explicit logging markers in your post-processing middleware (e.g., `logger.info("ACTION_SUCCESS: ")`). - **Benefit**: Your integration tests can grep logs for these stable markers to verify tool success, rather than painfully parsing variable natural language responses.