Now that #33325 has been merged, Monitoring can collect the arbitrary cluster.metadata.* keys. Across Kibana and ES, we can agree to use specific keys to define added behavior that benefits both sides, such as cluster.metadata.display_name.

We can use that as a way to allow the user to override the cluster_name (e.g., if it was never set or it is set to something like a UUID) as described in elastic/kibana#23022. The easiest approach would be to explicitly grab that key and include it in the cluster_stats, or possibly include all of the cluster.metadata key/value pairs and simply have the UI pluck the one that is interesting.