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

controlio-monitor

v0.0.14

Published

The controlio base system

Downloads

8

Readme

controlio-monitor

The core system.

Description

The core app that handles everything.

TODO

  • inspector/status: Rewrite/Simplify status information to make more sense. Split config and status.

  • inspector: Track duration and output of every result

  • Log all pertinent information (check results, results and their output, status changes etc) to a useful database.

    • Database options: SQLite, MongoDB, MySQL
    • Check values must be parseable
  • valueChange

    • Trigger results when a monitored value changes from last time
  • inspector.getOption: Generate error when parameters are missing

Status data

Host

For every hos two states are kept:

  • current: The latest data.
  • previousStatus: When the ok status for the hostchanges, current is copied to previousStatus.

Each state has the following values:

  • counter: Is incremented with every execution of a check that set to changeReachable.
  • ok: Boolean value determining whether the host is reachable. Used to decide whether checks for this host should be executed.

Check

For every check three states are kept:

  • current: The latest data.
  • previous: Before current is updated with the latest check results, it is copied to previous.
  • previousStatus: When the value for ok changes, current is copied to previousStatus.

Each state has the following values:

  • counter: Number of checks with the current ok value. Is reset when ok changes.
  • since: Date on which ok last changed.
  • ok: Boolean value determining whether the check was successful or not. Set to null on launch or when the check can't be executed due to the host being unreachable.
  • msg: Message from check execution.
  • output: Output from check execution.
  • values: Data values from check execution.
  • start: Start of the last check execution.
  • end: End of the last check execution.
  • duration: Duration of the last check execution.

Additionally each check has a meta object with the following values:

  • counter: Number of checks since app launch. Incremented with each check update.
  • running: Boolean value that is set to true while the check is being executed.
  • runningSince: Date when the check was started. Is null while the check is not running.
  • next: Date for which the next check execution is scheduled.

on

Each on event has the following status values:

  • counter: Number of times this event was executed.
  • running: Boolean value that is set to true while the event is being executed.
  • start: Start of the last event execution.
  • end: End of the last event execution.
  • duration: Duration of the last event execution.
  • error: Error (if any) of the last event execution.
  • output: Output (if any) of the last event execution.