Failure information monitoring method and device, equipment, storage medium and product
By monitoring and comparing business information between nodes and within nodes, the reliable consumption problem of message queues in failure scenarios is solved, the accuracy of message queue consumption is improved, and the integrity of business information is ensured.
Patent Information
- Application Number
- CN202411115700.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-14
- Publication Date
- 2024-12-10
AI Technical Summary
The message queue cannot ensure reliable consumption in the failure scenario, resulting in the risk of message omission and reducing the accuracy of message queue consumption.
By obtaining the service information of different nodes and the key values of the service primary keys, comparing the access results between nodes, filtering out the failure information between nodes and within nodes, and summing them to generate an exception display table for monitoring and early warning.
It avoids the risks of misscreening and missing screening, improves the accuracy of message queue consumption, and ensures the integrity and reliability of business information.
Smart Images
Figure CN119105883A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of information monitoring technology, and in particular to a failure information monitoring method, device, equipment, storage medium and product. Background Art
[0002] As business systems have higher demands for timeliness and concurrency, business process message queues have emerged. Compared with traditional batch task processing models, business process message queues not only greatly improve processing timeliness, but also enhance system flexibility and scalability. However, message queues also face the problem of being unable to ensure reliable consumption in failure scenarios.
[0003] In the related art, methods such as persistent messages, manual confirmation, and mirror queues are used to ensure reliable consumption. However, the above methods have the risk of message omissions, which reduces the accuracy of message queue consumption. Summary of the invention
[0004] The main purpose of this application is to provide a failure information monitoring method, device, equipment, storage medium and product, aiming to solve the technical problem of reducing the accuracy of message queue consumption.
[0005] To achieve the above purpose, the present application proposes a failure information monitoring method, the failure information detection method comprising:
[0006] Obtaining business information of different nodes and obtaining key values of business primary keys of different nodes, wherein the key values represent the number of visits between nodes;
[0007] Comparing the key value with the target key value of the target service information after performing the inter-node service access, and determining the first invalidation information between the nodes based on the result of the comparison;
[0008] Based on the target service information after the inter-node service access is performed in the node, the service information is screened to obtain second failure information in the node;
[0009] The first failure information and the second failure information are aggregated to obtain failure information.
[0010] In one embodiment, the step of comparing the key value with the target key value of the target business information after the inter-node business access, and determining the first inter-node invalidation information based on the result of the comparison, includes:
[0011] Determine the key value, and if the key value is not a preset key value, subtract the preset key value from the key value to obtain an initial key value;
[0012] Performing inter-node business access based on the business information in the node to obtain an access result, wherein the access result includes a target key value of the target business information after the inter-node business access;
[0013] Compare the initial key value with the target key value to obtain a comparison result;
[0014] Based on the comparison result, first failure information is determined.
[0015] In one embodiment, the step of filtering the service information based on the target service information after the inter-node service access in the node to obtain the second failure information in the node includes:
[0016] Based on the access result, determining target business information accessed by the participating nodes;
[0017] The target service information is deleted from the service information to obtain second invalidation information.
[0018] In one embodiment, after the step of aggregating the first failure information and the second failure information to obtain the failure information, the following steps are included:
[0019] Performing format matching on the failure information to obtain target failure information;
[0020] Parsing the target failure information to obtain abnormal information;
[0021] Based on the exception information, an exception display table is generated.
[0022] In one embodiment, the step of filtering the service information based on the target service information after the inter-node service access in the node to obtain the second failure information in the node further includes:
[0023] Inputting the service information into a preset failure monitoring model to perform failure monitoring to obtain second failure information;
[0024] Before the step of filtering the service information based on the target service information after the inter-node service access in the node to obtain the second failure information in the node, the step further includes:
[0025] Acquire sample business information and acquire sample tags corresponding to the sample business information, wherein the sample business information has the same content but different survival times;
[0026] Obtaining an initial failure monitoring model;
[0027] Inputting the sample service information into the initial failure monitoring model to obtain the survival status of the sample service information;
[0028] Based on the survival status and the sample label, the initial failure monitoring model is optimized to obtain a preset failure monitoring model.
[0029] In one embodiment, the step of generating an exception display table based on the exception information includes:
[0030] Get the initial display table;
[0031] Based on the abnormal information, the initial display table is set to obtain an abnormal display table;
[0032] The step of generating an abnormality display table based on the abnormality information includes:
[0033] Comparing the data volume corresponding to the abnormal information with a preset data volume threshold to obtain a comparison result;
[0034] If the comparison result is that the data volume is greater than the preset data volume threshold, a warning message is generated, and the abnormal display table and the warning message are reported to the operation and maintenance platform for the operation and maintenance personnel to make system adjustments based on the abnormal information.
[0035] In addition, to achieve the above-mentioned purpose, the present application also proposes a failure information monitoring device, the failure information monitoring device comprising:
[0036] An acquisition module, used to acquire business information of different nodes and key values of business primary keys of different nodes, wherein the key values represent the number of visits between nodes;
[0037] A comparison module, used to compare the key value with the target key value of the target business information after the inter-node business access, and determine the first failure information between the nodes based on the result of the comparison;
[0038] A screening module, configured to screen the service information based on the target service information after the inter-node service access is performed in the node, and obtain the second failure information in the node;
[0039] The aggregation module is used to aggregate the first failure information and the second failure information to obtain failure information.
[0040] In addition, to achieve the above-mentioned purpose, the present application also proposes a failure information monitoring device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the failure information monitoring method described above.
[0041] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the failure information monitoring method described above are implemented.
[0042] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the failure information monitoring method described above are implemented.
[0043] One or more technical solutions proposed in this application have at least the following technical effects:
[0044] This application avoids the risk of misscreening and missed screening and improves the accuracy of message queue consumption by monitoring the business information status within and between business nodes after executing business access. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0046] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0047] Figure 1 A flowchart of the first embodiment of the failure information monitoring method of the present application is provided;
[0048] Figure 2 A schematic diagram of the execution of the business information section of the failure information monitoring method of this application;
[0049] Figure 3 A schematic diagram of monitoring between business nodes of the failure information monitoring method of this application;
[0050] Figure 4 A schematic diagram of internal monitoring of a business node of the failure information monitoring method of this application;
[0051] Figure 5 A flow chart of the second embodiment of the failure information monitoring method of the present application;
[0052] Figure 6 This is a schematic diagram of Redis failure monitoring of the failure information monitoring method of this application;
[0053] Figure 7This is intended to indicate the abnormal display of the failure information monitoring method of this application;
[0054] Figure 8 A schematic diagram of the failure information monitoring system architecture of the failure information monitoring method of the present application;
[0055] Fig. 9 This is a schematic diagram of the module structure of the failure information monitoring device according to an embodiment of the present application;
[0056] Fig.10 Schematic diagram of the device structure of the hardware operating environment involved in the failure information monitoring method in the embodiment of the present application. DETAILED DESCRIPTION
[0057] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0058] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0059] The main solution of the embodiment of the present application is: obtain the business information of different nodes and obtain the key value of the business primary key of different nodes, wherein the key value represents the number of visits between nodes; compare the key value with the target key value of the target business information after the business access between nodes, and determine the first failure information between nodes based on the result of the comparison; based on the target business information after the business access between nodes within the node, filter the business information to obtain the second failure information within the node; summarize the first failure information and the second failure information to obtain failure information.
[0060] In the related art, methods such as persistent messages, manual confirmation, and mirror queues are used to ensure reliable consumption. However, the above methods have the risk of message omissions, which reduces the accuracy of message queue consumption.
[0061] This application avoids the risk of misscreening and missed screening and improves the accuracy of message queue consumption by monitoring the business information status within and between business nodes after executing business access.
[0062] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, etc. The following takes the failure information monitoring device as an example to illustrate this embodiment and the following embodiments.
[0063] Based on this, the present application embodiment provides a failure information monitoring method, referring to Figure 1 , Figure 1This is a flow chart of Example 1 of the failure information monitoring method of the present application.
[0064] In this embodiment, the failure information monitoring method includes steps S100 to S400:
[0065] Step S100, obtaining business information of different nodes and obtaining key values of business primary keys of different nodes, wherein the key values represent the number of accesses between nodes;
[0066] It should be noted that the executor of this embodiment is an invalidation information monitoring device, which is provided with a storage system Redis. The business primary key is one or a group of fields used to uniquely identify data rows in database design, and these fields are directly associated with business logic. The Redis of the invalidation information monitoring device obtains the business information with expired information of different nodes entering the business node aspect and the key value Key of the business primary key of different nodes, where the business information includes process nodes and message packets, please refer to Figure 2 , Figure 2 Provides a business information aspect execution diagram.
[0067] Step S200, comparing the key value with the target key value of the target business information after the inter-node business access, and determining the first invalidation information between the nodes based on the result of the comparison;
[0068] It is understandable that the first failure information is the failure information when each node performs inter-node access. The failure information monitoring device compares the key value of each node's business information after executing the business logic with the key value of the initial business logic that has not been executed, and determines the failure information when performing inter-node business access based on the comparison result. Please refer to Figure 3 , Figure 3 Provides a schematic diagram of monitoring between business nodes.
[0069] In a feasible implementation manner, step S200 includes the following steps:
[0070] Determine the key value, and if the key value is not a preset key value, subtract the preset key value from the key value to obtain an initial key value;
[0071] It should be noted that the preset key value is 1 in this implementation. Before judging the key value, the failure information monitoring device must first detect the operating status of the Redis of the failure information monitoring device, and can only monitor the failure information when the operating status is normal. The failure information monitoring device needs to determine whether the key of the node business information has a corresponding key in Redis. If not, record the exception. If so, judge whether the current key value is 1. If the key value is not 1, subtract 1 from the current value of this key value to get the initial key value.
[0072] In addition, if the current key value is 1, delete this key.
[0073] Performing inter-node business access based on the business information in the node to obtain an access result, wherein the access result includes a target key value of the target business information after the inter-node business access;
[0074] It is understandable that inter-node business access is the process of executing business logic. The target business information is the business information that effectively executes the business logic. After the failure information monitoring device executes the business logic, it determines whether the Key exists in the Redis of the failure information monitoring device. If the Key exists, the current initial key value is added to n (n is the number of downstream business nodes) to obtain the target key value, and the expiration time is refreshed. Then, the failure information monitoring device compares the initial key value with the target key value to obtain a comparison result.
[0075] In addition, if the Key does not exist in the Redis of the invalidation information monitoring device, a new Key is created and the key value is set to n to obtain the target key value, and an expiration time is set. Then, the invalidation information monitoring device compares the initial key value with the target key value to obtain a comparison result.
[0076] Based on the comparison result, first failure information is determined.
[0077] It should be noted that the failure information monitoring device judges the failure information based on the comparison result. If the target key value is inconsistent with the number of downstream business nodes of the node compared to the initial key value, it is determined that failure information exists and the first failure information is determined based on the monitoring process.
[0078] Step S300, based on the target service information after the inter-node service access in the node, the service information is screened to obtain second failure information in the node;
[0079] It is understandable that the second failure information is the second failure information obtained by monitoring the failure information in the node. The failure information monitoring device deletes the business information of the business logic executed in the node to obtain the second failure information in the node. Please refer to Figure 4 , Figure 4 Provides a schematic diagram of internal monitoring of business nodes.
[0080] Step S400: Aggregate the first failure information and the second failure information to obtain failure information.
[0081] It should be noted that the failure information monitoring device aggregates the obtained first failure information and the second failure information to obtain the failure information.
[0082] In this implementation, the failure information monitoring device monitors the failure information within the node and between nodes, thereby avoiding the risk of misscreening and missed screening and improving the accuracy of message queue consumption.
[0083] The present application embodiment provides a failure information monitoring method, referring to Figure 5 , Figure 5 This is a flow chart of Example 2 of the failure information monitoring method of the present application.
[0084] In a feasible implementation manner, step S400 includes steps S10 to S30:
[0085] Step S10, performing format matching on the expiration information to obtain target expiration information;
[0086] It is understandable that the target failure information is the failure information obtained after filtering the failure information. The Redis of the failure information monitoring device passively monitors the failure information and matches the format of the failure information to obtain the target failure information that conforms to the failure format.
[0087] Step S20, parsing the target failure information to obtain abnormal information;
[0088] It should be noted that the failure information monitoring device analyzes the failure information to obtain abnormal information, where the abnormal information includes abnormal type, abnormal time, process node, message message and business primary key, etc. Please refer to Figure 6 , Figure 6 Provides a Redis failure monitoring diagram.
[0089] Step S30: Generate an exception display table based on the exception information.
[0090] It is understandable that the failure information monitoring device generates an exception display table based on the exception information, including the exception type, exception time, process node, message, business primary key and processing status. Please refer to Figure 7 , Figure 7 Provides an exception display intent, please refer to Figure 8 , Figure 8 A schematic diagram of the failure information monitoring system architecture is provided.
[0091] In a feasible implementation manner, step S300 further includes the following steps:
[0092] Inputting the service information into a preset failure monitoring model to perform failure monitoring to obtain second failure information;
[0093] It should be noted that the preset failure monitoring model is a model for detecting the failure status of business information. The failure information monitoring device is provided with a preset failure monitoring model, and the failure status of the business information can be determined by inputting the business information of each node into the preset failure monitoring model to obtain the second failure information.
[0094] In a feasible implementation manner, based on the target service information after the inter-node service access is performed in the node, the service information is screened, and before the step of obtaining the second failure information in the node, the step further includes:
[0095] Acquire sample business information and acquire sample tags corresponding to the sample business information, wherein the sample business information has the same content but different survival times;
[0096] It is understandable that the sample tag is the actual survival status of the sample business information. The expiration information monitoring device obtains sample business information with the same business content and expiration time but different survival times, and uses the survival time of the sample business information as the sample tag; although the content of the sample business information is the same, their survival times are different, which reflects the dynamic changes in the business environment.
[0097] Obtaining an initial failure monitoring model;
[0098] It should be noted that the failure information monitoring device first sets an initial failure monitoring model so as to obtain a preset failure monitoring model based on the initial failure monitoring model.
[0099] Inputting the sample service information into the initial failure monitoring model to obtain the survival status of the sample service information;
[0100] It is understandable that the survival status is used to characterize whether the service information is in a failed state. The failure information monitoring device inputs the sample service information into the initial failure monitoring model, and lets the initial failure monitoring model predict the survival status of each sample service information to obtain the survival status corresponding to the sample service information.
[0101] Based on the survival status and the sample label, the initial failure monitoring model is optimized to obtain a preset failure monitoring model.
[0102] It should be noted that the failure information monitoring device compares the corresponding survival status of the obtained sample business information with the sample label corresponding to the sample business information, and calculates the prediction error. This process is called forward propagation. Based on the result of forward propagation, the optimization algorithm is used to adjust the parameters of the model to reduce the prediction error. This process is called back propagation. The failure information monitoring device repeatedly performs forward propagation and back propagation until the performance of the model reaches the preset standard, and then obtains the preset failure monitoring model. The preset failure monitoring model can be used to monitor new business information in real time and predict its survival status, thereby helping the business team to promptly discover and deal with potential problems.
[0103] In a feasible implementation manner, step S30 includes the following steps:
[0104] Get the initial display table;
[0105] It is understandable that the initial display table is an unfilled table template. The failure information monitoring device obtains a blank or default filled table template, which will be used to display abnormal information later; this initial display table has predefined column headers and formats to facilitate the subsequent addition of specific data.
[0106] Based on the abnormal information, the initial display table is set to obtain an abnormal display table;
[0107] It should be noted that the failure information monitoring device fills and sets the initial display table with the detected exception information, which means that the specific details of the exception, such as exception type, exception time, process node, message, business primary key and processing status, will be filled in the corresponding fields of the display table. In this way, the original initial display table is converted into an exception display table containing exception information.
[0108] The step of generating an abnormality display table based on the abnormality information includes:
[0109] Comparing the data volume corresponding to the abnormal information with a preset data volume threshold to obtain a comparison result;
[0110] It is understandable that after generating the abnormal display table, the failure information monitoring device will automatically check the amount of data related to the abnormal information, such as the number of abnormal events or the total amount of abnormal data. These data amounts will be compared with the preset data amount threshold to determine the severity of the abnormal situation.
[0111] If the comparison result is that the data volume is greater than the preset data volume threshold, a warning message is generated, and the abnormal display table and the warning message are reported to the operation and maintenance platform for the operation and maintenance personnel to make system adjustments based on the abnormal information.
[0112] It should be noted that when the failure information monitoring device detects that the amount of abnormal data exceeds the preset threshold, the failure information monitoring device will automatically generate a warning message to indicate the urgency of the current abnormal situation. Subsequently, the abnormal display table together with the warning information will be reported to the operation and maintenance platform. After receiving this information, the operation and maintenance personnel can quickly locate the problem and take corresponding system adjustment measures to prevent the abnormal situation from deteriorating or recurring.
[0113] In this embodiment, the failure information monitoring device monitors the failure information through a preset failure monitoring model, and generates an abnormal report for the abnormal information of the failure information. When the number of abnormal information reaches a preset data volume threshold, it is reported to the platform, thereby improving the timeliness of failure information monitoring.
[0114] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the failure information monitoring method of the present application. More simple transformations based on this technical concept are all within the protection scope of the present application.
[0115] This application also provides a failure information monitoring device, please refer to Fig. 9 , the failure information monitoring device comprises:
[0116] An acquisition module, used to acquire business information of different nodes and key values of business primary keys of different nodes, wherein the key values represent the number of visits between nodes;
[0117] A comparison module, used to compare the key value with the target key value of the target business information after the inter-node business access, and determine the first failure information between the nodes based on the result of the comparison;
[0118] A screening module, configured to screen the service information based on the target service information after the inter-node service access is performed in the node, and obtain the second failure information in the node;
[0119] The aggregation module is used to aggregate the first failure information and the second failure information to obtain failure information.
[0120] Optionally, the comparison module includes:
[0121] A key value module is used to judge the key value. If the key value is not a preset key value, the preset key value is subtracted from the key value to obtain an initial key value; based on the business information in the node, inter-node business access is performed to obtain an access result, wherein the access result includes a target key value of the target business information after the inter-node business access; the initial key value and the target key value are compared to obtain a comparison result; based on the comparison result, the first failure information is determined.
[0122] Optionally, the screening module includes:
[0123] The deletion module is used to determine the target business information accessed by the participating nodes based on the access result; delete the target business information from the business information to obtain the second invalidation information.
[0124] A model module is used to input the business information into a preset failure monitoring model for failure monitoring to obtain second failure information; obtain sample business information and obtain sample labels corresponding to the sample business information, wherein the sample business information has the same content but different survival times; obtain an initial failure monitoring model; input the sample business information into the initial failure monitoring model to obtain the survival status of the sample business information; based on the survival status and the sample label, optimize the initial failure monitoring model to obtain a preset failure monitoring model.
[0125] Optionally, the aggregation module includes:
[0126] The exception module is used to perform format matching on the failure information to obtain target failure information; parse the target failure information to obtain exception information; and generate an exception display table based on the exception information.
[0127] Optionally, the abnormal module includes:
[0128] The reporting module is used to obtain an initial display table; based on the abnormal information, the initial display table is set to obtain an abnormal display table; the data volume corresponding to the abnormal information is compared with a preset data volume threshold to obtain a comparison result; if the comparison result is that the data volume is greater than the preset data volume threshold, an early warning message is generated, and the abnormal display table and the early warning message are reported to the operation and maintenance platform, so that the operation and maintenance personnel can make system adjustments based on the abnormal information.
[0129] The failure information monitoring device provided by the present application adopts the failure information monitoring method in the above embodiment, which can solve the technical problem of failure information monitoring. Compared with the prior art, the beneficial effects of the failure information monitoring device provided by the present application are the same as the beneficial effects of the failure information monitoring method provided by the above embodiment, and the other technical features in the failure information monitoring device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0130] The present application provides a failure information monitoring device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the failure information monitoring method in the above-mentioned embodiment one.
[0131] Reference below Fig.10 , which shows a schematic diagram of the structure of a failure information monitoring device suitable for implementing the embodiment of the present application. The failure information monitoring device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig.10 The failure information monitoring device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0132] like Fig.10 As shown, the failure information monitoring device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the failure information monitoring device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the failure information monitoring device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a failure information monitoring device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.
[0133] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0134] The failure information monitoring device provided by the present application adopts the failure information monitoring method in the above embodiment, which can solve the technical problem of failure information monitoring. Compared with the prior art, the beneficial effects of the failure information monitoring device provided by the present application are the same as the beneficial effects of the failure information monitoring method provided by the above embodiment, and the other technical features in the failure information monitoring device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0135] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0136] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0137] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the failure information monitoring method in the above-mentioned embodiment.
[0138] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0139] The computer-readable storage medium may be included in the failure information monitoring device; or may exist independently without being assembled into the failure information monitoring device.
[0140] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the failure information monitoring device, the failure information monitoring device: obtains the business information of different nodes and obtains the key values of the business primary keys of different nodes, wherein the key values represent the number of visits between nodes; compares the key values with the target key values of the target business information after the business access between nodes, and determines the first failure information between nodes based on the result of the comparison; based on the target business information after the business access between nodes in the node, the business information is screened to obtain the second failure information in the node; and the first failure information and the second failure information are summarized to obtain the failure information.
[0141] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0142] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0143] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0144] The readable storage medium provided in the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned failure information monitoring method, and can solve the technical problems of failure information monitoring. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the failure information monitoring method provided in the above-mentioned embodiment, and will not be repeated here.
[0145] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned failure information monitoring method when executed by a processor.
[0146] The computer program product provided by this application can solve the technical problem of failure information monitoring. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the failure information monitoring method provided by the above embodiment, which will not be repeated here.
[0147] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A failure information monitoring method, characterized in that: The failure information monitoring method comprises: Obtaining business information of different nodes and obtaining key values of business primary keys of different nodes, wherein the key values represent the number of visits between nodes; Comparing the key value with the target key value of the target service information after performing the inter-node service access, and determining the first invalidation information between the nodes based on the result of the comparison; Based on the target service information after the inter-node service access is performed in the node, the service information is screened to obtain second failure information in the node; The first failure information and the second failure information are aggregated to obtain failure information.
2. The failure information monitoring method according to claim 1, characterized in that: The step of comparing the key value with the target key value of the target service information after the inter-node service access and determining the first inter-node failure information based on the comparison result includes: Determine the key value, and if the key value is not a preset key value, subtract the preset key value from the key value to obtain an initial key value; Performing inter-node business access based on the business information in the node to obtain an access result, wherein the access result includes a target key value of the target business information after the inter-node business access; Compare the initial key value with the target key value to obtain a comparison result; Based on the comparison result, first failure information is determined.
3. The failure information monitoring method according to claim 2, characterized in that: The step of filtering the service information based on the target service information after the inter-node service access in the node to obtain the second failure information in the node includes: Based on the access result, determining target business information accessed by the participating nodes; The target service information is deleted from the service information to obtain second invalidation information.
4. The failure information monitoring method according to claim 1, characterized in that: After the step of aggregating the first failure information and the second failure information to obtain the failure information, the following steps are included: Performing format matching on the failure information to obtain target failure information; Parsing the target failure information to obtain abnormal information; Based on the exception information, an exception display table is generated.
5. The failure information monitoring method according to claim 1, characterized in that: The step of filtering the service information based on the target service information after the inter-node service access in the node to obtain the second failure information in the node also includes: Inputting the service information into a preset failure monitoring model to perform failure monitoring to obtain second failure information; Before the step of filtering the service information based on the target service information after the inter-node service access in the node to obtain the second failure information in the node, the step further includes: Acquire sample business information and acquire sample tags corresponding to the sample business information, wherein the sample business information has the same content but different survival times; Obtaining an initial failure monitoring model; Inputting the sample service information into the initial failure monitoring model to obtain the survival status of the sample service information; Based on the survival status and the sample label, the initial failure monitoring model is optimized to obtain a preset failure monitoring model.
6. The failure information monitoring method according to claim 4, characterized in that: The step of generating an exception display table based on the exception information includes: Get the initial display table; Based on the abnormal information, the initial display table is set to obtain an abnormal display table; The step of generating an abnormality display table based on the abnormality information includes: Comparing the data volume corresponding to the abnormal information with a preset data volume threshold to obtain a comparison result; If the comparison result is that the data volume is greater than the preset data volume threshold, a warning message is generated, and the abnormal display table and the warning message are reported to the operation and maintenance platform for the operation and maintenance personnel to make system adjustments based on the abnormal information.
7. A failure information monitoring device, characterized in that: The device comprises: An acquisition module, used to acquire business information of different nodes and key values of business primary keys of different nodes, wherein the key values represent the number of visits between nodes; A comparison module, used to compare the key value with the target key value of the target business information after the inter-node business access, and determine the first failure information between the nodes based on the result of the comparison; A screening module, configured to screen the service information based on the target service information after the inter-node service access is performed in the node, and obtain the second failure information in the node; The aggregation module is used to aggregate the first failure information and the second failure information to obtain failure information.
8. A failure information monitoring device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the failure information monitoring method according to any one of claims 1 to 6.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the failure information monitoring method according to any one of claims 1 to 6 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the failure information monitoring method according to any one of claims 1 to 6 are implemented.