Data interaction monitoring method and device, electronic equipment and storage medium

Abstract

The invention discloses a data interaction monitoring method and device, electronic equipment and a storage medium. Comprising the steps of determining interface information and to-be-interacted field information based on a to-be-sent service request, and determining at least one target monitoring field and a first monitoring rule corresponding to each target monitoring field based on an interface name and the to-be-interacted field information under the condition that an interface meets a preset monitoring condition; verifying the corresponding target monitoring field based on the first monitoring rule of each target monitoring field, and determining a first verification result of each target monitoring field; and when the first verification result of each target monitoring field satisfies the preset verification condition, sending the to-be-sent service request to a target receiving system, and receiving a request processing result returned by the target receiving system. According to the scheme, the interface needing to be monitored is screened through the preset condition, targeted verification of each field is achieved, request failures caused by field errors can be effectively reduced, and the service request sending reliability is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular, to a method, device, electronic device, and storage medium for monitoring data interaction. Background Art

[0002] With the development of application systems, the scope of business support has been expanding day by day, the system service functions have become increasingly diversified, and at the same time, with the increasing demand for data interaction with external systems, factors such as frequent data interaction between systems, increasing data volume, and expanding data scope, the quality of data interaction between systems has become increasingly important. Once a problem occurs in data interaction, it will affect the business operations of upstream and downstream systems simultaneously.

[0003] During the actual operation of the system, problems such as data problems, timeout problems, and connection exception problems often occur in the interaction between systems, which affect the normal business operations of upstream and downstream. The prior art cannot strictly control the quality of data interaction, the speed of data interaction, and the requirements of timeliness and effectiveness between systems, and there is a problem with poor interaction between systems. Summary of the Invention

[0004] The present invention provides a method, device, electronic device, and storage medium for monitoring data interaction to solve the problem of poor interaction quality between systems.

[0005] According to one aspect of the present invention, a method for monitoring data interaction is provided, including:

[0006] Obtain a service request to be sent, and determine interface information and fields information to be interacted based on the service request to be sent; wherein, the interface information includes an interface name;

[0007] Determine whether the corresponding interface meets a preset monitoring condition based on the interface name. When the interface meets the preset monitoring condition, determine at least one target monitoring field and the first monitoring rule corresponding to each target monitoring field based on the interface name and the fields information to be interacted;

[0008] For any target monitoring field, verify the corresponding target monitoring field based on the first monitoring rule of the target monitoring field to determine the first verification result of each target monitoring field;

[0009] When the first verification results of all target monitoring fields meet the preset verification condition, send the service request to be sent to the target receiving system and receive the request processing result returned by the target receiving system.

[0010] Optionally, determining whether the corresponding interface meets the preset monitoring conditions based on the interface name includes: obtaining the corresponding interface basic configuration information according to the interface name, where the interface basic configuration information at least includes interface validity information and monitoring status; determining that the interface meets the preset monitoring conditions when the validity information is a valid identifier and the monitoring status is an enabled state; determining that the interface does not meet the preset monitoring conditions when the validity information is an invalid identifier or the monitoring status is a closed state.

[0011] Optionally, the information of the fields to be interacted includes at least one interaction field; determining at least one target monitoring field and the first monitoring rule corresponding to each target monitoring field based on the interface name and the information of the fields to be interacted includes: obtaining the corresponding interface field configuration information according to the interface name, where the interface field configuration information at least includes source fields, source field monitoring status, and the first monitoring rule configuration information corresponding to the source fields; obtaining the source fields with the source field monitoring status being an enabled state from the interface field configuration information, and forming a candidate monitoring field set from the obtained source fields; for each interaction field, matching the interaction field with the candidate monitoring field set to obtain a matching result; in the case where the matching result is a successful match, determining the interaction field with a successful match as a target monitoring field, and determining the monitoring rule in the first monitoring rule configuration information corresponding to the interaction field with a successful match as the first monitoring rule of the corresponding target monitoring field.

[0012] Optionally, the interface field configuration information further includes second monitoring rule configuration information; after determining the interaction field with a successful match as a target monitoring field, the method further includes: determining the monitoring rule in the second monitoring rule configuration information corresponding to the interaction field with a successful match as the second monitoring rule of the corresponding target monitoring field.

[0013] Optionally, after receiving the request processing result returned by the target receiving system, the method further includes: verifying the corresponding target monitoring field based on the second monitoring rule of the target monitoring field to determine the second verification result of each target monitoring field.

[0014] Optionally, the method further includes: interrupting the sending of the service request to be sent and generating first exception information based on the first verification result when the first verification result does not meet the preset verification result; generating second exception information based on the second verification result when the second verification result does not meet the preset verification result; reminding the target user through a preset exception reminder method based on the first exception information or the second exception information.

[0015] Optionally, after receiving the request processing result returned by the target receiving system, the method further includes: obtaining the first receiving time of the service request to be sent, and obtaining the second receiving time of the request processing result, calculating the absolute value of the difference between the first receiving time and the second receiving time; in the case where the absolute value of the difference is greater than a preset time difference threshold, generating a corresponding third exception message based on the absolute value of the difference, and reminding the target user through a preset exception reminder method based on the third exception message.

[0016] According to another aspect of the present invention, there is provided a data interaction monitoring device, including:

[0017] An information acquisition module, configured to acquire a service request to be sent, and determine interface information and fields to be interacted based on the service request to be sent; wherein, the interface information includes an interface name;

[0018] A monitoring field and monitoring rule determination module, configured to determine whether a corresponding interface meets a preset monitoring condition based on the interface name, and in the case where the interface meets the preset monitoring condition, determine at least one target monitoring field and a first monitoring rule corresponding to each target monitoring field based on the interface name and the fields to be interacted;

[0019] A verification result determination module, configured to verify each target monitoring field based on the first monitoring rule of the target monitoring field, and determine a first verification result of each target monitoring field;

[0020] A request sending module, configured to send the service request to be sent to the target receiving system and receive the request processing result returned by the target receiving system in the case where the first verification results of all target monitoring fields meet the preset verification conditions.

[0021] According to another aspect of the present invention, there is provided an electronic device, the electronic device includes:

[0022] At least one processor; and

[0023] A memory communicatively connected to the at least one processor; wherein,

[0024] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the data interaction monitoring method of any embodiment of the present invention.

