Enable Apps Prometheus Metrics when OSM metrics is enabled

[vimorra]

Please describe the Improvement and/or Feature Request The proposal is to enable the prometheus metrics both from OSM but also from the application point of view. Currently when OSM metrics are enabled in the namespace, as per documentation .

prometheus.io/scrape: true prometheus.io/port: 15010 prometheus.io/path: /stats/prometheus This disable the annotations values of the apps itself, and this means that application metrics are not scraped by prometheus. So the suggestion is to add a feature to enable the coexistence of multiple metrics endpoints

Scope (please mark with X where applicable)

• New Functionality [X ]
• Install [ ]
• SMI Traffic Access Policy [ ]
• SMI Traffic Specs Policy [ ]
• SMI Traffic Split Policy [ ]
• Permissive Traffic Policy [ ]
• Ingress [ ]
• Egress [ ]
• Envoy Control Plane [ ]
• CLI Tool [ ]
• Metrics [X ]
• Certificate Management [ ]
• Sidecar Injection [X ]
• Logging [ ]
• Debugging [ ]
• Tests [ ]
• CI System [ ]
• Demo [ ]
• Project Release [ ]

Possible use cases An example scenario is in Azure AKS with Container Insight or the new managed promethus offering. https://learn.microsoft.com/en-us/azure/azure-monitor/containers/container-insights-prometheus?tabs=cluster-wide#prometheus-scraping-settings

[github-actions[bot]]

This issue will be closed due to a long period of inactivity. If you would like this issue to remain open then please comment or update.

[github-actions[bot]]

Issue closed due to inactivity.