IIS 7 full Raiders of failed request tracking configuration

Source: Internet
Author: User

With the failure request tracking feature, you can capture the corresponding XML-formatted log when a problem occurs, so that you do not have to reproduce the problem to start troubleshooting. In addition, you can define failure conditions for an application and configure trace events to be based on a URL record.

Failure request tracking can be configured at two levels:

-At the site level, you can enable or disable tracing and configure log file settings.

-At the application level, you can specify failure conditions when capturing trace events, and you can also configure trace events that should be captured in log file entries.

(i) View a list of failed request tracking rules

To manage the tracking rules for a failed request, you can view a list of all the failed request tracking rules for a specific configuration level. The list can be sorted by path, associated trace provider, HTTP status code, time or range (local or inherited) in which the request is processed. In addition, you can group rules by scope to quickly see which rules apply to the current configuration level and which rules are inherited from the parent.

1. Open IIS Manager, and then navigate to the level you want to manage.

2. In the feature view, double-click failed request tracking rules.

Alternatively, you can implement it by command-line, to see a list of failed request tracking rules, use the following syntax:

Appcmd Configure Trace "string"

The variable string is the name of the site for which you want to view a list of failed request tracking rules.

(ii) Enable trace logging for failed requests

If you want IIS to log information about requests that failed to provide site or application content, you can enable trace logging for failed requests. After you enable trace logging for a failed request, IIS provides a targeted log, eliminating the need to find a failed request from a list full of unrelated log entries. In addition, you can resolve them without reproducing the error.

You can configure the following:

-Location of log files

-Maximum number of log files to keep

-The maximum size of the log file.

1. Open IIS Manager, and then navigate to the level you want to manage.

2. In the Connections pane, click Web Site.

3. In the feature view, select the site for which you want to enable trace logging.

4. In the actions pane, under Configuration, click Failed Request tracking.

5. In the edit Web site failed Request Tracking Settings dialog box, select Enable to enable logging for the site.

6. In the Table of Contents text box, type the path you want to use to store the log files, or click the browse button (...) to find the location you want on your computer. The default path is%systemdrive%\inetpub\logs\failedreqlogfiles.

Note:

It is a best practice to store log files, such as log files for failed request tracking, in a directory other than systemroot.

7. In the maximum number of trace files text box, type the maximum number of trace log files that you want to keep, and then click OK.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.