What is hot-shots?
The hot-shots npm package is a Node.js client for StatsD, a network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP or TCP and sends them to Graphite or other backends. It is an extension of the original statsd client, adding new features and fixing some existing ones.
What are hot-shots's main functionalities?
Increment
Increments a counter by 1. Useful for counting page views, downloads, or other metrics that increase in quantity.
const StatsD = require('hot-shots');
const client = new StatsD();
client.increment('page.views');
Timing
Sends a timing command for tracking how long events take. Useful for tracking request response times or other time-based metrics.
const StatsD = require('hot-shots');
const client = new StatsD();
client.timing('response_time', 42);
Gauge
Sets a gauge to a specific value. Gauges are a simple metric that represent a number that can go up or down, like fuel level or temperature.
const StatsD = require('hot-shots');
const client = new StatsD();
client.gauge('fuel.level', 0.75);
Set
Records the number of unique events between flushes. Useful for tracking unique visitors, emails, or other metrics where you want to count the occurrence of unique items.
const StatsD = require('hot-shots');
const client = new StatsD();
client.set('unique.visitors', 205);
Other packages similar to hot-shots
node-statsd
A simple, lightweight StatsD client for Node.js. Similar to hot-shots, it allows for sending metrics to StatsD but lacks some of the extended features and bug fixes that hot-shots provides.
lynx
This package is another StatsD client for Node.js, offering functionality to send various types of metrics to StatsD. While it provides similar basic functionality to hot-shots, it may not have as many features or the same level of active development.
hot-shots
A Node.js client for Etsy's StatsD server, Datadog's DogStatsD server, and InfluxDB's Telegraf StatsD server.
This project is a fork off of node-statsd
Installation
$ npm install hot-shots
Usage
All initialization parameters are optional.
Parameters (specified as an options hash):
host
: The host to send stats to default: localhost
port
: The port to send stats to default: 8125
prefix
: What to prefix each stat name with default: ''
suffix
: What to suffix each stat name with default: ''
globalize
: Expose this StatsD instance globally? default: false
cacheDns
: Cache the initial dns lookup to host default: false
mock
: Create a mock StatsD instance, sending no stats to the server? default: false
globalTags
: Tags that will be added to every metric default: []
maxBufferSize
: If larger than 0, metrics will be buffered and only sent when the string length is greater than the size. default: 0
bufferFlushInterval
: If buffering is in use, this is the time in ms to always flush any buffered metrics. default: 1000
telegraf
: Use Telegraf's StatsD line protocol, which is slightly different than the rest default: false
All StatsD methods other than event have the same API:
name
: Stat name required
value
: Stat value required except in increment/decrement where it defaults to 1/-1 respectively
sampleRate
: Sends only a sample of data to StatsD default: 1
tags
: The Array of tags to add to metrics default: []
callback
: The callback to execute once the metric has been sent
If an array is specified as the name
parameter each item in that array will be sent along with the specified value.
The event method has the following API:
title
: Event title required
text
: Event description default is title
options
: Options for the event
date_happened
Assign a timestamp to the event default is now
hostname
Assign a hostname to the event.aggregation_key
Assign an aggregation key to the event, to group it with some others.priority
Can be ‘normal’ or ‘low’ default: normal
source_type_name
Assign a source type to the event.alert_type
Can be ‘error’, ‘warning’, ‘info’ or ‘success’ default: info
tags
: The Array of tags to add to metrics default: []
callback
: The callback to execute once the metric has been sent
var StatsD = require('hot-shots'),
client = new StatsD();
client.timing('response_time', 42);
client.increment('my_counter');
client.decrement('my_counter');
client.histogram('my_histogram', 42);
client.gauge('my_gauge', 123.45);
client.set('my_unique', 'foobar');
client.unique('my_unique', 'foobarbaz');
client.event('my_title', 'description');
client.increment(['these', 'are', 'different', 'stats']);
client.increment('my_counter', 1, 0.25);
client.histogram('my_histogram', 42, ['foo', 'bar']);
client.set(['foo', 'bar'], 42, function(error, bytes){
if(error){
console.error('Oh noes! There was an error:', error);
} else {
console.log('Successfully sent', bytes, 'bytes');
}
});
client.histogram('my_histogram', 42, 0.25);
client.histogram('my_histogram', 42, ['tag']);
client.histogram('my_histogram', 42, next);
client.histogram('my_histogram', 42, 0.25, ['tag']);
client.histogram('my_histogram', 42, 0.25, next);
client.histogram('my_histogram', 42, ['tag'], next);
client.histogram('my_histogram', 42, 0.25, ['tag'], next);
DogStatsD and Telegraf functionality
Some of the functionality mentioned above is specific to DogStatsD or Telegraf. They will not do anything if you are using the regular statsd client.
- globalTags parameter- DogStatsD or Telegraf
- tags parameter- DogStatsD or Telegraf
- telegraf parameter- Telegraf
- histogram method- DogStatsD or Telegraf
- event method- DogStatsD
Errors
In the event that there is a socket error, hot-shots
will allow this error to bubble up. If you would like to catch the errors, just attach a listener to the socket property on the instance.
client.socket.on('error', function(error) {
return console.error("Error in socket: ", error);
});
If you want to catch errors in sending a message then use the callback provided.
Submitting changes
Thanks for considering making any updates to this project! Here are the steps to take in your fork:
- Make sure you've added any new tests needed
- Run "npm install && npm test"
- Update the HEAD section in CHANGES.md with a description of what you have done
- Push your changes and create the PR, and we'll try to get this merged in right away
Name
Why is this project named hot-shots? Because:
- It's impossible to find another statsd name on npm
- It's the name of a dumb movie
- No good reason
License
hot-shots is licensed under the MIT license.