Repository navigation
Change how the relay application AWS Lambda layers logs its own activities. #1961
Description
Problem Statement
The provided AWS Lambda layer uses a relay extension to catch and distribute data to Sentry.
This relay extension writes a significant number of entries to Cloudwatch upon start and termination, which clutters logs with unneeded entries.
The requested functionality duplicates that requested in the Sentry-Javascript ticket 6921.
Solution Brainstorm
Please change the default behavior of the relay process to only write cloudwatch logs on unexpected behavior.
Reacted by Micah Engle-Eshleman
Activity
micah-redwood commentedon May 2, 2023
+1 to this! We're hoping to get our team to adopt Sentry and this is a major pain point. When log level is set to debug, CloudWatch is pretty much unusable.
antonpirker commentedon May 4, 2023
We are currently working on removing relay from the lambda layers: #2068
It did not bring the benefits we where hoping for, so with the next release of the lambda layers, the logs should be clean again.
antonpirker commentedon May 17, 2023
With our new Lambda layers we do not run
relayin the layer anymore, so all the log messages are gone. If you upgrade to the newest lambda layer @DM1145 and @micah-redwood and your logs are only yours and nothing from relay will be in there!micah-redwood commentedon May 17, 2023
Thanks @antonpirker !