Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section explains how to view and analyze statistics relating to WSO2 EI endpoints using WSO2 Analytics.

...

Table of Contents
maxLevel4
minLevel2
locationtop
styleborder:1
typeflat
separatorpipe

Endpoint Request Count 

View (Example)
DescriptionThis indicates the total number of requests sent to the selected endpoint during a selected time interval. The successfully processed messages as well as the failed messages are displayed as a percentage of the total number of messages sent to the endpoint.
PurposeThis allows you to assess the extent to which an endpoint is used as well as the validity of the endpoint.
Recommended action

Compare the endpoint success rate for different time intervals. If the success rate is low during a specific time interval, check whether any unusual occurrences have taken place during that time interval (e.g., system downtime, unavailability of the back-end service.

...

View (Example)
Description

This provides the list of message IDS that were processed by a proxy service. 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.

Info

When you are searching for information in the data table, you need to use the correct search syntax as described below.

  • If you are searching for a message with a payload that contains the text foo, the search text entered in the Search field should be as follows.
    beforePayload: \"foo\" OR afterPayload: \"foo\"
  • If you are searching for a message of which the message ID is foo, the search text entered in the Search field should be as follows.
    messageId: \"foo\"
PurposeThis 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.