Transaction influence fast report sending method and device, storage medium and electronic device

Abstract

The invention discloses a transaction influence fast report sending method and device, a storage medium and an electronic device, and the method comprises the steps: comparing a collected current transaction influence fast report with a sent transaction influence fast report through employing a repeated judgment condition, according to a comparison result of the comparison, whether the current transaction influence rapid report belongs to a repeated rapid report is determined, and the current transaction influence rapid report is generated based on historical transaction detail data; when it is determined that the current transaction influence fast report does not belong to the repeated fast report, whether the current transaction influence fast report belongs to a shielded fast report or not is judged by using a shielding business rule; and sending the current transaction influence fast report to a target object when determining that the current transaction influence fast report does not belong to the shielded fast report. By adopting the technical scheme, the problem that the operation and maintenance efficiency of a transaction system is low due to the fact that the transaction affects repeated sending of the quick report is solved.

Description

Technical Field

[0001] The present application relates to the technical field of data transaction analysis, and more specifically, to a method and device for sending a transaction impact quick report, a storage medium, and an electronic device. Background Art

[0002] When a bank's transaction system fails, it will send a transaction impact quick report. Since the transaction system is monitored in real time, if the business system fails and has not recovered, the transaction impact quick report will be continuously generated. In related technologies, once a transaction impact quick report is generated, it will be sent to the target object using a unified messaging platform, which results in repeated reports. This interferes with the operation and maintenance personnel's emergency recovery measures such as fault detection, location and disposal, and cannot handle the affected transactions in a timely manner, affecting the operation and maintenance efficiency of the transaction system.

[0003] Therefore, in the related art, there is a technical problem that the operation and maintenance efficiency of the trading system is low due to the repeated sending of transaction impact reports.

[0004] With regard to related technologies, no effective solution has been proposed so far to the technical problem of low operational efficiency of the trading system due to repeated sending of transaction impact reports.

[0005] Therefore, it is necessary to improve the related technology to overcome the above-mentioned defects in the related technology. Summary of the invention

[0006] The embodiments of the present application provide a method and device for sending a transaction impact quick report, a storage medium and an electronic device, so as to at least solve the technical problem of low operation and maintenance efficiency of the transaction system caused by repeated sending of the transaction impact quick report.

[0007] According to one aspect of an embodiment of the present application, a method for sending a transaction impact quick report is provided, including: using a duplication judgment condition to compare a collected current transaction impact quick report with a sent transaction impact quick report, and judging whether the current transaction impact quick report is a duplicate quick report based on the comparison result, wherein the current transaction impact quick report is generated based on historical transaction detail data; when it is determined that the current transaction impact quick report is not a duplicate quick report, using a shielding business rule to judge whether the current transaction impact quick report is a shielded quick report; when it is determined that the current transaction impact quick report is not a shielded quick report, sending the current transaction impact quick report to a target object.

[0008] In an exemplary embodiment, a duplicate judgment condition is used to compare the collected current transaction impact quick report and the sent transaction impact quick report, and whether the current transaction impact quick report is a duplicate quick report is judged according to the comparison result, including: when it is determined that the current transaction impact quick report has a root cause system, selecting a first judgment condition from preset judgment conditions, wherein the first judgment condition is that the root cause system of the current transaction impact quick report is the same as the root cause system of the sent transaction impact quick report, and there is an intersection between the affected system of the current transaction impact quick report and the affected system of the sent transaction impact quick report; when it is determined that the first judgment condition is met, determining that the current transaction impact quick report is a duplicate quick report.

[0009] In an exemplary embodiment, a duplicate judgment condition is used to compare the collected current transaction impact quick report and the sent transaction impact quick report, and whether the current transaction impact quick report is a duplicate quick report is judged according to the comparison result, including: when it is determined that the current transaction impact quick report does not have a root cause system, a second judgment condition is selected from preset judgment conditions, wherein the second judgment condition is that there is an intersection between the affected system of the current transaction impact quick report and the affected system of the sent transaction impact quick report, and the transaction record with the highest transaction volume in the intersection has the same transaction code; when it is determined that the second judgment condition is met, it is determined that the current transaction impact quick report is a duplicate quick report.

[0010] In an exemplary embodiment, shielding business rules are used to determine whether the current transaction impact quick report is a shielded quick report, including: determining whether the current transaction impact quick report is a shielded quick report according to a first shielding business rule, wherein the first shielding business rule indicates whether the root cause system of the current transaction impact quick report is in a maintenance period, and for the root cause system in the maintenance period, the current transaction impact quick report is determined to be a shielded quick report.

