Practise the standard verbs for managing Sentry error grouping and triage.
0 / 5 completed
1 / 5
Fill in: 'We ___ a custom fingerprint on errors that share a root cause but differ only in dynamic values like a user ID.'
We 'set a fingerprint' — the standard, established Sentry collocation for controlling how errors are grouped. The other options aren't the recognised term here.
2 / 5
Fill in: 'Leaving default grouping on a dynamic error message can ___ the same underlying bug split across hundreds of separate issues.'
We say default grouping will 'leave' one bug fragmented — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ resolved issues weekly so a genuinely fixed bug doesn't keep cluttering the active error list.'
We 'review issues' — the standard, simple collocation for periodically going through a list. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ an issue to the owning team automatically based on the file path in the stack trace.'
We 'assign an issue' — the standard, established collocation for routing a bug report to an owner. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ noisy, low-value errors so real regressions aren't buried under thousands of expected, ignorable warnings.'
We 'mute' an error — the standard, established Sentry collocation for silencing a known, non-actionable issue. The other options aren't the recognised term here.