Skip to content
A data visualizer that uses " Node Application Metrics" (appmetrics) to monitor and display Node.js application data as a html web application.
JavaScript HTML
Branch: master
Clone or download

Latest commit

dependabot and mattcolegate Bump codecov from 2.3.1 to 3.6.5
Bumps [codecov](https://github.com/codecov/codecov-node) from 2.3.1 to 3.6.5.
- [Release notes](https://github.com/codecov/codecov-node/releases)
- [Commits](https://github.com/codecov/codecov-node/commits)

Signed-off-by: dependabot[bot] <support@github.com>
Latest commit 0366dd3 Feb 19, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib Allow appsody apps to use socket.io (#184) Dec 10, 2019
public Add animated gif to the readme (#183) Nov 22, 2019
test Allow appsody apps to use socket.io (#184) Dec 10, 2019
.eslintignore Allow appsody apps to use socket.io (#184) Dec 10, 2019
.eslintrc Fix linting errors on profiling.js (#96) Jul 31, 2017
.gitignore Allow appsody apps to use socket.io (#184) Dec 10, 2019
.gitmodules
.project Squash internal history for public code drop Feb 16, 2017
.travis.yml Update .travis.yml (#175) Jun 19, 2019
AUTHORS.md Fix #140 by using URL prefix passed in as part of options (#165) Oct 25, 2018
CHANGELOG.md Squash internal history for public code drop Feb 16, 2017
CONTRIBUTING.md Update CONTRIBUTING.md to latest guidelines Oct 5, 2017
IBM-RuntimesTools-V1.0.1-CLA.odt add licence files (#60) Mar 15, 2017
LICENSE add Apache License 2.0 LICENSE file Mar 3, 2017
README.md Add animated gif to the readme (#183) Nov 22, 2019
REST-API.md Add units data to the summary report (#157) Aug 1, 2018
attach.js Support preloading (#144) Jun 6, 2018
index.js Squash internal history for public code drop Feb 16, 2017
monitor.js Support preloading (#144) Jun 6, 2018
package.json Bump codecov from 2.3.1 to 3.6.5 Feb 20, 2020

README.md

Node Application Metrics Dashboard

Build Status codebeat badge codecov.io Apache 2 Homepage Module LTS Adopted' IBM Support

Node Application Metrics Dashboard (appmetrics-dash) provides a very easy-to-use web based dashboard to show the performance metrics of your running Node.js application.

appmetrics-dash in action

If you want to add the dashboard to all HTTP servers created by your application then simply add:

// Before all other 'require' statements:
require('appmetrics-dash').attach();

to the very top of your main JavaScript source file.

Alternatively, to use preloading:

$ node --require appmetrics-dash/attach app.js

or use the NODE_OPTIONS environment variable:

$ export NODE_OPTIONS="--require appmetrics-dash/attach"

If you want to add the dashboard to one specific HTTP server then use:

var dash = require('appmetrics-dash');
// Other 'require' statements here
// Create HTTP server 'myHttpServer' here
dash.monitor({server: myHttpServer});

If you are not creating an HTTP server then use:

// Before all other 'require' statements:
require('appmetrics-dash').monitor();

or run your program with

$ node --require appmetrics-dash/monitor app.js

or via the NODE_OPTIONS environment variable:

$ export NODE_OPTIONS="--require appmetrics-dash/monitor"

This creates a new server for the dashboard on port 3001 by default. The path defaults to /appmetrics-dash. E.g. http://localhost:3001/appmetrics-dash

The data available on the dashboard is as follows:

  • CPU Profiling (via a separate tab)
  • HTTP Incoming Requests
  • HTTP Throughput
  • Average Reponse Times (top 5)
  • CPU
  • Memory
  • Heap
  • Event Loop Times
  • Environment
  • Other Requests
  • HTTP Outbound Requests

As well as displaying data, it also provides the ability to generate both Node Report and Heap Snapshots directly from the dashboard. The Node Report will display in a new tab in the browser whilst the Heap Snapshot will be written to disk for loading into the Chrome DevTools for analysis. These can both be triggered from the options menu in the top left of the screen

The dashboard uses Node Application Metrics to monitor the application.

Installation

npm install appmetrics-dash

Performance overhead

Our testing has shown that the performance overhead in terms of processing is minimal, adding less than 0.5 % to the CPU usage of your application. The additional memory required is around 30 MB to gather information about your system and application which is then visualized in the dashboard.

We gathered this information by monitoring the sample application Acme Air. We used MongoDB as our datastore and used JMeter to drive load though the program. We have performed this testing with Node.js version 6.10.3

API Documentation

attach(options)

  • options {Object} Options are the same as for dash.monitor().

Auto-attach to all http servers created after this call, calling dash.monitor(options) for every server.

Simple example using attach

var dash = require('appmetrics-dash');
dash.attach();

var http = require('http');

const port = 3000;

const requestHandler = (request, response) => {  
  response.end('Hello')
}

const server = http.createServer(requestHandler);

server.listen(port, (err) => {  
  if (err) {
    return console.log('An error occurred', err)
  }
  console.log(`Server is listening on ${port}`)
});

monitor(options)

  • options.url {String} Path to serve dashboard from. Optional, defaults to '/appmetrics-dash'.
  • options.console {Object} Some messages are printed to the console using console.log() and console.error(). Optional, defaults to the global console object.
  • options.server {Object} An instance of a node http server to serve the dashboard from. Optional, default is to create a server (see port and host).
  • options.port {String|Number} Port to listen on if creating a server. Optional, unused if server option is used.
  • options.host {String} Host to listen on if creating a server. Optional, unused if server option is used.
  • options.appmetrics {Object} An instance of require('appmetrics') can be injected if the application wants to use appmetrics, since it is a singleton module and only one can be present in an application. Optional, defaults to the appmetrics dependency of this module.
  • options.nodereport {Object} An instance of require('node-report') can be injected if the application wants to use node-report, since it is a singleton module and only one can be present in an application. Optional, defaults to the node-report dependency of this module. The ability to generate reports can be disabled by setting this to null or undefined.
  • options.title {String} Title for the dashboard.
  • options.docs {String} URL link to accompanying documentation.
  • options.middleware {Object} Pass in middleware function to be used by server.

Contributing

We welcome contributions. Please see CONTRIBUTING.md for details about the contributor licence agreement and other information. If you want to do anything more involved than a bug fix or a minor enhancement then we would recommend discussing it in an issue first before doing the work to make sure that it's likely to be accepted. We're also keen to improve test coverage and may not accept new code unless there are accompanying tests.

Module Long Term Support Policy

This module adopts the Module Long Term Support (LTS) policy, with the following End Of Life (EOL) dates:

Module Version Release Date Minimum EOL EOL With Status
V4.x.x Jun 2018 Dec 2019 Current

License

The Node Application Metrics Dashboard is licensed using an Apache v2.0 License.

You can’t perform that action at this time.