You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
On Wed, May 1, 2019 at 12:55 Matthew Horton ***@***.***> wrote:
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 <https://www.sentry.io> 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.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#96>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAEM4UYGWE2SRNPCANF53WTPTHYS5ANCNFSM4HJW7FVQ>
.
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.
The text was updated successfully, but these errors were encountered: