guardian / guardian/dotcom-rendering
Spike - How to improve Sentry usage [Placeholder]
Open
- Dominant language
- TypeScript
- Stars
- 274
- Forks
- 34
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 121
Description
Explore how we can improve our usage of Sentry. Currently we rarely look at Sentry dashboards as it's very noisy and confusing. We also don't use their alerting system (though this might be that we don't have this feature in our contract). Lets spike and create sub-tasks for the things we can do to help us use Sentry in a better way
Contributor guide
Research direction
Start by reviewing the current Sentry dashboards and the availability of Sentry alerting in the existing contract. Document the sources of noise and confusion, identify practical improvements, and create sub-tasks for the agreed follow-up work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100