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

express-monitoring

v1.0.1

Published

Express Monitoring

Downloads

12

Readme

Express Monitoring

codecov Build Status

Package allows to define custom monitoring controls (rules) and execute them using express handlers.

This NodeJS adaptation of Horat1us/yii2-monitoring package for PHP.

Written on Typescript.

Installation

Using NPM:

npm i express-monitoring

Documentation

Structure

  • Controller - controller with express request handlers
  • Control - interface for monitoring control items.
    • Compose - pre-defined control to compose another controls.
    • Dependency - pre-defined control to block execution of another control.
  • FailureError - error class to be thrown in controls.

Usage

You need to define your own Control or use one of pre-defined. Then, just create Controller instance and add it to routes.

// region Monitoring Controller Definition
// This should be placed to separate file
import * as monitoring from "express-monitoring";

// can also be async or return promise
const SomeControl: monitoring.Control = () => {
    // check for something
    const isSuccessful = false;
    
    if (!isSuccessful) {
        throw new monitoring.FailureError(
            "Something goes wrong.",
            0, // error code
            {}, // details, optional
            "NotSuccessful" // string error type
        );
    }
    
    return {}; // you also may return details
};

let controls = {
    "controlID": SomeControl, 
};
const Monitoring = new monitoring.Controller(controls);
// endregion

import * as express from "express";

const app = express();
const port = 3000;

app.get('/monitoring/:id', Monitoring.control); // route to check controls separately
app.get('/monitoring/full', Monitoring.full); // route to check all controls by one request


app.listen(3000, () => `Monitoring app listening on port ${port}`);

Then you can make request GET http://localhost:3000/monitoring/controlID. For response examples see Documentation.

License

MIT