Proposed change
Add a leafnode connection count to nats server ls (e.g. a Leafs column).
Use case
The number of leafnode connections on a server can affect its performance. You can rebalance them with nats server cluster balance --kind Leafnode, but it's hard to know when a server actually needs it. nats server report leafnodes lists every connection but doesn't total them per server, and nats server ls doesn't show leaf counts.
It's also useful for sizing up an environment. nats server ls already gives a good overview of the cluster, but leafnodes are a blind spot, so you can't see how big the deployment really is once leaf connections are counted.
A leaf count in nats server ls would let you spot an imbalance, know when to run balance, and get a true picture of the environment size.
Contribution
No response
Proposed change
Add a leafnode connection count to
nats server ls(e.g. aLeafscolumn).Use case
The number of leafnode connections on a server can affect its performance. You can rebalance them with
nats server cluster balance --kind Leafnode, but it's hard to know when a server actually needs it.nats server report leafnodeslists every connection but doesn't total them per server, andnats server lsdoesn't show leaf counts.It's also useful for sizing up an environment.
nats server lsalready gives a good overview of the cluster, but leafnodes are a blind spot, so you can't see how big the deployment really is once leaf connections are counted.A leaf count in
nats server lswould let you spot an imbalance, know when to run balance, and get a true picture of the environment size.Contribution
No response