fix(traces): downgrade handle_proxy body-read failure from ERROR to WARN#1046
Open
litianningdatadog wants to merge 1 commit intomainfrom
Open
fix(traces): downgrade handle_proxy body-read failure from ERROR to WARN#1046litianningdatadog wants to merge 1 commit intomainfrom
litianningdatadog wants to merge 1 commit intomainfrom
Conversation
When Lambda freezes or terminates a function instance, the OS closes the TCP connection mid-request. The extension's proxy handler fails to buffer the body and logs at ERROR level, creating noise with no actionable signal. This is expected Lambda lifecycle behavior — the function completed successfully and nothing in the extension is broken. Introduce `warn_response` (mirroring `error_response`) and use it for this path so the log level correctly reflects an external event rather than an extension fault. Fixes #1000
duncanista
approved these changes
Feb 25, 2026
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.
JIRA: https://datadoghq.atlassian.net/browse/SLES-2729
Issue: #1000
Overview
When AWS Lambda freezes or terminates a function instance, the OS immediately closes all TCP sockets. The extension's proxy HTTP handler (handle_proxy) was mid-read on the request body — this read fails with error reading a body from connection and was logged at ERROR level, generating noise with no actionable signal.
This is expected Lambda lifecycle behaviour: the Lambda function completed successfully and nothing in the extension is broken. The ERROR level implies an extension fault, which misleads operators.
Change
Introduce a warn_response helper (mirroring the existing error_response / success_response trio) and use it for body-read failures in handle_proxy. The log message content is unchanged — only the severity is downgraded from ERROR to WARN.
Testing