About Logging with Cloud 66
This documentation set has been merged with the Maestro Version 2 documentation and is officially deprecated. These pages will be redirected to their equivalents in that doc set within the next few weeks.
About logging with Cloud 66
When Cloud 66 deploys your servers, we also configure the logging for various services on your server. There are several logs available for different parts of your server. Depending on the specifics of your application, log names and directories may vary. The information below applies to most applications.
Given the ephemeral nature of containers, we recommend you use the
log_folder directive to persist container logs on your host, so that they don’t disappear when the container stops. By default, any folder specified with
log_folder will be available on the host under
/var/log/containers/<service_name>, for example:
Logs for background processes can also be found in
$STACK_PATH/log, and depend on the name of the process:
- Process log:
- Process bluepill log:
- Auth requests, Fail2Ban etc:
- Nginx access and errors:
Your logs in
/var/log are automatically rotated on a daily basis and by default kept for 14 days into a sub-directory called archive/ in each respective directory. These logs are compressed, and can be uncompressed with the following command:
gzip -d <log_file>.log.gz.
You can set the frequency and the number of rotations to be kept using toolbelt.