Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


realtime log streamer

Subscribe to updates I use supergrep

Statistics on supergrep

Number of watchers on Github 402
Number of open issues 2
Average time to close an issue 11 days
Main language JavaScript
Average time to merge a PR 2 months
Open pull requests 2+
Closed pull requests 3+
Last commit over 4 years ago
Repo Created over 7 years ago
Repo Last Updated about 2 years ago
Size 511 KB
Organization / Authoretsy
Page Updated
Do you use supergrep? Leave a review!
View open issues (2)
View supergrep activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating supergrep for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)


Supergrep is a web based log streamer written in node. It can be used quite nicely to surface new log lines (errors, etc.) that aren't normally expected.

Essentially, having supergrep running in your browser while changes are being made allows for new/novel log patterns to show up, because under the hood, what we're really doing is:

$ tail -f {log filename} | grep -v {stuff you'd expect to see in log lines}

It's intended on being a noise reduction and change-awareness tool.

This is an Archived Project

Supergrep is no longer actively maintained and is no longer in sync with the version used internally at Etsy.


In order to run supergrep, you need NodeJS and npm ( NodeJS package manager).

Getting Started

You can edit variables in localConfig.js and also in static/js/supergrep.js. Most of this should work out of the box but some of the cooler functionality is enabled by assuming certain pieces of data can be found in your logs. You'll have to adjust the regexes to suit your logs.

Then you can install the node packages:

$ npm install

Run it from your install directory like:

$ ./runlocal

Point your browser to localhost (default port:3000) and then click on Guide to get a tour.


After setting this up locally and seeing how it works you'll probably want to run in production. There are many init daemons that you can run this under. We've included a simple init.d script to get you started. This is known to work under RedHat flavors of linux. You will have to edit the OPTIONS to specify the path where supergrep is installed. It also sets a parameter for prodConfig.js that can take similar options as the localConfig.js that is included.

Log Format

Here is an example log line from our logs that this tool supports. You can modify it to support your log format.

web0081 : [Tue Aug 28 13:55:05 2012] [error] [client] [e4G2F4OpKIEiCj-eAQuEKo-H-XDB] [error] [ClientLogger] [/somepath/lib/Logger.php:140] [0] uncaught: message="Object doesn't support this action" referrer="" data="{"url":"","line":5,"userAgent":"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)"}", referer:


Patches welcome!

supergrep open pull requests (View All Pulls)
  • Change package.json to target an older version of Express (2.5.10)
  • Make supergrep work with Express 4+
supergrep list of languages used
Other projects in JavaScript