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

Identify gnatsd by pid/hostname/ip/port #30

Open
glycerine opened this issue Feb 23, 2016 · 2 comments
Open

Identify gnatsd by pid/hostname/ip/port #30

glycerine opened this issue Feb 23, 2016 · 2 comments
Assignees

Comments

@glycerine
Copy link

I'm running two gnatsd on the same host, to allow blue-green deployment.

To aid in distinguishing which instance I am looking at, would be nice to indicate which port we are monitoring at the top of the nats-top display, as well as other details of the gnatsd process itself.

For example, currently:

NATS server version 0.7.5 (uptime: 7d6h15m45s) 
Server:
  Load: CPU:  0.1%  Memory: 13.7M  Slow Consumers: 0
  In:   Msgs: 1.1M  Bytes: 467.2M  Msgs/Sec: 0.0  Bytes/Sec: 0      
  Out:  Msgs: 1.5M  Bytes: 655.2M  Msgs/Sec: 0.0  Bytes/Sec: 0      
...

With proposed helpful distinguishing information in the top line:

NATS server version 0.7.5 (uptime: 7d6h15m45s)  pid:1078 on host: blue-green.org[10.0.0.12]  port:4443  https_port:18822
Server:
  Load: CPU:  0.1%  Memory: 13.7M  Slow Consumers: 0
  In:   Msgs: 1.1M  Bytes: 467.2M  Msgs/Sec: 0.0  Bytes/Sec: 0      
  Out:  Msgs: 1.5M  Bytes: 655.2M  Msgs/Sec: 0.0  Bytes/Sec: 0    
...  
@wallyqs
Copy link
Member

wallyqs commented Feb 23, 2016

Good idea, will look into adding more info about the server. Thanks for the feedback.

@glycerine
Copy link
Author

@wallyqs you're certainly welcome. Thanks for your work on nats-top.

@mcqueary mcqueary added the idea label Mar 20, 2016
@mcqueary mcqueary changed the title feature request: identify which gnatsd nats-top is monitoring by pid/hostname/ip/port Identify gnatsd by pid/hostname/ip/port Mar 21, 2016
@bruth bruth removed idea labels Aug 18, 2023
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

4 participants