## Problem HTTP status code fields are currently logged inconsistently across different components, making it difficult to correlate logs and debug issues efficiently. This is particularly problematic for GitLab Dedicated which experiences 2-3x more incidents than GitLab.com. ## Current State The following variations of HTTP status fields exist in our logs: - `status` - `status_code` - `extra.status` - `status_text` - Present in the gitlab-pages repo / data view ## Proposed Solution Standardize on a single field name for HTTP status codes following the [Observability Field Standardisation pattern](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/observability_field_standardisation/#labkit). **Migration Strategy**: To ensure zero downtime and no impact to our observability setup, we will emit both old and new fields simultaneously during the migration period. This allows time to migrate all runbooks, alerts, and dashboards before deprecating the old fields. ## Acceptance Criteria - [x] Define the canonical field name for HTTP status codes in LabKit - [ ] Audit and document all current usage of status code fields in: - [ ] Runbooks - [ ] Alerting rules - [ ] Dashboards - [ ] Update all logging implementations to emit both old and new fields simultaneously - [ ] Verify the new field is consistently available across all index patterns - [ ] Migrate all runbooks, alerts, and dashboards to use the new field - [ ] Validate that all observability tooling works correctly with the new field - [ ] Deprecate and remove old field names after successful migration - [ ] Document the migration path for existing queries ## Decisions - On some repositories, we have to rename, remove, or change the type of some fields, which introduces breaking changes, see [comment](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/work_items/4088#note_3187108898). This should be taken out of scope for this issue and added to https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/work_items/4349+ where we collect all breaking changes.