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 🙏

© 2026 – Pkg Stats / Ryan Hefner

statsd-jut-backend

v0.0.9

Published

Jut backend for StatsD

Readme

statsd-jut-backend Build Status: Linux

statsd-jut-backend is a backend module for StatsD that allows users to write StatsD metrics directly into a Jut HTTP receiver.

Installing

Change to the StatsD root directory and execute the following:

npm install statsd-jut-backend

This should install the Jut backend module in the correct location. Alternatively, all of the .js files can be copied into the StatsD backend directory.

Configuring

First enable the Jut backend in StatsD config.js:

backends: ['./backends/graphite', 'statsd-jut-backend']

Then create a new config section for the Jut backend:

jut: {
    url: 'http://example.jut.io:9000/?source_type=metric'
}

Of course, use your own receiver URL from the Jut setup app.

Please see jut-config.js for more detailed information on configuring the backend.

Tagging

Each point is automatically given a number of tags before it is sent to the Jut receiver:

{
  "metric_type": "<counter|gauge|timer>",
  "name": "<name of metric"",
  "time": <epoch time in ms>,
  "value": <raw value>,
  "source_type": "metric",
  "stat": "<sum|avg|upper|etc..(mainly for timer)>",
  "interval": <statsd flush interval in ms>
}

In addition, arbitrary tags can be added to every point by setting jut.tags. This can be useful for identifying which part of the infrastructure the data originates from.

Key-Value Parsing

The Jut backend optionally supports tagging metrics based upon key-value pairs that are embedded in the name of a metric. To enable, first set jut.split_keys to true in config.js.

Now a tag can be created by separating the key from the value with __. This is easier indicated with an example:

pizza.topping__pepperoni.diameter_inches__18

This will send a metric to the Jut system with the name pizza, tagged with topping=pepperoni and diameter_inches=18. This is in addition to any standard tags that are applied to every point. Note that some tags are reserved for internal use (please see RESERVED_TAGS in lib/parse.js).

Testing

npm install
npm test

TODO

  • Implement sets and some more obscure StatsD metric types