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

response-system

v0.2.1

Published

plugable response system meant to work with Nervous and graphite

Downloads

8

Readme

Response - Monitoring doesn't have to suck.

Response is an simple Graphite proxy with plugable alerting support. It's first priority is to deliver messages to Graphite rapidly. In the event that Graphite goes down, messages will be buffered until Graphite is back. Eventually Redis will be optionally supported to provide arbitrary levels of durability/persistence

The second priority of Response is to provide a plugable alerting/response system.

Quick Start

./bin/response

Developing Plugins

Check out the example_plugins directory.

Plugins are expected to play nice by not blocking the event loop and being mindful to store state safely. They receive two objects which both of which inherit from EventEmitter2.

The first is the GraphiteEventEmitter. It can be used to subscribe to arbitrary events using wildcards. Plugins may use this to keep track of events they care about.

The second is the Dispatcher. It too can be used to subscribe to arbitrary events, but the source of these events is exclusively other plugins. Plugins may use this publish or subscribe to alerts.

Plugins generally fall under too categories by convention. Those that identify certain conditions by subscribing to Graphite events, and those that respond to the conditions identified by the former.