- What's New
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Application Service Mesh
- Buying a Service Mesh
- Mesh Management
- Service Management
- Gateway Management
- Grayscale Release
- Mesh Configuration
- Traffic Management
- Security
-
Best Practices
- Upgrading Data Plane Sidecars Without Service Interruption
- Service Governance for Dubbo-based Applications
- Reserving Source IP Address for Gateway Access
- Creating a Service Mesh with IPv4/IPv6 Dual Stack Enabled
- How Do I Query Application Metrics in AOM?
- Reducing the Agency Permissions of ASM Users
- Istio-ingressgateway HA Configuration
-
FAQs
- Service Mesh Cluster
-
Mesh Management
- Why Cannot I Create a Mesh for My Cluster?
- Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?
- How Do I Upgrade ICAgent?
- How Do I Enable Namespace Injection for a Cluster?
- How Do I Disable Sidecar Injection for Workloads?
- What Can I Do If A Pod Cannot Be Started Due to Unready Sidecar
- How Do I Handle a Canary Upgrade Failure?
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- How Do I Inject a Sidecar for the Pod Created Using a Job or CronJob?
- Performing Grayscale Release
-
Managing Traffic
- Why Are the Created Clusters, Namespaces, and Applications Not Displayed on the Traffic Management Page?
- How Do I Change the Resource Requests of the istio-proxy Container?
- Does ASM Support HTTP/1.0?
- How Can I Block Access from Some IP Address Ranges or Ports for a Service Mesh?
- How Do I Configure max_concurrent_streams for a Gateway?
- How Do I Fix Compatibility Issues Between Istio CNI and Init Containers?
-
Monitoring Traffic
- Why Cannot I View Traffic Monitoring Data Immediately After a Pod Is Started?
- Why Are the Latency Statistics on the Dashboard Page Inaccurate?
- Why Is the Traffic Ratio Inconsistent with That in the Traffic Monitoring Chart?
- Why Can't I Find Certain Error Requests in Tracing?
- Why Cannot I Find My Service in the Traffic Monitoring Topology?
- How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- User Guide
-
FAQs
- Service Mesh Cluster
- Mesh Management
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- Performing Grayscale Release
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Show all
Copied.
How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?
ASM can export traces to Jaeger or Zipkin. You can view them on the Jaeger or Zipkin UI. The following uses Zipkin as an example.
Prerequisites
The cluster and namespace where Zipkin is to be installed have been specified.
Procedure
- Create a Deployment named zipkin.
Log in to the CCE console and click the cluster name to go to the cluster console. In the navigation pane on the left, choose Workloads. On the Deployments tab, click Create from YAML, and copy the following content to the YAML file:
apiVersion: apps/v1 kind: Deployment metadata: name: zipkin namespace: monitoring spec: progressDeadlineSeconds: 600 replicas: 1 revisionHistoryLimit: 10 selector: matchLabels: app.kubernetes.io/instance: zipkin app.kubernetes.io/name: zipkin strategy: rollingUpdate: maxSurge: 25% maxUnavailable: 25% type: RollingUpdate template: metadata: labels: app.kubernetes.io/instance: zipkin app.kubernetes.io/name: zipkin spec: automountServiceAccountToken: false containers: - env: - name: STORAGE_TYPE value: mem image: openzipkin/zipkin-slim:latest # Community Zipkin image path. Ensure that you can access this path. imagePullPolicy: IfNotPresent name: zipkin readinessProbe: failureThreshold: 3 httpGet: path: /health port: 9411 scheme: HTTP initialDelaySeconds: 5 periodSeconds: 5 successThreshold: 1 timeoutSeconds: 1 resources: limits: cpu: 500m memory: 4Gi requests: cpu: 100m memory: 128Mi securityContext: readOnlyRootFilesystem: true runAsNonRoot: true runAsUser: 1000 terminationMessagePath: /dev/termination-log terminationMessagePolicy: File terminationGracePeriodSeconds: 30
The Deployment named zipkin is displayed on the Deployments tab. If the status of zipkin changes to Running, Zipkin has been installed in the monitoring namespace of the target cluster.
- Create a Service of the LoadBalancer type.
On the cluster console, choose Services & Ingresses in the navigation pane on the left. On the Services tab, click Create Service. Then, configure the parameters as follows:
- Service Name: Enter a name. zipkin is used as an example here.
- Service Type: Select LoadBalancer.
- Selector: Click Reference Workload Label. The label is automatically added.
- Ports: Configure the container port and Service port. 9411 is used as an example here.
Retain the default values for other parameters.
The Service named zipkin is displayed on the Services tab.
CAUTION:
If you do not need to access the Zipkin UI, set Access Type to ClusterIP.
- Buy a service mesh and interconnect it with Zipkin.
Log in to the ASM console and click Buy Mesh. In Cluster Configuration, select the cluster in 1. In Observability Configuration, enable tracing. Then, select Third-party Jaeger/Zipkin service for Version, set Service Address and Access Port, and configure other parameters as required.
- Deploy an experience service () by referring to Grayscale Release Practices of Bookinfo. After the deployment is complete, the services shown in the following figure are displayed on the Service Management page.
- Access the productpage details page to trigger tracing.
Go to the service mesh details page. In the navigation pane on the left, choose Service Management. On the displayed page, click the external access address http://{IP address}:{Port number}/productpage of the productpage service.
- View the traces on the Zipkin UI at http://{Public IP address of the load balancer configured for zipkin}:{Access port of zipkin}/zipkin/.
NOTE:
You can obtain the IP address and port for logging in to the Zipkin client as follows:
- IP address: Go to the console of the cluster where Zipkin is installed. In the navigation pane on the left, choose Services & Ingresses. On the Services tab, view the public IP address of the load balancer configured for zipkin.
- Port: On the Services tab, view the access port of zipkin.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot