-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send Request ID to Sentry #22
Comments
Hey @zupo, is it okay if I work on this? |
Sure go ahead! |
sourya
pushed a commit
to sourya/pyramid_heroku
that referenced
this issue
Sep 10, 2019
... to sentry and structlog logs Signed-off-by: Sourya Vatsyayan <sourya@deepsource.io>
sourya
pushed a commit
to sourya/pyramid_heroku
that referenced
this issue
Sep 10, 2019
... to sentry and structlog logs Signed-off-by: Sourya Vatsyayan <sourya@deepsource.io>
sourya
pushed a commit
to sourya/pyramid_heroku
that referenced
this issue
Sep 10, 2019
... to sentry and structlog logs Signed-off-by: Sourya Vatsyayan <sourya@deepsource.io>
Is this abandoned? |
Abandoned in the sense that noone is currently working on it: yes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First, read https://blog.sentry.io/2019/01/31/using-nginx-sentry-trace-errors-logs.
Second, read https://devcenter.heroku.com/articles/http-request-id.
Then here's the idea: add a tween to this package that, if Sentry is imported, binds the Request ID for all error reports. Also, if structlog is imported, it binds the Request ID for all logs..
The text was updated successfully, but these errors were encountered: