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 will generate 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 four seconds or longer, the trace log will be generated when the first of the following conditions is met:
- A request generates status code 404.
- A request takes longer than four seconds.
UI Element List
Select this option when you want a trace event to be logged for responses that generate the specified HTTP status code (and optionally a substatus 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 substatus 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: