Alibaba Cloud Service Mesh:View application mesh topology

Step 1: Enable Mesh Topology

1. Log on to the ASM console. In the left-side navigation pane, choose Service Mesh > Mesh Management.

2. On the Mesh Management page, click the name of the target instance. In the navigation pane on the left, choose Observability Management Center > Mesh Topology. In the Activate ASM mesh topology section, perform the following steps based on the ASM version.

   • For ASM instances earlier than V1.18.2.112: Click Activate.

   • For ASM instances V1.18.2.112 or later: Select one of the following deployment modes. For more information about the differences between the two modes and how to configure Managed Mode, see Enable Mesh Topology in Managed Mode.

     • Click In-Kubernetes-cluster Mode, enter the Prometheus service address used by ASM Mesh Topology, and then click Activate.

     • Click Managed Mode, and then click Activate. In the dialog box that appears, configure the required parameters and click OK.

Step 2: Access Mesh Topology with a CLB

1. Log on to the ASM console. In the left-side navigation pane, choose Service Mesh > Mesh Management.

2. On the Mesh Management page, click the name of the target instance. In the navigation pane on the left, choose Observability Management Center > Mesh Topology.

3. In the Access section, perform one of the following operations based on the ASM instance version.

   • For ASM instances earlier than V1.17.2.19: Turn on the Automatically Create an Internet-facing CLB Instance to Access ASM Mesh Topology switch. In the dialog box that appears, click OK.

   • For ASM instances V1.17.2.19 or later: Turn on the Create a CLB Instance to Access ASM Mesh Topology switch. In the dialog box that appears, configure the parameters as needed and then click OK.

   After you enable access to Mesh Topology, the Service Mesh instance briefly enters an updating state.

4. Verify that the Service Mesh instance has finished updating.

   1. In the navigation pane on the left, choose Instance Information > Base Information.

   2. In the Basic Information section, check the Status of the Service Mesh instance.

      If the Status is Updating, the update is in progress. If the Status is Running, the update is complete.

5. In the navigation pane on the left, choose Observability Management Center > Mesh Topology. On the Mesh Topology page, in the Access section, click Copy token and open in new window.

6. On the Mesh Topology login page, paste the token and click Login to enter the Mesh Topology console.

Step 3: View the application mesh topology

1. In the address bar of your browser, enter http://{IP_address_of_the_ingress_gateway}/productpage to access the Bookinfo application.

   To learn how to obtain the IP address of the ingress gateway, see Obtain the access gateway address.

2. In the Mesh Topology console, select the default namespace. From the Versioned App graph drop-down list, select Workload graph to view call relationships and traffic flow between workloads.

   Note

   In the Mesh Topology console, you can also set the namespace to default and select Application View, Service View, or Versioned View in the Versioned Application View to view the call relationships and traffic flow among apps, services, and application versions.

   The topology graph shows that istio-ingressgateway connects to productpage (v1). productpage then calls details (v1) and reviews (v1, v2, v3). Some versions of reviews call ratings (v1). All requests have a 100% success rate.

   Click reviews-v2 in the topology graph to view detailed information about the workload on the right, including its health status, inbound traffic, and outbound traffic.

Related documents

• If you notice that some requests have abnormally high latency, you can use access logs to identify the cause. For more information, see Troubleshoot abnormal request latency with access logs.

• To minimize service call latency, you can use zone-aware routing to keep traffic within the same zone. This feature prioritizes routing traffic to services within the same zone as the client. For more information, see Observe zone-aware routing by using Mesh Topology.

• If you need to observe the traffic topology of multiple clusters, you can use the Mesh Topology feature in Managed Mode. This reduces your configuration workload because you only need to deploy one Mesh Topology service for the entire ASM instance. For more information, see Enable Mesh Topology in Managed Mode.

• You can run mesh diagnostics on your instance to proactively identify potential issues, such as data plane version checks, service port checks, and service association checks. For more information, see Use ASM mesh diagnosis.