System alarm method and device, electronic equipment, and storage medium

By configuring scene identifiers for configuration objects and aggregating alarm information with the same identifier, the problem of unconsidered inter-system correlation is solved, achieving the effect of reducing the number of alarm information and quickly locating faults.

CN113722184BActive Publication Date: 2024-11-08CHINA CONSTRUCTION BANK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111029041.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-09-01
Publication Date
2024-11-08
Estimated Expiration
2041-09-01

AI Technical Summary

Technical Problem

Existing system alarm methods fail to effectively consider the correlation between systems, resulting in an excessive number of alarm messages, excessive operational and maintenance pressure, and an inability to quickly locate the cause of the fault.

Method used

By configuring a scene identifier for each configuration object, the scene identifier of the alarm object is determined using alarm information. Alarm information with the same scene identifier is aggregated into the final alarm information and fed back to the user, reducing the number of alarm information and taking into account the correlation between systems.

Benefits of technology

It effectively reduced the number of alarm messages, quickly grasped the status of upstream and downstream systems in the transaction process, reduced the pressure on operation and maintenance, and improved the efficiency of fault location.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113722184B_ABST
    Figure CN113722184B_ABST
Patent Text Reader

Abstract

The present application discloses a system alarm method and device, an electronic device, and a storage medium, wherein the system alarm method includes: obtaining alarm information generated by each system; determining the alarm object corresponding to the alarm information based on the alarm information; wherein the alarm object is a configuration object that triggers the alarm; marking the alarm information with a pre-configured scene identifier of the alarm object; wherein the scene identifier of the alarm object is a scene identifier of a business scene to which the transaction line associated with the alarm object belongs; respectively aggregating each of the alarm information that is in the current aggregation cycle and is marked with the same scene identifier into a final alarm information; and feeding back each of the final alarm information to the user. Thus, the aggregation of alarm information is achieved through scene identification, the amount of alarm information is reduced, and it is also convenient to quickly locate system failures.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of system alarms, and in particular to a system alarm method and device, electronic equipment, and storage medium. Background Art

[0002] With the rapid development of banking business, the technical support work of the financial technology department has become increasingly important, so it is necessary to monitor the system in real time and issue alarms when problems occur.

[0003] The current system alarm method is mainly to monitor data through multiple monitoring systems separately, and when the indicator value of the monitored preset indicator item exceeds the corresponding alarm threshold, the alarm is triggered to generate alarm information, and after the alarm information is parsed and processed, it is fed back to the corresponding system operation and maintenance personnel via SMS, email, etc., so that the system operation and maintenance personnel can log in to the corresponding system for inspection and maintenance.

[0004] However, nowadays a business scenario usually requires multiple systems to collaborate with each other, so when an abnormality occurs in one system, it also affects other systems. That is, the abnormalities of each system are related to each other. The existing method directly feeds back the alarm information generated by each system to the operation and maintenance personnel of the corresponding system, and does not take into account the correlation between the abnormalities of each system. As a result, not only the number of alarm messages is too large, causing excessive operation and maintenance pressure, but also the failure details cannot be grasped as a whole, so the cause of the failure cannot be quickly located. Summary of the invention

[0005] Based on the above-mentioned deficiencies of the prior art, the present application provides a system alarm method and device, an electronic device, and a storage medium to solve the problem that the prior art is difficult to quickly locate the cause of the fault.

[0006] In order to achieve the above objectives, this application provides the following technical solutions:

[0007] The first aspect of the present application provides a system alarm method, comprising:

[0008] Get the alarm information generated by each system;

[0009] Determining an alarm object corresponding to the alarm information based on the alarm information; wherein the alarm object is a configuration object that triggers the alarm;

[0010] The alarm information is marked with a pre-configured scenario identifier of the alarm object; wherein the scenario identifier of the alarm object is a scenario identifier of a business scenario to which the transaction line associated with the alarm object belongs;

[0011] Aggregating the pieces of warning information that are in the current aggregation period and are marked with the same scenario identifier into one piece of final warning information;

[0012] Feedback each piece of final warning information to the user.

[0013] Optionally, in the above-mentioned system alarm method, before obtaining the alarm information generated by the monitoring system in the target system, the method further includes:

[0014] Determine a plurality of transaction lines under the business scenarios;

[0015] Configuring a scenario identifier for each of the business scenarios;

[0016] For each of the configuration objects, an association relationship is established between the configuration object and the scenario identifier of the business scenario described in each of the transaction lines associated with the configuration object.

[0017] Optionally, in the above-mentioned system alarm method, the determining of the transaction lines under the plurality of business scenarios includes:

[0018] Get the transaction flow information of each transaction in the historical time period;

[0019] Generate multiple transaction lines based on the acquired transaction information;

[0020] According to the business to which each transaction line belongs, each transaction line is divided to obtain multiple business scenarios.

[0021] Optionally, in the above-mentioned system alarm method, establishing, for each of the configuration objects, an association relationship between the configuration object and the scenario identifier of the business scenario of each of the transaction lines associated with the configuration object, includes:

[0022] For each of the configuration objects, determining each of the transaction lines associated with the configuration object;

[0023] The scenario identifiers of the business scenarios to which the transaction lines associated with the configuration object belong are respectively added to the attribute information of the configuration object.

[0024] Optionally, in the above-mentioned system alarm method, before marking the alarm information with the pre-configured scene identifier of the alarm object, the method further includes:

[0025] Determining whether the alarm object is the configuration object with a configured scene identifier;

[0026] If the alarm object is the configuration object that has been configured with a scene identifier, marking the alarm information with the scene identifier of the alarm object that has been pre-configured;

[0027] If the alarm object is the configuration object that is not configured with a scene identifier, the alarm information is fed back to the user.

[0028] A second aspect of the present application provides a system alarm device, comprising:

[0029] An alarm information acquisition unit, used to acquire alarm information generated by each system;

[0030] An alarm object determination unit, configured to determine an alarm object corresponding to the alarm information based on the alarm information; wherein the alarm object is a configuration object that triggers the alarm;

[0031] A marking unit, configured to mark the alarm information with a pre-configured scenario identifier of the alarm object; wherein the scenario identifier of the alarm object is a scenario identifier of a business scenario to which the transaction line associated with the alarm object belongs;

[0032] an aggregation unit, configured to aggregate the pieces of warning information that are in a current aggregation period and are marked with the same scenario identifier into one piece of final warning information;

[0033] The first alarm unit is used to feed back each piece of the final alarm information to the user.

[0034] Optionally, in the above-mentioned system alarm device, it also includes:

[0035] A transaction line determination unit, configured to determine a plurality of transaction lines under the business scenarios;

[0036] An identification configuration unit, used to configure a scenario identification of each of the business scenarios;

[0037] An associating unit is used to establish, for each of the configuration objects, an associating relationship between the configuration object and the scenario identifier of the business scenario described in each of the transaction lines associated with the configuration object.

[0038] Optionally, in the above-mentioned system alarm device, the transaction line determination unit includes:

[0039] A transaction information acquisition unit, used to acquire transaction information of each transaction within a historical period;

[0040] A generating unit, configured to generate a plurality of transaction lines based on the acquired transaction flow information;

[0041] The division unit is used to divide each of the transaction lines according to the business to which each of the transaction lines belongs, so as to obtain multiple business scenarios.

[0042] Optionally, in the above-mentioned system alarm device, the association unit includes:

[0043] A first determining unit, configured to determine, for each of the configuration objects, the transaction lines associated with the configuration object;

[0044] An adding unit is used to add the scenario identifier of the business scenario to which each of the transaction lines associated with the configuration object belongs to the attribute information of the configuration object.

[0045] Optionally, in the above-mentioned system alarm device, it also includes:

[0046] A judging unit, configured to judge whether the alarm object is the configuration object with a configured scene identifier; wherein, if the alarm object is the configuration object with a configured scene identifier, the marking unit performs the marking of the alarm information using the pre-configured scene identifier of the alarm object;

