The Drupal watchdog log (drupal-watchdog.log) records Drupal-related actions on your application. The watchdog log is recorded on your infrastructure if you have enabled the syslog module.
In Cloud Next, Drush commands run within SSH, Cloud Hooks, and Scheduled Jobs log Watchdog messages to stdout/stderr. These commands do not log such messages in the drupal-watchdog logs and do not send them to Log Forwarding destinations. Ensure that any needed output is redirected to a log file in the /shared folder, and that Drupal's error reporting level is set to high so that these messages are not hidden.
You should avoid setting or overriding Syslog identity in settings.php as an override will cause the drupal-watchdog.log to only log output for the default website and not for the additional multisites. The Cloud Platform interface will write to drupal-watchdog.log for all of your websites in a multisite architecture if you do not set or override Syslog identity.
After March 2019, website requests are no longer logged to a single drupal-watchdog.log, and are instead aggregated on the infrastructure handling the request.
The maximum character limit for a single message in the drupal-watchdog.log file is 15384. If your message crosses this character limit, the system truncates the message.
Syslog suppresses large volumes of logs sent in a short span of time by using rate limiting. This prevents more than 1000 messages from being stored in 30 seconds by a single process. To store large volumes of messages in drupal-watchdog.log, Acquia recommends that you create summaries or digests of results rather than individual messages per action or activity. This affects both log files stored locally, logs available for download, and logs forwarded to an external service.
The following line is a representative example of the data written into your website’s Drupal watchdog log:
Aug 18 21:22:01 10.0.0.1 alphabeta: https://www.example.com|1503091321|
custom_module|151.0.0.1|https://example.com/documents||0||Warning: Invalid
argument supplied for foreach() in views_join->build_join
request_id="v-00000000-845b-0000-8178-22000ab832c9"
Each of the items in the Drupal watchdog is noted in the following table, along with its description:
Position
Data
Description
0
Aug1821:22:01
The date and time of the request
1
10.0.0.1
The internal hostname of the infrastructure handling this request. If no hostname exists, the internal IP address will be displayed.
2
alphabeta
The internal Acquia website name this request is for
3
http://www.example.com
The domain this request was for
4
1503091321
The Unix timestamp of the request
5
custom_module
If you want to search for a website in drupal-watchdog.log, you can use any of the following commands, which allow you to search log entries for a specific domain name:
grep: Allows you to search uncompressed log files
zgrep: Allows you to search compressed log files ending in .tar.gz
In Drupal 7, drushvgetsyslog_format displays information about the ordering and content of fields in the watchdog logs. API documentation about Drupal’s watchdog log is available for Drupal 7.
Drupal watchdog logs
The Drupal watchdog log (drupal-watchdog.log) records Drupal-related actions on your application. The watchdog log is recorded on your infrastructure if you have enabled the syslog module.
In Cloud Next, Drush commands run within SSH, Cloud Hooks, and Scheduled Jobs log Watchdog messages to stdout/stderr. These commands do not log such messages in the drupal-watchdog logs and do not send them to Log Forwarding destinations. Ensure that any needed output is redirected to a log file in the /shared folder, and that Drupal's error reporting level is set to high so that these messages are not hidden.
You should avoid setting or overriding Syslog identity in settings.php as an override will cause the drupal-watchdog.log to only log output for the default website and not for the additional multisites. The Cloud Platform interface will write to drupal-watchdog.log for all of your websites in a multisite architecture if you do not set or override Syslog identity.
After March 2019, website requests are no longer logged to a single drupal-watchdog.log, and are instead aggregated on the infrastructure handling the request.
The maximum character limit for a single message in the drupal-watchdog.log file is 15384. If your message crosses this character limit, the system truncates the message.
Syslog suppresses large volumes of logs sent in a short span of time by using rate limiting. This prevents more than 1000 messages from being stored in 30 seconds by a single process. To store large volumes of messages in drupal-watchdog.log, Acquia recommends that you create summaries or digests of results rather than individual messages per action or activity. This affects both log files stored locally, logs available for download, and logs forwarded to an external service.
The following line is a representative example of the data written into your website’s Drupal watchdog log:
Aug 18 21:22:01 10.0.0.1 alphabeta: https://www.example.com|1503091321|
custom_module|151.0.0.1|https://example.com/documents||0||Warning: Invalid
argument supplied for foreach() in views_join->build_join
request_id="v-00000000-845b-0000-8178-22000ab832c9"
Each of the items in the Drupal watchdog is noted in the following table, along with its description:
Position
Data
Description
0
Aug1821:22:01
The date and time of the request
1
10.0.0.1
The internal hostname of the infrastructure handling this request. If no hostname exists, the internal IP address will be displayed.
2
alphabeta
The internal Acquia website name this request is for
3
http://www.example.com
The domain this request was for
4
1503091321
The Unix timestamp of the request
5
custom_module
If you want to search for a website in drupal-watchdog.log, you can use any of the following commands, which allow you to search log entries for a specific domain name:
grep: Allows you to search uncompressed log files
zgrep: Allows you to search compressed log files ending in .tar.gz
In Drupal 7, drushvgetsyslog_format displays information about the ordering and content of fields in the watchdog logs. API documentation about Drupal’s watchdog log is available for Drupal 7.
The name of the module issuing this message
6
151.0.0.1
The originating IP address of this request
7
https://example.com/documents
The full URL of the requested page.
8
(blank)
The referrer for this request (the example line is blank for this value)
9
0
The Drupal user ID initiating the request. 0 means an anonymous user
10
(blank)
A relevant link, if one was passed to the logging function
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
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
The name of the module issuing this message
6
151.0.0.1
The originating IP address of this request
7
https://example.com/documents
The full URL of the requested page.
8
(blank)
The referrer for this request (the example line is blank for this value)
9
0
The Drupal user ID initiating the request. 0 means an anonymous user
10
(blank)
A relevant link, if one was passed to the logging function
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
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform