Currently, Cluster has an alt_stat_name field that is used for stats only. It seems that this would be useful for both tracing and access logs (to the extent that service names appear that at all). This allows for a semantically meaningful label to be consumed by monitoring and humans, regardless of the resource name (which might be reflecting addressing or config pipeline artifacts, e.g. when we start using xdstp:// URLs).

I'd like to propose we either repurpose alt_stat_name as the general observability name or create an explicit, more general, observability_name that applies across stats/logging/tracing. Within Envoy, we would have a clean C++ abstraction to access this in ClusterInfo.

Ultimately this would apply to other resources as well, but clusters is where we (Google) have a specific interest today.

CC @envoyproxy/api-shepherds