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 order to support syslogging and the use of docker logs, I propose the following:
Configure each process to log to console
Configure each process as defined with Supervisord to log to /dev/stdout and /dev/stderr. Note: to make use of logging to stdout, you should set both stdout and stderr_logfile_maxbytes=0 (for disable) as Supervisord doesn't need to attempt determining the size of these "logfile locations".
Update log contents to include a filterable prefix. The purpose of this is to have the syslog server filter those entries from alprd, alprlink, and beanstalk. Without this, the syslog wouldn't know what's what.
Additionally, these steps allows the user to monitor the logs with 'docker logs -f ' and make use of dockers logging capabilities.
The text was updated successfully, but these errors were encountered:
In order to support syslogging and the use of docker logs, I propose the following:
Additionally, these steps allows the user to monitor the logs with 'docker logs -f ' and make use of dockers logging capabilities.
The text was updated successfully, but these errors were encountered: