Win7 methods for operating system configuration to manage IIS logging

Logging is critical for any server. It is no exception for IIS servers. In the Windows7 operating system, there is a significant improvement over IIS logging, compared to 2003来. More than just the format of the log, or some other option, the operating system administrator has more choices. This is the basic page of IIS logging configuration management, as shown in the following illustration.

in the Windows7 operating system, IIS logging should be considered as necessary for ISS rather than an optional component. This is primarily because log files are critical for managing IIS servers. If the IIS server is under security threat, you can use the log file and perform a row-checking of the internal details contained therein. You can also use the information recorded in this log file to check the maintenance process and identify problems in the system after the IIS server has failed. I would like to introduce you to the WINDOWS7 operating system IIS log records compared to the Windows2003 operating system some of the new features, and to help you deploy a handy log management mode.

First, select the appropriate logging level.

in the IIS7.0 version, the system administrator can select the appropriate logging level to suit their needs. If you can manage logging at the server level, you can also implement it at the Web site, at the Web application file, or at the directory level. specifically to achieve at that level, mainly looking at the needs of system administrators. It should be noted, however, that the level of implementation is different, and that the supported log file formats are different. As implemented at the server level, there are only two types of log formats that are supported, namely, the "All-in-one" format and the binary format. If you choose to implement log management at the site level, there are three log formats supported, IIS, NCSA, and the format of the world in the world. and system administrators can customize the format they want by customizing them if they feel they are not satisfied. So when you choose the logging level, in addition to consider at what level of log management is more convenient and safe, but also need to combine their favorite log format. I personally like to manage the log at the site level. Because on a single server, it may be wasteful to deploy only IIS services. In other words, there may be multiple application services on the same server. In order to differentiate with other application services and server operating system logs, the author recommends that you manage at the site level. Of course, at which level of log management, there is no practical difference in the content of the log. It depends on the deployment of the server and the working habits of the system administrator.

Two, select the appropriate format for logging.

If you select a site level to manage logs, the format of this log has several options. Most importantly, the system administrator can select the logging format for IIS. This IIS logging format is text-based log records. Similar to the logging format of the HTTP.sys, it is controlled by the data. However, this IIS logging format is a core mode process. The previous log records were managed through user mode. There is a big change between the two. The Hypertext Transfer Protocol listener is implemented as a kernel-mode device driver named HTTP.sys. HTTP. SYS is an important part of the Windows network subsystem. In previous releases, when you created a Web site in IIS, you used http.sys to register the site, and then http.sys the Web request to a user-mode process that was running the Web site. At the same time, HTTP.sys will respond back to the client. In addition to retrieving the stored response from its internal cache, HTTP. SYS does not handle the requests it receives. Therefore, application-specific code will never be loaded into kernel mode. But some system administrators want HTTP.sys to run in core mode. You need to use the IIS log format at this point. In addition, IIS is text-based logging, and unlike binary format logging, you can view log information directly through tools such as a text browser. So it's more convenient to read.