Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor all NATS servers in a cluster #31

Open
glycerine opened this issue Feb 24, 2016 · 7 comments
Open

Monitor all NATS servers in a cluster #31

glycerine opened this issue Feb 24, 2016 · 7 comments
Assignees

Comments

@glycerine
Copy link

So I've been running a little 2 node cluster, and watching one of the nodes with nats-top.

It was very surprising to see two out of the three clients disappear. But then I checked and realized that those two had simply failed over to the other gnatsd in the cluster. I had to verify this was the case by firing up a separate nats-top instance and pointing it at the other node in the cluster.

It would be of great utility and convenience to be able to monitor an entire cluster from one nats-top display.

Hence this suggestion: have one nats-top connect to all gnatsd in a cluster and provide information on all of them. I really want to see all that information in one place to not be panicked that some service has died unexpectedly.

@glycerine
Copy link
Author

And thanks again for nats-top. It rocks!

@mcqueary mcqueary changed the title feature suggestion: have nats-top monitor all gnats in a cluster feature suggestion: have nats-top monitor all gnatsd in a cluster Mar 20, 2016
@mcqueary mcqueary changed the title feature suggestion: have nats-top monitor all gnatsd in a cluster feature suggestion: have nats-top monitor all gnats in a cluster Mar 20, 2016
@mcqueary mcqueary added the idea label Mar 20, 2016
@mcqueary mcqueary changed the title feature suggestion: have nats-top monitor all gnats in a cluster Monitor all NATS servers in a cluster Mar 21, 2016
@shinji62
Copy link

Hi,

Any update on that ? I mostly a 4 nodes cluster and have to connect to all of them each time, is not really convenient.

Thanks

@wallyqs
Copy link
Member

wallyqs commented May 16, 2016

@shinji62 think this would be a good addition, other servers could possibly be discovered via /routez/ if
not set explicit as well. I will make updates soon to have this built into nats-top, thanks for the feedback 👍

@glycerine
Copy link
Author

glycerine commented Dec 31, 2016

Ping. Hi @wallyqs! By chance is this in progress? If not, could you provide an outline of how it could be done? I don't really understand how /routez and related internal stuff works.

@oren-nonamesecurity
Copy link

Bump.
Is there a plan or an alternative for that?

@jsirianni
Copy link

I was also surprised to see that this tool only returns data on the server it is connected to. It would be nice if could connect to all servers in the cluster.

@aklesh-sakunia
Copy link

would be really valuable to have this feature, wish I could make a contribution but I dont know golang 🥲

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants