How to track Live Data in Betaout

  1. How Does Betaout Live Data Tracking work?

 

Live data tracking is being brought under general settings option. Live data tracking is used to track the requests made on the API endpoints. A selection of tabs are visible under the LIVE DATA TRACKING option in Betaout Settings.

4png

Upon clicking the Live data Tracking option, user is taken to the SELECTION OF TABS under Live data tracking panel which has the following tabs each :

  1.    Live data Accepted
  2.    Live data Rejected
  3. Live data Failed
  4.    Logs
  5. System Logs

5

By default, Live Data Accepted tab is displayed.

  1. Under the IDENTIFY tab :

A selection of error codes are provided to provide a message for each process. The results of each are shown in the form of codes which help facilitate ease of deciphering.

6

 

  1. Under the USER PROPERTIES tab :

The process details are provided in the following format.

7

 

The error codes as provided have the following definitions :

8

 

  1. Under the CUSTOM EVENTS tab :

The process details are provided in the following format.

9

10

 

  1. Under the JS ISSUES tab :

The error codes as provided have the following definitions:

11

12

  1. Under the ORDERS tab :

 

Upon clicking the Live data Tracking option, user is taken to the Orders Live data tracking panel which has the following tabs, under each tab:

 

  1.    Live data Accepted
  2.    Live data Rejected
  3.    Live data Failed
  4.    Logs
  5.    System Logs

13

By default, live data accepted tab is displayed.

 

Live data Accepted Tab

This tab shows the live data requests that have been accepted at the API endpoint.

The format for the data should be :

 

  1. The request received should be shown under the Request Received Column along with  date in    a DD – MMM – YYYY , HH:MM format followed by UNIX timestamp of the request.

14

2. The second column would be Process Details , under which data should be shown in a tabular   format in the following columns:

 

  • Error Code : This should show the error code of the process performed on the Request received.
  • Error Message : This should describe the Functioning of the process.
  • Time : This should show the time of process completion in DD – MMM – YYYY , HH:MM format.
  • Timestamp : This should show the time of process completion in UNIX Timestamp.
  • JSON Data : This should be a hyperlink . The text of the hyperlink should be JSON . Upon clicking the JSON hyperlink , the required JSON for the process should be shown in a new Pop-up .The title of the popup should be JSON data. The popup should have a Close button and a (X) sign for closing the pop-up.
  • The pagination of the page should be 15 requests.

15

Live Data Rejected Tab  

This tab shows the requests that were rejected at the required API endpoint.

The format of the data should be :

 

  1. The data should be :
  • Error message – The error description should be provided along with a JSON array of the rejected request.
  • Error Code – The error code corresponding to the error message that caused the rejection.
  • Time – the time occurrence of the rejected request.
  1. The pagination should be set at 15 requests.
  2. The requests should be shown in descending order i.e. the latest request should be shown first.

 

16

Live Data Failed Tab   

This tab shows the requests that were marked as failed in order processing flow. These requests were accepted at the API endpoint validator but failed in the order processing due to some internal exceptions or data validation.

The format of the data should be :

1.The data should be :

  •         Error message – The error description should be provided along with a JSON array of the    rejected request.
  •         Error Code – The error code corresponding to the error message that caused the rejection.
  •         Time – the time occurrence of the failed request.
  1. The pagination should be set at 15 requests.
  2. The requests should be shown in descending order i.e. the latest request should be shown first.

 

Logs

This tab shows the collective error count for the specific issue type on a date basis. This tab has the data for all the requests rejected classified on a date basis.

The data should be shown in for the following format:

  1. Date
  2. Total Issues
  3. The pagination should be set at 30.
  4. The date field should have the following format : DD – MMM – YYYY , Day .
  5. The date field should be a hyperlink and the user should be redirected to the Error Type Page   upon clicking the Hyperlink.

17

Total Error Count Page

This page should be redirected upon clicking the date hyperlink from the Logs page. This page shows the entire issues for a day, grouped on the basis of the error message occurred.

The format of data on the page should be as follows:

1.The page should have a title: Total Error Count for “Selected Date” : “Total Number of Errors”.

2.The data should be shown in a tabular format under the following columns :

  •         Error message – The error description should be provided along with a JSON array of the    rejected request.
  •         Error Code – The error code corresponding to the error message that caused the rejection.
  •         Total Instance – the total number of errors of the specific error type that occurred in a day.

3.The pagination of the page should be 20.

4.The Total Instance column should be a hyperlink. Upon clicking the hyperlink the user should be redirected to the error explanation page.

18

Error Explanation Page

This page should be redirected upon clicking the total instance column in Total error count in a day page. This page shows all the rejected request of the type that user wants to check.

The format of data on the page should be:

  •  Error message – this should contain the error message along with the faulty API Request.
  •  Error Code
  • Time of occurrence.    
  • Upon clicking on an error code, its explanation should be shown in a JSON request.
  • There should be a back button to take user back to the previous page.
  • The pagination should be set at 20
  • The requests should be shown in descending order i.e. the latest request should be shown first.

19

System Logs

This tab shows the collective error count for all the different Issue types on a date basis. This tab has the data for all the requests rejected classified on a date basis.

The data should be shown in for the following format:

  1. Date
  2. Total Issues
  3. The pagination should be set at 30.
  4. The date field should have the following format : DD – MMM – YYYY , Day .
  5. The date field should be a hyperlink and the user should be redirected to the Error Type Page upon clicking the Hyperlink.