Failed Request Tracing Rules
Updated: February 29, 2012
Applies To: Windows Server 2012 R2, Windows Server 2012
Use the Failed Request Tracing Rules feature page to manage a list of tracing rules for failed requests.
Sort the list by clicking one of the feature page column headings or select a value from the Group by drop-down list to group similar items.
In this document
The following tables describe the UI elements that are available on the feature page and in the Actions pane.
Displays the URL that was identified by a tracing rule for failed requests. The URL can contain, at most, one wildcard and must be local to the directory where the failed request definition is set. For example, the wildcard patterns, such as *.aspx and ind* match the URL www.contoso.com/index.aspx.
Displays the trace providers associated with a tracing rule for failed requests. A provider defines the functional area for tracing. One example is the ASP.NET trace provider, which traces transitions into and out of managed code, including *.aspx requests.
Displays the HTTP status codes and sub-status code combinations identified by a tracing rule for failed requests. There can be multiple status codes in this list, with commas that separate each code.
Displays the maximum time, in seconds, that the request should take.
Displays whether the item is local or inherited. Local items are read from the current configuration file, and inherited items are read from a parent configuration file.
Opens the Add Failed Request Tracing Rule wizard in which you can add a rule to trace for failed requests.
Opens the Edit Failed Request Tracing Rule wizard in which you can edit the selected failed request tracing rule.
Removes the item that is selected from the list on the feature page.
Edit Site Tracing
Opens the Edit Web Site Failed Request Tracing Settings dialog box in which you enable and configure failed request tracing settings for the website. This action is available only when you are connected to a server and you have selected a specific site.
View Trace Logs
Opens the trace log file directory. This action is available only when you are connected to a server.
Revert to Inherited
Resets the feature to inherit settings from the parent configuration. This action deletes local configuration settings, including items from the list, for this feature. This action is not available at the server level.
View Ordered List
Displays the list in order of configuration. When you select the ordered list format, you can only move items up and down in the list. Other actions in the Actions pane do not appear until you select the unordered list format.
Moves up a selected item in the list. This action is available only when viewing items in the ordered list format.
Moves a selected item down in the list. This action is available only when viewing items in the ordered list format.
View Unordered List
Displays the list in an unordered format. When you select the unordered list format, you can sort and group items in the list, and perform actions in the Actions pane.
Use the Specify Content to Trace page of the Add Failed Request Tracing Rule Wizard to configure the content you want to trace with a tracing rule for failed requests.
All content (*)
Select this option to trace all files in a directory.
Select this option to trace all .aspx files in a directory.
Select this option to trace all .asp files in a directory.
Select this option and type a value, such as "xyz.exe" or "*.jpg", to trace a failure for a custom set of content. This value can contain, at most, one wildcard and must be local to the directory where the failed request definition is set. For example, the wildcard patterns, such as *.aspx and ind* match the URL www.contoso.com/index.aspx.
Use the Define Trace Conditions page of the Add Failed Request Tracing Rule Wizard or Edit Failed Request Tracing Rule Wizard to define a trace condition for a failed request tracing rule. This trace condition allows you to capture trace events for a failed request and log these trace events, as they occur, without having to reproduce the error.
If more than one trace condition is specified, the first condition that is met generates the failed request trace log file. For example, if you configure a trace rule to log requests that generate status code 404 and requests that take 4 seconds or longer, the trace log generates an event when the first of the following conditions is met:
A request generates status code 404.
A request takes longer than 4 seconds.
Select this option when you want a trace event to be logged for responses that generate the specified HTTP status code (and optionally a sub-status code). In the corresponding box, type the status code or codes you want to trace. Separate multiple status codes by using commas (,) between each code, or type a status code range by using a hyphen (-) between two codes. You can also refine your status codes by using sub-status codes, such as 404.2 or 404.3.
Time taken (in seconds)
Select this option when you want to trace events that exceed the time interval allocated for the request to complete processing. In the corresponding box, type the maximum time, in seconds, that a request should take.
Select this option when you want to trace events based on severity. In the corresponding list, select one of the following event severities on which to trace:
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 providers, verbosity level, and areas for the provider to trace.
Defines the functional area for tracing. You can select one or more of the following trace providers:
Specifies how much data each provider reports to the trace log. Verbosity levels are inclusive. For example, if you select Errors, then errors, critical errors, and general events will be included in the log file. You can select one or more of the following verbosity levels:
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:
If the provider selected is the WWW Server trace provider, select one or more of the following areas to trace: