Extension Error Reading A Body From Connection

[ggoranov-smar]

Hi Team!

We are currently using this lambda extension for tracing and we are experiencing failed lambda invocations with error log from the extension itself:

DD_EXTENSION | ERROR | TRACE_AGENT | handle_proxy | Error extracting request body: Failed to buffer the request body: error reading a body from connection

As far as I understand this is caused by the AWS Lambda runtime freezing or terminating the lambda instance without gracefully waiting for all traces to be processed. The business logic in the lambda function executes without issues so this does not cause any serious issues, just noise in the logs and maybe missing traces.

Is this understanding correct? Do you guys have a suggestion for how to setup the Lambda to avoid these error logs?

[duncanista]

Hey @ggoranov-smar,

Could you tell me which Extension version are you using?
Which runtime (node, python, .net, java, ruby, go, other) are you experiencing the error with?

Which products do you have enabled?

Based on this I might try to understand your problem properly

[ggoranov-smar]

Hey @duncanista,

Here are the requested details:

• Datadog Lambda Extension Version: 92
• Lambda Runtime: Go
• Go Packages:
  • github.com/DataDog/dd-trace-go/contrib/net/http/v2 v2.5.0
  • github.com/DataDog/dd-trace-go/v2 v2.5.0
  • gopkg.in/DataDog/dd-trace-go.v1 v1.74.0 -> This one I just noticed. I should replace it with the one above and see if the error persists.

Can you guide me how to get the products enabled? I know we use tracing, metrics and monitors for sure, no log shipping.