Each of the items in the Apache access log is noted in the following table, along with its description:
| Position | Data | Description |
|---|---|---|
| 0 | 200.0.0.1 | The remote host (client IP). |
| 1 | - | The identity of the user determined by identd. Rarely used. |
| 2 | - | The user name, determined by HTTP authentication. |
| 3 | [04/Jan/2017:23:20:38 +0000] | The date and time the request was received by the backend infrastructure. |
| 4 | "GET /contact_us HTTP/1.1" | The
|
| 5 | 404 | The HTTP status code sent from the infrastructure to the client. Production environments don’t display full information for HTTP 5xx status codes. |
| 6 | 10117 | The total size, in bytes, of the response to the client. |
| 7 | "-" | The referrer, which is the page (none in this case) that provided the link to this page. |
| 8 | "Pingdom.com bot version 1.4 (http://www.pingdom.com/)" | The user-agent, or browser identification string, encased in quotation marks as many browser names have spaces in them. |
| 9 | vhost=alphabeta.prod.acquia-sites.com | The underlying virtual host matching the requested domain name. |
| 10 | host=www.example.com | The domain name for the request, which does not have to match the virtual host (vhost) name. |
| 11 | hosting_site=alphabeta | The internal Acquia site name this request is for. |
| 12 | pid=26731 | The process ID (pid) on the infrastructure that handled this request. |
| 13 | request_time=10186417 | The time needed to serve the request, in microseconds (1/1000000 of a second). |
| 14 | forwarded_for="200.0.0.1, 162.0.0.1" | 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:
|
| 15 | request_id="v-00000zzz-d2d4-11e6-9bed-0aeea9eaf9af" | 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. |
| 16 | location="http://apache.example.com/" | The contents of the Location HTTP header. |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
200.0.0.1 - - [04/Jan/2017:23:20:38 +0000] "GET /contact_us HTTP/1.1" 404 10117 "-" "Pingdom.com bot version 1.4 (http://www.pingdom.com/)" vhost=alphabeta.prod.acquia-sites.com host=www.example.com hosting_site=alphabeta pid=26731 request_time=10186417 forwarded_for="200.0.0.1, 162.0.0.1" request_id="v-00000zzz-d2d4-11e6-9bed-0aeea9eaf9af" location="http://apache.example.com/"Each of the items in the Apache access log is noted in the following table, along with its description:
| Position | Data | Description |
|---|---|---|
| 0 | 200.0.0.1 | The remote host (client IP). |
| 1 | - | The identity of the user determined by identd. Rarely used. |
| 2 | - | The user name, determined by HTTP authentication. |
| 3 | [04/Jan/2017:23:20:38 +0000] | The date and time the request was received by the backend infrastructure. |
| 4 | "GET /contact_us HTTP/1.1" | The
|
| 5 | 404 | The HTTP status code sent from the infrastructure to the client. Production environments don’t display full information for HTTP 5xx status codes. |
| 6 | 10117 | The total size, in bytes, of the response to the client. |
| 7 | "-" | The referrer, which is the page (none in this case) that provided the link to this page. |
| 8 | "Pingdom.com bot version 1.4 (http://www.pingdom.com/)" | The user-agent, or browser identification string, encased in quotation marks as many browser names have spaces in them. |
| 9 | vhost=alphabeta.prod.acquia-sites.com | The underlying virtual host matching the requested domain name. |
| 10 | host=www.example.com | The domain name for the request, which does not have to match the virtual host (vhost) name. |
| 11 | hosting_site=alphabeta | The internal Acquia site name this request is for. |
| 12 | pid=26731 | The process ID (pid) on the infrastructure that handled this request. |
| 13 | request_time=10186417 | The time needed to serve the request, in microseconds (1/1000000 of a second). |
| 14 | forwarded_for="200.0.0.1, 162.0.0.1" | 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:
|
| 15 | request_id="v-00000zzz-d2d4-11e6-9bed-0aeea9eaf9af" | 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. |
| 16 | location="http://apache.example.com/" | The contents of the Location HTTP header. |
If this content did not answer your questions, try searching or contacting our support team for further assistance.