[0011] In an exemplary embodiment, the method also includes: for a root cause system that is not in a maintenance period, determining whether the current transaction impact quick report is a shielded quick report based on a second shielding business rule, wherein the second shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in the process of changing; when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in the process of changing, determining that the current transaction impact quick report is a shielded quick report.

[0012] In an exemplary embodiment, the method also includes: when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is not changing, judging whether the current transaction impact quick report is a shielded quick report according to a third shielding business rule, wherein the third shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report has a shielding period; when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report has a shielding period, judging that the current transaction impact quick report is a shielded quick report.

[0013] In an exemplary embodiment, the method also includes: when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report does not have a shielding period, judging whether the current transaction impact quick report is a shielded quick report according to a fourth shielding business rule, wherein the fourth shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in a disaster recovery drill; when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in a disaster recovery drill, judging that the current transaction impact quick report is a shielded quick report.

[0014] According to another aspect of an embodiment of the present application, a device for sending a transaction impact quick report is also provided, including: a comparison module, used to use a duplication judgment condition to compare the collected current transaction impact quick report and the sent transaction impact quick report, and judge whether the current transaction impact quick report is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on historical transaction detail data; a shielding judgment module, used to use a shielding business rule to judge whether the current transaction impact quick report is a shielded quick report when it is determined that the current transaction impact quick report is not a duplicate quick report; and a sending module, used to send the current transaction impact quick report to the target object when it is determined that the current transaction impact quick report is not a shielded quick report.

[0015] According to another aspect of the embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the method for sending the transaction impact bulletin when running.

[0016] According to another aspect of an embodiment of the present application, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the method for sending the transaction impact bulletin through the computer program.

[0017] Through this application, the collected current transaction impact quick report and the sent transaction impact quick report can be compared using the duplication judgment condition, and the current transaction impact quick report can be judged whether it is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on the historical transaction detail data; when it is determined that the current transaction impact quick report does not belong to a duplicate quick report, the shielding business rule is used to judge whether the current transaction impact quick report belongs to a shielded quick report; when it is determined that the current transaction impact quick report does not belong to a shielded quick report, the current transaction impact quick report is sent to the target object. It can be seen that by adopting the above technical solution, by setting the duplication judgment condition and the shielding business rule, the probability of repeated sending and mis-sending quick reports in specific circumstances is reduced, and the accuracy and efficiency of sending transaction impact quick reports are improved. This method solves the problem of low operation and maintenance efficiency of the transaction system caused by the repeated sending of transaction impact quick reports, which can not only reduce unnecessary information interference, but also ensure that the transaction impact information is conveyed to the operation and maintenance personnel in a timely and accurate manner without affecting the key business, thereby improving the operation and maintenance efficiency, thereby improving the overall operation quality and user experience of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The exemplary embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 It is a hardware structure block diagram of a computer terminal for executing the method for sending a transaction impact quick report according to an embodiment of the present application;

[0020] Figure 2 is a flow chart of a method for sending a transaction impact quick report according to an embodiment of the present application;

[0021] Figure 3 It is a schematic diagram of a process for determining repeated quick reports according to an embodiment of the present application;

[0022] Figure 4 It is a schematic diagram of a process for determining a blocked quick report according to an embodiment of the present application;

[0023] Figure 5 It is a structural block diagram of a device for sending transaction impact quick report according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0025] It should be noted that the terms and "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] The method embodiments provided in the embodiments of the present application can be executed in a computer terminal or a similar computing device. Taking running on a computer terminal as an example, Figure 1 1 is a hardware structure block diagram of a computer terminal for executing the method for sending transaction impact quick report of the embodiment of the present application. Figure 1 As shown, the computer terminal may include one or more ( Figure 1 The processor 102 (only one is shown) may include but is not limited to a microprocessor (Microprocessor Unit, MPU for short) or a programmable logic device (Programmable logic device, PLD for short) and a memory 104 configured to store data.

[0027] In an exemplary embodiment, the computer terminal may further include a transmission device 106 and an input / output device 108 configured to function as a communication device. Figure 1 The structure shown is only for illustration and does not limit the structure of the above-mentioned computer terminal. Figure 1 More or fewer components as shown, or with Figure 1 Equivalent functions or comparisons shown Figure 1 A different configuration with more features is shown.

