This is the latest release in the 6.x.x family. For EI 7.0.0, click here.

All docs This doc

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anchor
recommendation
recommendation

Note

Note that it is not recommended to enable tracing in production environments as it generates a large number of events that reduces the performance of the analytics profile. Therefore, tracing should only be enabled in development environments.

Step 1: Enabling message tracing for the ESB server

...

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.

...

...

In a clustered deployment, statistics should be enabled for the required artifacts in all the EI nodes if you have not enabled deployment synchronizing. If deployment synchronizing is enabled, you need to enable tracing for the required artifacts only in one node.

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).

    NoteNote that it is not recommended to enable tracing in production environments as it generates a large number of events that reduces the performance. Therefore, tracing should only be enabled in development environments

    .

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

...