[0047] The second alarm unit is configured to feed back the alarm information to the user if the alarm object is the configuration object that is not configured with a scene identifier.

[0048] A third aspect of the present application provides an electronic device, including:

[0049] Memory and processor;

[0050] Wherein, the memory is used to store programs;

[0051] The processor is used to execute the program, and when the program is executed, it is specifically used to implement the system alarm method as described in any one of the above items.

[0052] A fourth aspect of the present application provides a computer storage medium for storing a computer program, wherein when the computer program is executed, it is used to implement the system alarm method as described in any one of the above.

[0053] The present application provides a system alarm method, which configures a scene identifier for each configuration object in advance, and then obtains the alarm information generated by each system, and determines the alarm object corresponding to the alarm information based on the alarm information, wherein the alarm object is the configuration object that triggers the alarm. Then, the alarm information is marked with the scene identifier of the pre-configured alarm object, so that each alarm information in the current aggregation cycle and marked with the same scene identifier can be respectively aggregated into a final alarm information, and finally each final alarm information is fed back to the user, thereby realizing the system alarm. Since the scene identifier of the alarm object is the scene identifier of the business scene to which the transaction line associated with the alarm object belongs, the alarm information marked with the same scene identifier is aggregated into a final alarm information, which not only effectively reduces the number of alarm information fed back, but also takes into account the association relationship between systems when an abnormality occurs, so that the user can quickly grasp the situation of other systems downstream of the transaction line directly through the final alarm information, without logging into the system for one by one investigation. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] 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, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0055] Figure 1 A flowchart of a system alarm method provided in an embodiment of the present application;

[0056] Figure 2 A flowchart of a method for configuring a scene identifier of a configuration object provided in an embodiment of the present application;

[0057] Figure 3 A schematic diagram of a transaction line shown as an example provided in an embodiment of the present application;

[0058] Figure 4 A flowchart of a method for determining a transaction line in a business scenario provided in an embodiment of the present application;

[0059] Figure 5 A flowchart of a method for configuring an object-associated scene identifier provided in an embodiment of the present application;

[0060] Figure 6 A flowchart of another system alarm method provided in another embodiment of the present application;

[0061] Figure 7 A schematic diagram of the structure of a system alarm device provided in another embodiment of the present application;

[0062] Figure 8 A schematic diagram of the structure of a transaction line determination unit provided in another embodiment of the present application;

[0063] Fig. 9 A structural schematic diagram of an association unit provided in another embodiment of the present application;

[0064] Fig.10 A schematic diagram of the structure of an electronic device provided in another embodiment of the present application. DETAILED DESCRIPTION

[0065] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions 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 are within the scope of protection of this application.

[0066] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0067] The present application embodiment provides a system alarm method, such as Figure 1 As shown, the specific steps include the following:

[0068] S101. Obtain alarm information generated by each system.

[0069] Specifically, each system can be monitored in real time, and when each system has an abnormality and generates alarm information, the alarm information generated by each system can be obtained.

[0070] S102: Determine an alarm object corresponding to the alarm information based on the alarm information.

[0071] The alarm object is the configuration object that triggers the alarm. The configuration object refers to the object with configuration information in the system, which can be a system, an unfamiliar unit, a virtual machine, a transaction code, etc.

[0072] Optionally, the alarm information may include the name or identifier of the alarm object that triggers the alarm, which can be used to determine the alarm object, so the relevant information of the alarm object can be extracted from the alarm information, and the alarm object corresponding to the alarm information can be determined, that is, the alarm object that triggers the alarm information can be determined. Of course, other methods for determining the corresponding alarm object based on the alarm information can also be used.

[0073] S103: Mark the alarm information with a pre-configured scenario identifier of the alarm object, where the scenario identifier of the alarm object is a scenario identifier of a business scenario to which the transaction line associated with the alarm object belongs.

