TWI855948B - Monitoring and limiting system of requesting to access system resources and method thereof - Google Patents

Abstract

A monitoring and limiting system of requesting to access system resources and method thereof are provided. The monitoring and limiting system include a storage device and a processor. The storage device stores a traffic limiting and intercepting module, a data analysis module and an execution module. The processor receives request data for executing an application programming interface. The traffic limiting and intercepting module determines whether the requested data is a traffic limiting request based on a traffic limiting configuration table, and generates a judgment result. In response to the judgment result being a traffic limiting request, the traffic limiting and intercepting module rejects access to the requested data and outputs a preset message. In response to the judgment result being a non-traffic-limiting request, the traffic limiting and intercepting module inputs the request data to the execution module. The Execute module executes the request data. The data analysis module adjusts the traffic limiting configuration table based on resource data and application interface request processes.

Description

Monitoring current limiting system and method thereof

The present invention relates to a request data of a current limiting application program interface, and in particular to a monitoring current limiting system and method thereof.

Applications used to provide (business) services usually provide application programming interfaces (APIs) with specific capabilities to provide functional services to the outside world. However, in order to implement a certain business behavior, the system or user will usually call a specific application programming interface to obtain the desired execution service or output result (business data). However, when there is a large demand for service resources or a traffic peak in a period of time, it may cause the server or system providing the service to fail, respond/respond slowly, or crash. When a system fails, the entire service system will not work, resulting in a poor user experience. Therefore, traditional project servers connected to application programming interfaces have the problem of being unable to handle large amounts of request data and not being able to limit traffic or configure resources based on time periods or computing resources.

The present invention is directed to a monitoring and current limiting system and method thereof, which can automatically determine whether to limit the current of part of the requested data according to the time period of the requested data and the level of the called application program interface.

According to an embodiment of the present invention, the monitoring and current limiting system of the present invention includes a storage device and a processor. The storage device stores multiple modules and a current limiting configuration table. The processor is coupled to the storage device. The processor executes multiple modules and receives request data for executing an application programming interface. The multiple modules include a current limiting interception module, a data analysis module, and an execution module. The current limiting interception module determines whether the request data is a current limiting request based on the current limiting configuration table, and generates a judgment result. In response to the judgment result being a current limiting request, the current limiting interception module rejects access to the request data and outputs a default message. In response to the judgment result being a non-current-limited request, the current-limiting interception module inputs the request data to the execution module. The execution module executes the request data. The data analysis module adjusts the current-limiting configuration table based on the resource data and the API request history.

According to an embodiment of the present invention, the monitoring and current limiting method of the present invention includes the following steps: receiving request data for executing an application program interface; judging whether the request data is a current limiting request according to a current limiting configuration table through a current limiting interception module, and generating a judgment result; in response to the judgment result being a current limiting request, refusing access to the request data through the current limiting interception module, and outputting a preset message; in response to the judgment result being a non-current limiting request, inputting the request data into an execution module through the current limiting interception module; executing the request data through the execution module; adjusting the current limiting configuration table according to resource data and the application program interface request history through a data analysis module.

Based on the above, the monitoring and current limiting system and method of the present invention can set current limits for different application program interfaces and request data in different time periods according to the time period of the request data and the level of the called application program interface.

In order to make the above features and advantages of the present invention more clearly understood, embodiments are given below and described in detail with reference to the accompanying drawings.

Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Whenever possible, the same reference numerals are used in the drawings and description to represent the same or similar parts.

FIG1 is a schematic diagram of a monitoring and current limiting system of an embodiment of the present invention. Referring to FIG1 , the monitoring and current limiting system 100 includes a processor 110 and a storage device 120. The processor 110 is coupled to the storage device 120. The storage device 120 stores a limited flow interception module, a data analysis module, and an execution module. In this embodiment, the monitoring and current limiting system 100 may, for example, be set in a cloud server so that users can connect and execute related business service functions of different application programming interfaces (APIs) also set in the cloud server. The cloud server may be, for example, a Software as a Service (SaaS) server, and the application program interface corresponds to a Software as a Service application, but the present invention is not limited thereto. Alternatively, in one embodiment, the monitoring and current limiting system 100 may be set in an enterprise resource planning (ERP) system operated by a local server within the enterprise to provide relevant business service functions (such as generating purchase orders, purchase requisitions, quotations, and other such business services) through different application program interfaces, but the present invention should not be limited thereto.

