Method for monitoring interface access data anomaly, computer device, computer readable storage medium

Abstract

The application provides a method for monitoring interface access data exception, which comprises the following steps: obtaining interface access data, wherein the interface access data comprises interface access amount and interface access success rate; judging whether the interface access amount meets a preset interface access amount exception rule; if the interface access data meets the preset interface access amount exception rule, giving a warning to inform staff and judging whether the access success rate meets a preset interface access success rate exception rule; and if the access success rate meets the preset interface access success rate exception rule, giving a warning to inform staff. The application improves work efficiency.

Description

Technical Field

[0001] This invention relates to the field of financial technology, and in particular to a method for monitoring abnormal data access through an interface, a computer-readable storage medium, and a computer device. Background Technology

[0002] As the company's business continues to grow, the complexity of its business systems is also gradually increasing. Differences in physical configurations across different environments, variations in business system design, and the diversity of business product designs at various stages of the business process can all directly or indirectly generate unpredictable risks in the production environment. IT operations personnel, architects, developers, product designers, and testers may only be aware of the risks in their respective areas of responsibility, but it's almost impossible for them to have 100% awareness of all system risks. Even if they did, it's impossible to tolerate all risky aspects. The solution to these problems often involves using monitoring and alerting systems to monitor various resources at different stages from different dimensions. However, how to provide early warnings of problems in critical stages, improve the timeliness of problem investigation and handling by anticipating potential issues, and prepare contingency plans before problems arise, while also having sufficient time to coordinate relevant personnel to analyze and resolve the issues, makes the design of an effective business monitoring set particularly important, directly impacting the effectiveness of monitoring. Summary of the Invention

[0003] In view of this, it is necessary to provide a method, computer storage medium, and computer equipment for monitoring interface accessing abnormal data that can improve work efficiency.

[0004] Firstly, this application provides a method for monitoring abnormal interface access data. The method includes: acquiring interface access data, which includes interface access volume and interface access success rate; determining whether the interface access volume meets a preset rule for abnormal interface access volume; if the interface access data meets the preset rule for abnormal interface access volume, issuing an alert to inform staff; and determining whether the access success rate meets a preset rule for abnormal interface access success rate; if the access success rate meets the preset rule for abnormal interface access success rate, issuing an alert to inform staff.

[0005] Secondly, this application provides a computer device for monitoring interface access data anomalies, the computer device including a memory and a processor. The memory stores computer program instructions. The processor executes the computer program instructions to implement the method for monitoring interface access data anomalies.

[0006] Thirdly, this application provides a computer-readable storage medium for storing program instructions that can be executed by a processor to implement a method for handling abnormal data access by the monitoring interface.

[0007] In this application, abnormal rules for interface access data are pre-set in the monitoring system, including abnormal rules for interface access volume, abnormal rules for interface access success rate, and abnormal rules for interface latency. These rules are used to promptly and effectively detect abnormal transaction scenarios. After a large number of abnormal alarms are triggered, the authenticity and urgency of the business anomaly are determined by comparing historical failure rate data, which in turn drives the optimization rules for anomaly handling in the business system. The abnormal rules for interface latency monitor the performance of business interfaces, allowing for timely upgrades to server resources based on interface latency. In high-concurrency scenarios, monitoring data reflects the server's processing capacity and the business system's load capacity, providing quantifiable data references for business logic optimization. During actual operation, when abnormal interface access volume matches the preset abnormal rules, an alert is triggered, prompting staff to take action. This effectively monitors and alerts on abnormal situations in the business system, providing effective data support for the optimization and governance of the business system. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0009] Figure 1 This is a schematic diagram of the architecture of a system for monitoring interface access data that is abnormal, as provided in an embodiment of this application.

[0010] Figure 2 This is a flowchart illustrating a method for monitoring an interface accessing data that is abnormal, as provided in an embodiment of this application.

[0011] Figure 3 This is a schematic diagram of a sub-process of step S102 provided in an embodiment of this application.

[0012] Figure 4 This is a schematic diagram of a sub-process of step S103 provided in the embodiments of this application.

[0013] Figure 5 This is a schematic diagram of the internal structure of a server that experiences abnormal access to monitoring interface data, as provided in an embodiment of this application. Detailed Implementation

