Access Flow Production Tracking Logs
Local installations of Flow Production Tracking are no longer offered. This documentation is intended only for those with existing instances of Flow Production Tracking Enterprise Docker. Click here for a list of our current offerings.
Do not use docker logs without --tail or --since option on production container. Docker logs load the whole json file containing the logs in memory.
Flow Production Tracking Production Logs
Docker logs (7.7.0 and later)
The Flow Production Tracking app docker container outputs two types of logs:
The Flow Production Tracking app logs, also called production logs
Apache access logs
They are tagged respectively with SHOTGUN_APP and APACHE prefixes. These logs can be viewed with the docker logs command of the specific container and piped into a grep command with the use of the prefixes for better sorting:
#How to get sg app logs (production logs) only
sudo docker logs --since 2m <container_id> | grep SHOTGUN_APP#How to get Apache logs (access logs) only
sudo docker logs --since 2m <container_id> | grep APACHE#How to tail the production log starting from this moment in time
sudo docker logs --tail 0 -f <container_id> | grep "search_string_here"Docker logs (prior to 7.7.0)
#Print the last 2m of logs
sudo docker logs --since 2m <container_id>#How to grep
sudo docker logs --since 2m <container_id> 2>&1 | grep "ERROR:"#How to get production log only
sudo docker logs --since 2m <container_id> 2>&1 | grep "stdout:"Direct access to JSON files
The logs are also available on the host in json format. Rotated log files will be found in the same folder:
#find the long_container_id
sudo docker ps --no-trunc#tail
sudo tail -f /var/lib/docker/containers/<long_container_id>/<long_container_id>-json.logEmail notifier logs
As a standalone docker container, the email notifier has its own log output stream.
This log stream can be viewed with the same docker logs command of the specific container and piped into a grep command.