jneves / zappa-sentry

Glue with decent defaults for adding sentry to a zappa app

zappa-sentry

Sentry handler configuration with defaults for zappa lambdas.

Installation

pip install zappa_sentry

Zappa configuration

Setup your sentry DSN as the value of environment variable SENTRY_DSN, either on the zappa_setting.json file or in any of the other methods on https://github.com/miserlou/zappa/#setting-environment-variables

Then you can setup the zappa_sentry.unhandled_exceptions handler.

Example:

{
    "dev": {
        ...
        "environment_variables": {
            "SENTRY_DSN": "https://*key*:*pass*@sentry.io/*project*",
            ...
        },
        "exception_handler": "zappa_sentry.unhandled_exceptions",
        ...
    },
    ...
}

And that's all. Deploy your zappa function and you should see any errors appearing on sentry.

If you want the exception handler to capture the exception and capture it, just replace zappa_sentry.unhandled_exceptions by zappa_sentry.capture_exceptions. This version won't let the exceptions propagate.

Adding extra information

Just add it to the scope as normal for the new sentry-sdk: https://docs.sentry.io/enriching-error-data/context/?platform=python

zappa-sentry's Issues

Use SQSproxy to send exceptions to sentry

If my lambda is running inside a VPC I can't sent exception data to sentry directly, to fix this I need to configure a NAT on my VPC.

Or, I can use something like this: https://github.com/Netflix-Skunkworks/raven-sqs-proxy

But it need to be configurate to run on lambda. This workaround works only on server instance.

compared to netflix raven library

Hey it's great to see stuff like this that make it easier to use serverless with other services. Wondering if you have tried this project from netflix? I like that this one specifically calls out zappa :)

Does this package work with a Django project ?

Unfortunately this didnt work with my django project, do you have any pointers on how to get it working ? or is there a known pitfall ?

Thanks

Exception handler shou;dn

Or maybe we should have 2 handlers, where one explicitly eats the exceptions and the default one doesn't, so retries work and tracing is correctly informed of failures..

Don't create client on import so it's easier to test and doesn't slow down loading