● You monitor what you know
● You react after it has failed.
● What about unknown-unknowns?
● Doesn’t avoid failures.
● Tells something broke and now it isn’t.
● Always a comparative operator.
Question: What is Monitoring?
Slide 7
Slide 7 text
● Systems are Distributed.
● What about?
○ Accuracy
○ Latency
○ Correctness
○ Consistency
● It’s till or from Now.
What are we missing?
Slide 8
Slide 8 text
Monitoring Timeline
Late 2000s
● SOA
Early 2010
● Microservices
1990s
● Servers
2000s
● Monolith
Now
Lambda
Slide 9
Slide 9 text
The REAL question
If a tree falls in a forest and nobody
heard it, did it make a sound?
Slide 10
Slide 10 text
The REAL answer
All falling trees
yield Logs.
Slide 11
Slide 11 text
Software, by default, is opaque.
To debug & control a running
system,
you need observation pre-built.
Slide 12
Slide 12 text
Observability
Slide 13
Slide 13 text
Need
- Debugging
- Pattern Detection
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
Unlike monitoring, observability
is not failure-centric.
If your job allows, you can use
it to understand system
performance, just-like-that.
¯\_(ツ)_/¯