[0014] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0015] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data are interchangeable where appropriate; in other words, the described embodiments are implemented according to an order other than that illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, may also include other content; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] It should be noted that the use of terms such as "first" and "second" in this application is for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" and "second" may explicitly or implicitly include one or more of that feature. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0017] This application provides a method for monitoring interface access data anomalies, the method being executed as follows: Figure 1The system shown is experiencing abnormal access data via its monitoring interface. This system can be a monitoring platform such as Detector, CAT, Cacti, Nagios, Zabbix, or Promethenus, and different types of monitoring platforms can be selected based on actual business needs. The system consists of an application client 1 and a server client 2. Application client 1 displays the page and receives user actions on the page, requesting the corresponding interface path on server client 2 for the actions. Server client 2 responds to the request, processes the data, and returns the result to the page. Application client 1 and server client 2 communicate via network 3. The server can be a standalone server or a server cluster consisting of multiple servers. Application client 1 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices.

[0018] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating a method for monitoring an interface access data anomaly according to an embodiment of this application. It includes steps S101-S107.

[0019] Step S101: Obtain interface access data, which includes interface access volume and interface access success rate.

[0020] When a user interacts with a page on application 1, such as clicking an icon, the front-end retrieves the corresponding back-end API path for data processing and requests the back-end to process the data. For example, during a Double Eleven shopping festival on an e-commerce platform, there will be a large number of API requests. When the back-end successfully processes an access request, it is recorded as an successful API access. The success rate is calculated by dividing the number of successful requests by the total number of access requests.

[0021] Step S102: Determine whether the preset rule for abnormal interface access volume is met based on the interface access volume.

[0022] When interface access volume shows abnormal increases or decreases, business personnel need to take timely action to avoid business anomalies. The preset interface access volume anomaly rules are pre-set alarm triggering rules. By comparing interface call volume year-on-year or month-on-month, alarm notifications are issued for abnormal increases or decreases, allowing for timely monitoring of business operations. By comparing statistical data, the business growth rate can be predicted in advance. When the interface access volume is abnormal and meets the preset interface access volume anomaly rules, an early warning will be issued to notify staff to handle the situation, promptly expanding application resources and providing data support for business planning.

[0023] Step S103: If the interface access volume is determined to meet the preset interface access volume abnormality rule, an early warning is issued to inform the staff, and the access success rate is used to determine whether the preset interface access success rate abnormality rule is met.

[0024] The preset interface access success rate anomaly rule is a pre-set alarm triggering rule. When the interface access volume is abnormal and meets the preset access volume anomaly rule, it is a scenario where transaction anomaly is discovered. After a large number of anomaly alarm notifications occur, the authenticity and urgency of the business anomaly are judged by comparing the historical failure rate data, and at the same time, the business system is pushed to optimize the anomaly handling rules.

[0025] Step S104: If the access success rate meets the preset interface access success rate abnormality rules, an early warning will be issued to notify the staff.

[0026] When an interface is found to be malfunctioning and meets the rules for abnormal interface access success rate, an alarm is triggered to notify staff so that they can promptly address any business anomalies.

[0027] Please refer to Figure 3 This is a schematic diagram of a sub-process of step S102 provided in the embodiments of this application, including steps S1021-S1025.

[0028] Step S1021: Based on the interface access volume, determine whether the interface access volume in the same preset time period last week is greater than a preset first value and the interface access volume in the same preset time period this week is lower than a preset second value, and the interface access success rate in the same time period this week is lower than a preset third value.

[0029] The preset time is the monitoring time interval, which can be adjusted according to the importance of the business, such as 1 minute, 1 hour, or 2 hours; the preset first value is the number of interface access requests within the monitoring interval, for example, the request volume threshold for one hour is the total daily access volume QPS / 24 of the business system; the preset second value is the preset first value multiplied by 30%; the preset third value is fixed at 50% and can be adjusted downward according to the importance of the business.

[0030] For example, last week during the same period, there were over 100 visits per hour, but currently there are fewer than 30 visits and the success rate is less than 50%.

[0031] Step S1022: If not satisfied, determine whether the interface access volume within the preset hourly interval exceeds the first access volume of the preset hourly interval based on the interface access volume, but the interface access volume within the current hourly time period does not exceed the second access volume of the preset hourly time period, and the interface access success rate is lower than the first success value of the preset hourly time period, and the access volume of the current hour is less than the third access volume.

