Configuring Health Checks for Your Marathon Applications in DC/OS
21 students completed the lab in ~30m
Total available time: 50m
11 students rated this lab!
The Marathon container orchestration tool in DC/OS supports two types of checks to test the availability of applications: health checks and readiness checks. Health checks monitor the availability of an application's instances throughout the lifetime of the application. Readiness checks allow you to indicate when an application has finished initializing. In this Lab, you will see how to keep your applications up and running automatically by configuring health checks for your Marathon applications in DC/OS.
Upon completion of this Lab you will be able to:
- Add health and readiness checks to Marathon applications
- Describe the differences between health and readiness checks
- Diagnose issues related to health and readiness checks
You should be familiar with:
- Basic DC/OS concepts including master nodes, agents, services, tasks, and Marathon
- Working at the command-line in Linux
- AWS services to optionally understand the architecture of the pre-created DC/OS cluster
Before completing the Lab instructions, the environment will look as follows:
After completing the Lab instructions, the environment should look similar to:
Follow these steps to learn by building helpful cloud resources
Logging in to the Amazon Web Services Console
Your first step to start the Lab experience
Understanding the DC/OS Cluster Architecture
Understand the cluster architecture and the resources provisioned for this Lab
Connecting to the Virtual Machine using SSH
Create a secure connection to a remote machine
Installing the DC/OS CLI on Linux
Install the DC/OS command-line interface (CLI) on Linux.
Adding a Health Check to a Marathon Application
Use a health check to tell Marathon an application is functioning properly.
Adding a Readiness Check to a Marathon Application
Use a readiness check to tell Marathon an application is ready for health checks.