Today we are proud to announce IT Service Analytics (www.itserviceanalytics.com), a plug ´n play business intelligence platform for Microsoft System Center. With your IT services in focus this toolset is built on IT Service Management (ITSM). It allows you to combine IT process data such as incidents-, change-, problem management with operational data from Microsoft System Center Operations Manager (SCOM) and log analytics from Microsoft Operations Management Suite (OMS). Make qualified decisions based on intelligent and accurate information thanks to a 360 end-to-end view of operations management and the ability to extract, correlate and predict information about IT Service Management processes. By implementing advanced analytics and statistical capabilities from data already collected, IT Service Analytics will turn your data into knowledge. IT Service Analytics is a comprehensive toolset to keep you one step ahead of the business demands while delivering high quality IT services.
You have both hourly and daily data for service component availability, performance, events and alerts gathered in SCOM. Since it is just heaps of data, it can be difficult to get an understanding whether any of the logged events occur according to some kind of time pattern and when any of them relate to one another. Recognizing reocurrences is very beneficial when managing sparse and at first sight unrelated events. After grouping and filtering all events by an identified time pattern we are able to find correlations and (hopefully) causations of specific happenings. In this blog post we will review the built-in SCOM reports for analyzing this kind of data and will also show you how adding some extra capabilities makes life much easier.
I bet we would all agree that the ultimate goal of IT monitoring is to prevent IT service outages. But admit, even with all the monitors set up in System Center Operations Manager and alerts configured to notify admins when vital thresholds have been reached, we are still not being efficient enough in solving (not to mention preventing) critical issues on time. Dealing with alerts generated in SCOM has multiple complications. Too many alerts being generated and no clear priority system are a few examples, leading administrators into ‘alert ignorance’. In this article we are going to look at a different approach to identifying upcoming issues in your IT environment which will introduce clarity and guidance into the assorted jungle of alerts and capacity issues.
With the massive amount of data collected in the System Center Operations Manager from all servers and other monitored equipment, IT Operations departments are sitting on a gold mine of data just begging to be used. One of the areas that can benefit from such internal data capital is forecasting. By implementing forecasting processes you can predict the behavior of managed objects some months into the future. This knowledge enables you to act in advance in order to prevent service failures and service level breaches. Most business areas use some kind of forecasting methods when planning new investments, calculating yearly budgets etc. We believe that IT organizations should be no different and start using operational data to gain insights and learn from the past while planning their future.
Operations Manager is good at monitoring performance of separate software components.It also has an interface to bundle them together into groups in order to be able to understand what the health state of the whole as a group is. In SCOM context this is called a Distributed Application. At Approved we treat this (with addition of Live Maps Unity from Savision) as an interface for managing IT Services. As in most cases after getting data into SCOM and then into SCOM Data Warehouse, some day we want to extract and analyze this data or, better yet, use it as a base to predict future outcomes and deal with issues before users even notice them. And, as in most cases, extracting and querying SCOM DW Distributed Application data is not really straightforward. Lets start with finding the ‘services’ themselves.