Article
05/19/2016

Default Entry Points for .NET Application Monitoring

Updated: May 13, 2016

Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager

Application Performance Monitoring in Operations Manager is preconfigured with many well-known entry points (see below), but also lets you extend the default list by defining your own entry points. In addition to adding functions as entry points, you may also define entire Namespaces to act as entry points, so that the system begins timing execution the first time that it encounters the namespace during execution. Additionally, the application monitoring agent collects the values of variables for each entry point at the time the event occurs.

Entry points Monitored by Default

For ASP.NET pages

System.Web.UI.Page.ProcessRequest
(System.Web.IHttpHandler).ProcessRequest

For ASP.NET 2.0 asynchronous pages

For System Center 2012 SP1 only: System.Web.UI.Page.AsyncPageBeginProcessRequest
System.Web.Services.Protocols.LogicalMethodInfo.Invoke

For COM+ server-side

System.EnterpriseServices.ServicedComponent.RemoteDispatchHelper

For .NET Remoting server-side

System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.AsyncProcessMessage
System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage

For WCF Server Side

System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke

For WWF

System.Workflow.Runtime.WorkflowExecutor.RunScheduler

For AJAX.NET

System.Web.Script.Services.RestHandler.ExecuteWebServiceCall

For Windows Services

For System Center 2012 SP1 these entry points are included:

System.ServiceProcess.ServiceBase.ServiceCommandCallback
System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback
System.ServiceProcess.ServiceBase.Stop
System.ServiceProcess.ServiceBase.DeferredPowerEvent
System.ServiceProcess.ServiceBase.DeferredSessionChange

For MVC