$30 off During Our Annual Pro Sale. View Details »
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
MOM! My algorithms SUCK
Abe Stanway
September 19, 2013
Programming
15
2.4k
MOM! My algorithms SUCK
Given at Monitorama.eu 2013 in Berlin.
http://vimeo.com/75183236
Abe Stanway
September 19, 2013
Tweet
Share
More Decks by Abe Stanway
See All by Abe Stanway
Building Data Driven Organizations
astanway
1
190
A Deep Dive into Monitoring with Skyline
astanway
6
1.5k
Bring the Noise: Continuously Deploying Under a Hailstorm of Metrics
astanway
34
7.1k
Data Visualization in the Trenches
astanway
5
490
Gifs as Language
astanway
2
510
Your API is a Product
astanway
3
740
Zen and the Art of Writing Commit Logs
astanway
3
600
Other Decks in Programming
See All in Programming
Kubernetes Admission Webhook Deep Dive
zoetrope
7
660
[RubyConf 2022] Weaving & seaming mocks
palkan
0
110
KubeCon + CNCon Europe 2022 Recap ~ Istio Today and Tomorrow: Sidecars and Beyond
ksudate
0
140
競技プログラミングことはじめ
e869120
17
9.3k
ANGEL Dojo 最終発表資料
ten986
0
140
디자인에 이어 코딩까지 AI가 프로그램 개발을 척척? : GitHub Copilot, 어디까지 알아보셨나요
outsider
0
640
ビルドツールViteを10分で解説！
akitotsukahara
0
130
PyHack#141今日やったこと
soogie
0
100
AWSDevDay Japan 2022 Amazon Neptune and Serverless
curanosuke
0
160
Rails Girls 2022 LT
harunatsujita
0
220
[JJUG CCC 2022 fall] Fargate上のJVMからCPUを認識するまで 〜正しく認識されないCPUの謎を追え〜
orekyuu
0
180
RenovateをiOSアプリ開発に導入・運用した話
coffmark
0
110
Featured
See All Featured
Embracing the Ebb and Flow
colly
74
3.5k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
657
120k
It's Worth the Effort
3n
174
26k
Design by the Numbers
sachag
271
17k
A better future with KSS
kneath
228
16k
A Modern Web Designer's Workflow
chriscoyier
690
180k
Building Your Own Lightsaber
phodgson
96
4.8k
The Brand Is Dead. Long Live the Brand.
mthomps
48
2.9k
Debugging Ruby Performance
tmm1
67
11k
Designing for Performance
lara
599
64k
Happy Clients
brianwarren
89
5.8k
Code Reviewing Like a Champion
maltzj
508
38k
Transcript
@abestanway MOM! my algorithms SUCK
i know how to fix monitoring once and for all.
a real human physically staring at a single metric 24/7
that human will then alert a sleeping engineer when her
metric does something weird
Boom. Perfect Monitoring™.
this works because humans are excellent visual pattern matchers* *there
are, of course, many advanced statistical applications where signal cannot be determined from noise just by looking at the data.
can we teach software to be as good at simple
anomaly detection as humans are?
let’s explore.
anomalies = not “normal”
humans can tell what “normal” is by just looking at
a timeseries.
“if a datapoint is not within reasonable bounds, more or
less, of what usually happens, it’s an anomaly” the human definition:
there are real statistics that describe what we mentally approximate
None
“what usually happens” the mean
“more or less” the standard deviation
“reasonable bounds” 3σ
so, in math speak, a metric is anomalous if the
absolute value of latest datapoint is over three standard deviations above the mean
we have essentially derived statistical process control.
pioneered in the 1920s. heavily used in industrial engineering for
quality control on assembly lines.
traditional control charts specification limits
grounded in exchangeability past = future
needs to be stationary
produced by independent random variables, with well- defined expected values
this allows for statistical inference
in other words, you need good lookin’ timeseries for this
to work.
normal distribution: a more concise definition of good lookin’ μ
34.1% 13.6% 2.1% 34.1% 13.6% μ - σ 2.1%
if you’ve got a normal distribution, chances are you’ve got
an exchangeable, stationary series produced by independent random variables
99.7% fall under 3σ
μ 34.1% 13.6% 2.1% 34.1% 13.6% 2.1% μ - σ
if your datapoint is in here, it’s an anomaly.
when only .3% lie above 3σ...
...you get a high signal to noise ratio...
...where “signal” indicates a fundmental state change, as opposed to
a random, improbable variation.
a fundamental state change in the process means a different
probability distribution function that describes the process
determining when probability distribution function shifts have occurred, as early
as possible. anomaly detection:
μ 1
μ 1 a new PDF that describes a new process
drilling holes sawing boards forging steel
snapped drill bit teeth missing on table saw steel, like,
melted
processes with well planned expected values that only suffer small,
random deviances when working properly...
...and massive “deviances”, aka, probability function shifts, when working improperly.
the bad news:
server infrastructures aren’t like assembly lines
systems are active participants in their own design
processes don’t have well defined expected values
they aren’t produced by genuinely independent random variables.
large variance does not necessarily indicate poor quality
they have seasonality
skewed distributions! less than 99.73% of all values lie within
3σ, so breaching 3σ is not necessarily bad 3σ possibly normal range
the dirty secret: using SPC-based algorithms results in lots and
lots of false positives, and probably lots of false negatives as well
no way to retroactively find the false negatives short of
combing with human eyes!
how do we combat this?* *warning! ideas!
we could always use custom fit models...
...after all, as long as the *errors* from the model
are normally distributed, we can use 3σ
Parameters are cool! a pretty decent forecast based on an
artisanal handcrafted model
but fitting models is hard, even by hand.
possible to implement a class of ML algorithms that determine
models based on distribution of errors, using Q-Q plots
Q-Q plots can also be used to determine if the
PDF has changed, although hard to do with limited sample size
consenus: throw lots of different models at a series, hope
it all shakes out.
[yes] [yes] [no] [no] [yes] [yes] = anomaly!
of course, if your models are all SPC-based, this doesn’t
really get you anywhere
use exponentially weighted moving averages to adapt faster
fourier transforms to detect seasonality
second order anomalies: is the series “anomalously anomalous”?
...this is all very hard.
so, we can either change what we expect of monitoring...
...and treat it as a way of building noisy situational
awareness, not absolute directives (alerts)...
...or we can change what we expect out of engineering...
...and construct strict specifications and expected values of all metrics.
neither are going to happen.
so we have to crack this algorithm nut.
...ugh. @abestanway