You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
This section explains how to analyze mediation sequences in WSO2 EI using WSO2 Analytics.
Sequence Request Count
View (Example) | |
---|
Description | This indicates the total number of requests that have passed through a mediation sequence during a selected time period, and the rate of success within the same period. |
---|
Purpose | This allows you to identify the throughput of messages that have passed through a mediation sequence during different time periods in order to understand the usage patterns the related applications/services. Comparing the success rate during different time intervals helps you to identify any unusual occurrences that have taken place during specific times (e.g., system downtime). |
---|
Recommended action | Check the success/failure rate for a sequence 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 sequence for configuration errors. |
---|
Message Count
View (Example) | |
---|
Description | This provides a graphical view of the count for both successful and failed messages that have passed through a mediation sequence during a selected time interval. |
---|
Purpose | This allows you to identify any correlation that may exist between message failure rate, throughput and time for a specific sequence. |
---|
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 | The time taken by the selected sequence to complete the mediation it carries out per request. |
---|
Purpose | This enables you to understand the level of efficiency with which the mediation is carried out by sequences. |
---|
Recommended action | If the message latency of a sequence is too high, check its configuration and consider alternative configurations through which the same mediation can be done. |
---|
Messages
View (Example) | |
---|
Description | This provides the list of message IDs that were processed by the selected sequence. 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. |
---|
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. |
---|
Recommended action | - Sort the messages by the status and check whether message failure correlates with specific time intervals. If such a pattern is identified, check whether any unusual activity (e.g., system downtime, unavailability of the backend service) has occurred during that time.
- Sort the messages by the status and check whether message failure correlates with a specific host. If message failures mainly occur for a specific port(s) investigate further.
- Click on the message IDs that have failed for further information about them in the OVERVIEW/MESSAGE/<MESSAGE_ID> page.
|
---|
Message Flow
View (Example) | |
---|
Description | This provides a graphical view of the mediation flow through which the messages handled by a sequence have passed. |
---|
Purpose | This allows you to understand the different stages of mediation that a selected message ID has passed. |
---|
Recommended action | - Check whether the message flow is correctly configured based on your requirement, and make modifications if required.
- Click on different mediators included in the message flow to view more details about them.
|
---|