[[_TOC_]] ## Overview This epic is for all the issues that represent a first iteration of emitting namespace-level webhook audit events. As we are SaaS-first, implementing group and project level audit events to an external source is the first thing we should tackle. Consider reading the [parent epic](https://gitlab.com/groups/gitlab-org/-/epics/5925) for additional context. ## Overall Goals * Root-group/Namespace owners should be able to modify a setting within the group settings. e.g. "Audit event HTTP destination." This should take, and validate a URL as its input. * All audit events created for that group, all subgroups and all projects within those groups and subgroups should be sent, via HTTPS, as JSON in the same format that we currently store audit logs in `log/audit_json.log` on self-managed instances. ## Implementation Issues * Development of this epic's issues should be behind a ~"feature flag" * ~backend [Set audit event HTTP destination](https://gitlab.com/gitlab-org/gitlab/-/issues/332746) * ~backend [Emit audit event to HTTP destination](https://gitlab.com/gitlab-org/gitlab/-/issues/332747) <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->