All Products
Search
Document Center

Application Real-Time Monitoring Service:Enable tracing analysis for Ingresses

Last Updated:Jun 30, 2023

You can enable Tracing Analysis for NGINX Ingresses in a Container Service for Kubernetes (ACK) cluster. Tracing data is imported to the Tracing Analysis console. You can view traces and the trace topology in the Tracing Analysis console. This topic describes how to enable Tracing Analysis for NGINX Ingresses.

Prerequisites

Background information

Alibaba Cloud Tracing Analysis provides various features for distributed applications, including trace mapping, request counting, and trace topology. These features allow you to analyze and diagnose the performance bottlenecks of distributed applications, and improve the efficiency of microservice development and diagnostics. You can enable tracing analysis for NGINX Ingress controllers that are provided by ACK based on your requirements. After tracing analysis is enabled, you can view the tracing data.

Step 1: Obtain an endpoint

  1. Log on to the Managed Service for OpenTelemetry console.
  2. In the left-side navigation pane, click Cluster Configurations. Then, click the Access point information tab.

  3. In the top navigation bar, select a region. In the Cluster Information section, turn on Show Token.

  4. In the Client section, select the client that you want to use to collect trace data. In this example, Jaeger is selected.

  5. In the Related Information column of the table, click the copy icon next to the endpoint that you want to use.

    Jaeger endpoints
    • If you use OpenTelemetry HTTP, Zipkin HTTP, or Jaeger HTTP, the token is contained in an HTTP URL.

    • If you use SkyWalking gRPC, OpenTelemetry gRPC, or Jaeger gRPC, the system specifies Authentication=<token> in the metadata of gRPC and then sends the metadata to the server for authentication.

Step 2: Enable Tracing Analysis for Ingresses

  1. Log on to the ACK console.
  2. In the left-side navigation pane of the ACK console, click Clusters.
  3. On the Clusters page, find the cluster that you want to manage and click the name of the cluster or click Details in the Actions column. The details page of the cluster appears.
  4. In the left-side navigation pane of the details page, choose Configurations > ConfigMaps.
  5. In the upper part of the ConfigMap page, select kube-system from the Namespace drop-down. Then, enter nginx-configuration in the Name search box and click the search icon. Find the nginx-configuration ConfigMap and click Edit in the Actions column.

  6. Configure tracing analysis.

    Edit the ConfigMap based on the client that is used. In this example, a Zipkin client is used. For more information about how to configure tracing analysis, see Preparations.

    In the Edit panel, click Add. Set Name to zipkin-collector-host. Set Value to the endpoint that is obtained in Step 1: Obtain an endpoint.

  7. Enable Tracing Analysis.

    Click Add. Set Name to enable-opentracing. Set Value to true. Then, click OK.

Step 3: View the tracing data

  1. Log on to the Managed Service for OpenTelemetry console. In the left-side navigation pane, click Applications.
  2. On the Applications page, select a region in the top navigation bar and click the name of the application that you want to manage.
  3. In the left-side navigation pane of the details page, click Interface Calls. On the page that appears, click the Traces tab. You can view up to 100 traces on the tab. These traces are sorted in descending order of elapsed time. For more information about the tracing data, see View the details of span calls.