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
1 maintainer
Metadata
1 maintainer
Release files for zappa-sentry 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| zappa_sentry-0.4.1.tar.gz | 2.3 kB | Without provenance | Details |
Release files / zappa_sentry-0.4.1.tar.gz
| Download URL | zappa_sentry-0.4.1.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f41f954c903584aa729974bacfd033d293661268cd890ae044555dd0dd582e32
|
|
BLAKE2b-256 checksum How to use checksums |
5ec66f2b6395306a94691a0323f31738c5842aeed04d915f1896d8252de5cbab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.9
|
Security for zappa-sentry 0.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
