[ https://issues.apache.org/jira/browse/MESOS-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113669#comment-16113669 ]
Adam B commented on MESOS-4086: ------------------------------- [~kaysoky] Let's see if we can close out this Epic and create a new one for further improvements. > Containerizer logging modularization > ------------------------------------ > > Key: MESOS-4086 > URL: https://issues.apache.org/jira/browse/MESOS-4086 > Project: Mesos > Issue Type: Epic > Components: containerization, modules > Reporter: Joseph Wu > Assignee: Joseph Wu > Labels: logging, mesosphere > > Executors and tasks are configured (via the various containerizers) to write > their output (stdout/stderr) to files ("stdout" and "stderr") on an agent's > disk. > Unlike Master/Agent logs, executor/task logs are not attached to any formal > logging system, like {{glog}}. As such, there is significant scope for > improvement. > By introducing a module for logging, we can provide a common/programmatic way > to access and manage executor/task logs. Modules could implement additional > sinks for logs, such as: > * to the sandbox (the status quo), > * to syslog, > * to journald > This would also provide the hooks to deal with logging related problems, such > as: > * the (current) lack of log rotation, > * searching through executor/task logs (i.e. via aggregation) -- This message was sent by Atlassian JIRA (v6.4.14#64029)