[0074] Among them, a transaction line consists of multiple nodes connected by directed lines. Each node corresponds to a system, and each system implements a specific transaction in the order of connection. The configuration object associated with the transaction line refers to the configuration object related to the transaction line, for example, the system that constitutes the transaction line, and the transaction code related to the transaction line.

[0075] It should be noted that the implementation of the embodiment of the present application requires the configuration of the scene identifier of the configuration object in advance, so that when the configuration object is an alarm object, the scene identifier of the configuration object is used to mark the alarm information later.

[0076] Optionally, another embodiment of the present application provides a method for configuring a scene identifier of a configuration object, such as Figure 2 As shown, including:

[0077] S201. Determine transaction lines under multiple business scenarios.

[0078] Specifically, multiple transaction lines are obtained, and then the obtained transaction lines are divided into multiple business scenarios according to the business meaning of the transaction lines. Figure 3 The "Third-Party Payment Service (Big Promotion) - China UnionPay" shown is composed of multiple transaction lines. Each base point represents a system, and the lines between the nodes represent the calling relationship between the systems.

[0079] Optionally, in another embodiment of the present application, a specific implementation of step S201 is as follows: Figure 4 As shown, the following steps are included:

[0080] S401. Obtain transaction flow information for each transaction within a historical period.

[0081] Specifically, the flow information of each transaction can be recorded by the application monitoring system according to the transaction code, and then the flow information of each transaction in the historical time can be obtained, for example, the flow information of all transactions in the previous day can be obtained.

[0082] S402: Generate multiple transaction lines based on the acquired transaction information.

[0083] S403. Divide each transaction line according to the business to which it belongs, and obtain multiple business scenarios.

[0084] S202: Configure a scenario identifier for each business scenario.

[0085] S203: For each configuration object, establish an association relationship between the configuration object and the scenario identifier of the business scenario of each transaction line associated with the configuration object.

[0086] It should be noted that if a configuration object is associated with multiple transaction lines, an association relationship between the configuration object and the scenario identifier of the business scenario to which each transaction line belongs is established respectively, thereby realizing the configuration of the scenario identifier of the configuration object.

[0087] Optionally, in the embodiment of the present application, a specific implementation of step S203 is as follows: Figure 5 As shown, the following steps are included:

[0088] S501. For each configuration object, determine each transaction line associated with the configuration object.

[0089] S502: Add the scenario identifiers of the business scenarios to which the transaction lines associated with the configuration object belong to the configuration object to the attribute information of the configuration object.

[0090] It should be noted that each configuration object itself has corresponding attribute information. In the embodiment of the present application, an attribute is added to the attribute information of the configuration object, that is, the scene identifier of the business scene to which each transaction line associated with the configuration object belongs is added, thereby realizing the association relationship between the configuration object and the scene identifier.

[0091] It should also be noted that a business scenario involves multiple systems, multiple deployment units, multiple virtual machines, multiple transaction codes, etc. Then, the scenario identifier of the business scenario is configured as the scenario identifier of each configuration object involved.

[0092] A configuration object can be associated with one transaction line or multiple transaction lines at the same time. For example, a system can belong to only one transaction line, but the system can also belong to multiple transaction lines at the same time, and these transaction lines need to use the system to implement corresponding transaction processing. Therefore, a configuration object can have one or more scenario identifiers. When marking the alarm information with the scenario identifier of the pre-configured alarm object, all scenario identifiers of each alarm object are marked with the alarm message. Therefore, an alarm message can be marked with multiple business scenario identifiers.

[0093] Optionally, if there are multiple alarm objects corresponding to the alarm information and they have the same scene identifier, then when marking the alarm information, only one of the same scene identifiers may be marked.

[0094] S104: Aggregate each piece of alarm information that is in the current aggregation period and is marked with the same scene identifier into one piece of final alarm information.

