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
{{ message }}
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.
I plan to work on improving the current logging setup when I have time. First sentry and I'll probably try to look into adding a configuration option for sending stack-traces by emails.
The text was updated successfully, but these errors were encountered:
I would personally prefer to have the logging in the same file as other configuration.
Does sentry send diagnostic information on crashes to the developers? As paperless can possible deal with very sensitive data (bills, taxes, healthcare) I think we should be careful about user acceptance.
I would personally prefer to have the logging in the same file as other configuration.
I would too but the configuration file is using dotenv and AFAIK there is no way to have complex key/value.
Does sentry send diagnostic information on crashes
Yes
to the developers?
No, the idea is not to have a global sentry for all paperless instances but to allow someone that has a self-hosted sentry and/or the hosted version to link his paperless instance with it. That way it's easier to investigate if one of your file didn't import. As example Gitlab and Nextcloud support sentry for error reporting.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I plan to work on improving the current logging setup when I have time. First sentry and I'll probably try to look into adding a configuration option for sending stack-traces by emails.
The text was updated successfully, but these errors were encountered: