Open timobrembeck opened 2 years ago
Does this cover JavaScript and/or Python errors? If this is about Python errors, I would currently not use Sentry for this and keep our mechanism with logging + InfluxDB + Grafana. AFAICT this makes sense for remote software like apps. But on our servers we have our log files that are easily accessible.
The linked docs only describe how to track Python errors, so yes, it's a bit redundant. But according to the docs, it should be fairly easy to integrate everything, also the Javascript errors: https://docs.sentry.io/platforms/javascript/
Can we make this issue about tracking JS errors in the browsers? I would prefer to not transfer any server data to sentry :D I currently do not see any benefit of integrating that into the back end. Reason: Sentry itself is a deep rabbit hole and I prefer to not start pouring work into it if we do not actually need it. I see a benefit when collecting remote information, but not as a GUI to our server logs which are easy to access & read. With the latest versions Sentry is making it pretty hard to run it on premise and I'm not sure if we want to keep the service at all in the long run.
Alright, makes sense. I updated the issue description.
Motivation
To monitor Javascript errors on the user clients, it should be possible to integrate Sentry.
Proposed Solution
Follow the documentation:
Additional Context
It should be possible to configre both the sentry server and the key via the config file
/etc/integreat-cms.ini
(which means that the values need to be read from the environment variables insettings.py
).