Standardize logging fields across all index patterns for GitLab.com
## Participants - @e_forbes ## Problem Statement We know that our logging fields have grown out of hand and require some effort to standardize, put things in the right place, and have a solid answer as to what belongs in logging and what belongs in metrics. This work will be driven by the Scalability:Observability team, but will have a significant impact across all stage groups and anyone who outputs logging. We have more questions than answers at this point, but some of the understanding of the scope of this will come from https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1407 and https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1430. The single pane of glass that we expect to be an outcome of the second epic will be vital to make sure that logs and metrics are stored in the location that makes the most sense for them but are usable by the stage groups appropriately. Questions: - What the impact is - What the cost of getting it wrong is - What the value of getting it right is - Potential solutions - Labkit - Who needs to be involved ## Resources Helpful Walkthrough of Field Consolidation - HTTP Status Example Video: https://gitlab.com/groups/gitlab-org/quality/-/epics/344#note_3087260462 ## Exit Criteria <!--STATUS NOTE START--> <!--STATUS NOTE END-->
epic