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

process-watcher

v0.0.2

Published

Monitors nodejs processes for endless loops and other abnormal behaviours and kills it.

Downloads

2

Readme

process-watcher

It is responsible for:

  • Listen to all the nodejs processes.

  • Send SIGHUP to the process, which didn't have any throughput of events within 30 seconds.

  • Send SIGKILL to the process, which didn't die after getting SIGHUP withing 30 seconds.

  • Send SIGKILL to the process, which stopped sending status updates for 60 seconds.

  • Write following metrics for respective events described above.

    • watcher.proc.died: Incremented when process has died for any reason, potentially caused by SIGKILL or other means.
    • watcher.proc.graceful: Incremented if SIGHUP was sent to process.
    • watcher.proc.killed: Incremented when watcher sends the SIGKILL to the process.
    • watcher.reqcpu: Metric demonstrating an average of how many CPU jiffies per request process consumes.

Note: process-watcher depends on monitr to provide status of worker process. For every worker, monitr needs to be started. For more details on monitr, please refer - https://github.com/yahoo/monitr/blob/master/README.md and for code example refer to https://github.com/yahoo/monitr/blob/master/examples/monitor_me.js.

install

With npm do:

npm install process-watcher

usage

var watcher = require('process-watcher');
var watcher_instance = new watcher.Watcher({ metric : watcher_metric, config : watcher_config });

example

var watcher = require('process-watcher');

/*
 * Dummy metric monitoring object.
 */
var watcher_metric = {
    /**
     * Increments metric
     */
    increment : function (name, v) {
        // Add implementation as necessary
    },
    /**
     * Set the metric or multiple metrics at the same time.
     * */
    set : function (names, v) {
        // Add implementation as necessary
    }
};

var dgpath = '/tmp/watcher_test_dgram',
    statusPath = '/tmp/watcher_status_path_test',
    watcher_config = { max_inactive : 0.001, monitor : 0.001,  monPath: dgpath,
        timeout : 30, timeout_start : 60 };

//Instantiate watcher
var watcher_instance = new watcher.Watcher({ metric : watcher_metric, config : watcher_config });

Build Status

Build Status

Node Badge

NPM