The Balancer access log provides information about requests received at the balancer level. Since most customers use shared load balancers, Varnish logs are only available using the log stream feature and cannot be downloaded from either the Cloud Platform interface or your infrastructure.
For a list of the log files handled by Cloud Platform, including accessing these log files, log file retention, and their locations, see About Cloud Platform logging. You can also review information about how to streaming Varnish log entries in real time from your browser.
Note for log forwarding users
Acquia’s log forwarding feature adds information to the beginning of each line that is forwarded to an external service. For more information, see File formats in forwarded log files.
Parsing the log file
The following line is a representative example of the data written into your website’s balancer access log:
127.0.0.1 - - [30/Dec/2016:18:12:20 +0000] "GET /names HTTP/1.1" 200 12750 "-"
"facebookexternalhit/1.1" http_host=www.example.com affinity="-" upstream_addr="171.0.0.1:80" hosting_site=alphabeta request_time=1.263 forwarded_for="173.0.0.1, 172.0.0.1" upstream_status="200"
request_id="v-0000zzzz-cebb-0000-9948-0efda0c0zzzz" ssl_protocol="TLSv1.2" ssl_cipher="AES128-GCM-SHA256"
Each of the items in the balancer access log is noted in the following table, along with its description:
Position | Data | Description |
|---|---|---|
0 |
| The IP address of the web client accessing the balancer. |
1 |
| The name of a remote log file, if used ( |
2 |
| The username the web client was authorized under, if used ( |
3 |
| The date and time of the request. |
4 |
| The method of the request—frequently |
5 |
| The document requested, relative to the docroot of the website. |
6 |
| The HTTP protocol used for the request. |
7 |
| The HTTP status code returned by the balancer—note that it may differ from the HTTP status code returned by the backend infrastructure the request was forwarded to, and production environments don’t display full information for HTTP 5xx status codes. |
8 |
| Size, in bytes, of the infrastructure’s response. |
9 |
| The referrer URL, if any ( |
10 |
| The user-agent of the request. |
11 |
| The requested domain name. |
12 |
| The backend infrastructure this request was pinned to, if any ( |
13 |
| The backend infrastructure the balancer forwarded this request to. |
14 |
| The internal Acquia site name this request is for. |
15 |
| Time in seconds needed to complete this request. |
16 |
| The full set of IP addresses tracked as “requester IP,” which will contain the IP addresses of the following if they are in use by the subscription:
|
17 |
| The HTTP status code returned by the backend infrastructure the request was forwarded to—note that it may differ from the HTTP status code returned by the balancer. |
18 |
| A unique ID attached to this request by the load balancer, which appears in several Cloud Platform log files. For more information, see Using HTTP request IDs. |
19 |
| The SSL protocol used for this request, if any. |
20 |
| The SSL cipher used for this request, if any. |