This is the latest release in the 6.x.x family. For EI 7.0.0, click here.
WSO2 Enterprise Integrator 6.6.0 Documentation

All docs This doc
Expand all   Collapse all
||
Skip to end of metadata
Go to start of metadata

The following configurations in the ESB profile of WSO2 EI ensures that ESB data is published to Jaeger. The published data can then be visualized via the Jaeger UI.

Configuring the ESB to connect with Jaeger

Open the synapse.properties file (stored in the <EI_HOME>/conf/ directory) and configure the properties given below.

PropertyDescription
opentracing.enable

Set this property to true and enable statistics for the required ESB artifact, to record information such as the following.

  • The time spent on each mediator.
  • The time spent to process each message.
jaeger.sampler.manager.host

Host of Jaeger Sampler Manager. Defaults to localhost.

jaeger.sampler.manager.port

Port of Jaeger Sampler Manager. Defaults to 5778.

jaeger.sender.agent.host

Host of Jaeger Sender Agent. Defaults to localhost.

jaeger.sender.agent.portPort of Jaeger Sender Agent. Defaults to 6831.
jaeger.reporter.log.spansSet this property to true, in order to log reporting of each span.
jaeger.reporter.max.queue.sizeMaximum queue size of Jaeger Reporter. Defaults to 100.
jaeger.reporter.flush.intervalFlush interval (milliseconds) of Jaeger Reporter. Defaults to 10000.

Enabling message tracing

Follow the instructions give below to enable statistics monitoring and message tracing. You can use message tracing to track a message (including the message payload) throughout a mediation flow.

Step 1: Enabling message tracing for the ESB server

Open the synapse.properties file (stored in the <EI_HOME>/conf/ directory) and configure the properties given below.

PropertyDescription
mediation.flow.statistics.tracer.collect.payloads

Set this property to true and enable tracing for the required ESB artifact, to record the message payload before and after the mediation performed by individual mediators. Note that message tracing is not recommended for production environments.

mediation.flow.statistics.tracer.collect.properties

Set this property to true and enable tracing for the required ESB artifact, to record the following information.

  • Message context properties.
  • Message transport-scope properties. 

Note that message tracing is not recommended for production environments.

mediation.flow.statistics.collect.all

Set this property to true and set the mediation.flow.statistics.enable property also to true, to enable mediation statistics for all the artifacts in the ESB profile by default.

If you set this property to false, you need to set the mediation.flow.statistics.enable property to true and manually enable statistics for the required ESB artifact.

Step 2: Enabling message tracing for ESB artifacts

If you have enabled the mediation.flow.statistics.collect.all property in the synapse.properties file as explained in the previous section, you will be monitoring the statistics of all the ESB artifacts (proxy services, REST APIs, sequences, and endpoints)  by default. Alternatively, you have the option of enabling statistics for only the required artifacts.

Follow the steps below to enable tracing for a REST API artifact:

  1. Open the REST API artifact from WSO2 Integration Studio.
  2. Click the REST API icon (in the design view) to open the Properties tab for the REST API. 

  3. To enable mediation tracing for the REST API, select Enable Tracing (shown above).

Follow the steps below to enable tracing for an Endpoint artifact:

  1. Open the Endpoint artifact from WSO2 Integration Studio.
  2. Go to the Form view and then set the Trace Enabled value to 'True' as shown below.

Similarly, you can enable tracing for all the required artifacts.

  • No labels
||