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.

...

  1. Open the carbon.xml file (stored in the <EI_HOME>/conf/ directory).
  2. Under <Analytics>, enter the relevant configurations as described in the table below. 

    PropertyRequired ValueExample
    ServerURL

    The URL to which the EI statistics are published as events. The format of this URL can be one of the following:

    • <protocol>://<hostname
    • <ip>:<port>

    When you deploy EI Analytics as an HA cluster, enter the URLS of the Analytics nodes as a list of comma-separated URLSURLs that are separated by vertical bars (|).

    AuthServerURL

    When the authentication of EI statistics published to EI Analytics is carried out in a separate server, set this parameter to specify the URL of that authentication server.

    The format of this URL can be one of the following:

    • <protocol>://<hostname
    • <ip>:<port>
    ssl://localhost:7712
    UsernameThe username to use when accessing the WSO2 EI Analytics server to publish configurations.admin
    PasswordThe password to use when accessing the WSO2 EI Analytics server to publish configurations.admin



  3. Open the synapse.properties file (stored in the <EI_HOME>/conf/ directory) and configure the following property.

    PropertyDescription
    mediation.flow.statistics.enable

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

    • The time spent on each mediator.
    • The time spent to process each message.
    • The fault count of a single message flow.

Configuring the ESB to publish data to Jaeger

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.

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

...

    • following property.

Enabling statistics/message tracing

...

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 statistics/message tracing for the ESB server

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

...

Info
titleUsing the management console?

The following table specifies the path to the Enable Statistics link for each ESB artifact type that can be analyzed using the Analytics Dashboard using the management console.

EI Artifact TypePath
Proxy ServiceMain tab => Services => List => Deployed Services page => <Proxy_Service_Name>
REST APIMain tab => APIs => Deployed APIs page
SequenceMain tab => Sequences => Mediation Sequences page
EndpointMain tab => Endpoints => Manage Endpoints page
Inbound EndpointMain tab => Inbound Endpoints => Manage Inbound Endpoints page