[0032] The preset hourly interval is the monitoring time interval, which can be adjusted according to the importance of the business, such as 1 minute, 1 hour, or 2 hours; the first access volume is the number of interface access requests within the monitoring interval. For example, the request volume threshold for a time period is a multiple of the total daily access volume (QPS) of the business system / 24; the second access volume is the preset first value multiplied by 30%; the first success value is fixed at 50% and can be adjusted downwards according to the importance of the business. The third access volume is ten times the request volume of the aforementioned time period.

[0033] For example, if there were more than 10 visits in the first 3 hours but less than 3 visits currently, with a success rate of less than 50%, and less than 100 visits in the current hour.

[0034] Step S1023: If not satisfied, determine whether the first interface access volume within a preset long time period is greater than the first access value within a preset long time period, and whether the first interface access volume within the same preset long time period last week is reduced by a preset reduction value, based on the interface access volume.

[0035] The preset first access value is seven times the daily interface access volume of the business system, and the preset value is adjusted according to the importance of the business.

[0036] For example, the number of requests decreased by 80% compared to the same period last week, while the number of requests in the same period was greater than that of the previous week.

[0037] Step S1024: If not satisfied, determine whether the second interface access volume within a preset long time period is greater than the second access value within a preset long time period, and whether the second interface access volume within the same preset long time period last week has increased by a preset increase value, based on the interface access volume.

[0038] The preset growth value is adjusted according to the business, and the preset second access value for a certain time period is a multiple of the total access volume.

[0039] For example, the number of visits increased by 500% compared to the previous week and exceeded 100,000.

[0040] Step S1025: If not satisfied, obtain transaction volume data and determine whether the transaction volume data value is always zero within a preset transaction time and the access volume at the same time within the previous preset number of days exceeds the preset access volume based on the interface access volume.

[0041] The preset transaction time, preset number of days, and preset number of visits are all adjusted according to the importance of the business. The preset transaction time, the preset number of days, and the preset number of visits all decrease as the business becomes more important.

[0042] For example, the trading volume dropped to zero for 3 consecutive hours and the number of visits during the same period in the past 7 days exceeded 5.

[0043] Please refer to Figure 5 This is a schematic diagram of a sub-process of step S103 provided in the embodiments of this application, including steps S1031-S1033.

[0044] Step S1031: Based on the access success rate, determine whether the interface access success rate is lower than the preset access success rate value within a preset period of time, and the interface access volume is greater than the preset first access value.

[0045] The preset time period is adjusted according to the importance of the business, and can be one minute, one hour, two hours, etc.; the preset access success rate value is adjusted downward according to the importance of the business; the preset first access value is the number of interface access requests within the monitoring interval. For example, the request volume threshold for one hour is the total daily access volume QPS of the business system / 24.

[0046] For example, the success rate is less than 30% within 1 minute and the number of requests is greater than 500.

[0047] Step S1032: If not satisfied, determine whether the access success rate value at the same time this week is lower than the access success rate value at the same time last week by a preset first decrease value, and the access success rate at the same time this week is greater than a preset first probability value, and the number of requests in the current hour is greater than a preset second access value.

[0048] The first decrease value is adjusted downwards based on the importance of the business and should be less than 50%; the first probability value is adjusted upwards based on the importance of the business and should be greater than 50%; the second access value is preset by staff.

[0049] For example, the success rate has decreased by 40% compared to last week, while the original success rate was greater than 50%, and the current number of requests is greater than 100.

[0050] Step S1033: If not satisfied, determine whether the access success rate is lower than the access success rate value of the previous hour by a preset second decrease value, and whether the current success rate is greater than the preset second probability value, and whether the number of requests in the current hour is greater than the preset third access value.

[0051] The preset second decrease value is adjusted upwards based on the importance of the business and should be less than 50%; the preset second probability value is adjusted upwards based on the importance of the business and should be greater than 50%; the second access value is preset by staff.

[0052] For example, the success rate decreased by 40% compared to the previous hour, while the original success rate was greater than 50% and the current number of requests was greater than 100.

[0053] In real-world scenarios, interface performance can be time-consuming. By monitoring the performance time of interfaces using these rules and metrics, the performance of business interfaces can be monitored, and server resources can be upgraded in a timely manner based on the interface's latency. In high-concurrency scenarios, monitoring data can reflect the server's processing capacity and the load capacity of the business system, providing quantifiable data references for business logic optimization.

[0054] Based on the interface time consumption data, determine whether the interface access volume of the interface with interface time consumption data greater than the preset interface time consumption value is greater than the preset fourth access value within the preset first interface time consumption time.

