<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Collaborate/take over this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=611331) </details> <!--IssueSummary end--> ## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/604452) currently behind the `audit_event_streaming_via_nats` feature flag. - DRI: @huzaifaiftikhar1 - Team Slack channel: `#sec-compliance` > [!note] > Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. > "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. > [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? The flag is a per-root-group overlay on top of the `Gitlab::Nats.enabled?` capability check. When on for a group, audit events for that group publish to NATS JetStream instead of enqueuing a Sidekiq job per event. - Blast radius is limited to the enabled root group(s); everyone else stays on the existing Sidekiq path. - Any NATS publish failure falls back to the Sidekiq path, preserving at-least-once delivery, so a NATS outage degrades to the current behaviour rather than dropping audit events. - Dashboards to watch on https://dashboards.gitlab.net: the audit event streaming NATS publish/fallback counters (`gitlab_audit_event_streaming_nats_publish_total`, `gitlab_audit_event_streaming_nats_publish_fallback_total`), the dispatch error-rate and lag apdex SLIs, and the JetStream stream/consumer depth. A rising fallback ratio is the primary signal that the NATS path is unhealthy. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#sec-compliance`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set audit_event_streaming_via_nats 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set audit_event_streaming_via_nats true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set audit_event_streaming_via_nats <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss audit_event_streaming_via_nats true /chatops gitlab run feature set --group=gitlab-org,gitlab-com audit_event_streaming_via_nats true /chatops gitlab run feature set --user=huzaifaiftikhar1 audit_event_streaming_via_nats true ``` ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check <merge-request-url> <milestone> /chatops gitlab run feature delete audit_event_streaming_via_nats --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set audit_event_streaming_via_nats false # production /chatops gitlab run feature set audit_event_streaming_via_nats false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete audit_event_streaming_via_nats --dev --pre --staging --staging-ref --production # remove entirely ```