You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In docker, logs are picked up from stdout. This is how commands such as docker logs are able to present log activity. We have already got Apache and PHP error logs, but we do not have logs properly routed for applications with their own syslog facility.
Rather than use a technique such as https://www.drupal.org/project/log_stdout, let's configure the container to split off Drupal logs into a dedicated file descriptor, whether that's a standard /var/log location or explicitly stdout.
If it is a /var/log/drupal, we already know how to use symlink magic to reroute that to stdout, check out the Dockerfile.
The text was updated successfully, but these errors were encountered:
I know it's been three years, but I just took an interest in this problem. Did you settle on a resolution? My use case is Drupal running on AKS. I want to capture the Drupal log in Azure Monitor for containers, which consumes STDOUT and STDERR container logs output.
In docker, logs are picked up from stdout. This is how commands such as
docker logs
are able to present log activity. We have already got Apache and PHP error logs, but we do not have logs properly routed for applications with their own syslog facility.Rather than use a technique such as https://www.drupal.org/project/log_stdout, let's configure the container to split off Drupal logs into a dedicated file descriptor, whether that's a standard /var/log location or explicitly stdout.
If it is a /var/log/drupal, we already know how to use symlink magic to reroute that to stdout, check out the Dockerfile.
The text was updated successfully, but these errors were encountered: