Skip to content

Redesign Logging for Syslog and 'docker logs' #4

Open
@SysEngDan

Description

@SysEngDan

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions