Alibaba Cloud Service Mesh:Use Managed Service for OpenTelemetry to trace applications inside and outside an ASM instance

Run the following command to deploy the Bookinfo application in the ACK cluster that is added to the ASM instance.

kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG} apply -f bookinfo.yaml

Run the following command to deploy virtual services for the Bookinfo application.

kubectl --kubeconfig=${ASM_KUBECONFIG} apply -f virtual-service-all-v1.yaml

Run the following command to deploy destination rules for the Bookinfo application.

kubectl --kubeconfig=${ASM_KUBECONFIG} apply -f destination-rule-all.yaml

Run the following command to deploy a gateway for the Bookinfo application.

kubectl --kubeconfig=${ASM_KUBECONFIG} apply -f bookinfo-gateway.yaml

Log on to the Managed Service for OpenTelemetry console. In the left-side navigation pane, click Overview.

On the Overview page, click the Access process tab, and then click View access point information.

View the access endpoint.

1. In the upper part of the page, select the desired region.

   Select the region of the ACK cluster where the Bookinfo application is deployed. If you select another region, the tracing data of the Bookinfo application cannot be reported to Managed Service for OpenTelemetry.

2. On the Access point information tab, turn on Show Token for the Cluster Information parameter. Select the public or private endpoint based on the place where you want to deploy the ExternalProxy application.

   In this example, the tracing data of ExternalProxy is reported by using the API of Zipkin V1. Therefore, you must use the public or private endpoint of Zipkin V1.

Create an ExternalProxy.py file that contains the following content and save the file in the runtime environment of the ExternalProxy application.

• Replace {XTRACE_ZIPKIN_V1_ENDPOINT} with the endpoint that you obtained in Step 2. If you need to report the tracing data to a custom tracing system, replace the variable with the access endpoint of the custom tracing system.

• Replace {INGRESS_GATE_WAY_IP} with the endpoint of the ingress gateway that is deployed for the ACK cluster.

  Show the ExternalProxy.py file

  import requests
  from flask import Flask
  from py_zipkin.zipkin import zipkin_span,create_http_headers_for_new_span
  from py_zipkin.util import generate_random_64bit_string
  from py_zipkin.util import ZipkinAttrs
  import time
  
  app = Flask(__name__)
  
  def do_stuff(trace_id, span_id, parent_span_id):
      time.sleep(2)
      headers = create_http_headers_for_new_span()
      headers["X-B3-TraceId"] = trace_id
      headers["X-B3-SpanId"] = span_id
      headers["X-B3-ParentSpanId"] = parent_span_id
      print "SEND TO INGRESS HEADERS : {0}".format(headers)
      r = requests.get('http://${INGRESS_GATE_WAY_IP}/productpage', headers=headers)
      return 'OK'
  
  
  def http_transport(encoded_span):
      # encoding prefix explained in https://github.com/Yelp/py_zipkin#transport
      body=encoded_span
      zipkin_url="${XTRACE_ZIPKIN_V1_ENDPOINT}"
      headers = {"Content-Type": "application/x-thrift"}
  
      # You'd probably want to wrap this in a try/except in case POSTing fails
      r=requests.post(zipkin_url, data=body, headers=headers)
      print(body)
  
  
  @app.route('/')
  def index():
      with zipkin_span(
          service_name='external-proxy',
          span_name='external-proxy/inbound',
          transport_handler=http_transport,
          port=5000,
          sample_rate=100, 
      ) as inbound_span:
      do_stuff(inbound_span.zipkin_attrs.trace_id, inbound_span.zipkin_attrs.span_id, inbound_span.zipkin_attrs.parent_span_id)
  
      return 'OK', 200
  
  if __name__=='__main__':
      app.run(host="0.0.0.0",port=5000,debug=True)

Run the following command to start ExternalProxy:

python ExternalProxy.py

 * Serving Flask app "main" (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: on
 * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 317-792-686

Run the following command to call ExternalProxy:

curl localhost:5000

OK

Log on to the Managed Service for OpenTelemetry console.

In the left-side navigation pane, click Applications. In the upper part of the Applications page, select the region where the ACK cluster resides. Then, click ExternalProxy in the application list.

On the page that appears, click Application Details in the left-side navigation pane. On the Application Details page, click the Traces tab. Then, click the trace ID of the call trace that you want to query.

A call trace is generated between the ExternalProxy application that is deployed outside the ASM instance and the Bookinfo application that is deployed inside the ASM instance.