concept status in category mesos
appears as: status, status, statuses

This is an excerpt from Manning's book Mesos in Action.
Now that you understand this order of events for a real-world workload, let’s take a look at more ways you can observe the output and status of the frameworks and tasks running on a Mesos cluster.
E1018 21:24:48.423717 18610 slave.cpp:3112] Container '978cc82b-6838-4c2a- 8487-3516357a8641' for executor 'docker-invalid-container-example.a753e2af- 75de-11e5-a1ac-56847afe9799' of framework '20150930-024708-16842879-5050- 1180-0000' failed to start: Failed to 'docker pull fake- org/thisisnotmybeautifulcontainer:latest': exit status = exited with status 1 stderr = Error: image fake-org/thisisnotmybeautifulcontainer:latest not found
Depending on your organization, team, and preferred medium for receiving alerts and notifications, you might prefer email notifications on job failures, Slack notifications for your team, or a monitoring system like Nagios to periodically check the status of your jobs via the REST API. Fortunately, solutions exist for each of these.