Guide for System Center Management Pack for Windows Azure Pack: Web Sites

Guide for System Center Management Pack for Windows Azure Pack: Web Sites

Microsoft Corporation

Published: October 2013

Send feedback or suggestions about this document to . Please include the management pack guide name with your feedback.

The Operations Manager team encourages you to provide feedback on the management pack by providing a review on the management pack’s page in the Management Pack Catalog (http://go.microsoft.com/fwlink/?LinkID=82105).

Copyright

This document is provided "as-is". Information and views expressed in this document, including URL and other Internet Web site references, may change without notice.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.

© 2013 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Bing, BizTalk, Forefront, Hyper-V, InternetExplorer, JScript, SharePoint, Silverlight, SQL Database, SQLServer, Visio, VisualBasic, VisualStudio, Win32, Windows, WindowsAzure, WindowsIntune, WindowsPowerShell, Windows Server, and WindowsVista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Contents

Guide for System Center Management Pack for Windows Azure Pack: Web Sites 4

Guide History 4

Supported Configurations 4

Management Pack Scope 4

Files in this Management Pack 5

Management Pack Purpose 5

Monitoring Scenarios 5

Classes 6

How Health Rolls Up 7

Configuring the Management Pack for Windows Azure Pack Web Sites 8

Best Practice: Create a Management Pack for Customizations 8

Links 8

System Center 2012 - Operations Manager 8

Operations Manager 2007 R2 9

Appendix: Management Pack Contents 9

Guide for System Center Management Pack for Windows Azure Pack: Web Sites

This guide was written based on version 1.0.0.0 of the Management Pack for Windows Azure Pack: Web Sites.

Use the management pack to monitor the web role instances within a Windows Azure Pack: Web Sites deployment.

Guide History

Release Date / Changes /
October 2013 / Original release of this guide

Supported Configurations

This management pack requires System Center 2012 - Operations Manager or later. This management pack does not require a dedicated Operations Manager management group.

This Management Pack supports monitoring of a Windows Azure Pack: Web Sites deployment, the web role servers, and key services.

The following table details the supported configurations for the Management Pack for Windows Azure Pack Web Sites:

Operating system / Virtual Servers / Physical Servers /
(x64) / (x86) / (x64) / (x86)
Microsoft Windows Server2012 / X / NA / X / NA
Microsoft Windows Server2012 R2 / X / NA / X / NA

Management Pack Scope

The Management Pack contains the following features:

· Discovery of Windows Azure Pack: Web Sites servers and their roles.

· Ability to perform "Reboot a server role" operation.

· Status monitoring for Windows Azure Pack: Web Sites required services.

· Event generation for select Windows Azure Pack: Web Sites services.

Files in this Management Pack

The Management Pack for Windows Azure Pack: Web Sites includes the following files:

· Microsoft.WebSites.Library.mp

· Microsoft.WebSites.Monitoring.mp

Management Pack Purpose

In this section:

· Monitoring Scenarios

· How Health Rolls Up

For details on the discoveries, rules, monitors, views, and reports contained in this Management pack, see Appendix: Management Pack Contents.

Monitoring Scenarios

Monitoring scenario / Description / Associated rules and monitors /
Controller Role health / This scenario checks essential services that the Controller role uses. The scenario verifies that the services operate and have sufficient resources. / · Controller Web Farm Controller Service
· Controller Resource Metering
Front End health / This scenario checks essential services that the Front End role uses. The scenario verifies that the services operate and have sufficient resources. / · Front End Web Farm Agent Service
· Front End Resource Metering
Publisher health / This scenario checks essential services that the Publisher role uses. The scenario verifies that the services operate and have sufficient resources. / · Publisher FTP Service
· Publisher Resource Metering
· Publisher Web Deployment Agent Service
· Publisher Web Farm Agent Service
Management Server health / This scenario checks essential services that the Management Server role uses. The scenario verifies that the services operate and have sufficient resources. / · Management Service Web Farm Agent Service
· Management Service Resource Metering
· Management Service Usage Service
Web Worker health / This scenario checks essential services that the Web Worker role uses. The scenario verifies that the services operate and have sufficient resources. / · Web Worker Web Farm Agent Service
· Web Worker DWAS Service
· Web Worker Resource Metering

Classes

The following illustration shows the classes defined in this management pack.

How Health Rolls Up

The following diagram shows how the health states of objects roll up in this management pack.

Configuring the Management Pack for Windows Azure Pack Web Sites

This section provides guidance on configuring and tuning this management pack.

· Best Practice: Create a Management Pack for Customizations

Best Practice: Create a Management Pack for Customizations

By default, Operations Manager saves all customizations such as overrides to the Default Management Pack. As a best practice, you should instead create a separate management pack for each sealed management pack you want to customize.

When you create a management pack for the purpose of storing customized settings for a sealed management pack, it is helpful to base the name of the new management pack on the name of the management pack that it is customizing.

Creating a new management pack for storing customizations of each sealed management pack makes it easier to export the customizations from a test environment to a production environment. It also makes it easier to delete a management pack, because you must delete any dependencies before you can delete a management pack. If customizations for all management packs are saved in the Default Management Pack and you need to delete a single management pack, you must first delete the Default Management Pack, which also deletes customizations to other management packs.

Links

The following links connect you to information about common tasks that are associated with System Center management packs:

System Center 2012 - Operations Manager

· Management Pack Life Cycle

· How to Import a Management Pack

· Tuning Monitoring by Using Targeting and Overrides

· How to Create a Run As Account

· How to Export a Management Pack

· How to Remove a Management Pack

Operations Manager 2007 R2

· Administering the Management Pack Life Cycle

· How to Import a Management Pack in Operations Manager2007

· How to Monitor Using Overrides

· How to Create a Run As Account in Operations Manager2007

· How to Modify an Existing Run As Profile

· How to Export Management Pack Customizations

· How to Remove a Management Pack

For questions about Operations Manager and management packs, see the System Center Operations Manager community forum.

A useful resource is the System Center Operations Manager Unleashed blog, which contains "By Example" posts for specific management packs.

For additional information about Operations Manager, see the System Center 2012 - Operations Manager Survival Guide and Operations Manager 2007 Management Pack and Report Authoring Resources

Important

All information and content on non-Microsoft sites is provided by the owner or the users of the website. Microsoft makes no warranties, express, implied, or statutory, as to the information at this website.

Appendix: Management Pack Contents

The Management Pack for Windows Azure Pack: Web Sites discovers the object types described in this appendix. The management pack does not automatically discover all of the objects. Use overrides to discover those objects that the management pack does not discover automatically.

Discoveries

Discoveries / Description / Method /
Microsoft.WebSites.Controller.Discovery / Registry Discovery to discover Web Sites Controller Role Instance class. / Registry Discovery
Microsoft.WebSites.ControllerRole.Discovery / Registry Discovery to discover Web Sites Controller Role class. / Registry Discovery
Microsoft.WebSites.ControllerRole.Membership / Registry Discovery to discover Web Sites Controller Role Membership. / Registry Discovery
Microsoft.WebSites.FrontEnd.Discovery / Registry Discovery to discover Web Sites Front End Role Instance class. / Registry Discovery
Microsoft.WebSites.FrontEndRole.Discovery / Registry Discovery to discover Web Sites Front-End Role class. / Registry Discovery
Microsoft.WebSites.FrontEndRole.Membership / Registry Discovery to discover Web Sites Front End Role Membership. / Registry Discovery
Microsoft.WebSites.ManagementServer.Discovery / Registry Discovery to discover Web Sites Controller Role Instance class. / Registry Discovery
Microsoft.WebSites.ManagementServerRole.Discovery / Registry Discovery to discover Web Sites Management Server Role class. / Registry Discovery
Microsoft.WebSites.ManagementServerRole.Membership / Registry Discovery to discover Web Sites Management Server Role Membership. / Registry Discovery
Microsoft.WebSites.Publisher.Discovery / Registry Discovery to discover Web Sites Management Server Role Instance class. / Registry Discovery
Microsoft.WebSites.PublisherRole.Discovery / Registry Discovery to discover Web Sites Publisher Role class. / Registry Discovery
Microsoft.WebSites.PublisherRole.Membership / Registry Discovery to discover Web Sites Publisher Role Membership. / Registry Discovery
Microsoft.WebSites.WebWorker.Discovery / Registry Discovery to discover Web Sites Publisher Role Instance class. / Registry Discovery
Microsoft.WebSites.WebWorkerRole.Discovery / Registry Discovery to discover Web Sites Web Worker Role class. / Registry Discovery
Microsoft.WebSites.WebWorkerRole.Membership / Registry Discovery to discover Web Sites Web Worker Role Membership. / Registry Discovery
Microsoft.WebSites.Service.Discovery / Registry Discovery to discover Web Sites Service Role class. / Registry Discovery
Microsoft.WebSites.Service.Membership / Registry Discovery to discover Web Sites Service Role Membership. / Registry Discovery

This management pack adds the following monitors. Reach Role Type has Role instances that are machines running various services that Windows Azure Pack: Web Sites requires to run in a healthy fashion.

Monitors

Role / Monitor / Error Level / Condition Detected / Auto Resolve / Troubleshooting /
Controller / Web Farm Controller Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check event logs, and restart the service.
Controller / Resource Metering / Critical / Alert triggered if the service is in stopped state. / Yes / Check SQL DB Disk Space, event logs, and restart the service.
Front End / Web Farm Agent Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check event logs, and restart the service.
Front End / Resource Metering / Critical / Alert triggered if the service is in stopped state. / Yes / Check SQL DB Disk Space, event logs, and restart the service.
Publisher / Microsoft FTP Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check event logs, and that proper ports are open in machine as well as in domain firewall.
Publisher / Resource Metering / Critical / Alert triggered if the service is in stopped state. / Yes / Check SQL DB Disk Space, event logs, and restart the service.
Publisher / Web Deployment Agent Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check event logs, and that proper ports are open in machine as well as in domain firewall.
Publisher / Web Farm Agent Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check event logs, and restart the service.
Management Server / Web Farm Agent Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check event logs, and restart the service.
Management Server / Resource Metering / Critical / Alert triggered if the service is in stopped state. / Yes / Check SQL DB Disk Space, event logs. and restart the service.
Management Server / Usage Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check SQL DB Disk Space, event logs, and restart the service.
Web Worker / Web Farm Agent Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check event logs, and restart the service.
Web Worker / DWAS Service / Critical / Alert triggered if the service is in stopped state. / Yes / Check event logs, and restart the service.
Web Worker / Resource Metering / Critical / Alert triggered if the service is in stopped state. / Yes / Check SQL DB Disk Space, event logs, and restart the service.

Groups

Role / Monitors / Error Level / Condition Detected / Auto Resolve / Troubleshooting /
Controller Role Monitor / Role Instance Service Cumulative Service Health / Critical / Alert Triggered if 50% of the Controllers are unhealthy. / Yes / Controllers become unhealthy due to non-availability and critical services not running.
Management Role Monitor / Role Instance Service Cumulative Service Health / Critical / Alert Triggered if 50% of the Management Servers are unhealthy. / Yes / Management servers become unhealthy due to non-availability and critical services not running.
Publisher Role Monitor / Role Instance Service Cumulative Service Health / Critical / Alert Triggered if 25% of the Publishers are unhealthy. / Yes / Publishers become unhealthy due to non-availability and critical services not running.
Front End Role Monitor / Role Instance Service Cumulative Service Health / Critical / Alert Triggered if 25% of the Front End are unhealthy. / Yes / Front Ends become unhealthy due to non-availability and critical services not running.
Web Worker Role Monitor / Role Instance Service Cumulative Service Health / Critical / Alert Triggered if 25% of the Web Worker are unhealthy. / Yes / Web Workers become unhealthy due to non-availability and critical services not running.

5