[0025] According to another aspect of the present invention, there is provided a computer-readable storage medium, the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the data interaction monitoring method of any embodiment of the present invention when executed.

[0026] In the technical solution of the embodiment of the present invention, by obtaining a service request to be sent, interface information and information of fields to be interacted are determined based on the service request to be sent; wherein, the interface information includes an interface name; it is determined whether the corresponding interface meets a preset monitoring condition based on the interface name, and in the case that the interface meets the preset monitoring condition, at least one target monitoring field and a first monitoring rule corresponding to each target monitoring field are determined based on the interface name and the information of fields to be interacted; by screening and monitoring the interface corresponding to the service request to be sent and the field parameters in the interface, the interface that meets the preset monitoring condition is screened out, avoiding indiscriminate monitoring of all interfaces, improving the monitoring efficiency, accurately positioning the target monitoring field in combination with the interface name and the information of fields to be interacted and matching the first monitoring rule, realizing the targeted monitoring plan for key fields, and providing a clear basis for subsequent field verification; for any target monitoring field, the corresponding target monitoring field is verified based on the first monitoring rule of the target monitoring field to determine the first verification result of each target monitoring field; in the case that the first verification results of all target monitoring fields meet the preset verification condition, the service request to be sent is sent to the target receiving system, and the request processing result returned by the target receiving system is received, realizing the verification of the target monitoring field according to the rule, ensuring the compliance of the field, reducing the request failure; only sending the request after the verification passes, reducing the risk of system interaction anomalies, ensuring the stability of data interaction; and dynamically intercepting non-compliant requests, reducing resource waste, and optimizing the efficiency and reliability of the business process. This solution determines the interface and field information by obtaining the service request, screens out the interfaces to be monitored according to the interface name, avoids ineffective monitoring, and at the same time clarifies the target monitoring field and rules, providing a basis for verification; then verifies the field according to the rule, intercepts the field anomaly problem, reduces the request failure; finally sends the request after the field verification passes, solves the problem of poor interaction quality between systems, ensures the accuracy of data interaction, reduces the anomaly risk, and improves the efficiency of the business process and the stability of data transmission between systems.

[0027] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present invention, nor is it used to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention, and those of ordinary skill in the art can obtain other drawings without creative efforts based on these drawings.

[0029] Figure 1 is a flowchart of a data interaction monitoring method provided in Embodiment 1 of the present invention;

[0030] Figure 2 It is a flowchart of a data interaction monitoring method provided in the second embodiment of the present invention;

[0031] Figure 3 It is a schematic flowchart of a data interaction monitoring applicable to the embodiment of the present invention;

[0032] Figure 4 It is a schematic structural diagram of a data interaction monitoring device provided in the third embodiment of the present invention;

[0033] Figure 5 It is a schematic structural diagram of an electronic device for implementing the data interaction monitoring method of the embodiment of the present invention. Detailed implementation manners

[0034] In order to enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

[0035] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present invention described herein can be implemented in an order different from those illustrated or described herein. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0036] Embodiment 1

[0037] Figure 1 It is a flowchart of a data interaction monitoring method provided in the first embodiment of the present invention. This embodiment is applicable to the situation of monitoring data interaction between systems. This method can be executed by a data interaction monitoring device, which can be implemented in the form of hardware and / or software, and the data interaction monitoring device can be configured in electronic devices such as computers, servers, and intelligent terminals. As Figure 1 shown, this method includes:

[0038] S110. Obtain the service request to be sent, and determine the interface information and the information of fields to be interacted based on the service request to be sent; wherein, the interface information includes the interface name.

[0039] Among them, the service request to be sent can be specifically understood as a set of service operation instructions generated in the service system but not yet sent to the target receiving system. The service request to be sent contains all the information required to complete a specific service function, such as the interface name and the information of fields to be interacted. The interface name is used to specify the service interface to be called, and the information of fields to be interacted includes but is not limited to specific interaction contents such as business data and parameter configuration. These information are organized into a request message according to the established protocol format to trigger the target system to execute the corresponding service processing process. Before actual sending, it needs to go through pre - processing links such as interface monitoring condition screening and field verification to ensure the compliance and effectiveness of the request and avoid service processing anomalies caused by information errors.

[0040] It should be noted that before monitoring the service request to be sent, it is necessary to pre - configure the complete interface information of the interfaces called by the service system or service module, including interface basic configuration information, interface field configuration information, and monitoring rule configuration. Specifically, the interface configuration module can be used to configure the information corresponding to the interface basic configuration information, interface field configuration information, and monitoring rule configuration respectively for subsequent direct calling. Interface basic information configuration is to configure various basic parameters for the interface, and overall control functions such as interface registration, management, and monitoring from a general perspective, including but not limited to multiple configuration items such as interface name, interface description, application scenario, whether it is invalid, whether to monitor, message type, whether to monitor response time, response time threshold, whether to send an email, and contact person, providing controllable interface basic information configuration management. Monitoring rule configuration provides selectable field verification rules for each interface, including three types: regular expression, tool - class monitoring, and numerical deviation monitoring. Interface field information configuration can manage the specific fields in each interface, including but not limited to information such as interface name, source field node name, source field node description, whether to monitor, pre - monitoring rules, and post - monitoring rules. For each field of the interface, personalized configuration can be performed. For fields configured with whether to monitor, pre - monitoring rules, and post - monitoring rules, monitoring can be performed before subsequent data interaction and at the end of the overall data interaction phase. Both pre - monitoring and post - monitoring can query the data of existing field verification rules in the current system and configure the desired monitoring rules, and support configuring multiple rules simultaneously. Among them, pre - monitoring represents the monitoring before data interaction, and post - monitoring represents the monitoring at the end of the overall data interaction phase.

[0041] Specifically, receive the business request to be sent generated by the business system or business module. By parsing the business request to be sent and extracting the interface information and the fields to be interacted with, the interface information can be the interface name, and the fields to be interacted with can be the request parameters and data fields. The request parsing process depends on the format parsing of the request protocol or extracts the target fields from the request message through preset data mapping rules to ensure the accurate identification of the interface name and the interaction fields. In the actual application process, there are often multiple business requests to be sent generated by the business system or business module. The generated business requests to be sent can be stored in the queue to be processed. When monitoring and processing, multiple business requests to be sent can be obtained from the queue to be processed and processed simultaneously. The parallel processing method can be used to process the business requests to be sent to determine the interface information and the fields to be interacted with corresponding to each business request to be sent, and perform subsequent monitoring and processing.

[0042] In this embodiment, by extracting the interface and field information from the business request to be sent, the accurate positioning of the data source is realized, providing a basic basis for subsequent interface screening and field monitoring; clarifying the interface name can quickly match the interface configuration rules, avoiding processing deviations caused by information loss. At the same time, the early identification of the fields to be interacted with can provide a clear goal for subsequent field verification planning, improving the pertinence and efficiency of business processing and reducing the interference of invalid information.

[0043] S120. Determine whether the corresponding interface meets the preset monitoring conditions based on the interface name. When the interface meets the preset monitoring conditions, determine at least one target monitoring field and the first monitoring rule corresponding to each target monitoring field based on the interface name and the fields to be interacted with.

[0044] Among them, the preset monitoring conditions specifically characterize the conditions set for determining whether an interface needs to be monitored. Exemplarily, it can be set that if the interface name exists in the preset interface monitoring set, it is determined that the interface meets the preset monitoring conditions. It can also be set that if the interface monitoring identifier corresponding to the interface is a monitorable identifier, it is determined that the interface meets the preset monitoring conditions. There is no limitation here. The first monitoring rule can be specifically understood as the monitoring rule carried out before the target monitoring field is transmitted to the target receiving system. The first monitoring rule characterizes the monitoring rule before data interaction, that is, the pre-monitoring rule, including but not limited to regular expression rules and custom verification rules. Among them, the regular expression rule: for the selected fields to be monitored, perform adaptation verification according to the configured regular expression content. For example: fixed date format, non-empty string, numerical value within a specified size range, etc.; the custom verification rule is used to monitor fields with special requirements. By writing a custom tool class method applicable to a certain field, provide personalized monitoring functions for it. The field value of the target monitoring field needs to be monitored and calculated according to the configured custom verification rule to determine whether it conforms to the rule. For example: a certain XX field in a certain XX interface needs to meet the conditions in special scenario X to conform to the verification and meet the rules, which is specifically set according to the business characteristics of the field.

[0045] Specifically, call the pre-established interface monitoring set, and by comparing the interface name with the interface monitoring set, determine whether the interface name exists in the interface monitoring set. If the interface name exists in the interface monitoring set, it is determined that the interface meets the corresponding preset monitoring conditions, indicating that the interface needs to be monitored and processed. If the interface name does not exist in the interface monitoring set, it is determined that the interface does not meet the corresponding preset monitoring conditions and there is no need to monitor and process the interface; when the interface meets the preset monitoring conditions, obtain the corresponding field monitoring rule mapping table from the interface information configuration library according to the interface name, match the fields in the table with the information of the fields to be interacted, screen out the target fields to be monitored, and associate the first monitoring rules corresponding to each field.

[0046] In this embodiment, through the precise matching of the interface name and the preset conditions, the dynamic screening of the monitoring interface is realized, meaningless monitoring is avoided, and the resource utilization rate is improved; by combining the interface configuration and the fields to be interacted to determine the monitoring target and rules, the monitoring work is made more targeted, providing a clear standard for subsequent field verification, ensuring the consistency between the monitoring rules and the actual business fields, reducing verification errors caused by rule mismatches, and at the same time improving the standardization and efficiency of the business processing process.

[0047] Optionally, determining whether the corresponding interface meets the preset monitoring conditions based on the interface name includes: obtaining the corresponding interface basic configuration information according to the interface name, where the interface basic configuration information at least includes interface validity information and monitoring status; determining that the interface meets the preset monitoring conditions when the validity information is a valid identifier and the monitoring status is an enabled state; determining that the interface does not meet the preset monitoring conditions when the validity information is an invalid identifier or the monitoring status is a closed state.

[0048] Among them, the interface basic configuration information specifically represents the general configuration information used to store the interface, including but not limited to interface validity information and monitoring status. The interface validity information includes the interface validity status, which is used to represent whether the interface is available. If the interface identifier is in a valid state, it is determined that the interface is an available interface; if the interface identifier is in an invalid state, it is determined that the interface is an unavailable interface. The monitoring status represents whether the interface needs to be monitored. If the interface monitoring status is the monitoring status / enabled state, it is determined that the interface is an interface that needs to be monitored; if the interface monitoring status is the non-monitoring status / closed state, it is determined that the interface is an interface that does not need to be monitored.

[0049] Specifically, first retrieve the corresponding interface basic configuration information from the configuration management system according to the interface name. This information includes interface validity information, such as a valid identifier or an invalid identifier, and monitoring status, such as an enabled state or a closed state; then perform a logical judgment on these two pieces of information. When the validity information is a valid identifier and the monitoring status is enabled, it is determined that the interface meets the preset monitoring conditions. When the validity information is an invalid identifier or the monitoring status is a closed state, it is determined that the interface does not meet the preset monitoring conditions. In the case where the interface is unavailable, corresponding exception information can also be generated and the user can be reminded to perform an exception query.

[0050] In this embodiment, through the dual-condition screening of interface validity and monitoring status, it is ensured that only the interfaces that are normally available and need to be monitored are processed subsequently, avoiding invalid operations on invalid interfaces or interfaces with monitoring not enabled, improving the accuracy and resource utilization rate of the monitoring process; using standardized configuration information as the judgment basis makes the determination process of interface monitoring conditions clear and controllable, facilitating system maintenance and rule adjustment, and at the same time laying a reliable foundation for subsequent field monitoring work, ensuring the standardization and efficiency of the monitoring process.

[0051] S130. For any target monitoring field, verify the corresponding target monitoring field based on the first monitoring rule of the target monitoring field, and determine the first verification result of each target monitoring field.

[0052] Specifically, for each target monitoring field, the actual value of the field is verified item by item according to each monitoring rule item in the first monitoring rule, so as to obtain the verification result of the target monitoring field relative to each monitoring rule item. Finally, the first verification result of the field is generated according to the verification result, including whether each monitoring rule passes or fails the monitoring, and the specific error reason corresponding to the monitoring failure.

[0053] In this embodiment, by precisely matching the preset rule with the actual field value, the refined verification of the field quality is realized, ensuring the accuracy and compliance of business data; the rule-driven verification method is reusable and easy to maintain. When the business rule changes, only the corresponding rule configuration needs to be updated, without modifying the verification logic, improving the flexibility of the system; at the same time, the clear verification result can provide a direct basis for the subsequent request sending decision, intercepting non-compliant fields in time, avoiding business processing failures caused by data anomalies, and ensuring the efficiency and reliability of the process.

