Remove relay extension from AWS layer #2068
Conversation
sl0thentr0py
force-pushed
the
neel/remove-relay-aws
branch
from
daa3804
to
47ab86d
Compare
sl0thentr0py
force-pushed
the
neel/remove-relay-aws
branch
2 times, most recently
from
2f4e16b
to
13853af
Compare
sl0thentr0py
force-pushed
the
neel/remove-relay-aws
branch
from
13853af
to
2bb95b3
Compare
* Add `loguru` integration Actually, this is the solution in comments under #653 adapted to codebase and tested as well. #653 (comment) I also changed `logging` integration to use methods instead of functions in handlers, as in that way we can easily overwrite parts that are different in `loguru` integration. It shouldn't be a problem, as those methods are private and used only in that file. --------- Co-authored-by: Anton Pirker <anton.pirker@sentry.io>
we're reverting back to the older setup since the whole 'relay as AWS extension' experiment didn't really work out. * revert port override in DSN * remove gh action that bundles relay * zip in place as part of `make build_aws_lambda_layer` part of getsentry/team-webplatform-meta#58
|
I came across this issue while investigating how to setup the aws lambda extension for some python lambdas I have integrated with sentry. My original goal was to improve lambda performance when events are delivered to sentry.io. I found docs on how to setup a more point and click integration with lambda here: https://docs.sentry.io/product/integrations/cloud-monitoring/aws-lambda/#configure but these don't seem to have limited configuration support through a few environment variables, where I have specific config for the sentry python sdk and a few integrations that don't appear to be supported. Is the lambda extension running relay no longer supported? |
we're reverting back to the older setup since the whole 'relay as AWS extension' experiment didn't really work out.
make build_aws_lambda_layerpart of getsentry/team-webplatform-meta#58