You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
What's the purpose of logging if messages are truncated ? At least it should be configurable #6056
Hi @onaly , Thanks for the request. To ensure the fix addresses your needs, could you share a bit more context on your specific use case and how you would prefer to configure these logging limits in your workflow?
I reproduced the logging use case with a real InMemoryRunner and a local
scripted model: a tool returns a long diagnostic dictionary whose error detail
falls after the 300-character cutoff, so the console output omits the error.
Would two keyword-only LoggingPlugin constructor options, max_content_length=200 and max_args_length=300, with None disabling
truncation, fit the intended direction? I have a small patch preserving the
current defaults, with 31 logging tests passing on Python 3.10 through 3.14 and
a runner reproduction. I will open it as a draft for concrete review of this
proposal, pending agreement on the API.
@sanketpatil06 I've opened #7489 with configurable max_content_length / max_args_length options on LoggingPlugin (current defaults unchanged, None disables truncation), with tests. It replaces #7079, which closed automatically when I deleted my fork. Happy to adjust the API if you'd prefer a different shape.
adk-python/src/google/adk/plugins/logging_plugin.py
Line 315 in 89f6e59