Filtering Azure Applications in SCOM 2012 Performance Views

Okay, so you now have your shiny, new installation of SCOM 2012 up and running. You have migrated your old Windows Azure management pack using the Visual Studio Authoring Extensions for Visual Studio 2010, using techniques from my previous post here. You have created some new Performance views based on the now shipping SCOM 2012…

0

Using the New Visual Studio 2010 Authoring Extensions to Create SCOM 2012 Rules for Windows Azure

Unless you enjoy creating SCOM 2012 management packs by hand, you will want a tool to ease the creation of rules and monitors that target Windows Azure PaaS applications. Well you’re in luck with the new System Center 2012 Visual Studio Authoring Extensions (VSAE) for Visual Studio 2010 Professional, which you can download here. This…

1

Resolving Windows Azure Diagnostics Connection String Issues with SCOM 2007 R2

In earlier versions of the Windows Azure SDK, the default Windows Azure Diagnostics string provided by the Visual Studio template in the service configuration file was named DiagnosticsConnectionString. Later Windows Azure SDKs have changed this name to Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString. By default, however, the SCOM 2007 R2 Windows Azure Management Pack continues to reference the DiagnosticsConnectionString setting…

4

Grooming Collected Diagnostics Data from Windows Azure Storage in SCOM 2007 R2

Recently, I had a colleague ask me how to groom diagnostic data collected in Windows Azure storage from Windows Azure applications. Since he is using SCOM, there is a ready answer for configuring regular grooming of Windows Azure diagnostic data, thus saving on storage consumption costs and preventing massive quantities of data from accumulating over…

0

SCOM 2007 R2 Event Log Alerting and Monitoring for Azure Applications

Through rules, SCOM provides a powerful system for capturing specific events from the event log of Windows Azure applications and notifying various groups of critical events through SCOM alerts. Events are stored in the SCOM database, which can be analyzed in views and reports. This walkthrough will demonstrate how to create a rule that captures…

5

Configuring SCOM 2007 R2 Performance Views and Dashboards for Monitoring Azure Applications

In previous blog posts I demonstrated how to setup your Azure performance counters, how to install SCOM 2007 R2 along with the Windows Azure Management Pack, and how to configure Azure Diagnostics performance counter monitoring in SCOM 2007 R2. In this post, I will pick up where I left off to demonstrate how to build…

0

Configuring Azure Diagnostics Performance Counter Monitoring in SCOM 2007 R2

In my last post, I provided a primer on installing SCOM 2007 R2 along with the Azure Management Pack (which is still currently in Release Candidate status). In the post before that, I showed you how to setup the performance counters in your web and worker roles in Visual Studio 2010 so you could generate…

8

A Primer on Installing SCOM 2007 R2 and Windows Azure Application Monitoring

You can find the full procedures in the SCOM 2007 R2 Deployment Guide and Azure Management Pack documentation, but I am providing this to give you visuals with some “hard won” experience that augments those instructions and provides a bit more hand-holding. The first order of business will be to verify that you have your…

6

Setting Up Performance Counters In Your Azure Web and Worker Roles

For those wondering how to setup performance counters on your web or worker roles when you deploy your Azure applications, wonder no more, as this post will help to get you started. Azure does not automatically setup performance counters for you from your Azure roles.  You must set them up yourself in the OnStart method…

2

XML Namespace Issue in Azure Diagnostics Event Log Entries

I recently had a customer migrating an application to Azure whose policy is to send well-formed XML with detailed error information to the event log whenever errors are detected in their applications. The customer was getting errors when including XML namespaces in their detailed event log entries.  For example, their event log entries were constructed…

0