[0055] The preset first interface timeout is adjusted according to the importance of the business, such as one minute or one hour; the preset interface timeout value is the maximum tolerable timeout designed for a single interface of the business system.

[0056] For example, the number of API requests that took more than 4900 milliseconds within 1 minute is greater than 30.

[0057] Based on the interface time consumption data, determine whether the following conditions are met: within the preset second interface time consumption time, the proportion of interface accesses with interface time consumption data greater than the preset interface time consumption data is greater than the preset ratio, and the total number of interface accesses is greater than the preset fifth access value.

[0058] The preset ratio is adjusted downwards based on the importance of the interface.

[0059] For example, the proportion of API requests taking more than 4900 milliseconds within 1 minute is greater than 30%, and the minimum number of requests is greater than 30.

[0060] Based on the time consumption data, determine whether the following conditions are met: within the preset third interface time consumption time, the interface time consumption time has increased by a preset probability compared to the previous year, and the time consumption time is greater than the preset time consumption value, and the interface access volume is greater than the preset sixth access value.

[0061] The higher the importance of the business interface, the lower the preset time consumption probability.

[0062] For example, the time taken within 1 minute increases by 500% compared to the previous period, the time taken is greater than 2000ms, and the number of requests is greater than 30.

[0063] Based on the time consumption data, determine whether the average time consumption of the interface access volume is greater than the preset average time consumption within the preset third interface time consumption period, and whether the interface access volume is greater than the preset sixth access value.

[0064] The preset average processing time is the number of services that the system can process per second multiplied by 100.

[0065] For example, the average request time exceeds 3 seconds and the number of requests is greater than 100.

[0066] Please check Figure 5 This is a schematic diagram of the internal structure of a server that monitors abnormal access data via a monitoring interface, as provided in an embodiment of this application. The server 200, used for control, includes a processor 201 and a memory 202. The processor 201 executes an executable program to implement the method for monitoring abnormal access data via a monitoring interface as provided in the above embodiment, and the memory 202 stores the computer-executable program and the system for monitoring abnormal access data via a monitoring interface as provided in the above embodiment.

[0067] In some embodiments, the processor 201 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip, used to run a computer-executable program stored in the memory 202. Specifically, the processor 201 executes the executable program to implement the method provided in the above embodiments for monitoring interface access data anomalies.

[0068] The memory 202 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 202 can be an internal storage unit of the computer device 200, such as the hard disk of the computer device 200. In other embodiments, the memory 202 can also be an external storage device of the computer device 200, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 200. Furthermore, the memory 202 can include both internal storage units and external storage devices of the computer device 200. The memory 202 can be used not only to store application software and various types of data installed on the computer device 200, such as code implementing methods for monitoring interface access data anomalies, but also to temporarily store data that has been output or will be output, and system modules that are monitoring interface access data anomalies.

[0069] Computer device 200 also includes bus 203. Bus 203 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation,

[0070] Figure 5 The bus is represented by only one thick line, but this does not indicate that there is only one bus or one type of bus. Furthermore, the computer device 200 may also include a display component 204. The display component 204 may be an LED display, a liquid crystal display, a touch-screen liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen, etc. The display component 204 may also be appropriately referred to as a display device or display unit, used to display information processed in the computer device 200 and to display a visual user interface.

[0071] Furthermore, the computer device 200 may also include a communication component 205. The communication component 205 may optionally include a wired communication component and / or a wireless communication component (such as a Wi-Fi communication component, a Bluetooth communication component, etc.), which is typically used to establish a communication connection between the computer device 200 and other computer devices.

[0072] Figure 5 Only a computer device 200 with partial components and a method for implementing monitoring interface access to data anomalies is shown. Those skilled in the art will understand that... Figure 5 The structure shown does not constitute a limitation on the computer device 200, and may include fewer or more components than shown, or combine certain components, or have different component arrangements.

[0073] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0074] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to embodiments of the present invention is generated. The computer device may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0075] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0076] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units through some interfaces, and may be electrical, mechanical, or other forms.

[0077] The unit described as a separate component may or may not be physically separate. The component shown as a unit may or may not be a physical unit; that is, it may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0078] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0079] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard disks, read-only storage media (ROM), random access storage media (RAM), magnetic disks, or optical disks.

[0080] It should be noted that the sequence numbers of the above embodiments of the present invention are merely for descriptive purposes and do not represent the superiority or inferiority of the embodiments. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, apparatus, article, or method. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, apparatus, article, or method that includes that element.

