Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
Why Monitoring Sucks
And what Configuration Management can
do about it
James Turnbull
@kartar
1
Who
• VP of Engineering at Kickstarter
• Advisor at Docker
• Open source chap
• Funny accent
2
The Docker Book
www.dockerbook.com
3
The Art of Monitoring
www.artofmonitoring.com
4
Who are you folks?
5
What's this all about?
6
Monitoring Sucks
7
It fucking does and I
can prove it.
8
Data. We have data.
9
Step out of the
bubble
10
The wrong folks
monitor
11
Only 9% of
developers do
monitoring
12
We monitor the
wrong things.
13
68% of folks don't
monitor business
logic
14
For the wrong reasons
15
90% have
unmonitored failures
16
80% have un-
actioned alerts
17
33% monitor
reactively
18
Our tools don't scale
19
They're centralized
20
And not self-service
21
So why?
22
Well ... lots of
"maybe"
23
Horses hate talking
about unicorns
24
A few unicorns do not
make horses magic
25
Change is slow
26
ROI isn't as obvious
Investment is expensive
Don't know what you don't know
27
But there is hope
28
Configuration
Management as
default
29
73% of y'all use it
30
Aren't y'all
awesome?
31
How can we take
advantage of this?
32
Blessed are the tool
makers
33
Events
34
APIs and endpoints
35
Create monitoring
abstractions
36
Build monitoring
patterns into content
37
Set the quality bar to
include monitoring
38
Testing compliments
monitoring
39
Make service
discovery and
registration a first
class citizen
40
Build tools that
enable self-service
41
Questions?
42
Nächste SlideShare
Wird geladen in …5
×

Why Monitoring Sucks and what Configuration Management can do about it

8.951 Aufrufe

Veröffentlicht am

We're slowly starting to see Configuration Management become a default rather than an exception. Increasingly large numbers of organizations see CM as a requirement and not an extra. Sadly we don't see this maturity reflected in the monitoring world. Change has been slow, we're often not monitoring the right things or the right places and environments remain heavily manual.

So why hasn't monitoring advanced at the same pace as CM? What's different about it? More importantly, what can we do about it?

Veröffentlicht in: Daten & Analysen, Software, Business
  • Tired of being scammed? Take advantage of a program that, actually makes you money! ♣♣♣ http://ishbv.com/ezpayjobs/pdf
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • What Men Secretly Want? He Will Be Addicted To You Forever, Click Here  http://ishbv.com/hissecret/pdf
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • Your opinions matter! get paid BIG $$$ for them! START NOW!!.. ★★★ https://tinyurl.com/make2793amonth
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • A Penis Growth Program With Actual Video Proof That It Works! REAL Growth With Video Proof, You Can't Fake These Enlargement Results... ♣♣♣ https://tinyurl.com/yaygh4xh
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • EVERY MAN'S OBSESSION >> The secret ingredient to lasting love, click now ...  http://tinyurl.com/y4b2om2w
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier

Why Monitoring Sucks and what Configuration Management can do about it

  1. Why Monitoring Sucks And what Configuration Management can do about it James Turnbull @kartar 1
  2. Who • VP of Engineering at Kickstarter • Advisor at Docker • Open source chap • Funny accent 2
  3. The Docker Book www.dockerbook.com 3
  4. The Art of Monitoring www.artofmonitoring.com 4
  5. Who are you folks? 5
  6. What's this all about? 6
  7. Monitoring Sucks 7
  8. It fucking does and I can prove it. 8
  9. Data. We have data. 9
  10. Step out of the bubble 10
  11. The wrong folks monitor 11
  12. Only 9% of developers do monitoring 12
  13. We monitor the wrong things. 13
  14. 68% of folks don't monitor business logic 14
  15. For the wrong reasons 15
  16. 90% have unmonitored failures 16
  17. 80% have un- actioned alerts 17
  18. 33% monitor reactively 18
  19. Our tools don't scale 19
  20. They're centralized 20
  21. And not self-service 21
  22. So why? 22
  23. Well ... lots of "maybe" 23
  24. Horses hate talking about unicorns 24
  25. A few unicorns do not make horses magic 25
  26. Change is slow 26
  27. ROI isn't as obvious Investment is expensive Don't know what you don't know 27
  28. But there is hope 28
  29. Configuration Management as default 29
  30. 73% of y'all use it 30
  31. Aren't y'all awesome? 31
  32. How can we take advantage of this? 32
  33. Blessed are the tool makers 33
  34. Events 34
  35. APIs and endpoints 35
  36. Create monitoring abstractions 36
  37. Build monitoring patterns into content 37
  38. Set the quality bar to include monitoring 38
  39. Testing compliments monitoring 39
  40. Make service discovery and registration a first class citizen 40
  41. Build tools that enable self-service 41
  42. Questions? 42

×