metric cluster_name for leaf node is not correct

[AnjeiKozhev]

Observed behavior

Endpoint for leaf node metrics, in my case curl http://127.0.0.1:5888/varz returns the value of the cluster_name metric, which does not correspond to the name of the cluster to which this leaf node is connected, but coincides with the value of the server_name metric.

# curl http://127.0.0.1:5888/varz
{
  "server_id": "***********************************************",
  "server_name": "sandbox-v3",
  "version": "2.10.18",
  "proto": 1,
  "git_commit": "57d23ac",
  "go": "go1.22.5",
  "host": "localhost",
  "port": 5222,
  "auth_required": true,
  "max_connections": 65536,
  "ping_interval": 120000000000,
  "ping_max": 2,
  "http_host": "localhost",
  "http_port": 5888,
  "http_base_path": "",
  "https_port": 0,
  "auth_timeout": 2,
  "max_control_line": 4096,
  "max_payload": 1048576,
  "max_pending": 67108864,
  "cluster": {
     "name": "sandbox-v3"
  },
  "gateway": {},
  "leaf": {
    "remotes": [
      {
        "local_account": "************************************************************",
        "urls": [
          "sandbox-nats-vm01.****************:7422",
          "sandbox-nats-vm02.****************:7422",
          "sandbox-nats-vm03.****************:7422"
        ]
      },
      {
        "local_account": "*************************************************************",
        "urls": [
          "sandbox-nats-vm01:7422",
          "sandbox-nats-vm02:7422",
          "sandbox-nats-vm03:7422"
        ]
      }
    ]
  },

At the same time, the same metric from the server node returns the value of the cluster_name with the actual value of the cluster name specified in the configuration file:

# curl http://sandbox-nats-vm01.**************:4888/varz
{
  "server_id": "***********************************************",
  "server_name": "node-01",
  "version": "2.10.18",
  "proto": 1,
  "git_commit": "57d23ac",
  "go": "go1.22.5",
  "host": "sandbox-nats-vm01.**************",
  "port": 4222,
  "auth_required": true,
  "connect_urls": [
    "sandbox-nats-vm01.**************:4222",
    "sandbox-nats-vm02.**************:4222",
    "sandbox-nats-vm03.**************:4222"
  ],
  "max_connections": 65536,
  "ping_interval": 120000000000,
  "ping_max": 2,
  "http_host": "sandbox-nats-vm01.*****************",
  "http_port": 4888,
  "http_base_path": "",
  "https_port": 0,
  "auth_timeout": 2,
  "max_control_line": 4096,
  "max_payload": 2097152,
  "max_pending": 67108864,
  "cluster": {
    "name": "sandbox-nats-cluster",
    "addr": "sandbox-nats-vm01.******************",
    "cluster_port": 6222,
    "auth_timeout": 2,
    "urls": [
      "sandbox-nats-vm01.***************:6222",
      "sandbox-nats-vm02***************:6222",
      "sandbox-nats-vm03.***************:6222"
    ],
    "tls_timeout": 2,
    "pool_size": 3
  },

The mismatch of the values ​​of the cluster_node metric for the modes of the leaf node and the server node makes it impossible to use this metric in monitoring for all types of nodes simultaneously.

Expected behavior

If this is possible, then I would like to receive the current value of the cluster_name metric, corresponding to the cluster name for further identification of all nodes, one way or another participating in the work of this cluster

Server and client version

nats-server -v

nats-server: v2.10.18

nats --version

0.0.35

Host environment

Cluster. 3 nodes of:
Debian GNU/Linux 11 (bullseye)
AMD Ryzen 7 7700 8-Core Processor (family: 0x19, model: 0x61, stepping: 0x2)
64Gb RAM

Client:
Debian GNU/Linux 11 (bullseye)
AMD Ryzen 9 3900 12-Core Processor
128Gb RAM

Steps to reproduce

No response