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.

Sign up for GitHub

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

Jump to bottom

when logging exceptions to Sentry, include context #1018

Closed
drewda opened this issue Mar 10, 2017 · 0 comments · Fixed by #1019
Closed

when logging exceptions to Sentry, include context #1018

drewda opened this issue Mar 10, 2017 · 0 comments · Fixed by #1019
Assignees
@drewda

Comments

@drewda
Copy link
Member

drewda commented Mar 10, 2017

When Sentry logs errors from FeedEater, FeedFetcher, and other workers/services, we aren't able to tell what feed and feed version are throwing the exception.

Looks like Sentry will take extra context in tags: https://docs.sentry.io/clients/ruby/usage/#optional-attributes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@drewda drewda

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

when logging exceptions to Sentry, include context transitland/transitland-datastore
1 participant
@drewda