In the present embodiment, the processor 110 may be a system on a chip (SOC), or may include, for example, a central processing unit (CPU) or other programmable general-purpose or special-purpose microprocessors, digital signal processors (DSP), programmable controllers, application specific integrated circuits (ASIC), programmable logic devices (PLD), other similar processing devices, or a combination of these devices. The storage device 120 may include a memory and/or a database, wherein the memory may be, for example, a dynamic random access memory (DRAM), a flash memory, or a non-volatile random access memory (NVRAM). The storage device 120 may store relevant programs, modules, systems, or algorithms useful for implementing various embodiments of the present invention, so that the processor 110 can access and execute them to implement the relevant functions and operations described in various embodiments of the present invention. In this embodiment, the current limiting interception module, the data analysis module, the execution module and other modules in this case can be implemented in programming languages such as JSON (JavaScript Object Notation), Extensible Markup Language (XML) or YAML, but the present invention is not limited to this.

In this embodiment, the user can, for example, execute the monitoring and current limiting system 100 through a personal computer device, and input the request data into the monitoring and current limiting system 100 to request the execution of the corresponding application program interface. In another embodiment, the monitoring and current limiting system 100 and the project service system are set in the same server, and then the user inputs the request data into the server through a personal terminal device to request the execution of the project service. The monitoring and current limiting system 100 can automatically execute the current limiting interception module, the data analysis module and the execution module according to the request data to automatically generate the corresponding current limiting judgment result and the execution result (business data).

In this embodiment, the current limiting interception module can determine whether the current request data is a current limiting request according to the current limiting configuration table stored in the storage device 120, and generate a judgment result. When the judgment result is that the current request data belongs to a current limiting request, the current limiting interception module rejects the access to the current request data and the call of the application program interface, and the current limiting interception module simultaneously outputs a preset message to the terminal device corresponding to the current request data. On the other hand, when the judgment result is a non-current limiting request, the current limiting interception module inputs the request data to the execution module. Then, the execution module executes the request data. It is worth noting that the data analysis module adjusts the current limiting configuration table based on resource data and application program interface request history.

FIG2 is a flow chart of a monitoring and current limiting method of an embodiment of the present invention. Referring to FIG1 and FIG2, the monitoring and current limiting system 100 may execute the following steps S210 to S260 to automatically generate corresponding judgment results, and execute corresponding results according to the type of request data and the time period. In this embodiment, the user may input request data to the monitoring and current limiting system 100 to execute a (specific) application program interface. In step S210, the processor 110 may receive request data for executing the application program interface. Specifically, the user outputs the request data for using the project system (for example, calling a specific application program interface) through his terminal device to a server equipped with the monitoring and current limiting system 100. Then, the server inputs the request data into the monitoring and current limiting system 100.

In step S220, the processor 110 can determine whether the request data is a current limiting request according to the current limiting configuration table through the current limiting interception module, and generate a judgment result. In this embodiment, the current limiting configuration table includes a current limiting time period, each application program interface level in the current limiting time period, and a current limiting ratio corresponding to each application program interface level. In this way, the current limiting interception module compares the current request data with the current limiting configuration table, and then determines whether the current request data belongs to a request (such as a service request) that needs to limit the flow in the current limiting configuration table. In addition, the current limiting interception module generates a judgment result based on the comparison result.

In step S230, in response to the judgment result being a current limiting request, the current limiting interception module denies access to the request data. Specifically, when the judgment result is that the current request data belongs to a current limiting request, the current limiting interception module denies the current request data to achieve control of computing resources and flow limitation. In step S240, a default message is output through the current limiting interception module. In one embodiment, the current limiting interception module outputs a default message to the terminal device corresponding to the current request data. In other words, the current limiting interception module outputs a default message to the terminal device that issued the current request data, and then informs the user of the reason why the current request data failed to be successfully requested. The default message may be "There are too many service requests at this time, please wait" or "There is a traffic jam at this time, please wait".

