After you enable Microservices Governance for a microservice application in a Container Service for Kubernetes (ACK) cluster, the application may not appear correctly in the Microservices Engine (MSE) console. Use this guide to diagnose and resolve the issue.
Symptoms
When Microservices Governance is enabled for an application in an ACK cluster, the following issues may occur:
The application does not appear in the MSE console.
The application name appears in the MSE console, but the instance count is 0.
The instance count is correct, but service metadata is missing on the service details page.
Possible causes
The preceding issues may occur due to the following reasons:
The operations for enabling Microservices Governance are incorrect.
MSE does not support the version of the application for which you want to enable Microservices Governance.
Prerequisites
Before you begin, make sure that you have:
Access to the ACK console with permissions to view cluster workloads
Terminal access to the application pod (for running the diagnostic script)
Step 1: Check application version compatibility
MSE Microservices Governance supports specific framework versions. If your application uses an unsupported version, MSE cannot discover or govern it.
Spring Cloud applications: Edgware or later is required.
If your application uses a version earlier than Edgware, upgrade to a supported version before you enable Microservices Governance.
Step 2: Check application logs
Inspect the application logs to verify that the application starts and responds to requests without errors.
Log on to the ACK console.
In the left-side navigation pane, click Clusters.
On the Clusters page, find your cluster and click the cluster name or click Details in the Actions column.
In the left-side navigation pane, choose Workloads > Deployments.
On the Deployments page, click the name of your application, then click the Logs tab.
Set Lines to 500 to view the complete startup log.
Step 3: Run the MSE agent diagnostic script
If the logs show no obvious errors, check whether the MSE agent is installed on the application. Run the service_metadata_diagnosis script on the application terminal:
wget -O - https://edas-public.oss-cn-hangzhou.aliyuncs.com/oneAgent/service_metadata_diagnosis.sh | sh -sInterpret the diagnostic results
| Result | Cause | Action |
|---|---|---|
| Java agent version is not displayed | The MSE agent is not installed on the application | Verify that Microservices Governance is enabled for the namespace. For more information, see Enable Microservices Governance for microservice applications in an ACK cluster. |
| No relevant files are displayed | Log files are missing because the application started before the MSE agent was installed | Check the YAML configuration file of your application. |
| Configurations are correct, but no service records are displayed | The application version is not supported by MSE | Verify that your application framework version meets the minimum requirements (see Step 1). |
Step 4: Submit a support ticket
If the issue persists after you complete Steps 1 through 3, submit a ticket with the following information:
| Information | Description |
|---|---|
| User account ID | Your Alibaba Cloud account ID |
| Region | The region where your cluster is deployed. Example: China (Shanghai) |
| Product | MSE or Enterprise Distributed Application Service (EDAS) |
| Issue description | A summary of the symptoms and the steps you have already tried |
| Application startup logs | The complete startup log from Step 2 |
| Diagnostic results | The output from the diagnostic script in Step 3 |
| kubeconfig file (optional) | The kubeconfig file for your ACK cluster. For more information, see Generate a temporary kubeconfig file. |