Why Monitoring Sucks

51
1 #zendd Zenoss Proprietary Information October 2, 2012 VP Community, Technical Evangelist Zenoss Investigates: Why Monitoring Sucks Transforming IT Operations

description

For far too long, hardware manufacturers, independent software vendors, and even internal IT organizations have treated IT monitoring as an afterthought. While virtualization, provisioning, and orchestration get all the hype, monitoring is stuck within a reactive paradigm built on expensive legacy proprietary frameworks, cobbled together open source projects, expensive niche tools, or cheap downloadable solutions that offer flash with not much substance. To make matters worse, IT monitoring is susceptible to the ‘monitor everything’ syndrome that produces gigabytes of data and yields very little tangible results measured by statistics such as MTTR or SLAs. What it does yield is a scenario whereby IT is stuck with an abundance of disparate frameworks, solutions, elemental management systems (EMS) and tools that are expected to work together to create the mythical single-pane-of-glass. Join Zenoss as we investigate why monitoring sucks and the implications of continuing down this path within today’s new paradigms of cloud computing, programmable datacenter, or the software defined datacenter. Zenoss will provide answers to why monitoring sucks and we will introduce the 7 Stages of IT Monitoring Grief: 1. Excitement 2. Frustration 3. Denial 4. Anger 5. Disappointment 6. Resolve 7. Hope

Transcript of Why Monitoring Sucks

Page 1: Why Monitoring Sucks

1 #zenddZenoss Proprietary

Information

October 2, 2012

VP Community, Technical Evangelist

Zenoss Investigates:Why Monitoring Sucks

Transforming IT Operations

Page 2: Why Monitoring Sucks

2 #zenddZenoss Proprietary

Information

Agenda

• Housekeeping

• About Zenoss

• Why Monitoring Sucks

• 7 Stages of IT Monitoring Grief

• How to break the cycle

• Questions and Answers

Page 3: Why Monitoring Sucks

3 #zenddZenoss Proprietary

Information

Housekeeping

• Interactive Discussions•#zendd•WebEx Questions

• Keep the Dialog Going•[email protected]

• Ongoing•@zenoss•@platenreport•Google+•Facebook•blog.zenoss.com

Page 4: Why Monitoring Sucks

4 #zenddZenoss Proprietary

Information

Zenoss at a Glance

Transforming IT Operations• Founders lived the pain of legacy platforms at pioneering cloud

providers• New approach to both technology and business

Leading Commercial Open Source Player in Category• Large Global Footprint: 2.5M Downloads, 30K Organizations, 175

Countries• Large Active Community: 100K Members• Rapid Innovation & Lower Costs

Fastest Growing Enterprise Management Software Company

• 2010 and 2011 Inc 500• 2011 #22 on Deloitte Fast 500• Growth across key segments: Enterprise, Web, Federal, SMB, Service

Provider

Most Widely Adopted Cloud Management Console• Largest install-base of any cloud-capable management product in the

market• Unifies physical, virtual & cloud monitoring• Enables public, private and hybrid cloud scenarios

Strong Business & Team• Rapid growth with new customer acquisition and retention• Annapolis, MD & Austin, TX & San Jose, CA

Cool Vendor inIT Operations 2010

Best Monitoring Toolfor the Cloud

Page 5: Why Monitoring Sucks

5 #zenddZenoss Proprietary

Information

The Past

Page 6: Why Monitoring Sucks

6 #zenddZenoss Proprietary

Information

The Mainframe

Source: www.computersciencelab.com

Page 7: Why Monitoring Sucks

7 #zenddZenoss Proprietary

Information

SNA - Cisco

Source: Cisco Document 13178

Page 8: Why Monitoring Sucks

8 #zenddZenoss Proprietary

Information

Token Ring

Page 9: Why Monitoring Sucks

9 #zenddZenoss Proprietary

Information

The Present

Page 10: Why Monitoring Sucks

10 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 11: Why Monitoring Sucks

11 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 12: Why Monitoring Sucks

12 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 13: Why Monitoring Sucks

13 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 14: Why Monitoring Sucks

14 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 15: Why Monitoring Sucks

15 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 16: Why Monitoring Sucks

16 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 17: Why Monitoring Sucks

17 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 18: Why Monitoring Sucks

18 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 19: Why Monitoring Sucks

19 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 20: Why Monitoring Sucks

20 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 21: Why Monitoring Sucks

