2. AgendaAgenda
1. Understand the problem.
2. Understand what monitoring is.
3. Example use-case(s)
4. A different approach
5. Learn methodologies and tools
10. Our data is lacking.Our data is lacking.
_rootCauseAnalysis:
inertia. that's how it was, that's ho
w it is.
11. We separateWe separate
monitoring frommonitoring from
applicationapplication
_rootCauseAnalysis:
we're not used to this. (Ops problem)
12. We monitorWe monitor
reactively, notreactively, not
proactivelyproactively
_rootCauseAnalysis:
reaction requires less initial energy
than anticipation.
13. We put uptimeWe put uptime
above system andabove system and
product qualityproduct quality
_rootCauseAnalysis:
it's much easier.
14. We deal with hardWe deal with hard
limits.limits.
_rootCauseAnalysis:
arbitrary numbers are easier to set.
15. Monitoring is non-Monitoring is non-
functional butfunctional but
resource hungryresource hungry
_rootCauseAnalysis:
we just don't accept it.
16. Good monitoringGood monitoring
requires the rightrequires the right
people, not just Ops!people, not just Ops!
_rootCauseAnalysis:
delegation is natural. other have mor
e important things to do.
17. Alert fatigue isAlert fatigue is
common.common.
_rootCauseAnalysis:
solving issues is much easier than so
lving problems, and apparently, we ar
e additted to non-actionable alerts.
21. So, after all, why do weSo, after all, why do we
not monitor properly?not monitor properly?
1. SimplificationSimplification
2. DelegationDelegation
3. RationalizationRationalization
_rootCauseAnalysis:
22. No fear,No fear,
Let's see how we can makeLet's see how we can make
this all betterthis all better
is here!is here!
23. “ If a service crashes and no one is
around to monitor it, does it raise an
alert?