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

Intent to add remote logging capabilities #96

Open
mkhorton opened this issue May 1, 2019 · 1 comment
Open

Intent to add remote logging capabilities #96

mkhorton opened this issue May 1, 2019 · 1 comment

Comments

@mkhorton
Copy link
Member

mkhorton commented May 1, 2019

We've having a lot of different users have VASP jobs fail for various reasons, and we'd like the capability to be able to aggregate Custodian errors so that we can more easily tell if there are errors that are occurring more often than would be expected (that is, that they reflect an underlying weakness in our input sets or error handlers, rather than user error).

I'd like to propose we integrate Sentry support via their Python client.

By default, this will result in no change to Custodian by default, except an additional optional dependency. However, if you set a SENTRY_DSN environment variable, we can set it up to log and aggregate errors automatically.

If there are no objections to this, I will go ahead and implement.

I think a similar addition to log stack traces in FireWorks when jobs fizzle might also be useful.

@shyuep
Copy link
Member

shyuep commented May 1, 2019 via email

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

No branches or pull requests

2 participants