This section explains how to view and analyze statistics relating to inbound endpoints in WSO2 EI using WSO2 Analytics.
Use one of the following methods to view information in this page.
- When you open the EI Analytics dashboard, the Overview page is displayed by default. Click on an inbound endpoint in the TOP INBOUND ENDPOINTS BY REQUEST COUNT gadget to view information relating to that inbound endpoint.
- Click on the INBOUND ENDPOINT page and search for the inbound endpoint for which you want to view information.
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.
Inbound Endpoint Request Count
|Description||This indicates the total number of requests received by an inbound endpoint during a selected time interval, and the percentage of these requests that were successfully processed.|
|Purpose||This allows you to assess the extent to which an endpoint is used as well as the validity of the endpoint.|
|Recommended action||Check the success rate for an inbound endpoint at different time intervals. If the success rate was low only during particular time interval(s), check for unusual activities during that time interval(s) (e.g., system downtime, unavailability of the backend service etc.). If the success rate is low at all time intervals, check the configuration of the inbound endpoint as well as that of the mediation sequence used to call the inbound endpoint.|
|Description||This provides a graphical view of the count for both successful and failed messages that have been sent to an inbound endpoint during a selected time interval.|
|Purpose||This allows you to identify any correlation that may exist between message failure rate, throughput and time. As a result, you can identify unusual occurrences that may have occurred during specific times (e.g., system downtime) as well as be aware if an inbound endpoint cannot handle a high throughput.|
|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.|
|Description||This gadget provides a graphical illustration of the average time taken to process a request sent to the inbound endpoint at different times within the selected time interval.|
|Purpose||This allows you to understand the efficiency with which requests were sent to an inbound endpoint within a specific time interval in terms of the time taken per request.|
|Recommended action||If the message latency for an inbound endpoint is high during a specific time interval, check the number of requests sent to the inbound endpoint during the same time interval to identify whether the high latency was caused by an overload of requests.|
This provides the list of message IDS that were sent to the inbound endpoint during the selected time interval. Details including the port, time stamp and whether the message is successfully processed are displayed for each message ID. Messages can be sorted in an ascending or descending order based on the message ID, host, start time or status. You can search for specific message IDs, as well as click on a message ID to view more details about it in the OVERVIEW/MESSAGE/<MESSAGE_ID> page.
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 message IDs that were not successfully processed and click on them to find more details in order to take corrective action.|
|Description||This provides a graphical view of the mediation flow through which the messages sent to a specific inbound endpoint have passed.|
|Purpose||This allows you to identify the different stages of the message flow that all the messages sent to the inbound endpoint have passed through.|