[0054] S140. When the first verification result of each target monitoring field meets the preset verification condition, the business request to be sent is sent to the target receiving system, and the request processing result returned by the target receiving system is received.

[0055] Among them, the preset verification condition can be specifically understood as the condition set for verifying whether the target monitoring field meets the sending requirements. It can be set that when the verification results of all target monitoring fields meet the successful verification, the sending of the business request will be triggered, so as to ensure the accuracy and compliance of data interaction and avoid business processing failures caused by field anomalies.

[0056] Specifically, after obtaining the first verification results of all target monitoring fields, the first verification results of all target monitoring fields are uniformly verified to confirm that all fields meet the preset verification conditions. Subsequently, the business request to be sent is encapsulated into a standard message according to the established communication protocol (such as HTTP, TCP / IP) and transmitted to the target receiving system through the network; after receiving the request, the target system executes the corresponding processing logic and returns the processing result (such as successful response, error code, data return, etc.) along the original protocol path, and the sending system listens and receives this result in real time.

[0057] In this embodiment, with the field verification result as a precondition, it is ensured that only compliant business requests are sent to the target system, avoiding invalid requests from occupying network resources and target system processing resources, and improving the interaction efficiency; through a strict verification result screening mechanism, the accuracy and effectiveness of data interaction are guaranteed, and the risk of communication failures between systems caused by field anomalies is reduced; at the same time, the standardized request sending and result receiving processes facilitate system docking and exception problem tracking, ensuring the coherence and traceability of the business process, and providing reliable data support for subsequent business analysis and optimization.

[0058] Based on the above embodiments, after receiving the request processing result returned by the target receiving system, the method further includes: obtaining the first receiving time of the service request to be sent, and obtaining the second receiving time of the request processing result, and calculating the absolute value of the difference between the first receiving time and the second receiving time; in the case where the absolute value of the difference is greater than the preset time difference threshold, generating a corresponding third exception information based on the absolute value of the difference, and reminding the target user through a preset exception reminder method based on the third exception information.

[0059] Among them, the first receiving time specifically represents the time point when the service request to be sent enters the system sending queue or is first received by the system, and is used to mark the initial moment when the service request starts to be processed; the second receiving time specifically represents the time point when the system receives the request processing result returned by the target receiving system, and is used to record the moment when the request processing is completed and a response is obtained. The time difference between the two can reflect the time-consuming situation of the request processing. The third exception information represents the exception notification information generated by the system based on the timeout difference when the absolute value of the difference between the first receiving time and the second receiving time exceeds the preset time difference threshold, and usually includes specific time-consuming, request identifier, exception type, etc., and is used to inform the target user of the exception situation of request processing timeout through a preset reminder method, so as to timely check and solve the problem of system response delay.

[0060] Specifically, after receiving the request processing result returned by the target system, obtain the first receiving time of the service request to be sent, that is, the time when the request initially enters the sending queue, and obtain the second receiving time of the request processing result, that is, the time when the response is received, and calculate the absolute value of the difference between these two time points to determine the request processing time-consuming; then compare this time-consuming with the preset time difference threshold. If the difference exceeds the threshold, trigger an exception handling process. Exemplarily, a third exception information including time-consuming information, request identifier, etc. can be generated based on the difference, and the exception information is pushed to the target users, such as system administrators and business leaders, through a preset exception reminder method. The preset exception reminder methods include but are not limited to emails, text messages, and system pop-ups.

[0061] In this embodiment, by quantifying the request processing time-consuming and setting threshold monitoring, the system response delay problem can be discovered in real time, potential performance bottlenecks or fault hazards can be warned in time, providing data basis for system optimization; the automated exception reminder mechanism ensures that problems are quickly perceived and processed, reducing the manual monitoring cost and improving the system operation and maintenance efficiency; at the same time, the accurate time-consuming data and request context included in the exception information facilitate technicians to quickly locate the root cause of the problem, shorten the fault repair time, ensure the continuity and stability of the business process, and improve the user experience.

[0062] The technical solution of this embodiment is to obtain a service request to be sent, and determine interface information and fields to be interacted based on the service request to be sent; where the interface information includes the interface name; determine whether the corresponding interface meets the preset monitoring conditions based on the interface name, and when the interface meets the preset monitoring conditions, determine at least one target monitoring field and the first monitoring rule corresponding to each target monitoring field based on the interface name and the fields to be interacted; for any target monitoring field, verify the corresponding target monitoring field based on the first monitoring rule of the target monitoring field to determine the first verification result of each target monitoring field; when the first verification results of all target monitoring fields meet the preset verification conditions, send the service request to be sent to the target receiving system and receive the request processing result returned by the target receiving system. This solution determines the interface and field information by obtaining the service request, filters out the interfaces to be monitored according to the interface name to avoid ineffective monitoring, and at the same time clarifies the target monitoring fields and rules to provide a basis for verification; then verifies the fields according to the rules to intercept field exception problems and reduce request failures; finally, sends the request after the field verification is passed, solves the problem of poor interaction quality between systems, ensures accurate data interaction, reduces abnormal risks, and improves the efficiency of business processes and the stability of data transmission between systems.

[0063] Embodiment 2

[0064] Figure 2 It is a flowchart of a data interaction monitoring method provided by Embodiment 2 of the present invention. The method of this embodiment is a further optimization of the method of the above embodiment. Optionally, obtain the corresponding interface field configuration information based on the interface name, where the interface field configuration information at least includes the source field, the source field monitoring status, and the first monitoring rule configuration information corresponding to the source field; obtain the source fields with the source field monitoring status being the enabled state from the interface field configuration information, and form a candidate monitoring field set from the obtained source fields; for each interaction field, match the interaction field with the candidate monitoring field set to obtain a matching result; when the matching result is a successful match, determine the interaction field with the successful match as the target monitoring field, and determine the monitoring rule in the first monitoring rule configuration information corresponding to the interaction field with the successful match as the first monitoring rule of the corresponding target monitoring field.

[0065] As Figure 2 shown, the method includes:

[0066] S210. Obtain a service request to be sent, and determine interface information and fields to be interacted based on the service request to be sent; where the interface information includes the interface name, and the fields to be interacted include at least one interaction field.