[0095] It should be noted that, since an alarm message can be marked with multiple scene identifiers, an alarm message can be aggregated with multiple other alarm messages. As long as there is any scene identifier like it between the alarm messages, it will be aggregated as a set to obtain a final alarm message. So, an alarm message can be in multiple sets and aggregated to obtain different final alarm messages. For example, alarm message 1 has two scene identifiers A and B, alarm message 2 has three scene identifiers B, C, and D, and alarm message 3 has four scene identifiers D, E, F, and G. When aggregated, alarm message 1 and alarm message 2 are aggregated together because they have the same scene identifier B, and alarm message 2 and alarm message 3 are aggregated together because they have the same scene identifier D. However, scene message 1 and scene message 3 do not have the same scene identifier, so they cannot be aggregated.

[0096] It should be noted that, for alarm information that does not have the same scene identifier as other alarm information, that is, alarm information that cannot be merged with other alarm information, the alarm information is directly determined as a final alarm information to be fed back to the user.

[0097] S105: Feedback each final warning information to the user.

[0098] The embodiment of the present application provides a system alarm method, which configures a scene identifier for each configuration object in advance, and then obtains the alarm information generated by each system, and determines the alarm object corresponding to the alarm information based on the alarm information, wherein the alarm object is the configuration object that triggers the alarm. Then, the alarm information is marked with the scene identifier of the pre-configured alarm object, so that each alarm information in the current aggregation cycle and marked with the same scene identifier can be respectively aggregated into a final alarm information, and finally each final alarm information is fed back to the user, thereby realizing the system alarm. Since the scene identifier of the alarm object is the scene identifier of the business scene to which the transaction line associated with the alarm object belongs, the alarm information marked with the same scene identifier is aggregated into a final alarm information, which not only effectively reduces the number of alarm information fed back, but also takes into account the association relationship between systems when an abnormality occurs, so that the user can quickly grasp the situation of other systems downstream of the transaction line directly through the final alarm information, without logging into the system for one by one investigation.

[0099] Another embodiment of the present application provides another system alarm method, such as Figure 6 As shown, the following steps are included:

[0100] S601. Determine transaction lines under multiple business scenarios.

[0101] It should be noted that the specific implementation of step S601 may refer to step S201 accordingly and will not be described in detail here.

[0102] S602: Configure a scenario identifier for each business scenario.

[0103] S603: For each business scenario, establish an association relationship between each configuration object associated with each transaction line under the business scenario and the scenario identifier of the business scenario.

[0104] In the embodiment of the present application, for each business scenario, each configuration object involved in the business scenario is associated with the scenario identifier of the business scenario, and specifically, the scenario identifier of the business scenario is added to the attribute information of each configuration object involved in the business scenario.

[0105] S604: Obtain alarm information generated by each system.

[0106] It should be noted that the specific implementation of step S604 may refer to step S101 accordingly, and will not be described in detail here.

[0107] S605: Determine an alarm object corresponding to the alarm information based on the alarm information.

[0108] The alarm object is the configuration object that triggers the alarm.

[0109] It should be noted that the specific implementation of step S605 may refer to step S102 accordingly, and will not be described in detail here.

[0110] S606: Determine whether the alarm object is a configuration object that has been configured with a scenario identifier.

[0111] Considering that the system is relatively complex, the alarm object may be a configuration object that is not configured with a scene identifier. At this time, it is impossible to mark the alarm information and perform subsequent aggregation, but the alarm information needs to be fed back to the user. Therefore, in an embodiment of the present application, it is first determined whether the alarm object is a configuration object that has been configured with a scene identifier. Specifically, the determination can be made based on whether there is a scene identifier in the attribute information of the alarm object.

[0112] If it is determined whether the alarm object is a configuration object that is not configured with a scene identifier, step S607 is executed; if it is determined whether the alarm object is a configuration object that is configured with a scene identifier, step S608 is executed.

[0113] S607: Feedback the warning information to the user.

[0114] S608: Mark the alarm information using the pre-configured scene identifier of the alarm object.

[0115] The scenario identifier of the alarm object is the scenario identifier of the business scenario to which the transaction line associated with the alarm object belongs.

[0116] It should be noted that the specific implementation of step S608 may refer to step S103 accordingly, and will not be repeated here.

