zomato/log.io — explained in plain English
Analysis updated 2026-08-08 · repo last pushed 2023-03-16
Watch logs from multiple servers in one browser tab instead of keeping terminal sessions open on each machine.
Spot errors as they happen by flipping between web server, database, and background job log streams in a single dashboard.
Pipe logs from custom scripts or non-standard sources directly into Log.io using its text-based protocol.
Search through live log messages in the web interface to quickly find specific errors or events.
| zomato/log.io | ctcpip/yakyak | omgitsads/coffeescript-twitter-streamer | |
|---|---|---|---|
| Stars | 2 | 1 | 3 |
| Language | CoffeeScript | CoffeeScript | CoffeeScript |
| Last pushed | 2023-03-16 | 2016-09-26 | 2011-05-09 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires deploying harvesters on each machine with log files plus running a central server, and configuring network connectivity between them.
Log.io lets you watch your application's log files update live in a web browser, so you can see what's happening across your systems in real time without SSH-ing into individual servers to tail files. The project works through two pieces. First, small programs called "harvesters" run on the machines where your log files live. They watch those files for new entries and send any new log messages to a central server over a standard network connection. The server then pushes those messages out to any browser tabs that are connected, updating them instantly. In the web interface, you organize logs by "streams" (which you define by mapping file paths to a friendly name) and "nodes" (the machines they come from). You pick which stream and node combination you want to watch, and the messages appear in a screen widget where you can also search through them. This would appeal to anyone running multiple servers or services who wants a single dashboard for spotting errors as they happen. For example, if you have a web server, a database, and a background job processor each writing their own logs, you could configure harvesters on all three and then flip between their streams in one browser window instead of keeping three terminal sessions open. The server also exposes a simple text-based protocol, meaning third-party tools or custom scripts can send log messages directly without using the built-in harvester. This could be handy if you want to pipe in logs from something that doesn't write to standard log files. The project is written in CoffeeScript and built on Node.js. It was originally developed by Narrative Science and is released under the Apache 2.0 license.
Log.io is a real-time log monitoring tool that shows your application log files live in a web browser, so you can watch logs from multiple servers in one place without SSH-ing into each machine.
Mainly CoffeeScript. The stack also includes CoffeeScript, Node.js.
Dormant — no commits in 2+ years (last push 2023-03-16).
Use freely for any purpose including commercial use, with attribution, Apache 2.0 also grants patent rights.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.