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

forter-riemann

v0.4.3

Published

node.js client for Riemann, supports hybrid UDP/TCP connections.

Downloads

4

Readme

Riemann Node.js Client

because you should be monitoring all of those non-blocking buffet plates.

Installation

Riemann uses Google Protocol Buffers, so make sure thats installed beforehand, and available on your PATH.

npm install riemann

Getting Started

first things first, we'll want to establish a new client:

var client = require('riemann').createClient({ 
  host: 'some.riemann.server', 
  port: 5555 
});

client.on('connect', function() { 
  console.log('connected!');
});

Just like Riemann ruby client, the client sends small events over UDP, by default. TCP is used for queries, and large events. There is no acknowledgement of UDP packets, but they are roughly an order of magnitude faster than TCP. We assume both TCP and UDP are listening to the same port.

sending events is easy (see list of valid event properties):

client.send(client.Event({
  service: 'buffet_plates',
  metric:  252.2,
  tags:    ['nonblocking']
}));

If you wanted to send that message over TCP and receive an acknowledgement, you can specify the transport, explicitly:

client.on('data', function(ack) { 
  console.log('got it!');
});

client.send(client.Event({
  service: 'buffet_plates',
  metric:  252.2,
  tags:    ['nonblocking']
}), client.tcp);

You can also send events with custom attributes:

client.send(client.Event({
  service: 'buffet_plates',
  metric: 150,
  attributes: [{key: "sessionID", value: "000-001-165"}],
  tags: ['nonblocking']
}), client.tcp);

When you're done monitoring, disconnect:

client.on('disconnect', function(){ 
  console.log('disconnected!');
});
client.disconnect();

Contributing

Contributing is easy, just send me a pull request. Please take a look at the project issues, to see how you can help. Here are some helpful tips:

  • install the developer dependencies using npm install --dev
  • please add tests. I'm using Mocha as a test runner, you can run the tests using npm test
  • please check your syntax with the included jshint configuration using npm run-script lint. It shouldn't report any errors.