---
title: "Drupal request logs"
date: "2024-02-14T06:18:38+00:00"
summary: "Explore Drupal request logs to monitor and analyze your website's performance. Learn how to parse log entries, understand key metrics, and gain insights into user interactions and system behavior."
image:
type: "page"
url: "/acquia-cloud-platform/drupal-request-logs"
id: "41cefbe3-e4d0-4d37-a901-89c3fd75aa56"
---

The _Drupal request log_ (`drupal-requests.log`) contains a list of requests that Apache has sent to Drupal for processing and display.

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](/acquia-cloud-platform/monitor-apps/logs). You can also review information about how to [streaming Apache log entries in real time](/acquia-cloud-platform/monitor-apps/logstream) from your browser.

Note for log forwarding users

Acquia’s [log forwarding](/acquia-cloud-platform/monitor-apps/logs/forwarding) feature prepends information to the beginning of each line forwarded to an external service. For more information, see [File formats in forwarded log files](/acquia-cloud-platform/monitor-apps/logs/forwarding/files).

Parsing the log file
--------------------

The following line is a representative example of the data written into your website’s Drupal request log:

    [03/Feb/2017:00:14:36 +0000] www.example.com POST /dashboard
    http_code=302 query= uid=154496 php_pid=30961 php_time=0.203 queue_wait=0
    request_id="v-0000zzzz-e9a5-11e6-98b5-0aeea9eaf9af" drupal_version="9.4.8"

Each of the items in the Drupal request log is noted in the following table, along with its description:

Contents
--------

Position

Data

Description

0

`[03/Feb/2017:00:14:36 +0000]`

Date and time of the request.

1

`www.example.com`

Domain name of the request.

2

`POST`

The HTTP method of the request, usually `GET` or `POST`. `POST` requests are form submissions.

3

`/dashboard/`

The path to the requested resource.

4

`http_code=302`

The HTTP status code returned by this request. Note that production environments don’t display full information for [HTTP 5xx status codes](5xx.html).

5

`query=`

The querystring, which is the portion of the `request_uri` after the question mark.

6

`uid=154496`

The Drupal user ID initiating the request. `0` means an anonymous user.

7

`php_pid=30961`

The PHP process ID (`pid`) for this request.

8

`php_time=0.203`

Time, in seconds, needed to process this request.

9

`queue_wait=0`

The number of seconds this request had to wait for a PHP process to become available to handle it.

10

`request_id="v-bf1b9 6bc-e9a5-11e6-98b5-0a eea9eaf9af"`

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](/acquia-cloud-platform/develop-apps/drupal-apps/requestid).

11

`drupal_version="9.4.8"`

The Drupal version in the platform.

Note

A Drush command does not have an associated web request. Drupal request log entries corresponding to Drush commands do not have a `request_id` column.