npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

notare-monitor

v2.2.0

Published

Node.js Performance Observer - Monitor module

Downloads

51

Readme

notare-monitor -- Node.js observer

Extracted from the notare module, notare-monitor provides a Node.js streams Readable that monitors and reports on various Node.js performance metrics.

Example

const { Monitor } = require('notare-monitor');
const { pipeline, Writable } = require('stream');

class myWritable extends Writable {
  constructor() {
    super({ objectMode: true });
  }
  _write(chunk, encoding, callback) {
    console.log(JSON.stringify(chunk));
    callback();
  }
}

const monitor = new Monitor();
pipeline(monitor, new myWritable(), (err) => {
  if (err) {
    console.error('There was an error!');
    process.exit(1);
  }
});

API

Constructor: Monitor([options])

Create a new 'Monitor object.

  • options (object)
    • hz: (number) An integer between 1 and 1000 that specifies the number of samples per second the Monitor should generate. The higher this number, the greater the performance impact the Monitor will have. The default is 2. The NOTARE_HZ environment variable may also be used to set this value.
    • handles: (boolean) When true, the Monitor will track and report on the number of async resources in use by Node.js. Enabling this has a measurable performance impact on the Node.js process so it is off by default. Setting the NOTARE_HANDLES environment variable to 1 may also be used to set this value.
    • gc: (boolean) When true, the Monitor will track and report on garbage collection counts and durations. Enabling this has a measurable performance impact on the Node.js process so it is off by default. Setting the NOTARE_GC environment variable to 1 may also be used to set this value.

The Monitor object extends from Node.js stream.Readable.

Configuration via Environment Variables

  • NOTARE_HZ=n where n is the number of samples per second (default 2)
  • NOTARE_HANDLES=1 instructs notare to monitor async hook handle counts (disabled by default)
  • NOTARE_GZ=1 instructs notare to monitor garbage collection (disabled by default)