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

jarmo

v0.1.1

Published

Simple StatsD-like server.

Downloads

1

Readme

Jarmo is a simple StatsD-like server. This means that Jarmo can be used for stats aggregation similarly to StatsD.

However there are a few differences. Jarmo does not define any metric types, instead it expects data to be sent in a JSON format. Jarmo merely parses the received data as JSON and adds a timestamp to the data as it is received.

Jarmo runs a flush cycle, similarly to StatsD. Upon the end of each cycle, all the received data is flushed to reporters, which in StatsD terms are defined as backends.

Configuration

The available configuration is listed below:

  export default {
    reporters: [
      '../reporters/influxdb'
      // List the 'require':able paths of wanted reporters here...
    ],
    memoize:        false,  // Whether to 'cache' received data.
    port:           8000,   // Port to run the service on.
    flush_interval: 10000   // The interval between flushes (in milliseconds).
                            // If set to zero, received data will be flushed to
                            // reporters as soon as it is received.
  }

Reporter Configuration

Each reporter defines a name, for example our influxdb-reporter is simply called influxdb here. In order to pass configuration to initialize method of the reporter, we add the configuration object with the key influxdb to our configuration file, like so:

  export default {
    influxdb: {
      // reporter configuration for 'influxdb' goes here!
    },
    reporters: [
      '../reporters/influxdb'
    ],
    host: 'localhost'
  }

Reporter Interface

Reporters must be requireable using the NodeJS require. The exported module must have a flush function, which unsurprisingly is called each time data is to be flushed.

If a reporter defines an initialize function, it is called during the server initialization phase after reporters have been loaded. It is given the config hash keyed by its name in the server's configuration file.

Running

npm install && npm start

Sending Data

Jarmo expects simple JSON messages delivered via UDP.

echo "{\"foo\":\"bar\"}" | nc -u -w0 localhost 8000

Do note that Jarmo does not format your messages in any way. In fact it is the reporter that is responsible for extracting the required data from the JSON messages and reporting it to wherever.