SIsiliconc0w·Sep 12, 2014
Esty's Kale stack is an opensource way to do this with graphite data.
http://codeascraft.com/2013/06/11/introducing-kale/
https://github.com/etsy/skyline
https://github.com/etsy/oculus
In Show HN: Dynamic Thresholding Tooletsy
oculus
Java2013–2014
etsy / oculus · Archived
oculus
The metric correlation component of Etsy's Kale system
2Distinct people
2Mentions
0Explicit recommenders
706GitHub stars
What to know before exploring
What it is
The metric correlation component of Etsy's Kale system
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, 1:49:46 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 month2 dated mentions
Observed mentions: 2013-06-12 10:45:07 UTC to 2014-09-12 21:08:32 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 |
|---|---|---|---|---|---|
| Jun 2013 | 2013-06-01 00:00:00 UTC | 2013-07-01 00:00:00 UTC | 1 | 0 | 1 |
| Jul 2013 | 2013-07-01 00:00:00 UTC | 2013-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2013 | 2013-08-01 00:00:00 UTC | 2013-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2013 | 2013-09-01 00:00:00 UTC | 2013-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2013 | 2013-10-01 00:00:00 UTC | 2013-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2013 | 2013-11-01 00:00:00 UTC | 2013-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2013 | 2013-12-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2014 | 2014-01-01 00:00:00 UTC | 2014-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2014 | 2014-02-01 00:00:00 UTC | 2014-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2014 | 2014-03-01 00:00:00 UTC | 2014-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2014 | 2014-04-01 00:00:00 UTC | 2014-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2014 | 2014-05-01 00:00:00 UTC | 2014-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2014 | 2014-06-01 00:00:00 UTC | 2014-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2014 | 2014-07-01 00:00:00 UTC | 2014-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2014 | 2014-08-01 00:00:00 UTC | 2014-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2014 | 2014-09-01 00:00:00 UTC | 2014-10-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesI was very intrigued until I poked around the github repos and noticed the server specs Etsy was using to analyze the 250k metrics.
Oculus recommended setup (found at https://github.com/etsy/oculus):
* ElasticSearch
* At least 8GB RAM
* Quad Core Xeon 5620 CPU or comparable
* 1GB disk space
* two ElasticSearch servers in separate clusters
* a cluster of Worker boxes running Resque
* worker master runs redis
* additional resque worker boxes (and potentially slaves)
* At least 12GB RAM
* Quad Core Xeon 5620 CPU or comparable
* 1GB disk space
It'd be nice if there was a more established baseline set of server specs to get up and running. While many of us aspire to be at Etsy level monitoring, we're just not there.
In Loupe: Etsy's New Monitoring Stack