In step S250, in response to the judgment result being a non-current-limited request, the request data is input into the execution module through the current-limiting interception module. Specifically, when the judgment result is that the current request data does not belong to a current-limited request (i.e., it belongs to a non-current-limited request), the current-limiting interception module inputs the current request data into the execution module. Then, in step S260, the current request data is executed through the execution module. For example, the execution module executes the request data by calling the application programming interface corresponding to the request data, or executing the service operation corresponding to the request data. In one implementation, the execution module can determine the calling method of multiple application programming interface objects according to the structure of the request data, such as one call or multiple calls.

In this way, the monitoring and current limiting system 100 and method of the present invention can automatically determine whether the request data needs to be current limited according to the settings and annotations in the current limiting configuration table, thereby achieving service resource management and current limiting monitoring. In this way, the monitoring and current limiting system 100 can effectively avoid service resource overload and system failure by limiting the current in some time periods and some ratios.

FIG3 is a schematic diagram of the execution of multiple modules of an embodiment of the present invention. Refer to FIG3. In one embodiment, the multiple modules further include a data collection module 340, and the storage device is a database 350. The data collection module 340 collects resource data and application program interface request history regularly according to a preset time, and stores the resource data and application program interface request history in the storage device 120 or the database 350.

In one embodiment, the current limiting configuration table includes at least one of the following: application program interface level, current limiting time period, current service execution times, execution upper limits of multiple application program interface levels, current application program interface level execution times, current current application program interface level, current limiting calculation settings, executable rate, and current limiting coefficient. The application program interface level is a preset level for different application program interfaces. For example, the application program interface level is divided into three levels according to request frequency and computational complexity, namely, a first-level application program interface, a second-level application program interface, and a third-level application program interface. The computational complexity of a first-level application program interface is greater than that of a third-level application program interface.

In other words, the current limiting configuration table includes the level (i.e., application interface level) corresponding to each application program interface. The current limiting time period is the time period in multiple service time periods that is annotated as requiring current limiting. The current service execution times are the current total service request times. The execution upper limit of the application program interface level is the upper limit of each application program interface level that can be executed in the current limiting stage. For example, the first-level application program interface can be executed 100 times, and the second-level application program interface can be executed 50 times. The current application program interface level execution times are the number of times each application program interface level has been executed in the current time period. The current limiting calculation setting is a setting or formula for calculating the execution upper limit value of each application program interface level. The executable rate is the ratio of each application program interface level that can be executed, for example, the executable rate of the first-level application program interface is 90%, the executable rate of the second-level application program interface is 95%, and the executable rate of the third-level application program interface is 98%. The current limiting coefficient is the coefficient in the current limiting calculation setting. In one embodiment, the current limiting coefficient is a positive integer.

In one embodiment, the current limiting configuration table includes application program interface levels, and the application program interface levels include first-level application program interfaces, second-level application program interfaces, and third-level application program interfaces, and different application program interface levels have different executable rates. For example, the executable rate of the first-level application program interface is related to the value of the current limiting coefficient, the executable rate of the second-level application program interface is related to the product of the current limiting coefficient and a constant, and the executable rate of the third-level application program interface is related to the current limiting coefficient. Specifically, the executable rate of the first-level application program interface is inversely proportional to the value of the current limiting coefficient. In one embodiment, the executable rate of the first-level application programming interface is 1-1%*2 ⁿ , the executable rate of the second-level application programming interface is 1-1%*2n, and the executable rate of the third-level application programming interface is 1-1%*n. The present invention should not be limited to this. In this embodiment, n is the current limiting coefficient, and n is not greater than 5.

As shown in FIG3 , the monitoring and current limiting system 100 can execute the following steps S311 to S314 and step S351. The user sends request data to the monitoring and current limiting system 300 through the terminal device 360. In step S311, after the current limiting interception module 310 receives the request data, the current limiting interception module 310 determines whether the current request data needs to be current limited (i.e., whether it is a current limiting request). The determination of step S311 can be further divided into step S312 and step S313. In step S312, the flow limiting interception module 310 determines whether the request data is within the flow limiting range, such as within the flow limiting time period (such as 9 am to 10 am), or corresponds to a specific application programming interface. When the determination result of step S312 is that the current request data is within the flow limiting range, step S313 is then executed.

In step S313, the current limiting interception module 310 determines whether the current current limiting threshold corresponding to the request data (e.g., the number of executions of the current API level) has reached the current limiting threshold (e.g., the upper limit of the execution of the corresponding API level). When the determination result of step S312 is that the number of executions of the API level corresponding to the current request data has reached the upper limit, step S314 is then executed. In step S314, the current limiting interception module 310 outputs a friendly message to the user's terminal device 360. The friendly message is a default system message (i.e., a default message). When the judgment results of step S312 and step S313 are no, the current request data is executed by the execution module 330.

In one embodiment, the current limiting interception module 310 determines whether the request data is a current limiting request based on the current limiting configuration table and the application program interface request history. Specifically, the current limiting time period, the level of the application program interface, and the current limiting threshold and other information can be obtained through the current limiting configuration table. The current limiting threshold or the number of executions of the current application program interface level (for example, the current number of executions of the second-level application program interface is 20 times) can be obtained through the application program interface request history. The current limiting request is a service request in which the request data matches the monitoring time period, and the number of executions of the current application program interface level in the monitoring time period reaches the corresponding execution upper limit of the application program interface level.

FIG4 is a flow chart of the data analysis module 320 adjusting the current limiting configuration table of an embodiment of the present invention. In one embodiment, the current limiting configuration table includes the current limiting coefficient and the resource data threshold. Referring to FIG3 and FIG4, the monitoring current limiting system 300 can execute the following steps S410~S450. In step S410, the data analysis module 320 scans the resource data in the storage device/database 350. Specifically, the data analysis module 320 can be set to perform data scanning during non-peak traffic hours to avoid occupying peak computing resources. For example, the data analysis module 320 scans resource data at 12 o'clock every night. In step S420, the data analysis module 320 obtains the monitoring time period in the resource data that exceeds the resource data threshold. For example, the resource data includes the utilization rate of the central processing unit (CPU) and the memory utilization rate, and the resource data threshold is that the CPU utilization rate reaches 75% and the memory utilization rate reaches 80%. In step S420, the data analysis module 320 determines the request data history stored in the storage device/database 350, and then determines one by one whether the resource data of each time period is higher than the resource data threshold, and then obtains at least one monitoring time period in which the resource data exceeds the threshold.

In step S430, the data analysis module 320 determines whether the monitoring time period obtained in step S420 has been set with a current limiting coefficient. Specifically, the current limiting coefficient is included in the current limiting calculation setting. Therefore, by determining whether the monitoring time period has been set with a limited flow coefficient, the data analysis module 320 can determine whether the current monitoring time period has been monitored. For example, if the resource data from 7 pm to 9 pm on the first day is higher than the resource data threshold, the data analysis module 320 sets the current limiting coefficient from 7 pm to 9 pm to 1. Then, if the resource data from 7 pm to 9 pm on the second day is still higher than the resource data threshold, the data analysis module 320 determines that the limited flow coefficient has been set for the time period from 7 pm to 9 pm. In this way, in response to the time period from 7pm to 9pm being controlled with a limited flow coefficient, the data analysis module 320 executes step S450. On the contrary, when the data analysis module 320 determines that the current monitoring time period is not set with a limited flow coefficient, it executes step S440.