[0067] S220. Determine whether the corresponding interface meets the preset monitoring conditions based on the interface name.

[0068] S230. When the interface meets the preset monitoring conditions, obtain the corresponding interface field configuration information based on the interface name, where the interface field configuration information at least includes a source field, a source field monitoring status, and first monitoring rule configuration information corresponding to the source field.

[0069] Among them, the interface field configuration information refers to structured configuration data related to interface field monitoring. When the interface meets the preset monitoring conditions, the field configuration information can be retrieved from the configuration database or configuration center through the interface name. The interface field configuration information includes, but is not limited to, a source field, a source field monitoring status, and first monitoring rule configuration information corresponding to the source field. The source field refers to the field name stored in the data source or database; the source field monitoring status is used to identify the switch status of whether the field enables monitoring; the first monitoring rule configuration information corresponding to the source field stores the monitoring rule item number. Various rules that need to be monitored during the business processing process can be customized and stored in advance, and a corresponding identifier is set for each monitoring rule item. When configuring the monitoring rule items for each field, only the corresponding number needs to be filled in. The interface field configuration information provides a standardized basis for the monitoring range screening and verification rule matching of interface fields, ensuring the standardization and maintainability of the monitoring process.

[0070] Specifically, when the interface meets the preset monitoring conditions, the system uses the interface name as an index to retrieve the corresponding interface field configuration information from the predefined configuration database or configuration center. The interface field configuration information is stored in a structured form and at least includes a source field, a source field monitoring status, and first monitoring rule configuration information corresponding to the source field.

[0071] In this embodiment, through the precise mapping of the interface name and the configuration information, the dynamic loading of the monitoring rules is realized, avoiding the cumbersome and error-prone manual configuration; the switch mechanism of the source field monitoring status can flexibly control the monitoring range, and only the fields in the enabled state are processed subsequently, improving the monitoring efficiency and reducing resource consumption; at the same time, directly associating the monitoring rules with the source fields ensures that there is a clear and standardized rule basis for subsequent field verification, making the monitoring process more standardized and maintainable, and laying a data foundation for accurately identifying the target monitoring fields.

[0072] S240. Obtain the source fields with the source field monitoring status being the enabled state from the interface field configuration information, and form a candidate monitoring field set from the obtained source fields.

[0073] Specifically, after obtaining the interface field configuration information, the system traverses the source fields and their corresponding monitoring statuses therein, filters out all the source fields with the monitoring status marked as the enabled status, and aggregates these qualified source fields to form a candidate monitoring field set. This process realizes automatic filtering through a preset status filtering logic, ensuring that the fields in the set are all target fields that need to be monitored.

[0074] In this embodiment, the accurate control of the monitoring scope is achieved through the on-off mechanism of the monitoring status, avoiding ineffective processing of fields with monitoring not enabled, and improving the efficiency of field monitoring and resource utilization; the formation of the candidate set enables a clear target range in the subsequent interactive field matching process, ensuring that the monitoring work focuses on key business fields, reducing redundant operations, and laying a foundation for the accurate positioning of target monitoring fields, making the monitoring process more targeted and operable.

[0075] S250. For each interactive field, match the interactive field with the candidate monitoring field set to obtain a matching result; in the case where the matching result is a successful match, determine the successfully matched interactive field as the target monitoring field, and determine the monitoring rule in the first monitoring rule configuration information corresponding to the successfully matched interactive field as the first monitoring rule of the corresponding target monitoring field.

[0076] Specifically, for each interactive field to be processed, the system compares the name of the interactive field to be processed with the source fields in the candidate monitoring field set to determine whether there is a matching item. When an interactive field successfully matches a certain source field in the set, the interactive field is marked as a target monitoring field, and at the same time, the first monitoring rule configuration information corresponding to the source field is extracted from the interface field configuration information, and the specific monitoring rule therein is associated with the target monitoring field.

[0077] In this embodiment, through the accurate matching of the candidate set and the interactive field, the dynamic screening of the monitoring fields is realized, ensuring that only the fields that actually need to be monitored are subjected to verification, avoiding the consumption of resources by meaningless rule matching; the automatic rule association mechanism enables the monitoring rules to correspond one by one with the business fields, ensuring the accuracy and consistency of the verification logic, and reducing manual configuration errors; at the same time, this process can flexibly adapt to the field configuration requirements of different interfaces. When the business fields change, only the candidate set or the matching rules need to be adjusted to quickly respond, improving the scalability and operation and maintenance efficiency of the system.

[0078] Optionally, the interface field configuration information further includes second monitoring rule configuration information; after determining the successfully matched interactive field as the target monitoring field, the method further includes: determining the monitoring rule in the second monitoring rule configuration information corresponding to the successfully matched interactive field as the second monitoring rule of the corresponding target monitoring field.

[0079] Among them, the second monitoring rule can be specifically understood as the monitoring rule carried out at the end stage of the overall data interaction corresponding to the business request to be sent, that is, the post-event monitoring rule, including but not limited to the numerical deviation monitoring rule. The numerical deviation monitoring rule is used to monitor the numerical field data. This monitoring type is only applicable to the post-event monitoring stage, that is, the stage after the business request to be sent is sent. The interaction fields that affect the passing rate of the business request can be placed in the post-event monitoring stage for monitoring. While ensuring that the business request can be sent to the target receiving system in a timely and effective manner, it is also possible to perform anomaly monitoring on the interaction fields. In the case of anomalies, relevant users can be reminded in a timely manner to conduct verification. By counting the records of the target monitoring field over a period of time, calculating the deviation between the current value of the target monitoring field and the standard score, and matching it with the preset deviation threshold to determine the deviation monitoring result. The preset deviation threshold includes a preset positive deviation threshold and a preset negative deviation threshold. The standard score represents the distance from a specific number to the average in terms of standard deviation, showing the relative position of the data in the data group, that is, how many standard deviations. The calculation formula is as follows:

[0080] Standard deviation calculation formula: Among them, μ is the average, x i is the current value of the target monitoring field participating in the calculation each time, and N is the total amount of data.

[0081] Standard score (Z-score) calculation formula: Among them, x is the original data of the target monitoring field, μ is the average, and δ is the standard deviation. When the Z-score exceeds the preset positive deviation threshold or the preset negative deviation threshold, a corresponding abnormal record will be generated and the business personnel will be notified in a timely manner.

[0082] Specifically, when the interface field configuration information includes the second monitoring rule configuration information, after the interaction field successfully matches the candidate monitoring field set and the target monitoring field is determined, the system extracts the second monitoring rule configuration information corresponding to the successfully matched field from the interface field configuration information, and determines the monitoring rule therein as the second monitoring rule of the target monitoring field. This process realizes the loading of multi-level verification rules for fields by presetting a dual rule system in the configuration information.

[0083] Based on the above embodiments, after receiving the request processing result returned by the target receiving system, the method further includes: verifying the corresponding target monitoring field based on the second monitoring rule of the target monitoring field to determine the second verification result of each target monitoring field.

[0084] Specifically, after receiving the request processing result returned by the target receiving system, the system re-verifies the target monitoring fields based on the determined target monitoring fields and their corresponding second monitoring rules. Specifically, it includes obtaining the second monitoring rules from the configuration information, performing rule verification on the actual value of each field, specifically verifying the deviation degree of the target monitoring fields, and then generating a second verification result, that is, obtaining whether the deviation degree of the target monitoring fields meets the deviation threshold. If the deviation degree of the target monitoring fields is higher than the deviation threshold, it is determined that the second verification result is abnormal.

[0085] In this embodiment, by introducing the second monitoring rule to complete the monitoring in the post-sending stage of the service request to be sent, for monitoring after the data interaction between systems is completed, it is applicable to scenarios where this data interaction process cannot be interfered. After a complete data interaction, real-time post-event monitoring of the data interaction is performed. If the rules do not match, a warning notice is sent, thus improving the monitoring of the service request to be sent and helping to improve the quality of data interaction between systems. At the same time, the automatic association of the rules reduces manual intervention, ensures the consistency and traceability of the verification logic, and provides a more reliable guarantee for the high-quality interaction of business data.

[0086] S260. For any target monitoring field, verify the corresponding target monitoring field based on the first monitoring rule of the target monitoring field, and determine the first verification result of each target monitoring field.

[0087] S270. When the first verification results of all target monitoring fields meet the preset verification conditions, send the service request to be sent to the target receiving system and receive the request processing result returned by the target receiving system.

[0088] Based on the above embodiments, the method further includes: when the first verification result does not meet the preset verification result, interrupt the sending of the service request to be sent, and generate a first exception message based on the first verification result; when the second verification result does not meet the preset verification result, generate a second exception message based on the second verification result; and remind the target user through a preset exception reminder method based on the first exception message or the second exception message.

[0089] Among them, the first exception message specifically represents the exception message generated before the service request to be sent is sent, and the second exception message specifically represents the exception message generated after the service request to be sent is sent.

[0090] Specifically, when the first verification result does not meet the preset conditions, the system immediately interrupts the sending process of the service request to be sent, and generates a first exception message containing error fields, failure reasons, etc. according to the specific situation of the verification failure; if the second verification result does not meet the preset conditions, a second exception message is generated based on the corresponding verification failure result. Subsequently, the system pushes the first or second exception message to the target users, such as developers and business administrators, through a preset exception reminder method.

[0091] In this embodiment, by triggering the interruption mechanism through the real-time verification result, non-compliant requests can be intercepted in a timely manner, preventing invalid data from flowing into the target system and reducing resource waste in subsequent processing links; the accurate generation of the exception message can clearly indicate the root cause of the error, facilitating technicians to quickly locate the problem; the automated exception reminder mechanism ensures that the problem is perceived in a timely manner, shortening the fault response time. At the same time, the differential processing of multi-level verification failures enables the system to cover all-dimensional exception scenarios from basic formats to complex business logics, improving the robustness of the business process and the stability of data interaction.

[0092] In a specific embodiment, an interface integrating functions such as pre-monitoring, post-monitoring, response time monitoring, email reminder, and interface information configuration management performs interactive monitoring on the message sent by the business module. By providing functions such as pre-monitoring, post-monitoring, response time monitoring, and email reminder for data interaction between systems, a complete set of intelligent monitoring and warning solutions is provided. Configuration monitoring rules are provided for the corresponding interface fields, and multi-dimensional rule maintenance is supported through interface configuration management. The specific interactive monitoring process is as follows Figure 3 shown in a schematic diagram of the data interaction monitoring process. The business module calls the interface and sends a request. When the interface receives the request, it records the reception time, that is, the start time, processes the request, and determines the target monitoring field for pre-monitoring. The target monitoring field is pre-monitored through the built-in field monitoring and processing module. Specifically, rules are obtained from the interface configuration management for monitoring the target monitoring field to determine whether the target monitoring field passes the pre-monitoring. If it fails the pre-monitoring, the sending is interrupted, and an exception record and an email notification are made. The interface configuration management can also be notified to update the configuration; if the request passes the pre-monitoring, the request is sent to the target receiving system through the interface forwarding processing module, and the processing result returned by the target receiving system is received, and the return time is recorded, and then the response time monitoring and processing are performed. Whether there is a response timeout is judged according to the return time and the start time. If there is a response timeout, an exception record and an email notification are executed; after the request is sent, post-monitoring is triggered, and the target monitoring field is post-monitored through the built-in field monitoring and processing module. If it fails the post-monitoring, an exception record and an email notification are executed. If it passes the post-monitoring, the monitoring ends.

[0093] In the technical solution of this embodiment, by obtaining the service request to be sent to clarify the interface and interaction field information, the interfaces that meet the preset monitoring conditions are screened based on the interface name, avoiding ineffective monitoring; based on the interface name, the interface field configuration information including the monitoring status of the source field is obtained, and only the source fields with the monitoring status enabled are included in the candidate set, realizing accurate screening of the monitoring scope; through the matching of the interaction field and the candidate monitoring field set, the target monitoring field is accurately located and the corresponding first monitoring rule is associated, ensuring the efficient matching of the monitoring rule and the actual interaction field; the target monitoring field is verified according to the rule, and the request is sent only after all verifications pass. The whole process from field screening, rule matching to verification and sending not only reduces the request failure caused by field anomalies, but also avoids the waste of resources caused by ineffective interactions, solves the problem of poor data interaction quality between systems, ensures the accuracy of data interaction and the stability of system - to - system transmission, and improves the execution efficiency of business processes.

[0094] Embodiment III

