Sentry groups different ApiErrors w/ common stack traces together
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- backend, observability
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.
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)
- Dominant language
- Rust
- Stars
- 1.8k
- Forks
- 86
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 28
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from mozilla-services/syncstorage-rs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mozilla-services/syncstorage-rs#2670 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mozilla-services/syncstorage-rs#2596 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mozilla-services/syncstorage-rs#2653 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
mozilla-services/syncstorage-rs#2652 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
mozilla-services/syncstorage-rs#2651 ·
Maintainers usually reply within 1 day
All issues in mozilla-services/syncstorage-rs
Similar issues
-
agent duplicate providers tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
founders_reward panics on a configured Testnet when the slow-start subsidy is not a multiple of 5Openexternal-contribution
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ZcashFoundation/zebra#11792 ·
Maintainers usually reply within 1 day
-
content:edit documentation effort:high
Difficulty 1/5 1-3 hours Newbie friendliness 67/100
cloudflare/cloudflare-docs#34428 ·
Maintainers usually reply within 1 day
-
area/cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100