[0117] S609: Aggregate each piece of alarm information that is in the current aggregation period and is marked with the same scenario identifier into one piece of final alarm information.

[0118] It should be noted that the specific implementation of step S609 may refer to step S104 accordingly, and will not be described in detail here.

[0119] S610: Feedback each final warning information to the user.

[0120] It should be noted that the specific implementation of step S610 may refer to step S105 accordingly, and will not be repeated here.

[0121] Another embodiment of the present application provides a system alarm device, such as Figure 7 As shown, it includes the following units:

[0122] The alarm information acquisition unit 701 is used to acquire the alarm information generated by each system.

[0123] The alarm object determining unit 702 is used to determine the alarm object corresponding to the alarm information based on the alarm information.

[0124] The alarm object is the configuration object that triggers the alarm.

[0125] The marking unit 703 is used to mark the alarm information using the pre-configured scene identifier of the alarm object.

[0126] The scenario identifier of the alarm object is the scenario identifier of the business scenario to which the transaction line associated with the alarm object belongs.

[0127] The aggregation unit 704 is used to aggregate the pieces of warning information that are in the current aggregation period and are marked with the same scenario identifier into one piece of final warning information.

[0128] The first alarm unit 705 is used to feed back each final alarm information to the user.

[0129] Optionally, in another embodiment of the present application, the system alarm device further includes:

[0130] The transaction line determination unit is used to determine the transaction lines under multiple business scenarios.

[0131] The identification configuration unit is used to configure the scenario identification of each business scenario.

[0132] The association unit is used to establish, for each configuration object, an association relationship between the configuration object and a scenario identifier of a business scenario of each transaction line associated with the configuration object.

[0133] Optionally, in a system alarm device provided in another embodiment of the present application, the transaction line determination unit, such as Figure 8 As shown, including:

[0134] The transaction information acquisition unit 801 is used to acquire the transaction information of each transaction in a historical time period.

[0135] The generating unit 802 is used to generate multiple transaction lines based on the acquired transaction information.

[0136] The division unit 803 is used to divide each transaction line according to the business to which each transaction line belongs, so as to obtain multiple business scenarios.

[0137] Optionally, in a system alarm device provided in another embodiment of the present application, the association unit, such as Fig. 9 As shown, including:

[0138] The first determining unit 901 is used to determine, for each configuration object, each transaction line associated with the configuration object.

[0139] The adding unit 902 is used to add the scenario identifier of the business scenario to which each transaction line associated with the configuration object belongs to into the attribute information of the configuration object.

[0140] Optionally, in another embodiment of the present application, the system alarm device further includes:

[0141] The judging unit is used to judge whether the alarm object is a configuration object with a configured scene identifier.

[0142] If the alarm object is a configuration object that has been configured with a scene identifier, the marking unit marks the alarm information using the scene identifier of the pre-configured alarm object.

[0143] The second alarm unit is used to feed back alarm information to the user if the alarm object is a configuration object that is not configured with a scene identifier.

[0144] It should be noted that the specific working process of each unit provided in the above embodiments of the present application can refer to the corresponding steps in the above method embodiments, which will not be repeated here.

[0145] Another embodiment of the present application provides an electronic device, such as Fig.10 As shown, including:

[0146] Memory 1001 and processor 1002 .

[0147] The memory 1001 is used to store programs.

[0148] The processor 1002 is used to execute the program stored in the memory 1001, and when the program is executed, it is specifically used to implement the system alarm method provided in any one of the above embodiments.

[0149] Another embodiment of the present application provides a computer storage medium for storing a computer program. When the computer program is executed, it is used to implement the system alarm method provided in any one of the above embodiments.

[0150] Computer storage media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0151] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0152] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A system alarm method, characterized in that: include: Get the alarm information generated by each system; Determining an alarm object corresponding to the alarm information based on the alarm information; wherein the alarm object is a configuration object that triggers the alarm; The alarm information is marked with all scenario identifiers of the alarm object configured in advance; wherein the scenario identifier of the alarm object is the scenario identifier of the business scenario to which the transaction line associated with the alarm object belongs; the transaction line includes various systems that implement specific transaction transactions in a connection order; the configuration object associated with the transaction line refers to the configuration object related to the transaction line, including: the systems constituting the transaction line; and each of the configuration objects has one or more scenario identifiers; Aggregating the pieces of warning information that are in the current aggregation period and are marked with the same scenario identifier into one piece of final warning information; Feedback each piece of final warning information to the user.

2. The method according to claim 1, characterized in that Before obtaining the alarm information generated by each system, the method further includes: Determine a plurality of transaction lines under the business scenarios; Configuring a scenario identifier for each of the business scenarios; For each of the configuration objects, an association relationship is established between the configuration object and the scenario identifier of the business scenario described in each of the transaction lines associated with the configuration object.

3. The method according to claim 2, characterized in that The determining of the transaction lines under the plurality of business scenarios includes: Get the transaction flow information of each transaction in the historical time period; Generate multiple transaction lines based on the acquired transaction information; According to the business to which each transaction line belongs, each transaction line is divided to obtain multiple business scenarios.

4. The method according to claim 2, characterized in that: The step of establishing, for each of the configuration objects, an association relationship between the configuration object and the scenario identifier of the business scenario of each of the transaction lines associated with the configuration object comprises: For each of the configuration objects, determining each of the transaction lines associated with the configuration object; The scenario identifiers of the business scenarios to which the transaction lines associated with the configuration object belong are respectively added to the attribute information of the configuration object.

5. The method according to claim 1, characterized in that Before marking the alarm information with the pre-configured scene identifier of the alarm object, the method further includes: Determining whether the alarm object is the configuration object with a configured scene identifier; If the alarm object is the configuration object that has been configured with a scene identifier, marking the alarm information with the scene identifier of the alarm object that has been pre-configured; If the alarm object is the configuration object that is not configured with a scene identifier, the alarm information is fed back to the user.

6. A system alarm device, characterized in that: include: An alarm information acquisition unit, used to acquire alarm information generated by each system; An alarm object determination unit, configured to determine an alarm object corresponding to the alarm information based on the alarm information; wherein the alarm object is a configuration object that triggers the alarm; a marking unit, configured to mark the alarm information with all scenario identifiers of the alarm object pre-configured; wherein the scenario identifier of the alarm object is the scenario identifier of the business scenario to which the transaction line associated with the alarm object belongs; the transaction line includes various systems that implement specific transaction transactions in a connection order; the configuration object associated with the transaction line refers to the configuration object related to the transaction line, including: the systems constituting the transaction line; and each of the configuration objects has one or more scenario identifiers; an aggregation unit, configured to aggregate the pieces of warning information that are in a current aggregation period and are marked with the same scenario identifier into one piece of final warning information; The first alarm unit is used to feed back each piece of the final alarm information to the user.

7. The device according to claim 6, characterized in that Also includes: A transaction line determination unit, configured to determine a plurality of transaction lines under the business scenarios; An identification configuration unit, used to configure a scenario identification of each of the business scenarios; An associating unit is used to establish, for each of the configuration objects, an associating relationship between the configuration object and the scenario identifier of the business scenario described in each of the transaction lines associated with the configuration object.

8. The device according to claim 7, characterized in that The transaction line determination unit includes: A transaction information acquisition unit, used to acquire transaction information of each transaction within a historical period; A generating unit, configured to generate a plurality of transaction lines based on the acquired transaction flow information; The division unit is used to divide each of the transaction lines according to the business to which each of the transaction lines belongs, so as to obtain multiple business scenarios.

9. An electronic device, characterized in that: include: Memory and processor; Wherein, the memory is used to store programs; The processor is used to execute the program, and when the program is executed, it is specifically used to implement the system alarm method as described in any one of claims 1 to 5.

10. A computer storage medium, characterized in that: Used to store a computer program, which, when executed, is used to implement the system alarm method as described in any one of claims 1 to 5.