Document a process for reviewing error logs
Overview
Now we have https://gitlab.com/gitlab-org/developer-relations/contributor-success/lee-testing/error-tracking-test/-/error_tracking we need to find a way to take advantage of it.
Is there anything more we need to make this useful? (collaborate with @sguyon)
I personally think Error Tracking: Support for user data (gitlab-org/opstrace/opstrace#2345 - closed) will help a lot
We should document what we come up with.
We also need to repoint the error tracking config to log to "this" project rather than the one above if we're ready to do that?
Impacted categories
The following categories relate to this issue:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Edited by Lee Tickett