Chapter 16. Monitoring Application Health
When you deploy your application, OpenShift needs to know whether it has started up correctly before traffic is sent to it. Even after it has started up, you want it to be restarted if it is not working correctly.
To monitor the health of an application, you can define a readiness probe and a liveness probe. OpenShift will periodically run the probes to watch over your application.
The readiness probe is used to determine whether your application is in a state where it is okay for other applications or external users to communicate with it. The liveness probe is used to determine whether your application is still running correctly.
In this chapter you will learn more about what each of these probes is for and what actions are taken when they succeed or fail. You will also learn about the different ways you can implement the probes.
The Role of a Readiness Probe
A readiness probe checks whether an application is ready to service requests.
When a new pod is created for your application, if you provide a readiness probe, it will be used to periodically check whether the instance of your application running in that pod is ready to handle requests. When the probe succeeds for the new pod, the IP address for the pod will be added to the list of endpoints associated with the service.
Once the pod’s IP address is added to the list of active endpoints, other applications will be able to communicate with it via the IP address or internal hostname ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access