Sentry for logging frontend errors
Open
Technical Debt
- Dominant language
- Clojure
- Stars
- 66
- Forks
- 28
- Avg merge
- 7d 4h
- Merged PRs (30d)
- 2
Description
- [ ] investigate privacy policy features. can sentry be configured to not store e.g. IPs
- [ ] try out sentry for remsdev
- [ ] see which browser statistics could be collected with sentry
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the three checklist items and Sentry's privacy, frontend error logging, and browser-statistics capabilities; done means documenting the findings and deciding whether Sentry can be tried for remsdev.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- frontend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100