Resolving issues found in application logs
@lathrops1 @deniskar I don't know what you have in mind for this however I have provided an approach that is similar to what we already follow when we find issues via logs.
I suggest we add these to our Collaboration Rituals once the processed in agreed.
- A member of the Coko-NCBI BCMS team identifies an issue because a deployment has crashed or a user experiences an error that is not explained in the UI.
- The issue will be reported as a Bug ticket in Gitlab, and
- If the issue blocks NCBI from doing their critical daily work or any necessary testing, will give the issue a Blocker label, or
- If the issue does not block NCBI from doing their critical daily work, will give the issue a High Priority label.
- Any Blocker Gitlab issues will also be posted to the NCBI and Coko team Mattermost channel, with a ping to the Coko lead developer and project manager so that they are notified to address the issue.
- Coko developers (with NCBI developer collaboration as necessary or useful) will investigate the logs to identify the root cause of the problem.
- Coko developers will update the description of the problem and propose a solution to it in the Gitlab issue.
- If the issue is a Blocker, Coko developers will ping NCBI Product Owner in Mattermost to review the proposal with NCBI Technical staff as necessary to approve the work to begin ASAP.
- Any issue that is not a Blocker, will be added to the Backlog for triage as the next Backlog Refinement meeting.