Sourcing Operations Management Architecture Monitoring that works!

1. SourcingOperations Management ArchitectureMonitoring that works!

2. Agenda • Monitoring Overview • The Sourcing Business • Demonstration • The OMA Advantage • Next Steps • Questions

3. Monitoring Overview

4. Why Monitor? Actively know environment is working Actively know when its not! Continuous visibility Fault awareness before the end user Availability Is it working? Performance Is it working well? Visibility (The Truth) No finger pointing! Correlation Measurement See only the problem, not the noise! Information to manage Capacity Can it work better without more money? Notification Diagnosis Where is the problem? Always in touch! Sweat the assets! Half the time to resolve problems Diagnosis is MUCH simpler If you can see it, you can do something about it. Its what you cant see that will kill you!

5. Why Monitoring Systems don't work • High upfront investment • Availability (and accessibility) of in-house skills to implement and support the solution • Technical complexity • Heavy resource impact on device and network • Ability to rapidly deliver value • Lack of tool flexibility • Never-ending configuration, maintenance and administration Gartner

6. How do we fit in OMA (Single Pane of Glass) EM EM ESM

7. How we fit in • What we deliver: • Problem identification • Mission critical (apps+infr) alerting • Our Historic deliverables • Planning advice Review, Review, Review Weekly Baseline Incident Monthly Baseline Problem Incident Administration Capacity Integrate into your operation Problem, Change, Capacity, Incident P R O C E S S We will instrument and hook to applications in every way that we can A P P S • Trusted performance and capacity advisor. • Go to guys for performance problems OMA – What we use to collect data and produce outputs

8. The Sourcing Schema - Leading Indicators 10 000 Counters x 100 Servers = 1 000 000 100 Counters x 100 Servers = 10 000 We alert on <10% of these. We poll every 2 minutes 100 Tests x 100 Servers / 2 = 5 000 tests / min = 7.2 million tests / day. Imagine making it more complicated • Out of a possible 10 000 counters • (Exchange has 1 700) 99.99% of the action with < 1% of the footprint! The law of diminishing utility 1st 10 tests = 50% utility 2nd 10 tests = 25% utility 3rd 10 tests = 12.5% utility Etc The 101th test = 0.01% utility = 99.99% utility.

9. The Sourcing Schema - Leading Indicators Top 10 (50%) Next 10 (75%) Next 10 System uptime Critical error logs Other services System temp Virus services % Processor time Disk Space Other key Exchange services Disk array status MTA services PSU & status Memory hard page faults Queues/store Memory available SMTP queue Next 10 Next 10 Next 10 Fan status Other memory tests Non critical logs Processor cache status Top processors Nic errors Mail flow indicators Other CPU tests Other exchange counters 10 000 Counters x 100 Servers = 1 000 000 100 Counters x 100 Servers = 10 000 We alert on <10% of these. We poll every 2 minutes 100 Tests x 100 Servers / 2 = 5 000 tests / min = 7.2 million tests / day. Imagine making it more complicated • Out of a possible 10 000 counters • (Exchange has 1 700) 99.99% of the action with < 1% of the footprint! The law of diminishing utility 1st 10 tests = 50% utility 2nd 10 tests = 25% utility 3rd 10 tests = 12.5% utility Etc The 101th test = 0.01% utility = 99.99% utility.

10. Horizontal vs. Vertical We are not going to configure your Netbotz, - use the Netbotz tool. We will tell you that your data centre is overheating, every time, only when it is. We will tell the correct person, even if you changed the configuration. If you want 10 000 tests, get SCom If you Want 96 tests that cover the 99.99%, get OMA! BotzView Mom/SCom 10 000 tests OMA 96 tests

11. How does our solution work (technical)? 1 2 3 DB DB Secure Comms DB DB Q Monitored Device Web PE DB DB A • No correlation required • No name translation required • No test differentiation required • No Contextual knowledge required • Completely “Rules” based DB DB Are you there? How much?

12. The Sourcing Solution and Business Model Sourcing Solution Business Model Automation as a philosophy Source code owned and developed internally South African solution designed for South African environments Rand based pricing model Software-as-a-Service (SaaS) delivery model It must work No Deployment, Licensing, Upgrade or Maintenance fees Software is Free and Evergreen • Fully integrated end-to-end solution • Significantly lower resource impact on IT environment than traditional ESM solutions • Quick deployment ensures quick business benefit • “Go-to-show” in less than six weeks • Instantaneous value • “Low noise” 24x7 multichannel notification engine

13. Our current Client portfolio

14. System Inputs Technology Areas Operating Systems Active Directory QOS NBAR NAS & SAN Radio LANs Wan Jet BizTalk Desktops Application Response Message Queues Assets Log & Text Files Databases Database Tables

15. System Outputs Availability, Capacity, Performance, Diagnostics Incidents Technology Agnostic diagnosis Single Pane of Glass Technology Agnostic Reporting

16. Multi-Functional Dashboard(IT Management View)

17. Multi-Functional Dashboard (Executive View)

18. Function Based Dashboard

19. Graphing and Trending of Performance Counters

20. Router Dashboard

21. Protocol Analysis

22. Application Response Monitoring

23. User Experience

24. Application and End User Response Monitoring

25. Branch Ready

26. OMA Attendant

27. SLA & Availability Reporting

28. Application Monitoring

29. Log File Parsing

30. Log File Parsing

31. Backup Monitoring

32. Database Table Monitoring Secure Comms PE

33. Instrumentation Counters Counters Custom Application Code Counters

34. Application Monitoring

35. User Experience

36. Reporting Engine

37. Incidents

39. Availability