Application Performance Monitoring with Operations Manager 2012
As posted yesterday on the Server Cloud blog, we have released the Release Candidate of Operations Manager 2012. This is a significant milestone release, and in this article we will explore how Operations Manager 2012 Release Candidate delivers application performance monitoring.
For those of you who have downloaded and tested the Operations Manager Beta, there is new content and capability in the Release Candidate, so read on!
Operations Manager 2012 – the complete application monitoring solution
Operations Manager for many years has delivered Infrastructure monitoring, providing a strong foundation for which we can build on to deliver application performance monitoring. It is important to understand that in order to provide the application level performance monitoring, we must first have a solid infrastructure monitoring solution in place. After all, if an application is having a performance issue, we must first establish if the issue is due to an underlying platform problem, or within the application itself.
A key value that Operations Manager 2012 delivers is a solution that uses the same tools to monitor with visibility across infrastructure AND applications.
To deliver application performance monitoring, we provide 4 key capabilities in Operations Manager 2012:
- Infrastructure monitoring – network, hardware and operating system
- Server-side application monitoring – monitoring the actual code that is executed and delivered by the application
- Client-side application monitoring - end-user experiences related to page load times, server and network latency, and client-side scripting exceptions
- Synthetic transaction – pre-recorded testing paths through the application that highlight availability, response times, and unexpected responses
Configuring application performance monitoring
So it must be hard to configure all this right? Lots of things to know, application domain knowledge, settings, configurations? Rest assured, this is not the case! We make it incredibly easy to enable application performance monitoring!
It’s as easy as 1 – 2 – 3 …
1. Define the application to monitor.
2. Configure server-side monitoring to be enabled and set your performance thresholds
3. Configure client-side monitoring to be enabled and set your performance thresholds
And that’s it, you’re now set to go. Of course setting the threshold levels is the most important part of this, and that is the one thing we can’t do for you … you know your application and what the acceptable performance level is.
Configuring an application performance dashboard in 4 steps
It’s great that we make the configuration of application performance monitoring so easy, but making that information available in a concise, impactful manner is just as important.
We have worked hard to make the creation of dashboards incredibly easy, with a wizard driven experience. You can create an application level dashboard in just 4 steps:
1. Choose where to store the dashboard
2. Choose your layout structure. There are many different layouts available.
3. Specify which information you want to be part of your dashboard.
4. Choose who has access to the dashboard. As you will see a little later in this article, publishing information through web and SharePoint portals is very easy.
And just like that, you’ve created and published an application performance monitoring dashboard!
Open up the conversation
Anyone who has either worked in IT, or been the owner of an application knows the conversations and finger pointing that can go on when users complain about poor performance. Is it the hardware, the platform, a code issue or a network problem?
This is where the complete solution from Operations Manager 2012 really provides an incredible solution. It’s great that an application an associated resources is highly available, but availability does not equal performance. Indeed, an application can be highly available (the ‘5 nines’) but performing below required performance thresholds.
The diagram below shows an application dashboard that I created using the 4 steps above for a sample application. You can see that the application is available and ‘green’ across the board. But the end users are having performance issues. This is highlighted by the client side alerts about performance.
Deep Insight into application performance
Once you know that there is an issue, Operations Manager 2012 provides the ability to drill into the alert down to the code level to see exactly what is going on and where the issue is.
Reporting and trending analysis
An important aspect of application performance monitoring is to be able to see how your applications are performing over time, and to be able to quickly gain visibility into common issues and problematic components of the application.
In the report shown below, you can see that we can quickly see areas of the application we need to focus on, and also understand how these components are related to other parts of the application, and may be causing flow-on effects.
Easily make information available
With Operations Manager 2012, we have made it very easy to delegate and publish information across multiple content access solutions. Operations staff have access to the Operations Manager console, and we can now easily publish delegated information to the Silverlight based Operations web console and also to SharePoint webparts.
And best of all, the information looks exactly the same!
Calls to Action!
It looks great, you want to get started and see how Operations Manager application performance monitoring will work for you in your environment, so where do you start?
- Get involved in the Community Evaluation Program (CEP). We are running a private cloud evaluation program starting in November where we will step you through the entire System Center Private Cloud solution set, from Fabric and Infrastructure, through Service Delivery & Automation and Application Management. Sign up here.
- Read the online documentation
- Participate in the online TechNet Forums
- Download the Operations Manager 2012 Release Candidate here