Node Monitor

Node.js application monitoring
Alternatives To Node Monitor
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Pm239,7035,3701,7302 days ago278March 15, 2023832otherJavaScript
Node.js Production Process Manager with a built-in Load Balancer.
5 days ago5February 25, 2019166apache-2.0Java
CAT 作为服务端项目基础组件,提供了 Java, C/C++, Node.js, Python, Go 等多语言客户端,已经在美团点评的基础架构中间件框架(MVC框架,RPC框架,数据库框架,缓存框架等,消息队列,配置系统等)深度集成,为美团点评各业务线提供系统丰富的性能指标、健康状况、实时告警等。
Gtop9,474322 months ago15January 12, 202239mitJavaScript
System monitoring dashboard for terminal
Nodejs Dashboard3,94170292 years ago12November 22, 201915mitJavaScript
Telemetry dashboard for node.js apps from the terminal!
Express Status Monitor3,510765804 months ago42February 26, 202250mitJavaScript
🚀 Realtime Monitoring solution for Node.js/Express.js apps, inspired by, sponsored by
Pandora3,084672 years ago104December 14, 20184mitTypeScript
A Manageable, Measurable and Traceable Node.js Application Manager represented by Alibaba powered by TypeScript
Express Typescript Boilerplate2,946
5 months ago94mitTypeScript
A delightful way to building a RESTful API with NodeJs & TypeScript by @w3tecch
Easy Monitor2,852810a year ago63March 30, 20201bsd-2-clauseJavaScript
企业级 Node.js 应用性能监控与线上故障定位解决方案
Prom Client2,7711,0461,1355 days ago79March 13, 2023101apache-2.0JavaScript
Prometheus client for node.js
Puppeteer Examples2,377
3 years ago14apache-2.0JavaScript
Puppeteer example scripts for running Headless Chrome from Node.
Alternatives To Node Monitor
Select To Compare

Alternative Project Comparisons

Monitor your Node.js application

Build Status


Node-monitor is a library for remote monitoring and control of your Node.js app servers.

Like JMX in the Java world, node-monitor comes with a handful of general monitors, and allows you to create custom monitors for your application.

These monitors can be scripted using JavaScript, or placed onto a dashboard.

Project Guidelines

  • Simple - Get started quickly
  • Powerful - For multi-node enterprise deployment
  • Lightweight - Inactive until used, small footprint during use
  • Flexible - Easy to write custom monitors for your app
  • Stable - Well tested foundation for module developers

Getting Started

Run the following from your app server directory

$ npm install monitor

Then place the following line in your application bootstrap, and restart your server


Monitoring your app with a REPL console

Ad-hoc monitoring can be done from a REPL console.

Start up the REPL, and get the Monitor class. Feel free to copy/paste these lines into your console:

$ node
> var Monitor = require('monitor');

Now connect a monitor to a probe on your app server. There are a handful of built-in probes, and you can build custom probes for your application or npm module.

For this example, we'll monitor the Process probe:

> var processMonitor = new Monitor({probeClass:'Process'});
> processMonitor.connect();

The monitor is a Backbone.js data model so it updates in real time, and you can get all fields with toJSON():

> processMonitor.get('freemem');
> processMonitor.get('freemem');
> processMonitor.toJSON();

As the monitor changes, it emits change events:

> processMonitor.on('change', function() {
... console.log(processMonitor.get('freemem'));
... });

Monitoring your app with a custom script

Using Node.js as a scripting language, you can write custom monitors that do anything Node.js can do. Here's an example that prints to the console when free memory falls below a threshold.

Save this file to low-memory-warn.js, and run node low-memory-warn

// Low memory warning monitor
var Monitor = require('monitor');
var LOW_MEMORY_THRESHOLD = 100000000;

// Set the probe to push changes every 10 seconds
var options = {
  hostName: 'localhost',
  probeClass: 'Process',
  initParams: {
    pollInterval: 10000
var processMonitor = new Monitor(options);

// Attach the change listener
processMonitor.on('change', function() {
  var freemem = processMonitor.get('freemem');
  if (freemem < LOW_MEMORY_THRESHOLD) {
    console.log('Low memory warning: ' + freemem);

// Now connect the monitor
processMonitor.connect(function(error) {
  if (error) {
    console.error('Error connecting with the process probe: ', error);

Monitoring your app in a browser

The above script runs just as well within an html <script> tag as on the server. For example, change the var Monitor = require('monitor'); line to something like this:

<script src="/path/to/monitor/dist/monitor-all.min.js"></script>

The browser distribution included in node-monitor exports a single variable Monitor to the global namespace, and it can be used just like the Monitor variable in var Monitor = require('monitor').

Your browser will probably have to be pointing to localhost or behind your firewall in order to connect with the app server on the configured monitor port. See Security Concerns below.

Monitoring your app in a dashboard


The monitor-dashboard application lets you visualize your monitors in a dashboard.

$ npm install monitor-dashboard
$ npm start monitor-dashboard

Security Concerns

Exposing the internals of your app server is a high security risk. By default, the server listens on port 42000 and will connect with localhost clients only.

In order to monitor across machines, the default configuration must be changed to listen beyond localhost. Before doing this, it is recommended to understand the risks and have external measures in place to prevent unauthorized access.

See notes in the config/external.js file for more information.



May be freely distributed under the MIT license
See the LICENSE file.
Copyright (c) 2010-2014 Loren West

Popular Monitoring Projects
Popular Nodejs Projects
Popular Operations Categories

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.