Gathering detailed insights and metrics for express-hot-shots
Gathering detailed insights and metrics for express-hot-shots
Statsd route monitoring middleware for connect/express
Installations
npm install express-hot-shotsDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
10.14.0
NPM Version
6.4.1
Releases
Unable to fetch releases
Languages
1
JavaScript
JavaScript (100%)
Developer
withspectrum
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
2 Stars
14 Commits
2 Forks
2 Watchers
3 Branches
1 Contributors
Updated on Jan 27, 2023
Maintainers
1
Package Meta Information
Latest Version
1.0.2
Package Id
express-hot-shots@1.0.2
Unpacked Size
40.37 kB
Size
15.20 kB
File Count
11
NPM Version
6.4.1
Node Version
10.14.0
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
2
express-hot-shots
StatsD route monitoring middleware for Connect/Express. This middleware can be used either globally or on a per-route basis (preferred) and sends status codes and response times to StatsD.
Forked from uber/express-statsd for usage in Spectrum.
Installation
1npm install express-hot-shots
Usage
An example of an express server with express-hot-shots:
1var express = require('express'); 2var statsd = require('express-hot-shots'); 3var app = express(); 4 5app.use(statsd()); 6 7app.get('/', function (req, res) { 8 res.send('Hello World!'); 9}); 10 11app.listen(3000);
By default, the middleware will send status_code and response_time stats
for all requests. For example, using the created server above and a request to
http://localhost:3000/, the following stats will be sent:
status_code.200:1|c
response_time:100|ms
Per route example
However, it's highly recommended that you set req.statsdKey which
will be used to namespace the stats. Be aware that stats will only be logged
once a response has been sent; this means that req.statsdKey can be
set even after the express-hot-shots middleware was added to the chain. Here's an
example of a server set up with a more specific key:
1var express = require('express'); 2var expressStatsd = require('express-hot-shots'); 3var app = express(); 4 5function statsd (path) { 6 return function (req, res, next) { 7 var method = req.method || 'unknown_method'; 8 req.statsdKey = ['http', method.toLowerCase(), path].join('.'); 9 next(); 10 }; 11} 12 13app.use(expressStatsd()); 14 15app.get('/', statsd('home'), function (req, res) { 16 res.send('Hello World!'); 17}); 18 19app.listen(3000);
A GET request to / on this server would produce the following stats:
http.get.home.status_code.200:1|c
http.get.home.response_time:100|ms
Tags
You can set the tags of the metrics with the req.statsdTags property.
1 2function statsd (path) { 3 return function (req, res, next) { 4 var method = req.method || 'unknown_method'; 5 req.statsdKey = ['http', method.toLowerCase(), path].join('.'); 6 req.statsdTags = { 7 server: process.env.SERVER_NAME, 8 } 9 next(); 10 }; 11}
These will be sent with both the response time and status code metrics.
Plain http example
This module also works with any http server
1var http = require('http'); 2var expressStatsd = require('express-hot-shots'); 3 4var monitorRequest = expressStatsd(); 5 6http.createServer(function (req, res) { 7 monitorRequest(req, res); 8 9 // do whatever you want, framework, library, router 10 res.end('hello world'); 11}).listen(3000);
Options
1expressStatsd(options);
- options
Object- Container for settings- client
HotShots instance- a custom hot shots instance - hotShots
Object- The hotShots options if you don't want to provide your own instance - requestKey
String- The key on thereqobject at which to grab the key for the statsd logs. Defaults toreq.statsdKey.
- client
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 0/14 approved changesets -- score normalized to 0
Reason
project is archived
Details
- Warn: Repository is archived.
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
52 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-6cpc-mj5c-m9rq
- Warn: Project is vulnerable to: GHSA-rch9-xh7r-mqgw
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-92vm-wfm5-mxvv
- Warn: Project is vulnerable to: GHSA-9vvw-cc9w-f27h
- Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
- Warn: Project is vulnerable to: GHSA-h6ch-v84p-w6p9
- Warn: Project is vulnerable to: GHSA-gpvr-g6gh-9mc2
- Warn: Project is vulnerable to: GHSA-cm5g-3pgc-8rg4
- Warn: Project is vulnerable to: GHSA-jj78-5fmv-mv28
- Warn: Project is vulnerable to: GHSA-rv95-896h-c2vc
- Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
- Warn: Project is vulnerable to: GHSA-9qj9-36jm-prpv
- Warn: Project is vulnerable to: GHSA-957j-59c2-j692
- Warn: Project is vulnerable to: GHSA-qh2h-chj9-jffq
- Warn: Project is vulnerable to: GHSA-m5pj-vjjf-4m3h
- Warn: Project is vulnerable to: GHSA-j383-35pm-c5h4
- Warn: Project is vulnerable to: GHSA-rm36-94g8-835r
- Warn: Project is vulnerable to: GHSA-jcpv-g9rr-qxrc
- Warn: Project is vulnerable to: GHSA-44pw-h2cw-w3vq
- Warn: Project is vulnerable to: GHSA-jp4x-w63m-7wgm
- Warn: Project is vulnerable to: GHSA-c429-5p7v-vgjp
- Warn: Project is vulnerable to: GHSA-2pr6-76vf-7546
- Warn: Project is vulnerable to: GHSA-8j8c-7jfh-h6hx
- Warn: Project is vulnerable to: GHSA-jf85-cpcp-j695
- Warn: Project is vulnerable to: GHSA-fvqr-27wr-82fm
- Warn: Project is vulnerable to: GHSA-4xc9-xhrj-v574
- Warn: Project is vulnerable to: GHSA-x5rq-j2xg-h7qm
- Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-wrvr-8mpx-r7pp
- Warn: Project is vulnerable to: GHSA-hxm2-r34f-qmc5
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-7mc5-chhp-fmc3
- Warn: Project is vulnerable to: GHSA-f9cm-p3w6-xvr3
- Warn: Project is vulnerable to: GHSA-jjv7-qpx3-h62q
- Warn: Project is vulnerable to: GHSA-gqgv-6jq5-jjj9
- Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
- Warn: Project is vulnerable to: GHSA-7xfp-9c55-5vqj
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-xwg4-93c6-3h42
- Warn: Project is vulnerable to: GHSA-jgqf-hwc5-hh37
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-4rq4-32rv-6wp6
- Warn: Project is vulnerable to: GHSA-64g7-mvw6-v9qj
- Warn: Project is vulnerable to: GHSA-qhv9-728r-6jqg
- Warn: Project is vulnerable to: GHSA-g7q5-pjjr-gqvp
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-xc7v-wxcw-j472
- Warn: Project is vulnerable to: GHSA-cf4h-3jhx-xvhq
- Warn: Project is vulnerable to: GHSA-v2p6-4mp7-3r9v
Score
1.7
/10
Last Scanned on 2025-06-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More