---
MTPE: FanLin
Date: 2024-01-23
---

# One-click Diagnosis and Repair

DCE 5.0 service mesh has built-in one-click diagnosis and repair functions for managed services, which can be operated through a graphical interface.

1. Enter a specific Service Mesh and click __Service Management__ -> __Service List__ .
   In the __Diagnose Config__ column, next to services with an __Abnormal__ status,
   the word __Diagnose__ will appear. Click __Diagnose__.

    ![Diagnose](https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/mspider/user-guide/images/diagnose01.png)

2. A diagnosis popup will appear on the right-hand side. Follow the built-in checklist for inspection.
   Green checkmarks indicate that the item has <span style="color:green">Passed</span>, while red crosses indicate items that is <span style="color:red">Not Passed</span> and need to be repaired.

    Check the items that have <span style="color:red">Not Passed</span> and click the __One-Click Repair__ button.
    You can click __Rediagnose__ to refresh the checklist, and the repair is usually
    completed within a few minutes.

    ![Repair](https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/mspider/user-guide/images/diagnose02.png)

3. After successful repair, all items in the checklist will turn gray and display as
   <span style="color:green">Passed</span>. Click __Next__.

    ![Next](https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/mspider/user-guide/images/diagnose03.png)

4. A list of items that require __Manual Repair__ will be displayed.
   You can click __View Troubleshooting Guide__ to read the proper documentation page and manually repair the items.

    ![Manual repair](https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/mspider/user-guide/images/diagnose04.png)

!!! note

    For the services in the following system namespaces, it is not recommended to use one-click repair:

| Category             | Namespace          | Purpose                        |
| -------------------- | ------------------ | ----------------------------- |
| Istio System Namespace | istio-system       | Hosts Istio control plane components and resources |
|                      | istio-operator     | Deploys and manages Istio Operator |
| K8s System Namespace   | kube-system        | Control plane components      |
|                      | kube-public        | Cluster configurations, certificates, etc. |
|                      | kube-node-lease    | Monitors and maintains node activity |
| DCE 5.0 System Namespace | amamba-system      | Workbench         |
|                      | ghippo-system      | Global management             |
|                      | insight-system     | Observability                 |
|                      | ipavo-system       | Homepage dashboard            |
|                      | kairship-system    | Multicloud orchestration       |
|                      | kant-system        | Cloud-edge collaboration       |
|                      | kangaroo-system    | Container registry              |
|                      | kcoral-system      | Application backup             |
|                      | kubean-system      | Cluster lifecycle management  |
|                      | kpanda-system      | Container management          |
|                      | local-path-storage | Local storage                 |
|                      | mcamel-system      | Middleware                    |
|                      | mspider-system     | Service mesh                  |
|                      | skoala-system      | Microservice engine            |
|                      | spidernet-system   | Network module                |