Logs (3.1.17)

Overview

WEXAL® Page Speed Technology (hereinafter referred to as "PST") has various logs to which it outputs operating status. You can use these logs to check the status of the system and to find out the cause of any problems that may be occurring.

There are two types of logs: system-wide logs and PST profile logs.

PST Profile Logs

PST Profile Logs include the web server access log, the error log, the PST log, the proxy log, the webfont log, and the reverse proxy log.

System-wide Logs

The system-wide logs include the logs output by WEXAL services and the PST Manager log.

Web Server Access Log

The web server access log records client access to the web site.

In addition, when PST is enabled, the status of optimization strategies is recorded in the web server access log. In environments where PST is not applied or enabled, PST information will not be recorded.

Output Path

When using "nginx"
/home/kusanagi/%PROFILE-NAME%/log/nginx/access.log
/home/kusanagi/%PROFILE-NAME%/log/nginx/ssl_access.log

When using "httpd"
/home/kusanagi/%PROFILE-NAME%/log/httpd/access.log
/home/kusanagi/%PROFILE-NAME%/log/httpd/ssl_access.log

Syntax

Processing Time fcache [L=lcache:][B=]bcache[:D=PST] IP Address Remote Log Remote User Time "Request" Status Response Bytes "Referrer" "User Agent" "X-Forwarded-For"

Output Example

When "lcache" is disabled
0.253 BYPASS B=BYPASS:D=EXPIRE/CREATE xxx.xxx.xxx.xxx - - [27/Apr/2021:12:51:54 +0900] "GET / HTTP/2.0" 200 14980 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Moto G (4)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Mobile Safari/537.36" "-"

When "lcache" is enabled
0.023 HIT L=MISS/CREATE:B=BYPASS:D=HIT xxx.xxx.xxx.xxx - - [27/Apr/2021:12:57:17 +0900] "GET / HTTP/2.0" 200 15523 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Moto G (4)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Mobile Safari/537.36" "-"

When PST is disabled
0.035 BYPASS BYPASS xxx.xxx.xxx.xxx - - [17/Aug/2021:17:13:46 +0900] "GET / HTTP/2.0" 200 7692 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Moto G (4)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Mobile Safari/537.36" "-"

PST

HIT	PST applies the optimization strategy generated most recently.
EXPIRE/CREATE	PST applies the optimization strategy generated most recently, and will generate an optimization strategy again because the set time period has passed since the last generation. The generated optimization strategy will be applied from the next access.
MISS/CREATE	PST applies no optimization strategy because no optimization strategy has been generated. PST will generate an optimization strategy. The generated optimization strategy will be applied from the next access.
EXPIRE/FAIL	PST applies the optimization strategy generated most recently, and again tries to generate an optimization strategy because the set time period has passed since the last generation. However, the generation of an optimization strategy failed. If the most recently generated optimization strategy exists, the optimization strategy status will be valid.
MISS/FAIL	PST applies no optimization strategy because no optimization strategy has been generated. PST tried to generate an optimization strategy again, but failed. There continues to be no valid optimization strategy.

Error Log

The error log will output any errors that occur when a client accesses the profile web site.

Output Path

When using "nginx"
/home/kusanagi/%PROFILE-NAME%/log/nginx/error.log
/home/kusanagi/%PROFILE-NAME%/log/nginx/ssl_error.log

When using "httpd"
/home/kusanagi/%PROFILE-NAME%/log/httpd/error.log
/home/kusanagi/%PROFILE-NAME%/log/httpd/ssl_error.log

PST Log

PST logs are no longer in use after PST 3.1.17. Refer to the Resource Monitoring Service ("watch") log.

The status of the profile optimization process is recorded in the PST Log. The monitoring status of the original resource update and any errors in the optimization or purge process is also recorded in this log.

Output Path

/home/kusanagi/%PROFILE-NAME%/log/pst/page_speed_technology.log

Proxy Log

The status of resource acquisition by the proxy directive in the profile is recorded in the proxy log.

Output Path

/home/kusanagi/%PROFILE-NAME%/log/proxy/proxy.log

"webfont" Log

The "webfont" log records the status of the optimization process, including when "webfont" is in the style sheet and the style sheet is split.

Output Path

/home/kusanagi/%PROFILE-NAME%/log/proxy/webfont.log

Reverse Proxy Log

The status of resource acquisition by the reverse proxy in the profile is recorded in the reverse proxy log.

Output Path

/home/kusanagi/%PROFILE-NAME%/log/proxy/reverseproxy.log

Optimization Strategy Service ("strategy") Log

This log records the status of optimization strategies for each web page according to the browser environment.

Output Path

/var/log/wexal/wexal-strategy.log

Resource Monitoring Service ("watch") Log

This log records the monitoring of updates to the original resource.

Output Path

/var/log/wexal/wexal-watch.log

Resource Optimization Service ("optimizer") log

This log records the status of optimized resources generated from original resources.

Output Path

/var/log/wexal/wexal-optimizer.log

API Service ("api") Log

This log records the status of services provided by PST API.

Output Path

/var/log/wexal/wexal-api.log