About Cloud Platform logging

Available log files¶

Logs only in Cloud Next¶¶

Cloud Next environments make the following logs available for your use through various methods, such as downloading or log forwarding:

Logs only in Cloud Classic¶

Cloud Classic environments make the following logs available for your use through various methods, such as streaming, download, or log forwarding:

Downloading active log files¶

To download active log files:

1. Sign in to the Cloud Platform user interface as a user with the download logs permission for the subscription and environment you want.
2. Select the application and environment for which you want to download a log.

3. Select Logs > Download.

   

4. Click the Download link for the log that you want to download.

   • If the log file is available for immediate download, the system begins downloading the file.
   • If the log file must be created on-demand, the system displays a dialog box with the status of the request:
   

5. After the log file is ready for download, click Download to retrieve it.

   The system downloads the log file in the following format:

   logfilename-timestamp.tar.gz

Downloading historical logs¶

You can access or download historical logs by using the following:

The Logs page allows you to select a specific date and time range when attempting to download a log file. Logs are limited to 24 hour increments. 

Historical logs are stored in a location on the infrastructure that’s optimized for fast read/write activity. While this works for simultaneously updating several log files, the directory won’t persist after infrastructure is relaunched or resized. Log files do persist after infrastructure is rebooted. A relaunch can happen at any time. For example, in the event of infrastructure failure.

less /var/log/sites/[site].[env]/logs/[servername]/access.log

scp -i /path/to/private/key/file [site name]@[host name]:[log path]/[filename].log [local path]

scp -i /Users/esymbolist/.ssh/id_rsa [email protected]:/mnt/gfs/home/example/logs/access.log-20151225.gz/access.log /Documents/logs

Additional (inaccessible) logs¶

Acquia uses additional logs from the logs mentioned earlier on this page that aren’t available to subscribers. These logs are inaccessible for several reasons, including the potential for security issues related to shared resources.

• Binary logs: Binary log (binlog) files are used to replicate data from the master database to a replica database. All statements that change data, including create, update, and delete statements, add lines to the MySQL binlogs. Queries that only read from the database, without changing the contents, don’t add lines to the binlogs. Staging environments, despite not having redundant databases, also use binlogs to keep feature and performance parity between non-production and production environments. For more information, see Binlogs.

• Email logs: Email logs are often a shared infrastructure resource, may have sensitive information, and aren’t available to subscribers.

Related topics¶

• Using logs
• Searching the error logs to troubleshoot problems