Analyzing Statistics for Mediators

This section explains how to view statistics relating to the ESB profile mediators and analyze them using WSO2 Analytics.

This page displays information about a specific mediator configuration included in a specific proxy service/REST API/sequence. In order to view statistics for a specific mediator configuration, do the following.

Click on the PROXY SERVICE page and search for the proxy service with the mediator you want to analyze. Then click on the relevant mediator displayed in the MESSAGE FLOW gadget.
Click on the API page and search for the REST API with the mediator you want to analyze. Then click on the relevant mediator displayed in the MESSAGE FLOW gadget.
Click on the SEQUENCE page and search for the sequence with the mediator you want to analyze. Then click on the relevant mediator displayed in the MESSAGE FLOW gadget.

At any given time, this page displays the statistics for a selected time interval. Make sure you select the required time interval in the following bar displayed at the top of the page. If you want to define a custom time interval, click Custom and select the start and end dates of the required time interval in the calendar that appears.

Mediator Request Count

View (Example)
Description	This indicates the total number requests that have been processed by a specific mediator during a selected time interval, the percentage of these requests that were successfully processed.
Purpose	Viewing the request count for different mediators allows you to identify the nature of mediation performed for transactions processed for your applications and services. By comparing message count patterns for all the mediators included in a specific proxy service/REST API/sequence, you can identify configuration errors that have caused message failure.
Recommended action	Compare the request count of a mediator with that of the preceding/subsequent mediators in the mediation sequence. If there is a difference, it indicates that an error has occurred in the mediation flow between the two mediators.

Message Count

View (Example)
Description	This provides a graphical view of the count for both successful and failed messages that were processed by a specific mediator during a selected time interval.
Purpose	This allows you to identify any correlation that may exist between message failure rate, throughput and time.
Recommended action	If the message failure is particularly high during a specific time, you can check whether any unusual occurrences have taken place during that time (e.g., system downtime, unavailability of the back-end service) and take appropriate action.

Message Latency

View (Example)
Description	This provides a graphical illustration of the time spent per message to perform the mediation by the selected mediator over time.
Purpose	This enables you to understand the efficiency with which the mediation is performed by a selected mediator.
Recommended action	If the message latency is persistently high, check the mediator configuration for possible changes that can result in lower latency. You can also check the complete mediation flow of the relevant proxy service/API/sequence, and consider other combination of mediators that can be used to achieve the same mediation end result.

Messages

View (Example)
Description	This provides the list of message IDS that were processed using a mediator. Details including the port, time stamp and whether the message is successfully processed are displayed for each message ID. When you search for information in this table, you need to use the correct search syntax as explained in Searching for Messages.
Purpose	This allows you to identify the individual messages processed by a specific mediator that have failed, and check whether the mediator has been correctly used for that message (e.g., in combination with other mediators).
Recommended action	Click on a failed message ID to view the message in the OVERVIEW/MESSAGE/<MESSAGE_ID> page. Then click on the mediator (i.e. the one currently being analyzed) in the MESSAGE FLOW gadget. This updates the MEDIATOR PROPERTIES gadget with the payload, transport properties and context properties in the message before and after the mediation was carried out by the mediator. Analyze the differences to identify errors in the mediation performed.