Skip to main content

Health Check

This documentation explains Health Checks within the Hostless provider application. Health checks are automated mechanisms used to monitor the health and responsiveness of your deployed applications. They play a crucial role in maintaining the availability and reliability of your application within the Hostless environment.

Hostless health checks are periodic probes sent to your application instances (replicas) to assess their health and functionality. These checks can help identify potential issues before they significantly impact your application's users

Why Use Health Checks?​

There are several key benefits to using health checks in Hostless:

  • Early Detection of Issues: Health checks can detect problems with your application instances, such as crashes, timeouts, or resource saturation, before they cause outages or performance degradation.
  • Improved Application Availability: By identifying unhealthy instances, Hostless can automatically take corrective actions (e.g., restarting the instance or scaling up) to maintain overall application availability.
  • Enhanced Monitoring: Health checks provide valuable insights into the health and responsiveness of your application, aiding in troubleshooting and proactive maintenance.

Health Check Parameters​

Hostless Health Checks typically involve configuring two key parameters:

  • Health Check Probe Type: This parameter defines the specific type of probe used to assess your application's health. Common probe types include:
    • HTTP/HTTPS: Sends an HTTP request to a specific endpoint within your application and checks for a successful response code (e.g., 200 OK).
    • TCP: Attempts to establish a TCP connection to a specific port on your application instance.
  • Health Check Interval (in seconds): This parameter specifies the frequency at which Hostless performs the health check probe on your application instances. A shorter interval provides faster detection of issues but might increase resource consumption on your instances. A longer interval reduces resource usage but might delay detection of problems.