Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Select Trace Providers Wizard Page

Applies To: Windows Server 2008 R2

Use the Select Trace Providers page of the Add Failed Request Tracing Rules Wizard or Edit Failed Request Tracing Rules Wizard to define what to trace for a URL. This includes the trace provider(s), verbosity level, and area(s) for the provider to trace.

UI Element List

 

Element Name Description

Providers

Defines the functional area for tracing. You can select one or more of the following trace providers:

  • ASP - When you want to trace the start and completion of the execution of an ASP request.

  • ASP.NET - When you want to see transitions into and out of managed code. This includes all requests for .aspx files and any requests that are processed by managed modules, such as static files that are configured to use forms-based authentication.

  • ISAPI Extension - When you want to trace the transition of a request into and out of an ISAPI extension process.

  • WWW Server - When you want to trace requests through the IIS worker process.

Verbosity

Specifies how much data each provider reports to the trace log. Verbosity levels are inclusive, which means if you select Errors, for example, Errors, Critical Errors, and General events will be included in the log file. You can select one or more of the following verbosity levels:

  • General - Provides context information for the request activity, for example, IIS 7, IISGeneralEvents::GENERAL_REQUEST_START logs the URL and the verb for the request.

  • Critical Errors - Provides information about actions that can cause a process to end or that are about to cause a process to end.

  • Errors - Provides information about components that try to run on the server, encounter an error, and cannot continue to process requests. These errors are conditions that generally result in the end of request processing that is caused by some kind of error. An example of this would be an authorization event.

  • Warnings - Provides information about components that try to run on the server, encounter an error, but can continue to process requests.

  • Information - Provides general information about requests.

  • Verbose - Provides detailed information about requests.

Areas

Defines the areas for the provider to trace.

If the provider selected is the ASP.NET trace provider, select one or more of the following areas to trace:

  • Infrastructure - When you want to trace events that are primarily related to entering and leaving various parts of the ASP.NET infrastructure.

  • Module - When you want to trace events that are logged when a request enters and leaves various HTTP pipeline modules. This area is also used to capture trace events for managed modules.

  • Page - When you want to generate trace events that correspond to the execution of specific ASP.NET page-related events, such as Page_Load. This area is also used to capture ASP.net Page Trace.Write and Trace.Warn events.

  • AppServices - When you want to trace those events that are logged as part of the new application services functionality.

If the provider selected is the WWW Server trace provider, select one or more of the following areas to trace:

  • Authentication - When you want to trace authentication attempts, including the name of the authenticated user, the authentication scheme (Anonymous, Basic, or others), and the results of the authentication attempt (successful, failed, error, and so on).

  • Security - When you want to generate trace events when requests are rejected by the server running IIS for security-related reasons, for example, if a client request was denied access to a resource.

  • Filter - When you want to determine how long it takes an ISAPI filter to process requests.

  • StaticFile - When you want to trace how long it takes requests for static files to be completed or to see how filters might be changing the requests.

  • CGI - When a request is made for a CGI file and you want to generate trace events.

  • Compression - When a response is compressed and you want to generate trace events.

  • Cache - When you want to generate trace events for cache operations associated with the request.

  • RequestNotifications - When you want to capture all request notifications, both on entrance and on exit.

  • Module - When you want to trace events that are logged when a request enters and leaves various HTTP pipeline modules. This area is also used to capture trace events for managed modules.

See Also

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.