What are the nature and description of the request?

• We would like to have Application labels also in argocd events, the same way as it is possible to have them in Prometheus metrics (Exposing Application labels as Prometheus metrics)

3. Why does the customer need this?

• Our use case is almost the same as the one stated in the documentation for Exposing Application labels as Prometheus metrics.
  We have several Application labels which differentiate team (business application) and environment (dev/test/prod) and we would like to forward ArgoCD Application events (as well as container stdout) to central ELK, a particular index.
  Unfortunately, we don't have a strict naming convention for Kubernetes namespaces or ArgoCD applications which we could use for the correct messages distribution.

4. List any affected packages or components.

• ArgoCD

5. Additional notes

• There is an existing GitHub issue.
  • https://github.com/argoproj/argo-cd/issues/11381