mozilla-services / mozilla-services/syncstorage-rs
Sentry groups different ApiErrors w/ common stack traces together
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.8k
- Forks
- 86
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 21
Description
Sentry appears to group our ApiErrors together solely by their stack trace.
This particular event shows different ApiErrors triggered from commit_batch all under the same parent event:
https://sentry.prod.mozaws.net/operations/syncstorage-prod/issues/8179009/events/
- An attempt at a conflicting write #614
- 8-RESOURCE_EXHAUSTED #616
- 6-ALREADY_EXISTS #619
We had set the "attempt at a conflicting write" error to be ignored via Sentry, which inadvertently hid the last 2 from the dashboard completely (the ignore went away went the stack trace completely changed after the 0.3.1 deploy). (Note: We're aware of the other errors, as they were noted here: https://bugzilla.mozilla.org/show_bug.cgi?id=1623671)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Sentry event and the ApiError paths triggered from commit_batch; compare the conflicting-write, RESOURCE_EXHAUSTED, and ALREADY_EXISTS errors. Determine how their grouping and ignore behavior should distinguish these cases, then verify that each error remains separately visible in Sentry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100