Commit c96c15c
authored
fix(traces): downgrade handle_proxy body-read failure from ERROR to WARN (#1046)
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
- unit tests1 parent 12703d9 commit c96c15c
1 file changed
+8
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
659 | 659 | | |
660 | 660 | | |
661 | 661 | | |
662 | | - | |
| 662 | + | |
663 | 663 | | |
664 | 664 | | |
665 | 665 | | |
| |||
721 | 721 | | |
722 | 722 | | |
723 | 723 | | |
| 724 | + | |
| 725 | + | |
| 726 | + | |
| 727 | + | |
| 728 | + | |
| 729 | + | |
| 730 | + | |
724 | 731 | | |
725 | 732 | | |
726 | 733 | | |
| |||
0 commit comments