Walk through of Error Tracking
Description
Starting point - https://docs.gitlab.com/ee/user/project/operations/error_tracking.html
Brief Feature Overview and Expectations
Error Tracking is important because it gives an important sensing mechanism queued into your users interactions and errors. It serves an important workflow of some real user interaction testing during development in dev environments. I expect during this walk through that I can successfully configure Sentry in GitLab and witness the interaction between Sentry collected errors and GitLab issues.
Results
- GitLab Unfiltered Video
- Notes Google Doc
- Follow up issues added as related issues
Tasks
Pre-Walk Through
-
Post to shared calendar (Group, Stage or Section ones if they exist) so that other team members can attend if they wish -
Create Google Doc - https://docs.google.com/document/d/1urj6-6WQ6gBBXcdI0tHjTZZiowZIb0ZX4UkwmdyOEcs/edit -
Update the "Brief Feature Overview and Expectations" section
During Walk Through
-
Record Video -
Start with verbalizing the Brief Feature Overview and Expectations section -
Capture notes for issues to file in the GoogleDoc
After Walk Through
-
Post recording to GitLab Unfiltered YouTube channel -
Share recording and this issue in appropriate #s_ and #g_ channels -
Create follow up issues and ping relevant product managers -
Attach issues as related to this one -
Close this issue
Edited by Kenny Johnston