[0081] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method for monitoring interface access data anomalies, characterized in that, The method includes: Obtain interface access data, which includes interface access volume and interface access success rate; The system determines whether the interface access volume meets the preset rules for abnormal interface access volume. These rules include: determining whether the interface access volume within the same preset time period last week is greater than a preset first value, and the interface access volume within the same preset time period this week is lower than a preset second value, and the interface access success rate within the same time period this week is lower than a preset third value; if not, it determines whether the interface access volume within a preset hourly interval exceeds the first access volume of that preset hourly interval, but the interface access volume within the current hourly time period does not exceed the second access volume of that preset hourly time period, and the interface access success rate is lower than the first success value of that preset hourly time period, and the access volume in the current hour is less than the third access volume; if not, it determines whether the first interface access volume within a preset long time period is greater than the first access value of that preset long time period, and is reduced by a preset reduction value compared to the first interface access volume within the same preset long time period last week. If the interface access volume is determined to meet the preset interface access volume anomaly rule, an early warning is issued to inform staff. The access success rate is then used to determine whether the preset interface access success rate anomaly rule is met. This determination includes: whether the interface access success rate is lower than a preset access success rate value within a preset period, and whether the interface access volume is greater than a preset first access value; if not, whether the access success rate at the same time this week is lower than the access success rate at the same time last week by a preset first decrease value, and whether the access success rate at the same time this week is greater than a preset first probability value, and whether the number of requests in the current hour is greater than a preset second access value; if not, whether the access success rate is lower than the access success rate of the previous hour by a preset second decrease value, and whether the current success rate is greater than a preset second probability value, and whether the number of requests in the current hour is greater than a preset third access value. If the access success rate meets the preset interface access success rate abnormality rules, an early warning will be issued to notify the staff.

2. The method for handling abnormal data access through a monitoring interface as described in claim 1, characterized in that, The interface access data also includes interface time consumption data, and the method further includes: Based on the interface time consumption data, determine whether the preset rules for abnormal interface time consumption are met; If the interface time consumption data is used to determine whether the preset rule for abnormal interface time consumption is met, an early warning will be issued to notify the staff.

3. The method for handling abnormal data access at the monitoring interface as described in claim 1, characterized in that, The rule for determining whether the interface access volume meets the preset abnormal interface access volume criteria based on the interface access volume also includes: If not satisfied, determine whether the second interface access volume within a preset long time period is greater than the second access value within a preset long time period, and whether the second interface access volume within the same preset long time period last week has increased by a preset increase value, based on the interface access volume. If not satisfied, obtain transaction volume data and determine whether the transaction volume data value is always zero within a preset transaction time and the number of visits at the same time within the previous preset number of days exceeds the preset number of visits.

4. The method for handling abnormal data access at the monitoring interface as described in claim 2, characterized in that, The rules for determining whether the interface timeout is met based on the interface timeout data include: Based on the interface time consumption data, determine whether the interface access volume of the interface with interface time consumption data greater than the preset interface time consumption value is greater than the preset fourth access value within the preset first interface time consumption time. Based on the interface time consumption data, determine whether the following conditions are met: within the preset second interface time consumption time, the proportion of interface accesses with interface time consumption data greater than the preset interface time consumption data is greater than the preset ratio, and the total number of interface accesses is greater than the preset fifth access value.

5. The method for handling abnormal data access at the monitoring interface as described in claim 4, characterized in that, The rule for determining whether the interface timeout is met based on the interface timeout data also includes: Based on the time consumption data, determine whether the following conditions are met: within the preset third interface time consumption time, the interface time consumption time has increased by a preset probability compared to the previous year, and the time consumption time is greater than the preset time consumption value, and the interface access volume is greater than the preset sixth access value. Based on the time consumption data, determine whether the average time consumption of the interface access volume is greater than the preset average time consumption within the preset third interface time consumption period, and whether the interface access volume is greater than the preset sixth access value.

6. The method for handling abnormal data access at the monitoring interface as described in claim 4, characterized in that, The preset timeout for the first interface can be adjusted according to the importance of the service corresponding to the interface.

7. A computer device that monitors an abnormality in accessing data via its interface, characterized in that, The computer device includes: Memory is used to store computer program instructions; A processor for executing the computer program instructions to implement the method for monitoring interface access data anomalies as described in any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store program instructions that can be executed by a processor to implement the method for monitoring interface access data anomalies as described in any one of claims 1 to 6.

Images