Skip to content
This repository has been archived by the owner on May 2, 2024. It is now read-only.

How could Tutor better provide error logging & stack traces? #15

Closed
kdmccormick opened this issue Jan 27, 2022 · 3 comments
Closed

How could Tutor better provide error logging & stack traces? #15

kdmccormick opened this issue Jan 27, 2022 · 3 comments
Labels
discovery Pre-work to determine if an idea is feasible

Comments

@kdmccormick
Copy link
Collaborator

kdmccormick commented Jan 27, 2022

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).

@kdmccormick kdmccormick changed the title . As a developer, I want to collect error logs and stacktraces across multiple concurrently running IDAs Jan 27, 2022
@regisb
Copy link

regisb commented Feb 4, 2022

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.

@kdmccormick kdmccormick changed the title As a developer, I want to collect error logs and stacktraces across multiple concurrently running IDAs How could Tutor better provide error logging & stack traces? Feb 17, 2022
@kdmccormick kdmccormick added the discovery Pre-work to determine if an idea is feasible label Feb 17, 2022
@kdmccormick
Copy link
Collaborator Author

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.

@kdmccormick
Copy link
Collaborator Author

I'm not seeing any acute need for this.

@kdmccormick kdmccormick closed this as not planned Won't fix, can't repro, duplicate, stale Mar 28, 2024
@github-project-automation github-project-automation bot moved this from 📋 To Do to 🚀 Closed in Tutor DevEnv Adoption Mar 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
discovery Pre-work to determine if an idea is feasible
Projects
None yet
Development

No branches or pull requests

2 participants