Only log full webhook payload when small - #352
Merged
Merged
Conversation
Webhook debug logging previously wrote the full event payload on every send. For image messages with base64 data this can be tens of MB, producing oversized log lines and unbounded disk growth on resource-constrained hosts. Now the full payload is logged only when under 8KB; larger payloads log metadata (user, instance, byte size) instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Webhook debug logging previously wrote the full event payload on every send. For image messages with base64 data this can be tens of MB, producing oversized log lines and unbounded disk growth on resource-constrained hosts. Now the full payload is logged only when under 8KB; larger payloads log metadata (user, instance, byte size) instead.