Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redesign Logging for Syslog and 'docker logs' #4

Open
SysEngDan opened this issue Feb 10, 2019 · 0 comments
Open

Redesign Logging for Syslog and 'docker logs' #4

SysEngDan opened this issue Feb 10, 2019 · 0 comments

Comments

@SysEngDan
Copy link

In order to support syslogging and the use of docker logs, I propose the following:

  1. Configure each process to log to console
  2. 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".
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant