web/null is /dev/null for the Web. It silently agrees with and eats up any request
being VERBd to it, and keeps statistics of it.
web/null is great to use as a diagnostics end-socket of any distributed system you have, that works against another system sitting at an HTTP endpoint.
Replace any service with it, in order to have a real peek at what your other services are doing.
web/null is extremely useful (and being used) for getting stats data during stress testing a complex system.
clone this repository and run
$ npm install
You should then be able to run
$ node webnull
== web/null v0.0.1. I eat your HTTP. ==
* Listening on port 4000.
* Flushing to webnull.log every 10 seconds.
And now just experiment. Here is apachebench
$ ab -n 10000 -c 10 "http://localhost:4000/"
Here's how help looks like:
$ node webnull --help
Usage: webnull [options]
Options:
-h, --help output usage information
-V, --version output the version number
-d, --debug Show when flush happens.
-c, --canned-response [file] Existing file name to read a response from.
-o, --output [file] File name to output to.
-i, --interval [seconds] Flush interval.
-p, --port [number] Port to listen on.
Fork, implement, add tests, pull request, get my everlasting thanks and a respectable place here :).
Copyright (c) 2011 Dotan Nahum @jondot. See MIT-LICENSE for further details.