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

@wesp-up/health-reporter

v1.1.0

Published

This package provides a consistent health reporter, commonly used for deep health check routes on services.

Downloads

67

Readme

@wesp-up/health-reporter

This package provides a consistent health reporter, commonly used for deep health check routes on services.

The health reporter follows this health RFC and is intended to be used as a deep health check of a service to gather a fast report on the health of downstream dependencies. Most useful during an outage or degraded service. Recommended to also be used with API tests and canary tests.

What it is not:

  • Do not use for a standard health check route for load balancing purposes. Generating health reports is more intensive. Standard health check routes are meant to be as fast as possible and are used to determine whether a node should be pulled out of the pool.
  • Not intended to be used as a diagnostic tool, as shown in the RFC for metrics such as database connections, CPU and memory usage. Prefer to use standard tooling such as Grafana for those purposes. Because this health reporter is intended to be used as a publicly accessible deep health check route, you should be careful about what information you expose.

Installation

npm install --save @wesp-up/health-reporter

Usage

Express

import assert from 'node:assert';

import { HealthReporter, ResponseTimeHttpHealthChecker } from '@wesp-up/health-reporter';
import mongoose from 'mongoose';

async function bootstrap() {
  const connection = mongoose.createConnection('mongodb://127.0.0.1/dbname');

  const health = new HealthReporter()
    .add(
      new ResponseTimeComponentChecker({
        componentName: 'Mongo',
        check: () => connection.getClient().db('dbname').command({ ping: 1 }),
      }),
    )
    .add(
      new ResponseTimeHttpHealthChecker({
        componentName: 'ComponentServiceA',
        url: 'https://internal-lb.b1-prv.qops.net/service-a/healthcheck',
      }),
    );

  httpAdapter.get('/deepHealthcheck', async (req, res) => {
    const report = await this.health.report();
    if (report.status !== 'pass') {
      req.context.log.addAccessMeta({ report });
    }
    res.status(500);
    res.send(report);
  });
}

bootstrap();

Nest

import assert from 'node:assert';

import { Controller, Get } from '@nestjs/common';
import { InjectConnection } from '@nestjs/mongoose';
import { HealthReporter, ResponseTimeHttpHealthChecker } from '@wesp-up/health-reporter';
import { Connection } from 'mongoose';

@Controller()
export class AppController {
  private health: HealthReporter;

  constructor(@InjectConnection() connection: Connection) {
    this.health = new HealthReporter()
      .add(
        new ResponseTimeComponentChecker({
          componentName: 'Mongo',
          check: () => connection.getClient().db('dbname').command({ ping: 1 }),
        }),
      )
      .add(
        new ResponseTimeHttpHealthChecker({
          componentName: 'ComponentServiceA',
          url: 'https://internal-lb.b1-prv.qops.net/service-a/healthcheck',
        }),
      );
  }

  @Get('/deepHealthcheck')
  async deepHealthcheck(@ReqContext() context: RequestContext) {
    const report = await this.health.report();
    if (report.status !== 'pass') {
      context.log.addAccessMeta({ report });
      throw new InternalServerErrorException(report);
    }
    return report;
  }
}

Example Response

Following is what a response might look like for the above example usage.

{
  "status": "pass",
  "serviceId": "service-x",
  "releaseId": "5b7e2fe6803260c76903994362d273d6f3d2ba23",
  "checks": {
    "Mongo:responseTime": [
      {
        "status": "pass",
        "observedValue": 20,
        "observedUnit": "ms"
      }
    ],
    "DownstreamServiceA:responseTime": [
      {
        "status": "pass",
        "observedValue": 272,
        "observedUnit": "ms"
      }
    ]
  }
}

Documentation

For documentation on each exported member, see the docs.