Sentry Monitoring Retrospective
Background
We recently began a more define process for monitoring Sentry issues related to SFDC & Zuora. Since this is a new process, there are areas for improvement. This issue will be used to capture feedback on changes to the process based on the first two rounds of screening.
Details to be captured in table below.
Proposed Improvements
Summary | Details | Status | DRI | Related Issue(s)/MR(s) |
---|---|---|---|---|
Update issue template | Update issue template description based on the MR https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/8009+ to make the issue screen a bit easier. | Not yet started | TBD | |
Define other group ownership process | Define a handoff process for identified issues that should belong to another group. | Not yet started | TBD | |
Improved Sentry logging | Many different types of "Order preview in Zuora failed!" errors. Each sentry entry could have a mix of those types, making the issue linking less meaningful. Look into improving the logging, so Sentry errors are separated by type. | Not yet started | TBD | |
Consider updated weight | Consider a weight higher than one for screening issues given time spent investigating. | Not yet started | TBD | |
Update documentation | Include information about time commitment and expectations when taking on this issue. | Not yet started |
Edited by Courtney Meddaugh