All Products
Search

This Product

    Microservices Engine:Configure active health check for services

    Document Center

    Microservices Engine:Configure active health check for services

    Last Updated:Jun 17, 2026

    Active health checks automatically deactivate unhealthy service nodes and reactivate them when they recover. This improves the availability of routes to service interfaces in multi-replica deployments.

    Procedure

    Note

    If the gateway version is 1.2.1 or later, the TCP health check feature is automatically enabled when you create a service.

    1. Log on to the MSE console. In the top navigation bar, select a region.

    2. In the left-side navigation pane, choose Cloud-native Gateway > Gateways. On the Gateways page, click the ID of the gateway.

    3. In the left-side navigation pane, click Routes. Then, click the Services tab.

    4. On the Services tab, find the desired service and click Health Check Settings in the Actions column. In the Configure Health Check panel, turn on Enable Health Check, configure the parameters, and then click OK.

    Troubleshoot health check failures

    Troubleshoot a health check failure that occurs in common scenarios

    Determine whether a TCP health check or an HTTP health check fails:

    • If a TCP health check fails, the connection to the gateway node cannot be established. Check the following:

      • Check whether the node exists.

      • Check whether too many concurrent connections are established.

    • If an HTTP health check fails, first verify that the TCP health check passes. If it does, check whether the configured health check path is valid by using tools such as cURL or Postman.

    Troubleshoot a health check failure that occurs when you add a service for the first time

    Perform the following operations in sequence:

    1. Check whether the service VPC is the same as the gateway VPC, or whether the service environment is connected to the gateway VPC through Cloud Enterprise Network (CEN) or physical connections. If the VPCs are different and not connected, the gateway IP address is inaccessible.

      Note

      The gateway does not support on-premises services that are registered with Nacos and ZooKeeper instances.

    2. Check whether the service VPC is the same as the gateway VPC. If the VPCs are different and not connected, the gateway IP address is inaccessible.

    3. Check whether security group authorization is configured. If the service source is a Container Service for Kubernetes (ACK) cluster, verify that the gateway is added to the security group of the ACK cluster. For more information, see Perform security group authorization.

    4. If the unhealthy gateway uses a public IP address, check whether an Internet NAT gateway is enabled for the gateway VPC.