The monitoring center monitors a series of items for an application during its running and reports alarms based on the generated monitoring data and alarm thresholds configured by the developer. The major monitoring items include the application success rate, application traffic, security vulnerability monitoring, application availability ratio, and application response time. Developers can click Setting Alarms to set alarm thresholds for their own applications.
The application success rate is calculated as follows: Application success rate = Total times of successful API invocation within a day/Total times of effective API invocation within the same day. Developers can click Success Rate to check the daily success rate of their own applications. According to requirements on the open platform, an alarm will be generated if the developer’s application success rate is lower than 98%. Therefore, it is recommended that the developer pay attention to keeping the application success rate higher than or equal to 98%.
For details about the settings, click Monitoring and Warning Configuration.
Application traffic equals the total times of API invocation in a day. Developers can click API Invocation to check the daily API invocation of their own applications. Each time an application is created, it will obtain a traffic package, that is, the maximum times that APIs can be invoked per day. If the API invocation quantity of this application exceeds its traffic package, the application traffic will be limited. In this manner, it is recommended that developers keep watching the API invocation of their own applications, set an application traffic threshold, and submit a traffic application in a timely manner if the application traffic exceeds the preconfigured threshold.
During security vulnerability monitoring, the open platform uses a scanning tool to scan the code of applications. If any defects are detected in an application, an alarm will be generated. Developers can click Security Vulnerability to check the list of security vulnerabilities for their own applications. In the meantime, developers must comply with the Third-Party Application Security Specifications of the open platform.
The open platform detects the callback URL (that is, the binding domain name of a website application) of an application every 10 minutes and 144 times a day. The application availability ratio is calculated as follows: Application availability ratio = Times of successful callback URL detection/144. Developers can click Availability Ratio to check the availability ratio of their own applications.
If the availability ratio of an application is excessively low, it is very likely that this application has some errors (for example, a web page cannot be opened or a web page is opened abnormally). User experience will be seriously affected.
Currently, this application availability ratio monitoring service is a value-added service provided by the open platform. The application availability ratio reflects only the usage of an application, and is temporarily not associated with the traffic and AliExpress application permission if this application is usually capable of providing services stably.
For details about the settings, click Monitoring and Warning Configuration.
Each time the open platform makes a request to detect the callback URL of an application, it also records the response time. The average application response time is calculated as follows: Average application response time = SUM(Application response time)/144. Developers can click Response Time to check the response time of their own applications. If the application response time is excessively long, it is very likely that this application has some errors, and the user has to wait for a longer time before normal operations.
For details about the settings, click Monitoring and Warning Configuration.
