RYryandotsmith·Aug 19, 2013
You would really dig l2met.[1] It is a system that creates metrics from k=v log data.
https://github.com/ryandotsmith/l2met
In Log4r for Ruby on Rails: Scalable and Robust Logging for Web Applicationsryansmith3136
l2met
Go2013–2013
ryansmith3136 / l2met
l2met
Convert a formatted log stream into metrics
2Distinct people
2Mentions
0Explicit recommenders
282GitHub stars
What to know before exploring
What it is
Convert a formatted log stream into metrics
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week2 dated mentions
Observed mentions: 2013-05-01 02:05:41 UTC to 2013-08-19 16:58:32 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 29 | 2013-04-29 00:00:00 UTC | 2013-05-06 00:00:00 UTC | 1 | 0 | 1 |
| May 6 | 2013-05-06 00:00:00 UTC | 2013-05-13 00:00:00 UTC | 0 | 0 | 0 |
| May 13 | 2013-05-13 00:00:00 UTC | 2013-05-20 00:00:00 UTC | 0 | 0 | 0 |
| May 20 | 2013-05-20 00:00:00 UTC | 2013-05-27 00:00:00 UTC | 0 | 0 | 0 |
| May 27 | 2013-05-27 00:00:00 UTC | 2013-06-03 00:00:00 UTC | 0 | 0 | 0 |
| Jun 3 | 2013-06-03 00:00:00 UTC | 2013-06-10 00:00:00 UTC | 0 | 0 | 0 |
| Jun 10 | 2013-06-10 00:00:00 UTC | 2013-06-17 00:00:00 UTC | 0 | 0 | 0 |
| Jun 17 | 2013-06-17 00:00:00 UTC | 2013-06-24 00:00:00 UTC | 0 | 0 | 0 |
| Jun 24 | 2013-06-24 00:00:00 UTC | 2013-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 1 | 2013-07-01 00:00:00 UTC | 2013-07-08 00:00:00 UTC | 0 | 0 | 0 |
| Jul 8 | 2013-07-08 00:00:00 UTC | 2013-07-15 00:00:00 UTC | 0 | 0 | 0 |
| Jul 15 | 2013-07-15 00:00:00 UTC | 2013-07-22 00:00:00 UTC | 0 | 0 | 0 |
| Jul 22 | 2013-07-22 00:00:00 UTC | 2013-07-29 00:00:00 UTC | 0 | 0 | 0 |
| Jul 29 | 2013-07-29 00:00:00 UTC | 2013-08-05 00:00:00 UTC | 0 | 0 | 0 |
| Aug 5 | 2013-08-05 00:00:00 UTC | 2013-08-12 00:00:00 UTC | 0 | 0 | 0 |
| Aug 12 | 2013-08-12 00:00:00 UTC | 2013-08-19 00:00:00 UTC | 0 | 0 | 0 |
| Aug 19 | 2013-08-19 00:00:00 UTC | 2013-08-26 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesI've been experimenting with a different metrics toolchain of shh + log-shuttle + l2met recently (also written in Go):
https://github.com/freeformz/shh
https://github.com/ryandotsmith/log-shuttle
https://github.com/ryandotsmith/l2met
shh can be extended with custom pollers written in Go, but focuses on collecting system-level metrics. log-shuttle is a general-purpose tool for shipping logs over HTTP. l2met receives logs over HTTP and can be extended with custom outlets written in Go, but requires log statements in a specific format ("measure.db.latency=20" or "measure=db.latency val=20").
It's great to see so many new tools in this space. Previously I had a bunch of one-off "carbonize" scripts running out of cron, each collecting a specific kind of metric and sending it to Graphite or statsd. This worked OK but required quite a bit of cod
Read the rest
e to get things done. Heka's plugin system looks like a nice way to structure things.