Shulou(Shulou.com)06/02 Report--

Preface

If you want to count the access source information of the website, you can use php to obtain the information and record it in the form of a database, or you can directly use the access log provided by nginx to record the visit details of the website. The administrator can analyze the access source of the user, the details of the access behavior and the popularity of the website page by analyzing the access log of nginx. In addition, nginx also has its own error log, which makes it convenient for operators to debug nginx. For logging behavior, if you perform each disk operation, it will consume more resources. Based on this situation, you can turn on the nginx log buffer. When the buffer is full or the time for regular writing is up, write the log again.

Access log

Immediately after processing the request, nginx writes information about the client request in the access log. By default, in the access log bit logs/access.log, the information is written to the log in a predefined combined format.

To accurately record access information, you need to customize a more complete access log format, as follows:

Http {log_format geoproxy'[$time_local] $remote_addr''$realip_remote_addr $remote_user''$request_method $server_protocol''$scheme $server_name $uri $status'$request_time $body_bytes_sent'$geoip_city_country_code3 $geoip_region''"$geoip_city" $http_x_forwarded_for'$upstream_status $upstream_response_time'"$http_referer"$http_user_agent";.}

This logging configuration, named geoproxy, uses a number of nginx variables to demonstrate nginx logging capabilities. Explain in detail the specific meaning of each variable in the configuration options:

When a user initiates a request, the server time $time_local is recorded, and the $remote_user value is the user name approved by the basic authorization.

The IP address and client IP address of the open connection used by nginx to process geoip_proxy and realip_header instructions

Then record the HTTP request method $request_method, the protocol $server_protocol and the HTTP method $scheme:http or https

Of course, there are server name $server_name, request URI and response status code.

In addition to the basic information, there are also some statistical result data: including the millisecond time of request processing $request_time, the block size of the server response $body_bytes_sent

In addition, the client country $geoip_city_country_code3, region $geoip_region and city information $geoip_city are also recorded

The variable $http_x_forwarded_for is used to record X-Forwarded-For header messages for requests initiated by other proxy servers

Some data in the upstream module is also recorded in the log: the response status code of the proxied server $upstream_status, the time of establishing the link and receiving the last byte of the response subject from the upstream server $upstream_response_time, the time of establishing the link with the upstream server $upstream_connect_time, and the time of establishing the link and the first byte of the response header from the upstream $upstream_header_time.

Request source $http_referer and user agent $http_user_agent can also be recorded in the log

The logging function of nginx is very powerful and flexible, it should be noted that the log_format instruction used to define the log format is only applicable to http block-level instructions, and all time values are measured in milliseconds and millisecond resolution. .

The log configuration in this format produces the following types of logs:

[25/Feb/2019:16:20:42 + 0000] 10.0.1.16 192.168.0.122 Derek

GET HTTP/1.1 http www.example.com / 200 0.001 370 USA MI

"Ann Arbor"-200 0.001 "-"curl/7.47.0"

If you need to use this log configuration, you need to use the access_log directive in conjunction with the access_log directive to receive a log directory and the configuration name used as parameters:

Server {access_log / var/log/nginx/access.log geoproxy;...}

Access_log can be used in multiple contexts, each of which can define its own log directory and logging format.

Conclusion: the logging module in nginx allows you to configure log formats for different scenarios so that you can view different log files.

In practical application, it is very useful to configure different logs for different contexts. The contents of the logs can be recorded simply or all necessary information can be recorded in detail. Not only that, in addition to supporting text, the log content

You can also record data in json format and xml format. In fact, nginx logs help you understand server traffic, client usage, and client sources. In addition, access logs can help you locate responses and problems related to upstream servers or specific uri; access logs are also useful for testing, which can be used to analyze traffic conditions and simulate real user interaction scenarios. Logs play an indispensable role in troubleshooting, debugging, application analysis and business adjustment.

Error log

In order to accurately locate the error log of nginx, define the error log directory and record the error log level using the included error_log directive. The configuration is as follows:

Error_log / var/log/nginx/error.log warn

Error_log directive configuration requires a required log directory and an optional error level option.

Except for the if instruction, the error_log instruction can be used in all contexts. Error log levels include:

Debug, info, notice, warn, error, crit, alert and emerg. Given log

The ranking order is the log ranking order from the smallest to the most rigorous. It is important to note that the debug log

You need to compile the nginx server with the-- with-debug flag to use it.

When there is an error in server configuration, you first need to check the error log to locate the problem. Error log

It is also a powerful tool for locating application servers, such as FastCGI services. Through the error log, we can debug problems such as worker process connection errors, memory allocation, client IP, and application server. The error log format does not support a custom log format; but it also records data such as the current time, log level, and specific information.

Note: the default settings for the error log apply globally. To override it, place the error_log directive in the context of the main (top-level) configuration. Error_log added the ability to specify multiple instructions at the same configuration level in open source NGINX version 1.5.2.

Send logs to the unified server through syslog

Since you no longer need to write the log to a directory on disk, but send it to a unified log server, you can replace the original directory with server ip. The configuration is as follows:

Error_log syslog:server=10.0.1.42 debug;access_log syslog:server=10.0.1.42,tag=nginx,severity=info geoproxy;#error_log server=unix:/var/log/nginx.sock debug;#access_log syslog:server= [2001:db8::1]: 1234 minute local7 tagged nginx recording ityrecording info

The syslog parameters of the error_log and access_log instructions are followed by colons: and some parameter options. Including: the required server tag indicates the IP, DNS name, or UNIX socket to which you want to connect

You can use the high-end games as noted above.

Optional parameters include facility, severity, and tag:

The server parameter receives the IP address or DNS name with the port; the default is UDP port 514.

The facility parameter sets the type facility of syslog, which is one of the 23 values defined by the syslog RFC standard, and the default value is local7. Other possible values are: auth, authpriv, daemon, cron, ftp, lpr, kern, mail, news, syslog, user, uucp, local0. Local7

The tag parameter indicates the title when displayed in the log file, and the default value is nginx.

Severity sets the message severity, which defaults to the info level log.

Log buffer

When the system is under load, enable the log buffer to reduce nginx worker process blocking. A large number of disk reads and writes and the use of cpu resources is also a huge consumption of server resources. Buffering log data into memory may be a small optimization method. The buffer parameter means the size of the buffer. The function is that when the buffer is full, the log will be written to the file. The meaning of the flush parameter is the maximum time for the log in the buffer to be kept in the buffer memory. The function is that when the log in the cache exceeds the maximum cache time, it will also be written to the file. The deficiency is that there is a slight delay in writing to the log file. Log buffering should be turned off during debugging. . The configuration is as follows:

Http {access_log / var/log/nginx/access.log main buffer=32k flush=1m;}

Reference link:

Nginx cook booknginx configuration Lo

Summary

The above is the whole content of this article. I hope the content of this article has a certain reference and learning value for everyone's study or work. Thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.