[
https://issues.apache.org/jira/browse/MESOS-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178614#comment-14178614
]
Steven Schlansker commented on MESOS-1949:
------------------------------------------
Interesting. It seems that neither Singularity nor Marathon expose the
`message` field of TaskStatus anywhere useful? Would this be possible to
expose via the Mesos web interface?
Having the message would be great and solve 80% of the use cases here. I still
think collating the logs is a useful feature, though, for when something more
complex goes wrong.
> All log messages from master, slave, executor, etc. should be collected on a
> per-task basis
> -------------------------------------------------------------------------------------------
>
> Key: MESOS-1949
> URL: https://issues.apache.org/jira/browse/MESOS-1949
> Project: Mesos
> Issue Type: Improvement
> Components: master, slave
> Affects Versions: 0.20.1
> Reporter: Steven Schlansker
>
> Currently through a task's lifecycle, various debugging information is
> created at different layers of the Mesos ecosystem. The framework will log
> task information, the master deals with resource allocation, the slave
> actually allocates those resources, and the executor does the work of
> launching the task.
> If anything through that pipeline fails, the end user is left with little but
> a "TASK_FAILED" or "TASK_LOST" -- the actually interesting / useful
> information (for example a "Docker pull failed because repository didn't
> exist") is hidden in one of four or five different places, potentially spread
> across as many different machines. This leads to unpleasant and repetitive
> searching through logs looking for a clue to what went wrong.
> Collating logs on a per-task basis would give the end user a much friendlier
> way of figuring out exactly where in this process something went wrong, and
> likely much faster resolution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
