cityofaustin / cityofaustin/techstack
Send Production Joplin Errors to Slack
Open
Joplin Alpha
Team: Dev
- Dominant language
- No language data
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
As a dev, I want to know when errors happen in Joplin. We should be notified of errors before an author notifies us.
Tasks:
- [ ] Make a logger for all 500 Internal Server Errors in Joplin
- [ ] Send those logs to a dedicated slack channel for errors
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating how Joplin handles production 500 Internal Server Errors and how logging or Slack notifications are configured. Done means those errors are logged and delivered to a dedicated Slack channel for errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100