[0028] The memory 104 may be configured to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the method for sending the transaction impact quick report in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal via a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0029] The transmission device 106 is configured to receive or send data via a network. A specific example of the above network may include a wireless network provided by a communication provider of a computer terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0030] Next, some technical terms that are helpful for understanding the solution of the present application are explained.

[0031] Configuration management: The full name is Configuration Managed Database (CMDB), which is a logical database that contains information about the entire life cycle of configuration items and the relationships between configuration items.

[0032] Application monitoring: Application performance monitoring tool system collects, monitors, analyzes and alarms application performance data in real time. Common application monitoring collection indicators include transaction volume, business success rate, system success rate, response time, etc. Application monitoring alarms are divided into AP view (single machine view), deployment unit view, transaction code view, overview view (application system view), etc.

[0033] Transaction code: A transaction code identifies a specific business function. The transaction code passed when an interface is called between application systems represents the meaning of the business function of this call.

[0034] Transaction line: Multiple application systems connected in series by transaction codes constitute a transaction line.

[0035] Event integration platform: Alarms collected by various monitoring tools such as application monitoring and basic monitoring are centrally processed on the event integration platform and notified to relevant operation and maintenance personnel in the form of text messages, emails, etc.

[0036] Transaction impact quick report: Based on the data of real-time collection, monitoring and alarm of application performance, the impact of system abnormalities on transactions can be accurately perceived from multiple dimensions such as application system and transaction code performance monitoring indicators and alarms. The abnormal system, abnormal indicators, affected systems, and the type, quantity, degree, duration and other factors of affected transactions can be analyzed in real time. A hierarchical and classified transaction impact key prompt information report can be generated and sent within 1 minute, which can improve the efficiency of fault detection and impact range analysis.

[0037] In the transaction impact quick report, "root cause system" and "affected system" are two key concepts used to understand and locate the root causes of transaction anomalies in the bank's transaction system and the scope of their impact.

[0038] Among them, the root cause system refers to the source system that directly causes transaction anomalies or failures. In the transaction chain of the transaction system, a transaction may involve interactions between multiple systems. If a system has a problem, such as hardware failure, software error, network delay, etc., then the system with the problem is called the "root cause system." Identifying the root cause system can help operation and maintenance personnel quickly locate the fault point, which is the first step in fault recovery and problem solving.

[0039] Impacted Systems refer to systems that are indirectly affected by problems with the root cause system. In a trading environment, systems are usually interdependent and interconnected. If a root cause system fails, it may affect other systems that interact with it, causing the transaction processing capabilities of these systems to decline or transaction failures. There may be more than one affected system, but multiple systems in the entire transaction chain. Identifying the affected systems helps to fully assess the scope and impact of the failure, ensuring that all affected businesses receive timely attention and processing.

[0040] For example, if a bank's account management system (A) fails and cannot process transaction requests correctly, the transfer system (B), deposit system (C), and loan system (D) that interact with the account management system may be affected. These systems (B, C, D) are the "affected systems", and the account management system (A) is the "root cause system." The transaction impact report will record in detail the root cause system and the problems it causes, as well as the specific conditions of all affected systems, including transaction volume, success rate, response time, etc., to help banks manage and restore services more effectively.

[0041] In this embodiment, a method for sending a transaction impact quick report is provided. Figure 2 According to a flow chart of a method for sending a transaction impact quick report according to an embodiment of the present application, the process includes the following steps:

[0042] Step S202, using a duplication judgment condition to compare the collected current transaction impact quick report with the sent transaction impact quick report, and judging whether the current transaction impact quick report is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on historical transaction detail data;

[0043] Optionally, the process of generating the current transaction impact quick report based on the historical transaction detail data is, for example, to regularly collect data of the historical transaction impact quick report, which may include the root cause system, the affected system, the transaction code, the system maintenance period, the system change, the system disaster recovery drill, etc. Then, manual analysis is performed on the characteristic fields of the transaction impact quick report to form a duplication judgment condition for identifying duplicate quick reports and a shielding business rule for identifying shielded quick reports.

[0044] Optionally, during the above comparison process, a deduplication operation may be performed in advance to obtain deduplicated quick report data, and then a judgment may be made on duplicate quick reports and blocked quick reports. This can further improve the chances of not repeatedly reporting messages generated by the same fault and improve the accuracy of quick reports on transaction impacts.

[0045] Step S204, when it is determined that the current transaction impact quick report is not a duplicate quick report, use the shielding business rule to determine whether the current transaction impact quick report is a shielded quick report;

[0046] Step S206: When it is determined that the current transaction impact quick report is not a blocked quick report, the current transaction impact quick report is sent to the target object.

[0047] Furthermore, when it is determined that the pending quick report is a shielded quick report, the sending of the pending quick report to the target object is stopped, a shielding record is generated based on the shielded quick report, and the shielding record is sent to the target object.

[0048] Through the above steps, the collected current transaction impact quick report and the sent transaction impact quick report can be compared using the duplication judgment condition, and the current transaction impact quick report can be judged whether it is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on the historical transaction detail data; when it is determined that the current transaction impact quick report is not a duplicate quick report, the shielding business rule is used to judge whether the current transaction impact quick report is a shielded quick report; when it is determined that the current transaction impact quick report is not a shielded quick report, the current transaction impact quick report is sent to the target object. It can be seen that by adopting the above technical solution, by setting the duplication judgment condition and the shielding business rule, the probability of repeated sending and mis-sending quick reports in specific circumstances is reduced, and the accuracy and efficiency of sending transaction impact quick reports are improved. This method solves the problem of low operation and maintenance efficiency of the transaction system caused by the repeated sending of transaction impact quick reports, which can not only reduce unnecessary information interference, but also ensure that the transaction impact information is timely and accurately conveyed to the operation and maintenance personnel under the condition that the key business is not affected, thereby improving the operation and maintenance efficiency, thereby improving the overall operation quality and user experience of the system.

[0049] In addition, in addition to being able to automatically identify and process duplicate and erroneous reports, this application can also flexibly adjust shielding rules according to business needs. It is applicable to trading systems of various sizes, effectively improving the accuracy and efficiency of transaction impact reports, reducing the burden of information processing, and ensuring business continuity and stability. Furthermore, intelligent analysis functions can be integrated into this application to predict possible transaction impacts based on historical data and current transaction conditions, and to issue early warnings to help the business team take timely measures to reduce potential transaction risks. At the same time, through data analysis, it is possible to continuously optimize duplicate judgment conditions and shielding business rules, improve the intelligence level of the system, and better adapt to the ever-changing business environment. In actual applications, this application can be seamlessly connected with operation and maintenance systems, customer service systems, etc., to achieve automated processing and distribution of transaction impact reports, and improve overall business response speed and service quality.

[0050] In an exemplary embodiment, the process of comparing the collected current transaction impact quick report with the sent transaction impact quick report using a duplication judgment condition, and judging whether the current transaction impact quick report is a duplicate quick report according to the comparison result of the comparison, may specifically include: in the case of determining that the current transaction impact quick report has a root cause system, selecting a first judgment condition from preset judgment conditions, wherein the first judgment condition is that the root cause system of the current transaction impact quick report is the same as the root cause system of the sent transaction impact quick report, and there is an intersection between the affected system of the current transaction impact quick report and the affected system of the sent transaction impact quick report; in the case of determining that the first judgment condition is satisfied, determining that the current transaction impact quick report is a duplicate quick report. By identifying the intersection of the root cause system and the affected system, repeated notifications can be avoided when the same problem continues to affect, especially during system maintenance or failure, which can reduce the sending of duplicate quick reports, improve the accuracy of quick reports, and improve the efficiency of subsequent processing of quick reports.

[0051] Optionally, if the first judgment condition is not met, it is determined that the current transaction impact quick report is not a duplicate quick report, and subsequent judgments are continued.

[0052] In an exemplary embodiment, further, using a duplication judgment condition to compare the collected current transaction impact quick report with the sent transaction impact quick report, judging whether the current transaction impact quick report is a duplicate quick report according to the comparison result may also include: in the case of determining that the current transaction impact quick report does not have a root cause system, selecting a second judgment condition from the preset judgment conditions, wherein the second judgment condition is that there is an intersection between the affected system of the current transaction impact quick report and the affected system of the sent transaction impact quick report, and the transaction record with the highest transaction volume in the intersection has the same transaction code; in the case of determining that the second judgment condition is satisfied, determining that the current transaction impact quick report is a duplicate quick report. In the case of no clear root cause system, duplicate quick reports can also be effectively identified by comparing transaction codes and transaction volumes, which is suitable for system failures with unknown causes or complex transaction environments to ensure the accuracy and pertinence of information.

