Configuring the Management Pack for Operations Manager APM Web IIS 7
Applies To: System Center 2012 - Operations Manager
Not much needs to be configured for this management pack. This management pack only complements parts of APM that are already installed by default with System Center 2012 - Operations Manager.
This section provides guidance on configuring and tuning this management pack.
Best Practice: Create a Management Pack for Customizations
Configuring IIS 7.0 Discovery Rules
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.
Configuring IIS 7.0 Discovery Rules
This management pack only contains a set of special rules that essentially act as discoveries. Within this management pack, the “original” discoveries that ship with the Internet Information Services (IIS) 7 Management Pack are disabled through overrides and the new rules are enabled.
This mechanism has been implemented as a “pluggable” replacement of the existing IIS discoveries to achieve greater scalability, robustness, and performance of IIS discovery on agents that host hundreds of websites and web applications – while still discovering the same types of objects, hence maintaining compatibility with and preserving existing monitoring investments. It also allows Operations Manager to discover additional, new object types (such as WCF endpoints) that are not normally discovered by IIS MP.
The new rule/discovery can:
Automatically discover ASP.NET Web Applications that have at least a page with *.aspx file name extension
Automatically discover ASP.NET Web Services that have at least a file with *.asmx extension
Automatically discover ASP.NET Web Applications built using the MVC framework 2 and 3 if they also contain pages with *.aspx file name extension in the root folder
Automatically discover IIS-Hosted WCF endpoints that have at least a file with *.svc extension
Discover empty directories as either Web Applications or Web Services, if configured to do so
Discover directories with non-standard file name extensions, if configured to do so
IIS 7.0 Discovery Overrides
The rule “IIS 7.0 Web Application Discovery” is configurable through a set of overrides to achieve all of the possible combinations of the behaviors described above:
The overrides let you tweak the configuration to discover as “web applications” or “web services”, for monitoring with APM, directories that contain webpages or web services with non-standard file name extensions, or even empty directories. The parameters you can override are described in the following table:
| Parameter name | Description |
|---|---|
Additional file name extensions for ASP.NET Web Application discovery |
Provide a list of file name extensions, separated by a semi-colon (;), that should be used to identify an application as an ASP.NET Web Application. The default pattern used by the IIS 7.0 discovery is to look for .aspx files in the virtual directory, if any are found an ASP.NET Web Application endpoint will be created. An example of a new file name extension list string is "example;bar" that specifies files such as myFile.example and myFile.bar represent ASP.NET Web Applications. |
Additional file name extensions for ASP.NET Web Service discovery |
Provide a list of file name extensions, separated by a semi-colon (;), that should be used to identify an application as an ASP.NET Web Service. The default pattern used by the IIS 7.0 discovery is to look for .asmx files in the virtual directory, if any are found an ASP.NET Web Service endpoint will be created. An example of a new file name extension list string is "example;bar" that specifies files such as myFile.example and myFile.bar represent ASP.NET Web Services. |
Discover all directories as ASP.NET Web Application |
Set to True to discover an application that was not previously discovered as an ASP.NET Web Application or ASP.NET Web Service. This flag configures the IIS discovery workflow to discover the unknown applications as ASP.NET Web Applications so that you can monitor them with the .NET Application Performance Monitoring template. |
Discover empty directories as ASP.NET Web Application |
Set to True to treat applications with an empty root virtual directory as an ASP.NET Web Application. |
Discover empty directories as ASP.NET Web Service |
Set to True to treat applications with an empty root virtual directory as an ASP.NET Web Service. |
PeriodInSeconds |
How often the rule/discovery runs. |
Using the .NET Application Performance Monitoring Template
Although this management pack does not contain a template of its own, the discoveries it contains are necessary to have objects show up in the .NET Application Performance Monitoring template. It is therefore a prerequisite that this management pack is imported, or no object will be available for monitoring when running the .NET Application Performance Monitoring template.
For more information on how to configure the .NET Application Performance Monitoring template, see Using the .NET Application Performance Monitoring Template