# Application Health Check

# Overview

The Health Check of Application Performance feature enables us to continuously monitor the availability, responsiveness, and overall health of configured applications. This functionality is essential for maintaining application stability, identifying performance bottlenecks, and proactively addressing failures before they impact end users.

By configuring a health check endpoint in the YAML configuration file, the system can periodically send requests to the application and determine if it is functioning as expected. If the application does not respond within the specified timeout period, it is marked as unresponsive and creates an incident.

This feature is particularly useful for:

  • Detecting application failures in real-time.

  • Ensuring high availability of critical services.

  • Reducing downtime by enabling quick identification and resolution of issues.

  • Automating health monitoring to minimize manual intervention.

# Prerequisites:

To monitor the health of application performance, make sure you have the following:

  • A working installation of yCrash application.

  • Access to the yc-360 script

  • Access to the yc-360 script's configuration file: yc-config.yaml

# Configuration

To monitor the health of application performance, follow these steps:

  1. Open the config.yaml file in a text editor.

  2. Specify the application's endpoint URL and timeout duration in the YAML configuration file as follows:

processTokens:
     - 110736$APS
healthChecks:
APS:
     endpoint: http://localhost:8090
     timeoutSecs: 5
1
2
3
4
5
6

processTokens: A list of unique identifiers (such as application tokens) used to monitor the applications. NOTE: If you are not clear on how to configure process token, you can refer here.

healthChecks: The main section defining the health check configurations for different applications.

APS: The name of the application being monitored.

endpoint: The URL of the application's health check endpoint (e.g., http://localhost:8090).

timeoutSecs: The duration (in seconds) for how long it has to wait for a response from the health check endpoint before timing out.

  1. Save the config.yaml file

Suppose if you would like to monitor multiple applications, then you can specify the endpoint URLs as follows:

processTokens:
    - 110736$APS1
    - 110723$APS2
healthChecks:
    APS1:
      endpoint: http://localhost:8090
      timeoutSecs: 5
    APS2:
      endpoint: http://localhost:8085
      timeoutSecs: 10
1
2
3
4
5
6
7
8
9
10

Run M3 mode as mentioned here and if the application does not respond within the specified timeout period, it is marked as unresponsive and creates an incident.

← Configure Access Logs →