[0053] Optionally, if the second judgment condition is not met, it is determined that the current transaction impact quick report is not a duplicate quick report, and subsequent judgment continues.

[0054] In an exemplary embodiment, the process of using a shielding business rule to determine whether the current transaction impact quick report is a shielded quick report also includes: determining whether the current transaction impact quick report is a shielded quick report according to a first shielding business rule, wherein the first shielding business rule indicates whether the root cause system of the current transaction impact quick report is in a maintenance period, and for the root cause system in the maintenance period, the current transaction impact quick report is determined to be a shielded quick report. When the system is regularly maintained or upgraded, shielding related quick reports can avoid false alarms and reduce interference with business operations, especially in large enterprises or financial institutions, where system maintenance is a normal situation. This method can ensure the accurate sending of quick reports.

[0055] In an exemplary embodiment, further, for the root cause system that is not in the maintenance period, it is determined whether the current transaction impact quick report is a blocked quick report according to the second blocking business rule, wherein the second blocking business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in the process of changing; when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in the process of changing, it is determined that the current transaction impact quick report is a blocked quick report. During the system change or upgrade process, blocking the transaction impact quick report that may be caused by the change can avoid interference with the change team and ensure the smooth progress of the change process.

[0056] In an exemplary embodiment, further, when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is not being changed, it is determined whether the current transaction impact quick report is a shielded quick report according to the third shielding business rule, wherein the third shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report has a shielding period; when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report has a shielding period, it is determined that the current transaction impact quick report is a shielded quick report. By setting the shielding period, non-emergency quick reports can be avoided from being sent at specific times (such as at night and on holidays). For example, for a 24-hour operation scenario, unnecessary interference with the operation and maintenance work of operation and maintenance personnel can be reduced.

[0057] Optionally, it is possible to first determine whether this shielded period has an intersection with the generation period of the transaction impact quick report. If there is an intersection, it is determined to be a shielded quick report. If there is no intersection, it can be determined based on the above rules whether the current transaction impact quick report is a shielded quick report.

[0058] In an exemplary embodiment, when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report does not have a shielding period, it is determined whether the current transaction impact quick report is a shielded quick report according to the fourth shielding business rule, wherein the fourth shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in a disaster recovery drill; when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in a disaster recovery drill, it is determined that the current transaction impact quick report is a shielded quick report. When conducting a disaster recovery drill, shielding the transaction impact quick report related to the drill can avoid misjudgment of the drill effect and ensure the authenticity and effectiveness of the drill.

[0059] Obviously, the above-described embodiments are only a part of the embodiments of the present application, not all of the embodiments. In order to better understand the method for sending the above-mentioned transaction impact quick report, the above-mentioned process is described below in conjunction with the embodiments, but it is not intended to limit the technical solutions of the embodiments of the present application. Specifically:

[0060] In an optional embodiment, the sending process of the transaction impact quick report is further described in combination with the following content. The present application can firstly conduct manual analysis from the characteristic fields of the transaction impact quick report by regularly counting the data of the transaction impact quick report, including the root cause system, the affected system, the transaction code, the system maintenance period, the system change, and the system disaster recovery drill, and then form duplicate identification and shielding business rules through the obtained transaction impact quick report detailed data by comparison, and then perform duplicate rule identification (referred to as step A) and shielding business rule identification (referred to as step B). If the match is successful, it is determined to be a quick report that does not need to be sent. If the match is unsuccessful, it is determined to be a non-duplicate and non-shielded valid quick report and sent normally.

[0061] Among them, after the transaction impact quick report is generated, step A is started first to determine whether it is repeated with the transaction impact quick report that has been issued. If the result is repeated, the identification and inspection are terminated and the process is terminated. If the result is not repeated, continue to step B to check whether it matches the effective blocking rules. If it matches the effective blocking rules, the result is that it is blocked and not sent, and the process is terminated; if it does not match the effective blocking rules, the result is that it is not blocked and continues to be sent normally.

[0062] The implementation process of step A is as follows: Figure 3 As shown, the specific steps include:

[0063] Step 1: Generate the current transaction impact quick report, and query the quick reports sent within half an hour. You can also obtain a quick report set for comparison and deduplication. Specifically, all transaction impact details are summarized once a minute, and the current transaction impact quick report is generated. Query the quick reports sent within half an hour and obtain a quick report set for comparison and deduplication.

