Configuring OpenTelemetry trace for an integration server
You can configure OpenTelemetry trace for IBM® App Connect Enterprise integration servers on the Linux® x86-64, Linux zSeries, Linux on POWER® Systems - Little Endian, AIX®, and Windows platforms.
About this task
You can configure OpenTelemetry trace for all message flows in an integration server, and export span data to an OpenTelemetry collector. When OpenTelemetry is enabled for an integration server, spans are created for all message flow nodes that support OpenTelemetry, including callable flow nodes. By default, OpenTelemetry is not configured to export span data to an OpenTelemetry collector.
For supported transport input nodes, spans are created and then run until the message flow transaction for the flow is completed or rolled back. For supported transport request nodes, spans are created and then run for the duration of the node interaction with the transport (for example, sending and receiving an HTTP message).
- AIX (IBM App Connect Enterprise 12.0.10.0 and later)
- Linux x86-64 (IBM App Connect Enterprise 12.0.7.0 and later)
- Linux zSeries (IBM App Connect Enterprise 12.0.8.0 and later)
- Linux on POWER Systems - Little Endian (IBM App Connect Enterprise 12.0.10.0 and later)
- Windows (IBM App Connect Enterprise 12.0.8.0 and later)
- MQ:
- MQGet node
- MQInput node
- MQOutput node
- MQPublication node
- MQReply node
- HTTP:
- HTTPAsyncRequest node
- HTTPAsyncResponse node
- HTTPInput node
- HTTPReply node
- HTTPRequest node
- REST:
- RESTAsyncRequest node
- RESTAsyncResponse node
- RESTRequest node
- SOAP:
- SOAPAsyncRequest node
- SOAPAsyncResponse node
- SOAPInput node
- SOAPReply node
- SOAPRequest node
- CallableInput
- CallableReply
- CallableFlowInvoke
- CallableFlowAsyncInvoke
- CallableFlowAsyncResponse
When OpenTelemetry is enabled, a message flow span is created for callable flows starting with a CallableInput node, and a span is created around the CallableFlowInvoke node. For asynchronous callable flow nodes, a message flow span is created for flows starting with a CallableFlowAsyncResponse node, and a span is created around the CallableFlowAsyncInvoke node.
For more information about using OpenTelemetry, see OpenTelemetry considerations and limitations.
Procedure
Configure OpenTelemetry trace for all flows on an integration server by completing the following steps: