Access log acquisition/forward settings¶
Access logs on Managed Load Balancer instances can be forwardred to the customer's syslog server.
Only access logs for HTTP/HTTPS listeners are forwarded.
This section describes how to set access log acquisition/forwarding.
Contents
Note
This function uses the load balancing function of Managed Load Balancer to forward access logs.
ICMP is adopted as the health check method, and access logs can be forwarded when a Ping response from the Managed Load Balancer to the syslog server can be confirmed.
Configure the network and syslog server settings so that Managed Load Balancer can confirm the Ping response to the syslog server.
How to set/edit access log forward¶
1． From the control panel, select "Cloud/Server Local Network" → "Managed Load Balancer". The Managed Load Balancer list screen will be displayed.
2． From the Managed Load Balancer list screen, click "Edit Managed Load Balancer" from the action pulldown of the Managed Load Balancer resource to be edited.
3． The Managed Load Balancer edit screen will be displayed, so click the "SYSLOG SERVER" tab.
4． There is a check box for "Forward logs to syslog server". You can choose whether or not to forward the access log. Check the box if you do.
5． Specify the information required to forward the access log to the syslog server.
- Up to two destination syslog servers can be set.-When protocol is TCP：Access logs are forwarded to both of the two devices.-When protocol is UDP：Access logs are forwarded to only one device. The upper setting frame (first syslog server) of two setting frames has priority. The health check is executed by ICMP, and if the health check to the upper setting frame(first syslog server) fails, forwarding will switch to the lower setting frame(second syslog server).
Setting items |
content |
Input format |
IP address |
You can specify the IP address of the syslog server. |
IPv4 address format |
port |
You can specify the port number used for access log forward. |
Integer 1~65534 |
protocol |
You can select the protocol to use for access log forward. |
Select from TCP, UDP |
6． Enter the settings to be edited and click "Edit Managed Load Balancer" to confirm the settings.
7． On the Managed Load Balancer list screen, confirm that the "Configuration Status" of the corresponding Managed Load Balancer is "UPDATE_STAGED".
8． Click "Apply Managed Load Balancer Settings" from the Actions pull-down of the Managed Load Balancer resource to complete the access log forward settings..
Note
Application of Managed Load Balancer setting changes can be performed together with other setting items.
Check access log forward settings/stop forward¶
1． From the control panel, select "Cloud/Server Local Network" → "Managed Load Balancer". The Managed Load Balancer list screen will be displayed.
2． From the Managed Load Balancer list screen, click "Edit Managed Load Balancer" from the action pulldown of the Managed Load Balancer resource to be edited.
3． The Managed Load Balancer edit screen will be displayed, so click the "SYSLOG SERVER" tab.
4． You can check the setting information of the syslog server being set.
5． To stop forwarding, remove the check from the "Transfer logs to syslog server" check box. (If you remove the check, the setting information will also be deleted.) Click the "Edit Managed Load Balancer" button at the bottom right of the screen to confirm the settings.
6． On the Managed Load Balancer list screen, confirm that the "Configuration Status" of the corresponding Managed Load Balancer is "UPDATE_STAGED".
7． Click "Apply Managed Load Balancer Settings" from the Actions pull-down of the Managed Load Balancer resource to complete the access log forward settings..
Note
Application of Managed Load Balancer setting changes can be performed together with other setting items.
Access log format¶
Each log item output to the access log is explained using a sample log.
10.10.1.111 - - Mon Oct 24 09:16:05 2022 "GET /abc/index.htm HTTP/1.1" 9 "http://www.ntt.com/index.html" "curl/7.58.0" 172_16_100_100_32:80
| NO. | log entry |
sample |
| 1 | client IP address |
10.10.1.111 |
delimiter (always no data) |
‐ ‐ | |
| 2 | access date and time |
Mon Oct 24 09:16:05 2022 |
| 3 | request method |
GET |
Four |
request URI |
/abc/index.htm |
Five |
HTTP version |
HTTP/1.1 |
| 6 | request bytes |
9 |
| 7 | Referrer |
http://www.ntt.com/index.html |
| 8 | user agent |
curl/7.58.0 |
| 9 | Listener IP address and port number
(The example is when the listener IP address is 172.16.100.100 and the port number is 80. "_32" is given as a fixed value.)
|
172_16_100_100_32:80 |