[0064] Step 2: Determine whether the current quick report has a root cause system and identify different judgment rules. If yes, go to step 3, otherwise go to step 4.

[0065] Step 3: If there is a root cause system, determine whether the duplication condition is satisfied: whether the root cause system is the same and the influencing system has an intersection. If so, proceed to step 5; otherwise, proceed to step 6.

[0066] Step 4: If there is no root cause system, the condition for determining duplication is whether the affecting systems have intersections and the transaction code ranked first in transaction volume is the same. If so, proceed to step 5, otherwise proceed to step 6.

[0067] Step 5: If the result of step 3 and step 4 is a duplicate quick report, no other processing will be continued and the process ends.

[0068] Step 6: If the results of steps 3 and 4 are non-duplicate reports, continue to step B to check the shielding rules.

[0069] The implementation process of step B is as follows: Figure 4 As shown, specifically including:

[0070] Step 1, based on the above process, by using the root cause system and the influencing system of the current transaction affecting the quick report, determine whether it is repeated. If it is a repeated quick report, it will not be sent. If it is not a repeated quick report, continue to check the shielding rules.

[0071] Step 2, check whether the root cause system in the current transaction impact quick report is in the maintenance period. If yes, go to step 6, otherwise go to step 3. If it is determined to be yes, the current transaction impact quick report is generated by the root cause system under maintenance, and it is blocked and not sent. If it is determined to be no, proceed to the next step of checking.

[0072] Step 3, according to the root cause system or the impact system in the current transaction impact quick report, check whether the root cause system or the impact system is being changed. If so, go to step 6, otherwise go to step 4. That is, if it is determined to be yes, the current transaction impact quick report is generated by the changed root cause system and is blocked and not sent. If it is determined to be no, proceed to the next step of checking.

[0073] Step 4, according to the root cause system or the impact system in the current transaction impact quick report, check whether the root cause system or the impact system has been manually set to block the period. If so, go to step 6, otherwise go to step 5. If it is determined to be yes, the current transaction impact quick report is generated by the system that is manually set to be blocked, and it is blocked and not sent. If it is determined to be no, proceed to the next step of checking.

[0074] Step 5: Check whether the root cause system or the affected system is in the disaster recovery drill according to the root cause system or the affected system in the current transaction impact quick report. If yes, go to step 6, otherwise go to step 7. If it is judged as yes, the current transaction impact quick report is generated by the system in the disaster recovery drill, and it is blocked and not sent. If it is judged as no, it does not meet the blocking rules and can be sent normally.

[0075] In this embodiment, it can be seen that the method for sending transaction impact quick reports proposed in the present application can automatically identify duplicate transaction impact quick reports and blocked transaction impact quick reports, that is, based on the already generated transaction impact quick report data, the data of the root cause system, the affected system, the transaction code, the system maintenance period, the system change, and the system disaster recovery drill are obtained, and the sent quick reports within half an hour are found through a comparison method. In this way, the business rules of whether the influencing system and the root cause system are repeated are automatically identified, and then a series of blocked business rules such as whether the system is in the maintenance period, whether it is changing, and whether it is in a disaster recovery drill are automatically detected. Finally, non-duplicate or valid quick reports are determined and identified, which can effectively reduce duplicate and invalid transaction impact quick reports, improve the accuracy of transaction impact quick reports, and enable operation and maintenance personnel to quickly confirm the impact and severity of the fault, and locate and deal with the fault as early as possible, thereby improving the efficiency of operation and maintenance emergency response.

[0076] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0077] In this embodiment, a device for sending transaction impact quick report is also provided, which is used to implement the above embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0078] Figure 5 : is a structural block diagram of a device for sending a transaction impact quick report according to an embodiment of the present application, the device comprising:

[0079] A comparison module 52 is used to compare the collected current transaction impact quick report with the sent transaction impact quick report using a duplication judgment condition, and judge whether the current transaction impact quick report is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on historical transaction detail data;

[0080] The shielding judgment module 54 is used to judge whether the current transaction impact quick report is a shielded quick report by using a shielding business rule when it is determined that the current transaction impact quick report is not a duplicate quick report;

[0081] The sending module 56 is used to send the current transaction impact quick report to the target object when it is determined that the current transaction impact quick report does not belong to the blocked quick report.

[0082] Through the sending device of the transaction impact quick report of the embodiment of the present application, the collected current transaction impact quick report and the sent transaction impact quick report can be compared using the duplication judgment condition, and the current transaction impact quick report can be judged whether it is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on the historical transaction detail data; when it is determined that the current transaction impact quick report is not a duplicate quick report, the shielding business rule is used to judge whether the current transaction impact quick report is a shielded quick report; when it is determined that the current transaction impact quick report is not a shielded quick report, the current transaction impact quick report is sent to the target object. It can be seen that by adopting the above technical solution, by setting the duplication judgment condition and the shielding business rule, the probability of repeated sending and mis-sending quick reports in specific circumstances is reduced, and the accuracy and efficiency of sending transaction impact quick reports are improved. This method solves the problem of low operation and maintenance efficiency of the transaction system caused by the repeated sending of transaction impact quick reports, which can not only reduce unnecessary information interference, but also ensure that the transaction impact information is timely and accurately conveyed to the operation and maintenance personnel under the condition that the key business is not affected, thereby improving the operation and maintenance efficiency, thereby improving the overall operation quality and user experience of the system.

[0083] In an exemplary embodiment, the comparison module is further used to: when it is determined that the current transaction impact quick report has a root cause system, select a first judgment condition from preset judgment conditions, wherein the first judgment condition is that the root cause system of the current transaction impact quick report is the same as the root cause system of the sent transaction impact quick report, and there is an intersection between the affected system of the current transaction impact quick report and the affected system of the sent transaction impact quick report; when it is determined that the first judgment condition is met, determine that the current transaction impact quick report is a duplicate quick report.

[0084] In an exemplary embodiment, the comparison module is further used to: when it is determined that there is no root cause system in the current transaction impact quick report, select a second judgment condition from preset judgment conditions, wherein the second judgment condition is that there is an intersection between the affected system of the current transaction impact quick report and the affected system of the sent transaction impact quick report, and the transaction records with the highest transaction volume in the intersection have the same transaction code; when it is determined that the second judgment condition is met, determine that the current transaction impact quick report is a duplicate quick report.

[0085] In an exemplary embodiment, the shielding judgment module is also used to: determine whether the current transaction impact quick report is a shielded quick report based on a first shielding business rule, wherein the first shielding business rule indicates whether the root cause system of the current transaction impact quick report is in a maintenance period. For the root cause system in the maintenance period, the current transaction impact quick report is determined to be a shielded quick report.

[0086] In an exemplary embodiment, the shielding judgment module is also used to: for a root cause system that is not in a maintenance period, determine whether the current transaction impact quick report is a shielded quick report based on a second shielding business rule, wherein the second shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in the process of changing; and when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in the process of changing, determine that the current transaction impact quick report is a shielded quick report.

[0087] In an exemplary embodiment, the shielding judgment module is also used to: when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is not changing, determine whether the current transaction impact quick report is a shielded quick report according to a third shielding business rule, wherein the third shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report has a shielding period; when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report has a shielding period, determine that the current transaction impact quick report is a shielded quick report.

[0088] In an exemplary embodiment, the shielding judgment module is also used to: when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report does not have a shielding period, determine whether the current transaction impact quick report is a shielded quick report according to a fourth shielding business rule, wherein the fourth shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in a disaster recovery drill; when it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in a disaster recovery drill, determine that the current transaction impact quick report is a shielded quick report.

[0089] An embodiment of the present application further provides a storage medium, which includes a stored program, wherein any of the above embodiments is executed when the program is run.

[0090] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0091] S1, using a duplication judgment condition to compare the collected current transaction impact quick report with the sent transaction impact quick report, and judging whether the current transaction impact quick report is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on historical transaction detail data;

[0092] S2, when it is determined that the current transaction impact quick report is not a duplicate quick report, using a shielding business rule to determine whether the current transaction impact quick report is a shielded quick report;

[0093] S3: When it is determined that the current transaction impact quick report is not a blocked quick report, the current transaction impact quick report is sent to the target object.

[0094] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0095] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0096] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0097] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0098] S1, using a duplication judgment condition to compare the collected current transaction impact quick report with the sent transaction impact quick report, and judging whether the current transaction impact quick report is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on historical transaction detail data;

[0099] S2, when it is determined that the current transaction impact quick report is not a duplicate quick report, using a shielding business rule to determine whether the current transaction impact quick report is a shielded quick report;

