Analyzing EI Statistics Overview

The Overview page of the EI Analytics dashboard allows you to form a basic understanding of the performance your web services and applications by analyzing the activities carried out by WSO2 EI. This dashboard displays information such as the overall success rate of the EI in terms of request handling, and the ranking of different EI artifacts (such as proxy services, REST APIs, sequences etc.) based on their usage. This section explains how this information can be analyzed.

When you open the EI Analytics dashboard, the Overview page is displayed by default. For more information about accessing the EI Analytics Dashboard, see Analyzing WSO2 EI via the Analytics Dashboard.

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.

Request Summary

View (Example)
Description	This indicates the total number of requests that the EI has handled during the selected period of time. The number of requests that have been successfully processed as well as the number of requests that have failed during the selected time period are displayed as percentages of the total number of requests handled.
Purpose	This gadget can be used for the following purposes. Understanding he extent to which the EI was utilized during a selected time interval. Checking success rate of the EI during a selected time interval.
Recommended Action	If the success rate is too low, you can check the individual proxy services and REST APIs individually to identify which proxy services/REST APIs are affecting the overall success rate and take corrective action where required.

Overall TPS

View (Example)
Description	This indicates the number of transactions that the EI has processed during a second.
Purpose	This indicator allows you to analyse the overall efficiency of the EI in terms of the request processing speed.
Recommended Action	A high TPS value indicates that the EI is handling a high load of requests. This requires you to ensure that your system is running smoothly in terms of resource allocation, and add more EI nodes if required.

Overall Message Count

View (Example)
Description	This provides a graphical view of the total count of successful messages as well as failed messages during a selected time period.
Purpose	This helps you to identify any correlations that may exist during message failure 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) and take appropriate action.

Top Proxy Services by Request Count

View (Example)
Description	This ranks the most frequently used proxy services based on the usage. You can click on each proxy service displayed in this gadget to view more detailed information about it in the OVERVIEW/PROXY/<PROXY_SERVICE_NAME> page.
Purpose	This allows you to identify the most frequently used proxy services during specific time periods and understand usage patterns relating to your applications and services based on that.
Recommended Action	You can identify the most utilized proxy services during time intervals with a high rate of request failure, click on them to view whether their individual failure rates (in general) are high, and take corrective action if required.

Top APIs by Request Count

View (Example)
Description	This ranks the most frequently used REST APIs based on the usage.
Purpose	This allows you to identify the most frequently used REST APIs during specific time periods and understand usage patterns relating to your applications and services based on that.
Recommended Action	You can identify the most utilized REST APIs during time intervals with a high rate of request failure, click on them to view whether their individual failure rates (in general) are high, and take corrective action if required.

Top Endpoints by Request Count

View (Example)
Description	This ranks the most frequently used endpoints based on the usage.
Purpose	This allows you to identify the most frequently used endpoints during specific time periods and understand usage patterns relating to your applications and services based on that.
Recommended Action	You can identify the most utilized endpoints during time intervals with a high rate of request failure, click on them to view whether their individual failure rates (in general) are high, and take corrective action if required.

Top Inbound Endpoints by Request Count

View (Example)
Description	This ranks the most frequently used inbound endpoints based on the usage.
Purpose	This allows you to identify the most frequently used inbound endpoints during specific time periods and understand usage patterns relating to your applications and services based on that.
Recommended Action	You can identify the most utilized inbound endpoints during time intervals with a high rate of request failure, click on them to view whether their individual failure rates (in general) are high, and take corrective action if required.

Top Sequences by Request Count

View (Example)
Description	This ranks the most frequently used sequences based on their usage.
Purpose	This helps to identify the most frequently used mediation patterns, which in turn helps to understand the nature of activities carried out by users of your applications and services.
Recommended Action	You can identify the most utilized sequences during time intervals with a high rate of request failure, click on them to view whether their individual failure rates (in general) are high, and take corrective action if required.