Skip to content

Error in AWS Lambda when sending custom events #1074

@PatricioPoncini

Description

@PatricioPoncini

Description

Hi, I'm using go-agent for New Relic and I'm encountering a sporadic error in some cases. The error is the following:

[NR_EXT] Telemetry client error: .... read: connection reset by peer

My Lambda function is executed multiple times, and at the end of the handler it sends a custom event to New Relic. The problem is that sometimes this custom event is skipped and not sent; instead, I get the error mentioned above.

What could be causing this? My Lambda has a generous timeout(15 seconds), so I don't think that's the reason.

Additionally, it's a Lambda that simply parses a JSON and sends it via SNS, so it doesn't contain any complex logic. As additional information, this Lambda is triggered by DynamoDB Streams. My Lambda follows the same example and timing as this one: https://github.com/newrelic/go-agent/blob/master/v3/examples/short-lived-process/main.go

Steps to Reproduce

I haven't been able to find the conditions to reproduce the error.

Expected Behavior

What I expect is that 100% of the events are sent, but approximately 1% don’t make it, and when I check the logs in CloudWatch, I find this error.

NR Diag results

In the CloudWatch logs, I see the error I mentioned earlier.

Your Environment

My environment is AWS, with a Lambda triggered by DynamoDB Streams. It's built in Go and, upon parsing a JSON, it performs a publish to SNS.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions