Accelerate Troubleshooting and Reinvent Monitoring with Interactive Visualizations

Editor's Notes

• #5: Splunk safe harbor statement.
• #7: First of all I want to level set and talk about Splunk Because ITSI runs on top of the Splunk platform At it’s core, the Splunk platform enables you to: Collect data from anywhere – with universal forwarding and and of course our powerful indexing technology. Search and analyze across all your data – with powerful search and schema on the fly technology. Schema on the fly means you don’t have to structure your data before sending it into Splunk. We only need a couple of data fields host or sourcetype as an identifier and then essentially everything else is on the fly This gives you a very powerful search capability which allows you to pretty much search through anything without having to structure data. AlWe can Rapidly deliver real-time insights from machine data to IT and business people – through a powerful UI and dashboards all based on our search technology. This is what we call Operational Intelligence. So that rounds up the core functionality of the splunk platform which ITSI is built on.
• #8: So a quick chat about where splunk has come from Initially we were founded on enabling IT administrators to solve IT challenges but over the years we’ve manifested this into various other use cases including Application Management, Security and Compliance (the top 3 being our core use-cases) We now of course have exciting new use cases around Business Analytics and IoT, all of which has been led by our customers. As our customers grow their asks from Splunk also began to evolve. They’re looking for an integrated holistic packaged solution that helps them break-down information silos. They want to apply machine learning to enable their business analysts and IT practitioners with the right data at the right time. They want to exploit the data they have within Splunk to discover new ways to improve their operations against real business priorities with the end goal of achieve real differentiated advantage in the market and business growth. Of course to do this they want to gain the highest levels of adoption of these data insights into as many use cases as possible They want to Not just meet SLAs but use their captured performance data to plan and invest at the right time…integrated capacity planning They want to have operational visibility shared across a widest audience to improve communication They want to get ahead of service problems and empower their DevOps processes
• #9: That brings us to Splunk IT Service Intelligence – a packaged solution that enables real-time visibility into services driven by machine data. Splunk ITSI speeds and simplifies service monitoring and analytics and enables IT to make better, smarter and informed business decisions. It’s a solution which allows you to gain a really deep understanding of your services. With ITSI, you have real-time views into the health of your services… You can use advanced analytics to find patterns, detect anomalies and trends acting proactively to monitor and address issues. The end result is you have improved service visibility, reduced resolution times, and a transformation within your business and technology teams in their approach to monitoring and analytics driven by machine-data.
• #10: This slide rally gives you a good idea of where ITSI sits in the ecosystem of Splunk. You can see that ITSI which is shown really as the grey bar and the functionality above sits on and dependent on the core of the Splunk platform. We make use of the Time Series index ; Schema on Read ; its data model and of course the common information model What we’ve built in ITSI is that layer on top of Splunk… The ability to build dynamic service models to aide diagnostic and reporting processes To enable at-a-glance problem analytics we’ll talk in the next webinar about early warning on deviation and today we will focus on simplified incident workflows with the right dashboards and consoles at you fingertips…to go from detecting a deviation to a norm in a service view to deep technical diagnostics and root cause analysis
• #12: Concepts that we use with ITSI First of all, what is a service? I’m not exacting here, I don’t care what you which to define as a service, business or technology. A service is simply a contracted facility a group of processes that is offered by one group or team to another Services are high level concepts but very important to your organisations Business processes are the set of actions performance with specific business goals…..Request to fulfilment Business services will often be made up of many processes Theses processes will supported by systems, whether IT, manufacturing or people and the individual components of these systems we call entities We create entities in ITSI because they have data associated with them that we what to evaluate…simple really, hosts users, OS processes The data we are evaluating we group together and evaluate through KPIs…these are the significant metrics which we care about and are essential to ITSI…Things we want to measure
• #13: I’ve given you the preamble of Splunk and the terminology associated with ITSI Now we are going to start talking about what we are going to show you today, Troubleshooting with ITSI We’re going to show you how we can start with high level visualizations to review service health, to help us understand when we do have a problem with our service and to enable communication between teams How to progress into a deeper view for analysis and diagnostics. Root causes analysis using drilldown through custom visualizations and method with ITSI How we combine metrics to provide both automated and heuristic approaches to provide greater insight into service health …and how once we have found the root cause of a problem we can build preventative measures to make sure we proactive catch similar problems in the future
• #16: If you are looking to understand ITSI and evaluate it should be done in context of a service Complex organization will have countless services and these services can be layered on each other and be nested within other services…this hopefully all makes sense Now when we are modelling services we want to look at one that people care about. Bring experts together who are motivated And most of all design before implementation