Consider wiring up Sentry for errors
Open
- Dominant language
- Rust
- Stars
- 22
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
https://docs.sentry.io/platforms/rust/
Contributor guide
Research direction
The issue names no files, tests, or error-handling entry points. Start by reading the linked Sentry Rust documentation and inspecting the repository to locate how errors are currently handled. Before coding, clarify which errors should be reported and what successful Sentry wiring should cover.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100