21 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 22: Why Monitoring Sucks

22 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 23: Why Monitoring Sucks

23 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 24: Why Monitoring Sucks

24 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 25: Why Monitoring Sucks

25 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 26: Why Monitoring Sucks

26 #zenddZenoss Proprietary

Information

Monitoring Progression

Page 27: Why Monitoring Sucks

27 #zenddZenoss Proprietary

Information

The Future

Page 28: Why Monitoring Sucks

28 #zenddZenoss Proprietary

Information

Cloud via NIST

Source: NIST 500-293

Page 29: Why Monitoring Sucks

29 #zenddZenoss Proprietary

Information

The Challenge

Page 30: Why Monitoring Sucks

30 #zenddZenoss Proprietary

Information

IT Infrastructure “Stack”

Page 31: Why Monitoring Sucks

31 #zenddZenoss Proprietary

Information

IT Infrastructure “Stack”

DYNAMIC

Page 32: Why Monitoring Sucks

32 #zenddZenoss Proprietary

Information

IT Infrastructure “Stack”

CHANGES

DYNAMIC

Page 33: Why Monitoring Sucks

33 #zenddZenoss Proprietary

Information

The Protocols & More

• SNMP

• SSH

• WMI

• Telnet

• Bash

• Perl

• Javascript

• Rest, JSON, XML, SOAP

• Netconf

• ICMP / NMAP

• Netflow, Jflow, Cflow

• Syslog

• Windows Events

• Other APIs

• Screen scraping

• CDP, LLDP, EDP

• Packet Sniffing / Sampling

• SNMP/POP

• ICMP

• JMX

Page 34: Why Monitoring Sucks

34 #zenddZenoss Proprietary

Information

FrankenMonitor

Page 35: Why Monitoring Sucks

35 #zenddZenoss Proprietary

Information

Single Pane of Glass

Image Source: http://www.freeimageslive.co.uk/free_stock_image/shatteredglass2950jpg

Page 36: Why Monitoring Sucks

36 #zenddZenoss Proprietary

Information

The Standards

Page 37: Why Monitoring Sucks

37 #zenddZenoss Proprietary

Information

COBIT to the rescue?

Source: IBPI.org

Page 38: Why Monitoring Sucks

38 #zenddZenoss Proprietary

Information

ITIL to the rescue?

Source: www.tech-faq.com

Page 39: Why Monitoring Sucks

39 #zenddZenoss Proprietary

Information

Messages

Page 40: Why Monitoring Sucks

40 #zenddZenoss Proprietary

Information

Messages of the Big 4

Page 41: Why Monitoring Sucks

41 #zenddZenoss Proprietary

Information

The 7 Stages of IT Monitoring Grief

Page 42: Why Monitoring Sucks

42 #zenddZenoss Proprietary

Information

Excitement – Found a new solution

Page 43: Why Monitoring Sucks

43 #zenddZenoss Proprietary

Information

Frustration – Attempted to implement Solution

Page 44: Why Monitoring Sucks

44 #zenddZenoss Proprietary

Information

Denial – Challenges with the solution

Page 45: Why Monitoring Sucks

45 #zenddZenoss Proprietary

Information

Anger – Threaten solution provider

Page 46: Why Monitoring Sucks

46 #zenddZenoss Proprietary

Information

Disappointment – There is no solution

Page 47: Why Monitoring Sucks

47 #zenddZenoss Proprietary

Information

Resolve – We can do this ourselves

Page 48: Why Monitoring Sucks

48 #zenddZenoss Proprietary

Information

Hope – Searching for a solution

Page 49: Why Monitoring Sucks

49 #zenddZenoss Proprietary

Information

How to break this cycle?

Page 50: Why Monitoring Sucks

50 #zenddZenoss Proprietary

Information

How to Change this?• Elevate Monitoring to Tier I

• Strategy, Plan, Execute

• Rationalize current IT operations tools• Success vs. unsuccessful vs. failure

• Cross domain involvement• IT, Customer, Executives

• Beware of vendor lock-In• Open vs. Closed or Open Source vs. Proprietary

• Past, present, and future• Static, Dynamic, Cloud, ?

• People, process, and tools• What are you and/or the customer looking to solve?

• Be open to new paradigms• Test and verify

Page 51: Why Monitoring Sucks

51 #zenddZenoss Proprietary

Information

THANK YOU QUESTIONS & ANSWERS

Email: [email protected]

Twitter: @platenreport