The Varnish request log displays the requests that have been served by Varnish cache, and those that were not. Because most customers use shared load balancers, Varnish logs are available only using the log stream feature and cannot be downloaded from either the Acquia Cloud interface or your servers.
For a list of the log files handled by Acquia Cloud, including accessing these log files, log file retention, and their locations, see About Acquia Cloud logging. You can also review information about how to streaming Varnish request log entries in real time from your browser.
Parsing the log file
The following line is a representative example of the data written into your website's Varnish request log:
126.96.36.199 - - [30/Dec/2016:23:55:24 +0000] "GET http://www.example.com/carousel.min.js HTTP/1.1" 304 0 "https://www.example.com/" "Mozilla/5.0 Safari/601.1" 0.000127316 hit hit request_id="v-0000zzzz-ce7e-11e6-9fa2-22000ab8zzzz" "-" forwarded_for="188.8.131.52, 10.0.0.1"
Each of the items in the Varnish request log is noted in the following table, along with its description:
||The originating IP address of the request|
||The remote log name, if any — will usually be
||The remote user, if any — will usually be
|3||[30/Dec/2016:23:55:24 +0000]||The date and time of the request in HTTP date/time format|
||The method of the request (usually
||The HTTP status sent to the client|
||The size of the response in bytes, excluding HTTP headers.|
||The referrer for this request, if any, in quotation marks|
||The full user-agent for this request, in quotation marks, as many user-agent names contain spaces|
||Time to first byte|
||Whether the request was a cache
||How the request was handled: cache
||A unique ID attached to this request by the load balancer, which appears in several Acquia Cloud log files — for more information, see Using HTTP request IDs|
||This value is for Acquia internal use only|
||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: