Distributed tracing

In service graph, you can use the distributed tracing view to:

• Analyze the overall service performance.

• Visualize the communication flow between the selected service and its inter-dependent services.

• Identify which service indicates errors and troubleshoot the erroneous service.

• View transaction details between the selected service and its each inter-dependent service.

Prerequisites

To view the trace information for the service, you must:

• Ensure that an application maintains the following trace headers, while sending any east-west traffic:

  

• For CIC builds earlier than 1.7.23, update the CPX YAML file with NS_DISTRIBUTED_TRACING and value as yes

  

• For CIC builds later than 1.7.23, you must use a ConfigMap.

  ConfigMaps allow you to separate your configurations from your pods and make your workloads portable. Using ConfigMaps, you can easily change and manage your workload configurations and reduce the need to hardcode configuration data to pod specifications.

  With ConfigMap support, you can update the configuration automatically while keeping the Citrix ingress controller pod running. You do not need to restart the pod after the update. For more information, see ConfigMap support for the ingress controller.

  Using the ConfigMap, you can enable or disable distributed tracing, events, audit logs, and so on. To use the ConfigMap:

  1. Create a YAML file using the required parameters.

     The following example YAML file has the distributed tracing enabled and other variables such as audit logs, events, and transactions disabled:

     apiVersion: v1
     kind: ConfigMap
     metadata:
       name: cic-configmap
       namespace: default
     data:
       LOGLEVEL: 'debug'
       NS_PROTOCOL: 'http'
       NS_PORT: '80'
       NS_HTTP2_SERVER_SIDE: 'ON'
       NS_ANALYTICS_CONFIG: |
         distributed_tracing:
           enable: 'true'
           samplingrate: 100
         endpoint:
           server: <AgentIP> / <AppserverIP>
         timeseries:
           port: 5563
           metrics:
             enable: 'true'
             mode: 'avro'
           auditlogs:
             enable: 'false'
           events:
             enable: 'false'
         transactions:
           enable: 'false'
           port: 5557
     <!--NeedCopy-->