In step S440, in response to the monitoring time period not having a current limiting coefficient set, the data analysis module 320 sets the current limiting coefficient of the monitoring time period to 1. In step S450, in response to the monitoring time period having a current limiting coefficient set, the data analysis module 320 adds 1 to the current limiting coefficient of the monitoring time period as a new current limiting coefficient. For example, if the current limiting coefficient from 7:00 p.m. to 9:00 p.m. on the third day is 2, the data analysis module 320 sets 3 as the new current limiting coefficient for the current monitoring time period. In this embodiment, the current limiting coefficient has a coefficient threshold, and the coefficient threshold is, for example, 5. When the current limiting coefficient of the monitoring time period reaches the coefficient threshold, the data analysis module 320 stops increasing the value of the current limiting coefficient, and instead the data analysis module 320 outputs the message of the monitoring time period and the preset warning message. Specifically, when the data analysis module 320 executes step S430, it determines that the current limiting coefficient has been set for the monitoring time period, and the current limiting coefficient of the monitoring time period has reached the coefficient threshold. For example, the data analysis module 320 outputs a reminder message to the terminal device of the staff. In another embodiment, the data analysis module 320 records the messages of these time periods and stores them in a storage device (such as a database 350) for system personnel to review.

In one embodiment, the data analysis module 320 obtains a coefficient time period with a current limiting coefficient according to a current limiting configuration table. The data analysis module 320 scans the resource data to obtain a time period to be adjusted in which the resource data (such as CPU usage and memory usage) in the coefficient time period is lower than the resource data threshold. Then, the data analysis module 320 subtracts 1 from the current limiting coefficient of the time period to be adjusted as a new current limiting coefficient. When the current limiting coefficient is 0, the current limiting calculation is set to 0. That is to say, when the current limiting coefficient is 0, the corresponding time period is a non-monitoring time period.

In one embodiment, the current limiting configuration table includes a custom annotation table. Specifically, the custom annotation table includes at least one of the level of the application program interface, the description information of the application program interface, and the name of the application program interface. For example, the monitoring current limiting system 300 can obtain the annotation and information related to the application program interface, such as the level of the application program interface, according to the custom annotation table.

In one embodiment, the plurality of modules further include an asynchronous interception module. The asynchronous interception module is used to intercept request data and store the information of the request data in the storage device/database 350. The asynchronous interception module stores the API, the number of executions of the API, the time period, the API name, the access method of the API, the access address of the API and/or the input data structure of the API related to the request data in the request log table in an asynchronous manner. It is worth noting that the asynchronous interception module captures and stores information about request data in an asynchronous manner in order not to affect the execution of the project system and the business process, thereby avoiding affecting the resource data and computing efficiency of the project service. In this embodiment, the maximum value of the current limiting coefficient is 5, and the storage device 120 stores the request log table.

In summary, the monitoring and current limiting system (100, 300) and method of the present invention can determine the time period and application program interface level of the current request data according to the execution time period and the current limiting calculation setting, and then perform specific current limiting control according to the complexity of the execution and the execution time period. In addition, the monitoring and current limiting system (100, 300) obtains the resource data of each time period according to the request data history, and then increases or decreases the current limiting coefficient according to the resource data history to achieve step-by-step resource data control (i.e., current limiting), so as to effectively and step-by-step manage and control the current limiting ratio of each time period and each application program interface level.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technical personnel in this field should understand that they can still modify the technical solutions described in the above embodiments, or replace part or all of the technical features therein with equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present invention.

100: Monitoring current limiting system

110:Processor

120: Storage device

101: Data relationship acquisition and analysis module

102: Request data analysis unit

300: Monitoring current limiting system

310: Current limiting module

320:Data Analysis Module

330: Execution module

340:Data Collection Module

350: Database

360: Terminal Device

S210~S260, S311~S314, S351, S410~S450: Steps

FIG1 is a schematic diagram of a monitoring current limiting system of an embodiment of the present invention. FIG2 is a flow chart of a monitoring current limiting method of an embodiment of the present invention. FIG3 is a schematic diagram of the execution of multiple modules of an embodiment of the present invention. FIG4 is a flow chart of a data analysis module adjusting a current limiting configuration table of an embodiment of the present invention.

