Skip to content
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

Configure Sentry for error/crash report aggregation #406

Closed
motin opened this issue Jul 16, 2019 · 2 comments · Fixed by #434
Closed

Configure Sentry for error/crash report aggregation #406

motin opened this issue Jul 16, 2019 · 2 comments · Fixed by #434
Assignees

Comments

@motin
Copy link
Contributor

motin commented Jul 16, 2019

This supports resolving #255

Docs: https://sentry.io/for/python/, https://github.com/getsentry/sentry-python

@motin
Copy link
Contributor Author

motin commented Jul 22, 2019

With PR #415, activation of Sentry works fine (tried in a GCP crawl) and uncaught exceptions are caught. This at least allows us to get some notification on uncaught exceptions in a crawl.

In an additional PR, I hope that we can also report the caught exceptions to sentry so that we can get a good overview of what is causing driver-related crashes in the crawls.

Also, integrating with the OpenWPM logger (eg sending log messages to Sentry as well as per https://docs.sentry.io/platforms/python/logging/#usage) allows accessing the relevant log scrollback for each reported exception.

@englehardt Care to set that up? I am not sure where to best add that code.

@motin
Copy link
Contributor Author

motin commented Jul 31, 2019

Possibly useful for crawls as well, adding Redis commands as breadcrumbs: https://docs.sentry.io/platforms/python/redis/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant