For Service Mesh 3, we should look to introduce a handful of custom metrics that help to measure, in order of priority:

• Istio version counts (# of Control planes at each Istio version).
• Envoy Proxy counts (managed by an Istiod) - Is there a way to categorize as a sidecar, waypoint or gateway?
• ZTunnel counts (or potentially whether Ambient Mode is used/how many namespaces are configured for ambient mode)
• Namespace counts (managed by an Istiod) - not sure this is feasible

We could consider other metrics, though we are significantly limited in what we are able to report due to data collection and cardinality limitations. Even the above will need careful consideration to limit cardinality. There will need to be an investigation (spike) into the feasibility of collecting the above data.

Related: https://rhobs-handbook.netlify.app/products/openshiftmonitoring/telemetry.md/

AC:

• Get familiar with sending new metrics to the Red Hat Telemetry service.
  Related: https://rhobs-handbook.netlify.app/products/openshiftmonitoring/telemetry.md/
• Get famiilar with Telemetry metrics types and data collection
  Related: https://github.com/istio/istio/tree/master/pkg/monitoring
• Outline feasible implementation of new custom metrics data collection above and draft a plan in
  https://issues.redhat.com/browse/OSSM-11378