Help Center/ Ubiquitous Cloud Native Service/ User Guide/ Service Mesh/ Traffic Management/ Traffic Policies/ Outlier Detection

Updated on 2025-04-25 GMT+08:00

View PDF

Outlier Detection

When updating a traffic policy, you can determine whether to enable outlier detection. This option can improve microservice resilience.

The access statuses of service pods are traced to determine whether the pods are healthy. Unhealthy pods will be ejected from the connection pool to improve the overall access success rate. Outlier detection can be configured for HTTP and TCP services.

For HTTP services, pods that continuously return 5xx errors are considered unhealthy. For TCP services, pods whose connections time out or fail are considered unhealthy.

Parent topic: Traffic Policies

Previous topic: Connection Pool

Next topic: TLS

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.