← All drillsBuild a Server-Metrics Anomaly Detector
What you'll be able to do- ✓Show why a fixed threshold fires every evening on a metric with a daily rhythm, and replace it with a seasonal robust baseline
- ✓Detect point, contextual, collective and cross-metric anomalies in simulated server metrics
- ✓Fit Isolation Forest and Local Outlier Factor on window features and show how much contamination changes the result
- ✓Score a detector by incident, not by point, and measure how late it notices
- ✓Set an alert threshold from an alert budget, merge alerts into incidents, and test the detector against a shifted daily pattern
- ✓Write an operating note that states what normal means and when to refit
Build the alerting an operations or fraud team runs on a metric with a daily rhythm — learn what is normal at each time of day, catch what a fixed threshold cannot, and set the threshold from the number of alerts a person will read.
⌁ The monitoring and alerting behind cloud operations and payment systems — Datadog, PayPal and Splunk — wherever a few rare, unlabelled events must be found in a steady stream of normal ones.
Start this internshipCreate an account to unlock the 4 sections, the workbench, and askThili.
BeginSections
1. Build a Server-Metrics Anomaly Detector
🔒 locked2. Lesson 1 - The threshold that fires every evening
🔒 locked3. Lesson 2 - Let the forest find it
🔒 locked4. Lesson 3 - How many alerts will a person read?
🔒 lockedDig deeper
📄Isolation Forest (Liu, Ting & Zhou, 2008, IEEE ICDM)
paper📄LOF: Identifying Density-Based Local Outliers (Breunig, Kriegel, Ng & Sander, 2000, ACM SIGMOD)
paper📄Anomaly Detection: A Survey (Chandola, Banerjee & Kumar, 2009, ACM Computing Surveys)
paper🔗Numenta Anomaly Benchmark (NAB) — real server metrics with labelled incidents, MIT licence
article