Major Description
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.