[0095] Figure 4 It is a schematic structural diagram of a data interaction monitoring device provided in Embodiment III of the present invention. As Figure 4 shown, the device includes:

[0096] An information acquisition module 410, configured to acquire a service request to be sent, and determine interface information and interaction field information to be interacted based on the service request to be sent; wherein, the interface information includes an interface name;

[0097] A monitoring field and monitoring rule determination module 420, configured to determine whether the corresponding interface meets the preset monitoring conditions based on the interface name, and when the interface meets the preset monitoring conditions, determine at least one target monitoring field and the first monitoring rule corresponding to each target monitoring field based on the interface name and the interaction field information to be interacted;

[0098] A verification result determination module 430, configured to, for any target monitoring field, verify the corresponding target monitoring field based on the first monitoring rule of the target monitoring field, and determine the first verification result of each target monitoring field;

[0099] A request sending module 440, configured to, when the first verification results of all target monitoring fields meet the preset verification conditions, send the service request to be sent to the target receiving system, and receive the request processing result returned by the target receiving system.

[0100] In the technical solution of this embodiment, a service request to be sent is obtained through an information acquisition module, and interface information and fields to be interacted information are determined based on the service request to be sent; wherein, the interface information includes an interface name; a monitoring field and monitoring rule determination module determines whether a corresponding interface meets a preset monitoring condition based on the interface name, and when the interface meets the preset monitoring condition, at least one target monitoring field and a first monitoring rule corresponding to each target monitoring field are determined based on the interface name and the fields to be interacted information; a verification result determination module verifies a corresponding target monitoring field based on the first monitoring rule of the target monitoring field for any target monitoring field, and determines a first verification result of each target monitoring field; a request sending module sends the service request to be sent to a target receiving system when the first verification results of all target monitoring fields meet a preset verification condition, and receives a request processing result returned by the target receiving system. This solution determines the interface and field information by obtaining the service request, filters out the interfaces to be monitored according to the interface name, avoids ineffective monitoring, and at the same time clarifies the target monitoring fields and rules to provide a basis for verification; then verifies the fields according to the rules, intercepts field anomaly problems, reduces request failures; finally, sends the request after the field verification passes, solves the problem of poor interaction quality between systems, ensures accurate data interaction, reduces anomaly risks, and improves the efficiency of business processes and the stability of data transmission between systems.

[0101] Based on the above embodiment, optionally, the monitoring field and monitoring rule determination module 420 is specifically configured to obtain corresponding interface basic configuration information according to the interface name, where the interface basic configuration information at least includes interface validity information and a monitoring status; when the validity information is a valid identifier and the monitoring status is an enabled state, it is determined that the interface meets the preset monitoring condition; when the validity information is an invalid identifier or the monitoring status is a closed state, it is determined that the interface does not meet the preset monitoring condition.

[0102] Optionally, the information of the fields to be interacted includes at least one interaction field; the monitoring field and monitoring rule determination module 420 includes an interface field configuration information configuration unit, a candidate monitoring field set determination unit, and a monitoring field and monitoring rule determination module unit; the interface field configuration information configuration unit is used to obtain the corresponding interface field configuration information based on the interface name, where the interface field configuration information at least includes a source field, a monitoring status of the source field, and first monitoring rule configuration information corresponding to the source field; the candidate monitoring field set determination unit is used to obtain the source fields with the monitoring status of the source field being the enabled status from the interface field configuration information, and form a candidate monitoring field set from the obtained source fields; the monitoring rule determination module unit is used to match each interaction field with the candidate monitoring field set to obtain a matching result; in the case where the matching result is a successful match, determine the interaction field with the successful match as the target monitoring field, and determine the monitoring rule in the first monitoring rule configuration information corresponding to the interaction field with the successful match as the first monitoring rule of the corresponding target monitoring field.

[0103] Optionally, the interface field configuration information further includes second monitoring rule configuration information; after determining the interaction field with the successful match as the target monitoring field, the monitoring field and monitoring rule determination module 320 is further specifically used to determine the monitoring rule in the second monitoring rule configuration information corresponding to the interaction field with the successful match as the second monitoring rule of the corresponding target monitoring field.

[0104] Optionally, after receiving the request processing result returned by the target receiving system, the monitoring field and monitoring rule determination module 420 is further specifically used to verify the corresponding target monitoring field based on the second monitoring rule of the target monitoring field to determine the second verification result of each target monitoring field.

[0105] Optionally, the device is further used to interrupt the sending of the service request to be sent and generate first exception information based on the first verification result in the case where the first verification result does not meet the preset verification result; generate second exception information based on the second verification result in the case where the second verification result does not meet the preset verification result; and remind the target user through a preset exception reminder method based on the first exception information or the second exception information.

[0106] Optionally, after receiving the request processing result returned by the target receiving system, the device is further used to: obtain the first receiving time of the service request to be sent, and obtain the second receiving time of the request processing result, and calculate the absolute value of the difference between the first receiving time and the second receiving time; in the case where the absolute value of the difference is greater than the preset time difference threshold, generate corresponding third exception information based on the absolute value of the difference, and remind the target user through a preset exception reminder method based on the third exception information.

[0107] The data interaction monitoring device provided by the embodiments of the present invention can execute the data interaction monitoring method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method.

[0108] Embodiment 4

[0109] Figure 5 FIG. 7 is a schematic structural diagram of an electronic device provided by Embodiment 4 of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as, for example, a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as, for example, a personal digital processor, a cellular phone, a smart phone, a wearable device (such as a helmet, glasses, a watch, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present invention described and / or claimed herein.

[0110] As Figure 5 shown, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc. Among them, the memory stores a computer program executable by the at least one processor, and the processor 11 can execute various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. The input / output (I / O) interface 15 is also connected to the bus 14.

[0111] A plurality of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0112] The processor 11 may be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the data interaction monitoring method.

[0113] In some embodiments, the data interaction monitoring method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed onto the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the data interaction monitoring method described above may be executed. Alternatively, in other embodiments, the processor 11 may be configured to execute the data interaction monitoring method by any other suitable means (e.g., by means of firmware).

[0114] The various embodiments of the systems and techniques described above in this document may be implemented in digital electronic circuitry, integrated circuit systems, field-programmable gate arrays (FPGA), application-specific integrated circuits (ASIC), application-specific standard products (ASSP), system-on-a-chip systems (SOC), complex programmable logic devices (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that may be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a special-purpose or general-purpose programmable processor, that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit the data and instructions to the storage system, the at least one input device, and the at least one output device.

[0115] The computer program for implementing the data interaction monitoring method of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the computer program is executed by the processor, the functions / operations specified in the flowchart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0116] Embodiment Five

[0117] Embodiment 5 of the present invention also provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a processor to execute a data interaction monitoring method. The method includes:

[0118] Obtain a service request to be sent, and determine interface information and information of fields to be interacted based on the service request to be sent; wherein, the interface information includes an interface name;

[0119] Determine whether the corresponding interface meets a preset monitoring condition based on the interface name. When the interface meets the preset monitoring condition, determine at least one target monitoring field and the first monitoring rule corresponding to each target monitoring field based on the interface name and the information of fields to be interacted;

[0120] For any target monitoring field, verify the corresponding target monitoring field based on the first monitoring rule of the target monitoring field, and determine the first verification result of each target monitoring field;

[0121] When the first verification results of all target monitoring fields meet the preset verification condition, send the service request to be sent to the target receiving system, and receive the request processing result returned by the target receiving system.

[0122] In the context of the present invention, the computer-readable storage medium may be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium may be a machine-readable signal medium. More specific examples of the machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0123] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0124] The systems and techniques described herein can be implemented in a computing system including backend components (e.g., as a data server), or a computing system including middleware components (e.g., an application server), or a computing system including frontend components (e.g., a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described herein), or a computing system including any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include: local area network (LAN), wide area network (WAN), blockchain network, and the Internet.

[0125] The computing system can include a client and a server. The client and the server are generally far from each other and typically interact through a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system and solves the defects of difficult management and weak business scalability existing in traditional physical hosts and VPS services.

[0126] It should be understood that various forms of the processes shown above can be used, with steps reordered, added, or deleted. For example, the steps recited in the present invention can be executed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved, and no limitation is imposed herein.

[0127] The above specific embodiments do not constitute a limitation on the protection scope of the present invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A data interaction monitoring method, characterized in that, Including: Obtain a business request to be sent, and determine interface information and information of fields to be interacted based on the business request to be sent; wherein, the interface information includes an interface name. Determine whether the corresponding interface meets a preset monitoring condition based on the interface name. When the interface meets the preset monitoring condition, determine at least one target monitoring field and a first monitoring rule corresponding to each target monitoring field based on the interface name and the information of fields to be interacted. For any one of the target monitoring fields, verify the corresponding target monitoring field based on the first monitoring rule of the target monitoring field, and determine a first verification result of each target monitoring field. When the first verification results of all the target monitoring fields meet a preset verification condition, send the business request to be sent to a target receiving system, and receive a request processing result returned by the target receiving system.

2. The method according to claim 1, wherein The determining whether the corresponding interface meets the preset monitoring condition based on the interface name includes: Obtain corresponding interface basic configuration information according to the interface name, wherein the interface basic configuration information at least includes interface validity information and a monitoring status. When the validity information is a valid identifier and the monitoring status is an enabled state, determine that the interface meets the preset monitoring condition; when the validity information is an invalid identifier or the monitoring status is a disabled state, determine that the interface does not meet the preset monitoring condition.

3. The method according to claim 1, wherein The information of fields to be interacted includes at least one interaction field. The determining at least one target monitoring field and a first monitoring rule corresponding to each target monitoring field based on the interface name and the information of fields to be interacted includes: Obtain corresponding interface field configuration information according to the interface name, wherein the interface field configuration information at least includes a source field, a source field monitoring status, and first monitoring rule configuration information corresponding to the source field. Obtain the source fields with the source field monitoring status being the enabled state from the interface field configuration information, and form a candidate monitoring field set from the obtained source fields. For each interaction field, match the interaction field with the candidate monitoring field set to obtain a matching result; when the matching result is a successful match, determine the interaction field with the successful match as a target monitoring field, and determine the monitoring rule in the first monitoring rule configuration information corresponding to the interaction field with the successful match as the first monitoring rule of the corresponding target monitoring field.

4. The method according to claim 3, wherein The interface field configuration information further includes second monitoring rule configuration information; after determining the interaction field with the successful match as a target monitoring field, the method further includes: Determine the monitoring rule in the second monitoring rule configuration information corresponding to the interaction field with the successful match as the second monitoring rule of the corresponding target monitoring field.

5. The method according to claim 4, characterized in that After receiving the request processing result returned by the target receiving system, the method further includes: Verify the corresponding target monitoring field based on the second monitoring rule of the target monitoring field, and determine a second verification result of each target monitoring field.

6. The method according to claim 1 or 5, characterized in that, The method further includes: In the case that the first verification result does not meet the preset verification result, interrupt the transmission of the service request to be sent, and generate first exception information based on the first verification result; In the case that the second verification result does not meet the preset verification result, generate second exception information based on the second verification result; Remind the target user through a preset exception reminder method based on the first exception information or the second exception information.

7. The method according to claim 1, characterized in that, After receiving the request processing result returned by the target receiving system, the method further includes: Obtain the first reception time of the service request to be sent, and obtain the second reception time of the request processing result, and calculate the absolute value of the difference between the first reception time and the second reception time; In the case that the absolute value of the difference is greater than the preset time difference threshold, generate corresponding third exception information based on the absolute value of the difference, and remind the target user through a preset exception reminder method based on the third exception information.

8. A data interaction monitoring device, characterized in that Includes: An information acquisition module, configured to acquire a service request to be sent, and determine interface information and fields to be interacted based on the service request to be sent; wherein, the interface information includes an interface name; A monitoring field and monitoring rule determination module, configured to determine whether a corresponding interface meets a preset monitoring condition based on the interface name, and in the case that the interface meets the preset monitoring condition, determine at least one target monitoring field and the first monitoring rule corresponding to each target monitoring field based on the interface name and the fields to be interacted; A verification result determination module, configured to verify a corresponding target monitoring field based on the first monitoring rule of the target monitoring field for any one of the target monitoring fields, and determine the first verification result of each target monitoring field; A request sending module, configured to, in the case that the first verification results of all the target monitoring fields meet the preset verification conditions, send the service request to be sent to a target receiving system, and receive the request processing result returned by the target receiving system.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the data interaction monitoring method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing a processor to execute the data interaction monitoring method according to any one of claims 1-7 when executed.

Images