[0100] S3: When it is determined that the current transaction impact quick report is not a blocked quick report, the current transaction impact quick report is sent to the target object.

[0101] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor. Specific examples in this embodiment may refer to the examples described in the above embodiments and exemplary implementations, and this embodiment will not be repeated here.

[0102] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0103] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for sending a transaction impact quick report, characterized in that: include: Comparing the collected current transaction impact quick report with the sent transaction impact quick report using a duplication judgment condition, and judging whether the current transaction impact quick report is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on historical transaction detail data; In the case where it is determined that the current transaction impact quick report is not a duplicate quick report, using a shielding business rule to determine whether the current transaction impact quick report is a shielded quick report; When it is determined that the current transaction impact quick report is not a blocked quick report, the current transaction impact quick report is sent to the target object.

2. The method for sending transaction impact quick report according to claim 1, characterized in that: The collected current transaction impact quick report and the sent transaction impact quick report are compared using a duplication judgment condition, and whether the current transaction impact quick report is a duplicate quick report is judged according to the comparison result, including: In the case where it is determined that the current transaction impact quick report has a root cause system, a first judgment condition is selected from the preset judgment conditions, wherein the first judgment condition is that the root cause system of the current transaction impact quick report is the same as the root cause system of the sent transaction impact quick report, and there is an intersection between the affected system of the current transaction impact quick report and the affected system of the sent transaction impact quick report; When it is determined that the first judgment condition is met, it is determined that the current transaction impact quick report is a duplicate quick report.

3. The method for sending transaction impact quick report according to claim 2, characterized in that: The collected current transaction impact quick report and the sent transaction impact quick report are compared using a duplication judgment condition, and whether the current transaction impact quick report is a duplicate quick report is judged according to the comparison result, including: When it is determined that the current transaction impact quick report does not have a root cause system, a second judgment condition is selected from the preset judgment conditions, wherein the second judgment condition is that there is an intersection between the affected system of the current transaction impact quick report and the affected system of the sent transaction impact quick report, and the transaction record with the highest transaction volume in the intersection has the same transaction code; When it is determined that the second judgment condition is met, it is determined that the current transaction impact quick report is a duplicate quick report.

4. The method for sending transaction impact quick report according to claim 1, characterized in that: Use the shielding business rules to determine whether the current transaction impact quick report is a shielded quick report, including: Determine whether the current transaction impact quick report is a shielded quick report based on the first shielding business rule, wherein the first shielding business rule indicates whether the root cause system of the current transaction impact quick report is in a maintenance period. For the root cause system in the maintenance period, determine that the current transaction impact quick report is a shielded quick report.

5. The method for sending transaction impact quick report according to claim 4, characterized in that: The method further comprises: For a root cause system that is not in maintenance period, judging whether the current transaction impact quick report is a shielded quick report according to a second shielding business rule, wherein the second shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is being changed; When it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is being changed, it is determined that the current transaction impact quick report is a blocked quick report.

6. The method for sending transaction impact quick report according to claim 5, characterized in that: The method further comprises: When it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is not being changed, judging whether the current transaction impact quick report is a shielded quick report according to a third shielding business rule, wherein the third shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report has a shielding period; When it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report has a shielding period, it is determined that the current transaction impact quick report is a shielded quick report.

7. The method for sending transaction impact quick report according to claim 6, characterized in that: The method further comprises: In the case where it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report does not have a shielding period, judging whether the current transaction impact quick report is a shielded quick report according to a fourth shielding business rule, wherein the fourth shielding business rule indicates whether the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in a disaster recovery drill; When it is determined that the root cause system of the current transaction impact quick report or the affected system of the current transaction impact quick report is in a disaster recovery drill, it is determined that the current transaction impact quick report is a blocked quick report.

8. A device for sending transaction impact quick report, characterized in that: include: A comparison module, used to compare the collected current transaction impact quick report with the sent transaction impact quick report using a duplication judgment condition, and judge whether the current transaction impact quick report is a duplicate quick report according to the comparison result, wherein the current transaction impact quick report is generated based on historical transaction detail data; A shielding judgment module, used for judging whether the current transaction impact quick report is a shielded quick report by using a shielding business rule when it is determined that the current transaction impact quick report is not a duplicate quick report; The sending module is used to send the current transaction impact quick report to the target object when it is determined that the current transaction impact quick report does not belong to the blocked quick report.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method described in any one of claims 1 to 7 when executed.

10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 7 through the computer program.

Images