S210~S260: Steps

Claims (18)

A monitoring current limiting system includes: a storage device storing a plurality of modules and a current limiting configuration table; and a processor coupled to the storage device, executing the plurality of modules and receiving request data for executing an application programming interface, wherein the plurality of modules include a current limiting interception module, a data analysis module and an execution module, wherein the current limiting interception module performs a current limiting operation according to the current limiting configuration table. The flow configuration table determines whether the request data is a current limiting request and generates a determination result, wherein in response to the determination result being the current limiting request, the current limiting interception module rejects access to the request data and outputs a preset message, wherein in response to the determination result being a non-current limiting request, the current limiting interception module inputs the request data to the execution module, The execution module executes the request data, the data analysis module adjusts the current limiting configuration table according to the resource data and the application program interface request history, the current limiting configuration table includes application program interface levels, the application program interface levels include first-level application program interfaces, second-level application program interfaces, and third-level application program interfaces, and different application program interface levels have different executable rates, the executable rate of the first-level application program interface is related to the value of the current limiting coefficient, the executable rate of the second-level application program interface is related to the product of the current limiting coefficient and a constant, and the executable rate of the third-level application program interface is related to the current limiting coefficient. The monitoring and current limiting system as described in claim 1, wherein the multiple modules further include: a data collection module, which collects the resource data and the application program interface request history regularly according to a preset time, and stores the resource data and the application program interface request history in the storage device. The monitoring and current limiting system as described in claim 1, wherein the current limiting configuration table further includes at least one of the current limiting time period, the current service execution times, the execution upper limits of multiple application program interface levels, the current application program interface level execution times, the current current application program interface level, the current limiting calculation settings, the executable rate, and the current limiting coefficient. A monitoring and current limiting system as described in claim 1, wherein the current limiting configuration table includes a custom annotation table, wherein the custom annotation table includes at least one of the level of the application program interface, the description message of the application program interface, and the name of the application program interface. A monitoring and current limiting system as described in claim 1, wherein the data analysis module obtains a coefficient time period having the current limiting coefficient according to the current limiting configuration table, wherein the data analysis module scans the resource data to obtain a time period to be adjusted in which the resource data in the coefficient time period is lower than the resource data threshold, wherein the data analysis module subtracts 1 from the current limiting coefficient of the time period to be adjusted as a new current limiting coefficient. A monitoring and current limiting system as described in claim 1, wherein the current limiting configuration table includes a current current limiting coefficient and a resource data threshold, wherein the data analysis module scans the resource data in the storage device to obtain a monitoring time period in the resource data that exceeds the resource data threshold, wherein the data analysis module determines whether a current limiting coefficient is set for the monitoring time period, wherein in response to the monitoring time period not having the current limiting coefficient set, the data analysis module sets the current limiting coefficient for the monitoring time period to 1, wherein in response to the monitoring time period having the current limiting coefficient set, the data analysis module adds 1 to the current limiting coefficient for the monitoring time period as a new current limiting coefficient. The monitoring and current limiting system as described in claim 6, wherein when the current limiting coefficient of the monitoring time period reaches the coefficient threshold, the data analysis module outputs the message of the monitoring time period and the preset warning message. The monitoring and current limiting system as described in claim 6, wherein the current limiting interception module determines whether the request data is the current limiting request according to the current limiting configuration table and the application program interface request history, wherein the current limiting request is a service request in which the request data matches the monitoring time period, and the execution times of the current application program interface level in the monitoring time period reaches the execution upper limit value of the corresponding application program interface level. The monitoring and current limiting system as described in claim 6 further comprises: an asynchronous interception module for intercepting the request data and storing the information of the request data in the storage device, wherein the asynchronous interception module stores the application program interface related to the request data, the number of executions of the application program interface and the time period in the request log table in an asynchronous manner, wherein the maximum value of the current limiting coefficient is 5, and the storage device stores the request log table. A monitoring current limiting method comprises: receiving request data for executing an application program interface through a processor; executing a current limiting interception module through the processor, so that the current limiting interception module determines whether the request data is a current limiting request according to a current limiting configuration table, and generates a judgment result; in response to the judgment result being the current limiting request, The current limiting interception module rejects access to the request data and outputs a preset message; in response to the judgment result being a non-current limiting request, the request data is input to the execution module through the current limiting interception module; the execution module is executed by the processor so that the execution module executes the request data; and the processor executes the data According to the analysis module, the data analysis module adjusts the current limiting configuration table according to the resource data and the application program interface request history, wherein the current limiting configuration table includes an application program interface level, wherein the application program interface level includes a first-level application program interface, a second-level application program interface, and a third-level application program interface, and different application program interface levels have different executable rates, wherein the executable rate of the first-level application program interface is related to the value of the current limiting coefficient, wherein the executable rate of the second-level application program interface is related to the product of the current limiting coefficient and a constant, wherein the executable rate of the third-level application program interface is related to the current limiting coefficient. The monitoring and current limiting method as described in claim 10 further includes: executing a data collection module through the processor so that the data collection module collects the resource data and the application program interface request history regularly according to a preset time; and storing the resource data and the application program interface request history in a storage device through the data collection module. The monitoring and limiting method as described in claim 10, wherein the limiting configuration table further includes at least one of the limiting time period, the current service execution times, the execution upper limits of multiple application program interface levels, the current application program interface level execution times, the limiting calculation settings, the executable rate, and the limiting coefficient. A monitoring and limiting method as described in claim 10, wherein the limiting configuration table includes a custom annotation table, wherein the custom annotation table includes at least one of the level of the application program interface, the description message of the application program interface, and the name of the application program interface. The monitoring and limiting method as described in claim 10, wherein the step of adjusting the limiting configuration table according to the resource data and the application program interface request process through the data analysis module includes: Acquiring a coefficient time period having the limiting coefficient according to the limiting configuration table through the data analysis module; scanning the resource data through the data analysis module to obtain a time period to be adjusted in which the resource data in the coefficient time period is lower than the resource data threshold; and subtracting 1 from the limiting coefficient of the time period to be adjusted through the data analysis module as a new limiting coefficient. The monitoring and current limiting method as described in claim 10, wherein the current limiting configuration table includes a current current limiting coefficient and a resource data threshold, wherein the step of adjusting the current limiting configuration table according to the resource data and the application program interface request process through the data analysis module further includes: scanning the resource data in the storage device through the data analysis module to obtain the monitoring time of the resource data exceeding the resource data threshold segment; judging whether a current limiting coefficient is set in the monitoring time segment through the data analysis module, in response to the current limiting coefficient not being set in the monitoring time segment, setting the current limiting coefficient of the monitoring time segment to 1 through the data analysis module; and in response to the current limiting coefficient being set in the monitoring time segment, adding 1 to the current limiting coefficient of the monitoring time segment through the data analysis module as a new current limiting coefficient. The monitoring and current limiting method as described in claim 15, wherein the step of adjusting the current limiting configuration table according to the resource data and the application program interface request process through the data analysis module further includes: When the current limiting coefficient of the monitoring time period reaches the coefficient threshold, the message of the monitoring time period and the preset warning message are output through the data analysis module. The monitoring and current limiting method as described in claim 15, wherein the step of adjusting the current limiting configuration table according to the resource data and the API request history by the data analysis module further includes: judging whether the request data is the current limiting request according to the current limiting configuration table and the API request history by the current limiting interception module, wherein the current limiting request is a service request in which the request data matches the monitoring time period, and the execution times of the current API level in the monitoring time period reaches the corresponding execution upper limit of the API level. The monitoring and current limiting method as described in claim 15 further includes: executing an asynchronous interception module through the processor so that the asynchronous interception module intercepts the request data, and then storing the message of the request data in the storage device, wherein the asynchronous interception module stores the application program interface related to the request data, the number of executions of the application program interface, and the time period in the request log table in an asynchronous manner, wherein the maximum value of the current limiting coefficient is 5, and the storage device stores the request log table.

Images