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

Include more info about account, timeframe, etc. in Sentry errors #163

Closed
Mr0grog opened this issue Nov 11, 2018 · 1 comment
Closed

Include more info about account, timeframe, etc. in Sentry errors #163

Mr0grog opened this issue Nov 11, 2018 · 1 comment
Labels

Comments

@Mr0grog
Copy link
Member

Mr0grog commented Nov 11, 2018

We can usually figure out a lot about the configuration of a scraper run that errored from other anecdotal info in the error, but we should use Sentry’s breadcrumbs or contexts to be more explicit about it.

Specifically, we should make sure to include:

  • Timeframe (--before and --after)
  • Start time (of the actual run, not the timeframe being scraped)
  • Account name (relatively anonymized, like versionista1, versionista2, instead of e-mail)

We are currently on a deprecated version of the Sentry SDK (see #162). Relevant docs for it are at: https://docs.sentry.io/clients/node/

@stale
Copy link

stale bot commented May 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.

@stale stale bot added the stale label May 10, 2019
@stale stale bot closed this as completed May 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant