ddutta/skyline — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2014-06-19
Monitor thousands of server metrics and get alerted only when patterns actually break, not on fixed thresholds.
Feed StatsD or Graphite metric streams into Skyline to automatically detect anomalies.
Route detected anomalies to email, Hipchat, or PagerDuty so your team investigates quickly.
| ddutta/skyline | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | — | — | 0 |
| Language | Python | Python | Python |
| Last pushed | 2014-06-19 | 2022-11-22 | — |
| Maintenance | Dormant | Dormant | — |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires installing Python dependencies, configuring Redis, and running continuous metric streams.
Skyline is an automated system that watches your metrics and tells you when something looks wrong, without you having to set up manual alerts for each one. If you're running a service that generates thousands of measurements (like server response times, request counts, or database queries per second), Skyline learns what "normal" looks like for each metric and flags anything that deviates from that pattern. The system works by collecting metric data from sources like StatsD or Graphite, storing it temporarily, and then running it through multiple detection algorithms that vote on whether something is anomalous. When the algorithms reach consensus that a metric is behaving oddly, Skyline surfaces it in a web interface where you can investigate what happened. You can also configure automatic alerts to notify your team via email, Hipchat, or PagerDuty when anomalies are detected. Companies with large-scale infrastructure use this to avoid "alert fatigue", the exhausting problem of setting threshold-based alarms for thousands of metrics. Instead of saying "alert me if CPU goes above 80%," Skyline learns each server's typical CPU pattern and alerts you when the pattern breaks, which is often more meaningful. The system is designed to be passive, meaning new metrics are picked up automatically without requiring configuration for each one. Setting it up requires installing Python dependencies, configuring a Redis database to store data, and starting a few background processes. The README mentions this works best when you have continuous metric streams flowing in, and the project includes a test data utility to verify your installation is working. One practical note: the system's effectiveness depends on the quality of the algorithms monitoring your data, and the README acknowledges you may need to write custom detection logic if your metrics have unusual patterns that the default algorithms don't handle well.
Skyline automatically watches thousands of metrics, learns what's normal, and alerts your team when something looks anomalous without manual threshold setup.
Mainly Python. The stack also includes Python, Redis, StatsD.
Dormant — no commits in 2+ years (last push 2014-06-19).
License is not stated in the available content.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.