Fix Download for Linux

• ACEOpenTracingUserExit.lel, the IBM App Connect Enterprise user exit, intercepting the HTTP request and IBM MQ request and invoking the wrapped go Jaeger client library to create spans.
• tracelibrary.so, the wrapped go Jaeger client, provides functions to manage the lifecycle of spans and sends spans to the target tracing system.
• acetracingexit.conf, the configuration file to specify the target tracing system (Jaeger or Instana) and the parameters for span generation.

mqsistop <integrationNodeName>

Configuring IBM App Connect Enterprise tracing

2. Edit acetracingexit.conf file.

# configuration for ace tracing exit
LOG_LEVEL="info" #Log level: info, warn, error, debug
SPAN_FORMAT="instana" #specify opentracing span format as instana or jaeger
JAEGER_ENDPOINT = "http://127.0.0.1:14268/api/traces"
#JAEGER_AGENT_HOST="127.0.0.1"      #only effect for Jaeger
#JAEGER_AGENT_PORT=6831          #only effect for Jaeger
JAEGER_SAMPLER_TYPE = "const"   #only effect for Jaeger
JAEGER_SAMPLER_PARAM = 1.0      #only effect for Jaeger
#INSTANA_AGENT_HOST = "localhost" # instana agent host, localhost will be used by default
#INSTANA_AGENT_PROTO = "http" # connection type between ace tracing exit and instana agent, http and https are supported, http will be used by default
#HOST_ALIAS="<YOUR-HOST-NAME>" # host name to match with instana agent configuration.yaml

Where:

• LOG_LEVEL specifies the log level, which can be one of info, warn, error and debug, the log file is located at /var/mqsi/trace directory on Linux platform.
• SPAN_FORMAT specifies where the span data is sent to. The SPAN format can be set to instana or jaeger. If SPAN_FORMAT is set to instana, IBM App Connect Enterprise Tracing user exit send span data to the Instana host agent endpoint http://localhost:42699 by default, in such a case you can ignore JAEGER_* parameters in acetracingexit.conf file. Update the configuration items INSTANA_AGENT_HOST and INSTANA_AGENT_PROTO if you want to send the span data to a remote host agent using https protocol.  If SPAN_FORMAT is set to Jaeger, you need to configure JAEGER_* parameters, in such a case you can ignore INSTANA_* parameters. You should have the same SPAN_FORMAT setting for all IBM App Connect Enterprise instances.
• JAEGER_ENDPOINT specifies Jaeger collector endpoint.  You can choose to send tracing data to Jaeger collector or to the Jaeger agent.  If you want to send tracing data to Jaeger agent, comment this line and specify values for configuration items JAEGER_AGENT_HOST and JAEGER_AGENT_PORT.
• JAEGER_AGENT_HOST specifies the hostname or IP address of the Jaeger agent.
• JAEGER_AGENT_PORT specifies the Jaeger agent port.
• JAEGER_SAMPLER_TYPE specifies the sample type. The value can be one of const, probabilistic, ratelimiting and remote.
• JAEGER_SAMPLER_PARAM is interpreted based on the value of JAEGER_SAMPLER_TYPE. See more details at https://www.jaegertracing.io/docs/1.22/sampling/#client-sampling-configuration.
• INSTANA_AGENT_HOST specifies the Instana agent host where the Instana format span data is sent to, localhost is used by default. If you specify a remote Instana agent host, you also need to add a line http.listen=* in <instana-agent-dir>/etc/instana/com.instana.agent.main.config.Agent.cfg for the remote host agent first as the host agent is not reachable from other hosts by default.
• INSTANA_AGENT_PROTO specifies the connection type between IBM App Connect Enterprise tracing user exit and the Instana agent, http and https are supported, http is used by default. If you want to change it to https, you need to follow Setup TLS Encryption for Agent Endpoint to secure the Instana agent endpoint first.
• HOST_ALIAS specifies a host alias for the span data collected by IBM App Connect Enterprise Tracing user exit, so we can link calls to IBM App Connect Enterprise to the infrastructure entity if the integration node or integration server is also monitored by the IBM App Connect Enterprise sensor. The FQDN of IBM App Connect Enterprise host is used by default. The host alias value should match with the IBM App Connect Enterprise host specified in host agent configuration yaml. You only need to specify a host alias if the FQDN of IBM App Connect Enterprise host is not used in IBM App Connect Enterprise sensor configuration when the host agent is not on the local IBM App Connect Enterprise host. The IBM App Connect Enterprise sensor can discover the FQDN for the local integration nodes or integration servers.