This repository has been archived by the owner on May 2, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
How could Tutor better provide error logging & stack traces? #15
Labels
discovery
Pre-work to determine if an idea is feasible
Comments
At the time, what I had in mind was to offer a self-hosted Sentry stack to collect stacktraces across the entire Open edX platform, both for frontends and backends. Turns out that in 2022, it's incredibly difficult to run Sentry (docker-compose.yml). Maybe that we could use an alternative piece of software such as Glitchtip. |
Personally, I'd need to do some research in order to begin implementing anything, so I've turned this issue into a question/discovery item. |
I'm not seeing any acute need for this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Context
When I develop on Open edX, I sometimes stumble on errors that are hard to debug. To understand these issues, I need to have access to the error stacktrace. Currently, I do this by bind-mounting the IDA repository or virtual environment, then add a break point (
import pdb; pdb.set_trace()
) to the code and run the app in dev mode (./manage.py runserver
). This is all very inconvenient. Instead, what we could do is to collect the error logs and stacktraces using tools such as Sentry. Sentry could be added to Tutor as a plugin.Current state of error logs & stacktraces:
Note: there are different ways to approach this. Thus, the time estimate can vary.
Acceptance
Propose solution for improving the state of error tracking (or, propose that we do nothing).
The text was updated successfully, but these errors were encountered: