1. How to Model an Application for Monitoring Nathan Foreman @Nate_Foreman Nathan@Practice2Perfect.com Jonathan Almquist @jtalmquist jonathan@scomskills.com

2. #MMSMOA @jtalmquist Consultant, blogger, author, speaker TechNet Forum blog.scomskills.com 16 years experience in IT, past 10 years focused on Operations Manager Jonathan Almquist

3. #MMSMOA @Nate_Foreman Solutions Engineer Practice2Perfect.com 10+ years in IT Nathan Foreman

4. Overview and Agenda Session Overview Phases and activities Review management pack development lifecycle Discuss activities included in modeling an in-house application for monitoring Hands-on using basic or free tools Demonstrate how activities may be implemented in real-world scenario Demonstrate how to document requirements using the UML (umlet)

5. Phases and ActivitiesPhases and Activities How modeling fits into the development lifecycle

6. Phases and Activities Management Pack Development Lifecycle Application Analysis Requirement s Gathering Developmen t & Testing Implement, Validate & Tune 5% 40% 50% 5% Activities included in application modeling How much time is really spent in each of these phases?

7. Phases and Activities Activities Discovery >Explain phases and activities >Receive application diagram >Document key components >Show example of end result Dependencies Document dependency packs and relationships Company Knowledge Document potential monitoring scenarios Application Analysis Outputs What does it do? How does it work? Review diagrams, flowcharts Review example model Identify supporting technologies Reference vendor packs as dependencies Most common support incidents raised Well-defined failure modes (reproducible) Known application faults

8. Phases and Activities Activities Data Sources >Event log criteria >Performance counters >HTTP endpoints >Custom modules Service Model Single document including service model and all CI Requirements Gathering Outputs Transport s and interfaces Scripts and queries Loggers and queues Service and user endpoints UML elements library Plot classes and relationship s Identify propertie s Document CI for monitoring

9. Phases and Activities Key Takeaways Navigating the conversation with the customer Using activity diagrams to help conversation flow Customer understands phases and activities Customer has a vision of end result Developer has all necessary information Everyone has one source document to be used and referenced

10. Demo Walk-thru activities to model fictitious Widgets application

11. Umlet download http://www.umlet.com/ Umlet elements library http://blog.scomskills.com (coming soon) http://blog.scomskills.com

12. Evaluations: Please provide session feedback by clicking the EVAL button in the scheduler app (also download slides). One lucky winner will receive a free ticket to the next MMS! Session Title: How to Model an Application for Monitoring Discuss… Ask your questions-real world answers! Plenty of time to engage, share knowledge. SPONSORS