none
Application Monitoring not finding an IIS .NET app RRS feed

  • Question

  • Trying to test out APM and having a minor show stopper. Not sure where to start troubleshooting.

    I'm unable to find a newly created web site in the 'What To Monitor' pane of the APM Add Monitoring Wizard. All I see is 'Default Web Site' component when I Search (leaving the filter empty). I waited 24 hours to see if a discovery script needed to run, but it hasn't shown up yet. Any ideas where to start looking for the problem?

    Details of the environment:

    • OpsMgr 2012 RC on Windows 2008 R2 Server
    • SQL 2008 R2 SP1 on same box as OpsMgr (lab environment).
    • IIS Server is windows 2008 R2 with .NET 4.0 installed and OpsMgr Agent successfully installed.
    • Installed nopCommerce for testing on the IIS Server as NEW website (not in Default Web Site). App is up and running successfully.
    • In the OpsMgr Console > Monitoring > Microsoft Windows Internet Information Services > Web Site State, I can see the nopCommerce website on the IIS Server and it shows as healthy.

    Thanks!

    Bill


    gaurhoth

    Wednesday, February 29, 2012 3:00 PM

Answers

  • Which version of nopCommerce are you using? I see the latest one ( http://nopcommerce.codeplex.com/releases/view/69080 ) has been changed to use MVC as opposed to WebForms.

    In OpsMgr 2012 we don't yet discover nor officially support MVC-based applications by default --> we rely on the presence of an *.aspx page in the root directory to discover the application endpoint, by default. MVC applications don't have that.

    This said, there is a rule defined in the Operations Manager APM Web IIS 7 MP called "IIS 7.0 Web Application Discovery" (in RTM) or "Rule that extends the IIS Module Settings by setting registry keys" (in RC) that can overriden to specify how the IIS module handles discovery.  The key properties that need to be overriden are either "Discovery emptry directories as ASP.NET Web Application" or "Additional file extensions for ASP.NET Web Application Discovery".  Those overrides allow you to specify that you should discovery an empty IIS vdir as an ASP.NET
    web app or add additional 'finger print' files to use, for example ".asax" which coresponds to global.asax.

    This is being documented for RTM.

    Anyhow, being able to discover is only part of the issue. There are also namespaces, entry points, exception handlers, etc that are related to MVC and need to be properly added to get full monitoring of MVC applications. Full MVC support, adding namespaces, entrypoint, exception handlers and such is something we're working on.

    Let me know if this helps.


    Wednesday, February 29, 2012 4:56 PM
  • FYI, the discovery overrides and options have been now documented in the MP Guide at this address: http://technet.microsoft.com/en-us/library/hh916929.aspx
    Monday, April 2, 2012 4:04 PM

All replies

  • Which version of nopCommerce are you using? I see the latest one ( http://nopcommerce.codeplex.com/releases/view/69080 ) has been changed to use MVC as opposed to WebForms.

    In OpsMgr 2012 we don't yet discover nor officially support MVC-based applications by default --> we rely on the presence of an *.aspx page in the root directory to discover the application endpoint, by default. MVC applications don't have that.

    This said, there is a rule defined in the Operations Manager APM Web IIS 7 MP called "IIS 7.0 Web Application Discovery" (in RTM) or "Rule that extends the IIS Module Settings by setting registry keys" (in RC) that can overriden to specify how the IIS module handles discovery.  The key properties that need to be overriden are either "Discovery emptry directories as ASP.NET Web Application" or "Additional file extensions for ASP.NET Web Application Discovery".  Those overrides allow you to specify that you should discovery an empty IIS vdir as an ASP.NET
    web app or add additional 'finger print' files to use, for example ".asax" which coresponds to global.asax.

    This is being documented for RTM.

    Anyhow, being able to discover is only part of the issue. There are also namespaces, entry points, exception handlers, etc that are related to MVC and need to be properly added to get full monitoring of MVC applications. Full MVC support, adding namespaces, entrypoint, exception handlers and such is something we're working on.

    Let me know if this helps.


    Wednesday, February 29, 2012 4:56 PM
  • FYI, the discovery overrides and options have been now documented in the MP Guide at this address: http://technet.microsoft.com/en-us/library/hh916929.aspx
    Monday, April 2, 2012 4:04 PM
  • Daniele,  I am not finding this rule in the APM or IIS MP is there a newer MP for SCOM 2012?

    Wednesday, May 16, 2012 1:34 PM
  • It is documented in the MP Guide at this address: http://technet.microsoft.com/en-us/library/hh916929.aspx --> and it is contained in the MP that this guide refers to (Microsoft.SystemCenter.Apm.Web.IIS7.mp), which is on the Opsmgr media under the /ManagementPacks folder and not imported by default.

    Wednesday, May 16, 2012 3:29 PM
  • I figured it out I was missing the Microsoft.SystemCenter.Apm.Web.IIS7.mp.

    Wednesday, May 16, 2012 6:27 PM
  • Yup - "Before You Begin Monitoring .NET Applications" http://technet.microsoft.com/en-us/library/hh543994
    Wednesday, May 16, 2012 6:35 PM
  •  I had trouble trying to get the rule. Thanks to http://blogs.inframon.com/post/2012/06/13/Discovering-Web-Applications-in-SCOM-2012.aspx for the answer! Go to Authoring in  OM console, select Rules under Management Pack Objects. Change Scope to search for "IIS 7" in the "View all targets" and select IIS 7 Web Server target. Then look for "IIS 7.0 web" and you will get the "IIS 7.0 WEb Application Discovery" rule. Right click on it and select Overrides -->Override the Rule-->For all objects of class: IIS 7 Web Server to get the Overrides Properties window. Hope this helps someone!
    Tuesday, February 26, 2013 9:56 PM