search

lorenwest / monitor-dashboard

Dashboards for the Node.js monitor project
https://lorenwest.github.com/monitor-dashboard
MIT License
204 stars 28 forks source link

usage of node-monitor and node-monitor-dashboard in multiple VM setting #26

Open anilkun opened 9 years ago

anilkun commented 9 years ago

Hi Lorenwest,

Great work !!

I went through the documentation and got the node-monitor and monitor-dashboard up and configured the node-dashboard to listen to localhost. I am able to see details of node-monitor process in probe viewer.

My aim is to monitor nodejs applications running on multiple VMs. So to achieve this, should I run node-monitor on all the VMs and have the node-monitor-dashboard run on a separate VM and in the UI select the servers where the node-monitor is running ?

Or, can I run node-monitor on a single VM and use 'accept external connections' setting to listen to nodejs process on other VMs ? I am confused on the exact usage of node-monitor.

Since the cloud environment I am using has auto scaling capability. So how can I use node-monitor/dashboard in scale up and scale down scenarios ?

Thanks in advance.

lorenwest commented 9 years ago

You have the correct understanding. Node-monitor must be included in every app server that you want exposed to the monitor-dashboard. One VM has monitor-dashboard, and it's configured to listen to the nodes running node-monitor.

As for dynamic configuration, my advise is to get 2-3 nodes running and see where you want to be dynamic. You have options for dynamically creating configuration json files, triggering reloads, restarting the dashboard server, and sending push messages to the browser - all depending on how fast you need the update, and how much work you want to put into polling/eventing.

anilkun commented 9 years ago

Thank you Lorenwest. I will get started.