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

healthcheck

v0.1.3

Published

It polls backends and if they respond with HTTP 200 + an optional request body, they are marked good. Otherwise, they are marked bad.

Downloads

56

Readme

It polls backends and if they respond with HTTP 200 + an optional request body, they are marked good. Otherwise, they are marked bad. Similar to haproxy/varnish health checks.

new HealthCheck(options)

options can be an object.

Options:

  • servers: An array containing servers to check.
  • delay: Delay in msec between healthchecks. Defaults to 10000.
  • timeout: How long in msec a healthcheck is allowed to take place. Defaults to 2000.
  • failcount: Number of healthchecks good or bad in a row it takes to switch from down to up and back. Good to prevent flapping. Defaults to 2.
  • send: What to send for the healthcheck. Defaults to '/'.
  • expected: What to expect in the HTTP BODY, (meaning not the headers), in a correct response. If unset, just a HTTP 200 status code is required.
  • https: If true, https indicates that uses https to health check. Defaults to false.
  • logger: A function is invoked until every server finish in a healthcheck.

Example:

var dateformat = require('dateformat');
var HealthCheck = require("./").HealthCheck;
var Table = require('cli-table');

var instance = new HealthCheck({
    servers: [
        'localhost:3000',
        'localhost:3001'
    ],
    delay: 5000,
    timeout: 3000,
    failcount: 1,
    send: '/health.txt',
    expected: 'I_AM_ALIVE',
    https: true,
    logger: function(list) {
        var table = new Table({
            head: ['name', 'owner pid', 'action time', 'concurrent', 'since', "status", 'is down?']
        });
        var servers = Object.keys(list);

        servers.forEach(function(s) {
            var hc = list[s];
            var action_time = dateformat(hc.action_time, 'HH:MM:ss');
            var since = dateformat(hc.since, 'HH:MM:ss');
            table.push([s, hc.owner, action_time, hc.concurrent, since, hc.last_status, hc.down]);
        });
        console.log(table.toString());
    }
});

instance.status()

The status() method health status.

Example:

{
    'localhost:3000': {
        action_time: Wed Sep 10 2014 15: 28: 20 GMT + 0800(CST),
        concurrent: 1,
        down: false,
        failcount: 1,
        last_status: 'connect ECONNREFUSED',
        owner: 2300,
        since: Wed Sep 10 2014 15: 28: 20 GMT + 0800(CST)
    },
    'localhost:3001': {
        action_time: Wed Sep 10 2014 15: 28: 20 GMT + 0800(CST),
        concurrent: 1,
        down: false,
        failcount: 1,
        last_status: 'connect ECONNREFUSED',
        owner: 2300,
        since: Wed Sep 10 2014 15: 28: 20 GMT + 0800(CST)
    }
}
  • owner: Worker pid processing this healthcheck.
  • action_time: Date instance. Last time request was taken.
  • concurrent: Number of concurrent bad or good responses.
  • since: Date instance. How long this server's been concurrently bad or good.
  • last_status: Status of last finished check.
  • down: If true, the server is actually down.
  • failcount: Number of concurrent bad responses.

instance.is_down(name)

Return true if the given server has failed its healthcheck.

Example:

instance.is_down("localhost:3000");