Group management method and device for fault alarm response, equipment and medium

Abstract

The invention discloses a group management method, device and equipment for fault alarm response and a medium, and the method comprises the steps: monitoring a service system configured in a management server to judge whether a fault occurs, generating corresponding fault alarm information if the fault occurs, directly determining a group as a target group if an alarm processing group is established, and sending the alarm processing group to the management server; if the alarm processing group is not established, judging whether the fault alarm information is matched with the historical fault alarm response or not; and if the historical fault alarm response is matched with the fault alarm information, adding a concerning person corresponding to the fault alarm information into an alarm processing group corresponding to the historical fault alarm response and taking the alarm processing group as a target group, and if the historical fault alarm response is not matched with the historical fault alarm response, newly establishing an alarm processing group as the target group, and pushing detailed fault information of the fault alarm information in the target group. According to the group management method, whether a fault occurs or not can be monitored continuously, and group pulling can be carried out in time to push detailed fault information; therefore, the fault alarm pushing efficiency and accuracy are improved, and the fault solving speed is improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and particularly to a group management method, device, equipment and medium for fault alarm response. Background Art

[0002] During the research and development, operation, and maintenance of software systems, faults often occur, and the response efficiency to fault alarms directly affects the stability of the system and the user experience. As the scale of the system gradually expands, the types and complexity of fault alarms increase day by day, and the traditional fault alarm response process often fails to meet the need for quickly solving problems. Existing technologies usually rely on linear communication when conducting fault alarms, resulting in delays in fault handling due to poor information transmission. In addition, when team members work at different times and in different locations, there is a lack of effective collaboration tools, and the phenomenon of information silos is serious. These drawbacks lead to low response efficiency of fault alarms, and it is impossible to achieve fast and efficient response and solution to fault alarms. Therefore, there is a problem of poor information transmission in the communication method for fault alarm response in existing technical methods. Summary of the Invention

[0003] Embodiments of the present invention provide a group management method, device, equipment and medium for fault alarm response, aiming to solve the problem of poor information transmission in the communication method for fault alarm response in existing technical methods.

[0004] In a first aspect, embodiments of the present invention provide a group management method for fault alarm response. The method is applied to a management server, and the management server establishes a network connection with each user terminal to achieve data information transmission. The method includes:

[0005] Continuously monitor the business system configured in the management server according to preset monitoring indicators to determine whether a fault occurs;

[0006] If a fault occurs, obtain information related to the fault to generate a corresponding fault alarm information;

[0007] If the fault alarm information has formed a corresponding alarm handling group, determine it as the target group;

[0008] If the fault alarm information has not formed a corresponding alarm handling group, determine whether the fault alarm information matches the historical fault alarm response in a preset historical alarm library;

[0009] If the fault alarm information matches the historical fault alarm response, add the person concerned corresponding to the fault alarm information to the alarm handling group corresponding to the historical fault alarm response and use it as the target group;

[0010] If the fault warning information does not match the historical fault warning response, a new warning handling group is formed according to the concerned persons corresponding to the fault warning information, and it is used as the target group;

[0011] Obtain the detailed fault information of the fault warning information and push it within the target group, so that the user terminals corresponding to each concerned person in the target group receive the detailed fault information.

[0012] In a second aspect, an embodiment of the present invention further provides a group management device for fault warning response. Among them, the device is configured in a management server, and the management server establishes a network connection with each user terminal to realize the transmission of data information. The device is used to execute the group management method for fault warning response described in the first aspect above. The device includes:

[0013] A system monitoring unit, which is used to continuously monitor the service system configured in the management server according to preset monitoring indicators to judge whether a fault occurs;

[0014] An alarm information acquisition unit, which is used to obtain information related to the fault to generate corresponding fault alarm information if a fault occurs;

[0015] A target group determination unit, which is used to determine it as the target group if the fault warning information has formed a corresponding warning handling group;

[0016] A matching judgment unit, which is used to judge whether the fault warning information matches the historical fault warning response in a preset historical warning library if the fault warning information has not formed a corresponding warning handling group;

[0017] An adding unit, which is used to add the concerned persons corresponding to the fault warning information to the warning handling group corresponding to the historical fault warning response and use it as the target group if the fault warning information matches the historical fault warning response;

[0018] A forming unit, which is used to form a new warning handling group according to the concerned persons corresponding to the fault warning information and use it as the target group if the fault warning information does not match the historical fault warning response;

[0019] An information pushing unit, which is used to obtain the detailed fault information of the fault warning information and push it within the target group, so that the user terminals corresponding to each concerned person in the target group receive the detailed fault information.

[0020] In a third aspect, an embodiment of the present invention further provides a computer device. Among them, the device includes a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete mutual communication through the communication bus;

[0021] A memory for storing computer programs;

[0022] A processor, when executing the program stored in the memory, implements the steps of the group management method for fault alarm response described in the first aspect above.

[0023] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, wherein when the computer program is executed by a processor, the steps of the group management method for fault alarm response described in the first aspect above are implemented.

[0024] An embodiment of the present invention provides a group management method, device, equipment and medium for fault alarm response. The method includes: monitoring the business systems configured in the management server to determine whether a fault occurs. If a fault occurs, corresponding fault alarm information is generated. If an alarm handling group has been formed, the group is directly determined as the target group. If an alarm handling group has not been formed, it is determined whether the fault alarm information matches the historical fault alarm response. If they match, the person concerned corresponding to the fault alarm information is added to the alarm handling group corresponding to the historical fault alarm response and used as the target group. If they do not match, a new alarm handling group is created as the target group, and the detailed fault information of the fault alarm information is pushed within the target group. The above group management method for fault alarm response can continuously monitor whether a fault occurs. When a fault occurs, it can intelligently judge the correlation between the current fault alarm and the historical fault alarm response, and promptly form a group to push the detailed fault information, reducing the communication cost; greatly improving the efficiency and accuracy of fault alarm pushing, thereby enhancing the speed of fault resolution. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0026] Figure 1 It is a flowchart of the method for the group management method for fault alarm response provided by the embodiment of the present invention;

[0027] Figure 2 It is a schematic diagram of the application scenario of the group management method for fault alarm response provided by the embodiment of the present invention;

[0028] Figure 3 It is a schematic block diagram of the group management device for fault alarm response provided by the embodiment of the present invention;

[0029] Figure 4 It is a schematic block diagram of a computer device provided by an embodiment of the present invention. Detailed implementation manners

[0030] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0031] It should be understood that when used in this specification and the appended claims, the terms "comprises" and "comprising" indicate the presence of the described features, wholes, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0032] It should also be understood that the terms used in the specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms.

[0033] It should be further understood that the term "and / or" used in the specification of the present invention and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0034] An embodiment of the present invention provides a group management method for fault alarm response. This method is applied to a management server 10. The management server 10 executes the stored software program to implement the above-mentioned group management method for fault alarm response; the management server 10 can be a server side configured in an enterprise or institution for monitoring a business system to create a group and push fault alarms. The management server 10 can be a server device such as a cluster server or a parallel processing server. Please refer to Figure 2, as shown in the figure, the management server 10 establishes a network connection with each of the user terminals 20 to achieve the transmission of data information. Among them, the user terminal 20 can be devices such as a laptop, a desktop computer, a tablet computer, or a mobile phone. The user terminal 20 is also the terminal device used by software developers within an enterprise or institution. When a fault occurs in the business system, a fault alarm needs to be pushed to the corresponding user terminal 20. The software developer corresponding to the user terminal 20 views the fault alarm information displayed in the user terminal 20, so that the corresponding software developer can obtain the detailed fault information of the fault alarm in time to quickly handle the fault in the business system. As Figure 1 shown, the method includes steps S110 to S170.

[0035] S110. Continuously monitor the business system configured in the management server according to the preset monitoring indicators to determine whether a fault has occurred.

[0036] Continuously monitor the business system configured in the management server according to the preset monitoring indicators to determine whether a fault has occurred. The management server can continuously monitor the business system according to the preset monitoring indicators. Specifically, the monitoring period can be set to 10 seconds, and then the business system is monitored according to the monitoring indicators every 10 seconds to determine whether a fault has occurred in the business system.

[0037] In a specific embodiment, step S110 includes sub-steps: obtaining the index item value corresponding to the monitoring indicator in the business system; determining whether any of the index item values does not match the preset numerical range in the corresponding monitoring indicator to determine whether a fault has occurred.

[0038] Specifically, each time the business system is monitored, the index item values corresponding to the monitoring indicators can be obtained. The monitoring indicators can be access delay time, request throughput, node processing time-consuming, network traffic, page display information, etc. Each monitoring indicator corresponds to a preset numerical range, and then it can be determined whether the obtained index item value is within the preset numerical range of the corresponding monitoring indicator. If the index item value is within the corresponding preset numerical range, it indicates that the index item value matches the corresponding monitoring indicator; if the index item value is not within the corresponding preset numerical range, it indicates that the index item value does not match the corresponding monitoring indicator. If any index item value does not match the corresponding monitoring indicator, it is determined that a fault has occurred in the business system; if all index item values match the corresponding monitoring indicators, it is determined that no fault has occurred in the business system.

[0039] S120. If a fault occurs, obtain the information related to the fault to generate a corresponding fault alarm information.

[0040] If a failure occurs, obtain information related to the failure to generate a corresponding failure alarm message. If a failure occurs, trigger the corresponding alarm rule and initiate a failure alarm response. Information related to the failure can be obtained according to the alarm rule triggered by the failure, and the information related to the failure is integrated to generate a corresponding failure alarm message. The failure alarm message is also the information recording the content associated with the failure. If no failure occurs, return to execute step S110 after an interval monitoring period.

[0041] In a specific embodiment, step S120 includes sub-steps: obtaining the processing department corresponding to the failure as the target department; obtaining the person in charge corresponding to the failure within the target department; obtaining the rule identifier corresponding to the failure; and combining the target department, the person in charge, and the rule identifier into a failure alarm message corresponding to the failure.

[0042] Specifically, first, the alarm rule triggered by the failure can be determined. Different failures trigger different alarm rules; the same failure can trigger one or more alarm rules. Each alarm rule corresponds to an alarm department. The alarm department corresponding to the alarm rule triggered by the failure can be obtained and determined as the processing department corresponding to the failure, and the corresponding processing department is used as the target department. The alarm rule can divide different failures into different processing departments for processing. For example, the alarm rule triggered by the failure is a background software failure alarm, and the corresponding processing department of this alarm rule is the backend department; if the alarm rule triggered by the failure is a database failure, the corresponding processing department of this alarm rule is the data management department.

[0043] Furthermore, the person in charge corresponding to the alarm rule triggered by the failure can be obtained according to the target department. There is a job type set in the alarm rule, and the person in charge within the target department matching the job type triggered by the alarm rule can be obtained. For example, if the job types in an alarm rule include supervisor, technician, and tester, then all personnel within the target department whose positions match the supervisor, technician, and tester can be obtained as the corresponding persons in charge.

[0044] Furthermore, obtain the target department, the person in charge, and the rule identifier of the alarm rule triggered by the current failure, and combine them to obtain a failure alarm message corresponding to the failure. Furthermore, the failure alarm message also includes information such as the time point when the failure occurred.

[0045] The management server can judge whether to respond to the generated failure alarm message at intervals of a certain alarm processing time. For example, the alarm processing time can be set to 5 minutes, then every 5 minutes, a scan is performed on whether there are generated but unresponded failure alarm messages; thereby, the generated but unresponded failure alarm messages are obtained for alarm push processing.

[0046] S130. If the fault alarm information has formed a corresponding alarm handling group, it is determined as the target group.

[0047] If the fault alarm information has formed a corresponding alarm handling group, it is determined as the target group. It can be judged whether the rule identifier corresponding to the fault alarm information has formed an alarm handling group. If multiple alarm rules are triggered by the same fault, there is no need to repeatedly establish an alarm handling group. Only one alarm handling group needs to be established. It can be judged whether the fault occurrence time point and rule identifier corresponding to the established alarm handling group match the fault alarm information. If the fault occurrence time point of the alarm handling group matches the fault alarm information, and the rule identifier of this group matches any one of the rule identifiers in the fault alarm information, it indicates that the fault alarm information has formed a corresponding alarm handling group. At this time, there is no need to reconstruct the group, and the alarm handling group currently matching the fault alarm information can be determined as the target group. If the fault occurrence time point of the alarm handling group does not match the fault alarm information, or the rule identifier of the alarm handling group does not match any one of the rule identifiers in the fault alarm information, it indicates that the fault alarm information does not match this alarm handling group.

[0048] S140. If the fault alarm information has not formed a corresponding alarm handling group, it is judged whether the fault alarm information matches the historical fault alarm response in the preset historical alarm library.

[0049] If the fault alarm information has not formed a corresponding alarm handling group, it is judged whether the fault alarm information matches the historical fault alarm response in the preset historical alarm library. The management server is also configured with a historical alarm library, which stores historical fault alarm responses. Each historical fault alarm response corresponds to the response record information of a fault alarm for a fault that has occurred. If the fault alarm information has not formed an alarm handling group, it can be further judged whether the fault alarm information matches the historical fault alarm response.

[0050] In a specific embodiment, step S140 includes sub-steps: screening out the historical fault alarm responses that meet the status screening conditions from the historical alarm library according to the preset status screening conditions; judging whether the rule identifier and target department of the fault alarm information match the screened historical fault alarm responses to determine whether the fault alarm information matches the historical fault alarm response.

[0051] Specifically, the historical fault alarm responses in the historical alarm library can be filtered according to the status filtering conditions, so as to obtain the historical fault alarm responses that meet the status filtering conditions. Among them, the status filtering conditions may include that the alarm status is not recovered and the alarm parameter is that a response has been initiated. Through the status filtering conditions, some historical fault alarm responses that meet the status filtering conditions can be filtered out.

[0052] Furthermore, the corresponding rule identifier, target department, and group identifier are recorded in the historical fault alarm response. The group identifier is also the identification information of the alarm handling corresponding to the historical fault alarm response. It can be judged whether the rule identifier and target department of the fault alarm information match the historical fault alarm response obtained by filtering. If both the rule identifier and the target department match a certain historical fault alarm response, it is determined that the fault alarm information matches the historical fault alarm response. If the rule identifier or the target department does not match the historical fault alarm response, it is determined that the fault alarm information does not match the historical fault alarm response.

[0053] S150. If the fault alarm information matches the historical fault alarm response, add the person concerned corresponding to the fault alarm information to the alarm handling group corresponding to the historical fault alarm response and use it as the target group.

[0054] If the fault alarm information matches the historical fault alarm response, add the person concerned corresponding to the fault alarm information to the alarm handling group corresponding to the historical fault alarm response and use it as the target group. The historical fault alarm response contains a group identifier, and the group identifier is also the unique identifier corresponding to the alarm handling group constructed during the process of fault alarm for this historical fault alarm response. If the fault alarm information matches a certain historical fault alarm response, it can be judged whether all the persons concerned in the fault alarm information are added to the alarm handling group corresponding to the historical fault alarm response, so as to add the corresponding persons concerned according to the judgment result.

[0055] In a specific embodiment, step S150 includes sub-steps: obtain the target persons concerned in the persons concerned of the processing department corresponding to the fault alarm information who are not included in the group corresponding to the historical fault alarm response; add the identification information of the target persons concerned to the alarm handling group corresponding to the historical fault alarm response and use it as the target group.

[0056] Specifically, if all the persons concerned in the fault alarm information are added to the alarm handling group corresponding to the historical fault alarm response, then use this alarm handling group as the target group. If there are persons concerned who have not been added to the alarm handling group, the corresponding persons concerned can be added to this alarm handling group and determined as the target group. Then the target group must contain all the persons concerned in all the fault alarm information.

[0057] S160. If the fault warning information does not match the historical fault warning response, a new warning handling group is formed according to the concerned persons corresponding to the fault warning information and used as the target group.

[0058] If the fault warning information does not match the historical fault warning response, a new warning handling group is formed according to the concerned persons corresponding to the fault warning information and used as the target group. If the fault warning information does not match the historical fault warning response, a new warning handling group can be formed corresponding to the concerned persons in the fault warning information, and the new warning handling group is used as the corresponding target group. Specifically, each concerned person corresponds to a personnel identifier, which can be the telephone number or employee code of the person, and the personnel identifier corresponds to the communication account used by the concerned person.

[0059] According to the personnel identifiers of the concerned persons in the fault warning information, the communication accounts corresponding to each concerned person can be added to the newly created same warning handling group, and the newly created warning handling group is also used as the target group. There are at least two communication accounts corresponding to the concerned persons in the target group. Specifically, the communication account can be a software account built within the enterprise and only used for receiving and sending notification information within the enterprise, and the communication software corresponding to the communication account directly runs on the server within the enterprise; the communication account can also be a software account built outside the enterprise and used for receiving and sending notification information, and the communication software corresponding to the communication account can run on the server outside the enterprise. For example, the communication software can be DingTalk or WeChat.

[0060] S170. Obtain the detailed fault information of the fault warning information and push it within the target group so that the user terminals corresponding to each concerned person in the target group receive the detailed fault information.

[0061] Obtain the detailed fault information of the fault warning information and push it within the target group so that the user terminals corresponding to each concerned person in the target group receive the detailed fault information. The concerned person runs the communication software on the user terminal used by him / her and logs in with his / her own communication account, and can correspondingly receive the information pushed within the warning handling group containing his / her communication account; further, the detailed fault information of the fault warning information can be obtained and pushed into the target group, and the communication accounts of each concerned person in the target group can receive the detailed fault information. The detailed fault information of the fault warning information can include detailed information related to the fault such as the fault occurrence time point, fault code, fault type identifier, fault log record (Logs), system status, etc.

[0062] In a specific embodiment, after step S170, the method further includes: adding the fault alarm information as a historical fault alarm response to the historical alarm library; determining whether the fault corresponding to the added historical fault alarm response has been recovered; if the fault corresponding to the historical fault alarm response has been recovered, setting the alarm status of the historical fault alarm response to recovered.

[0063] After the detailed fault information of the fault alarm information has been pushed within the target group, the fault alarm information can be added as a historical fault alarm response to the historical alarm library. When adding the historical fault alarm response to the historical alarm library, the alarm parameters in the historical fault alarm response are default configured as having initiated a response.

[0064] Furthermore, it can be determined whether the fault corresponding to the currently added historical fault alarm response has been recovered. If the historical fault alarm response has been recovered, it indicates that the fault problem has been processed, and the alarm status of the historical fault alarm response is set to recovered; if the fault corresponding to the currently added historical fault alarm response has not been recovered, the fault corresponding to the historical fault alarm response is judged again after an interval of a preset cycle time.

[0065] In the group management method for fault alarm response disclosed in the above embodiment, the method includes: monitoring the business systems configured in the management server to determine whether a fault occurs. If a fault occurs, corresponding fault alarm information is generated. If an alarm handling group has been formed, the group is directly determined as the target group. If an alarm handling group has not been formed, it is judged whether the fault alarm information matches the historical fault alarm response; if they match, the person in charge corresponding to the fault alarm information is added to the alarm handling group corresponding to the historical fault alarm response and used as the target group. If they do not match, a new alarm handling group is created as the target group, and the detailed fault information of the fault alarm information is pushed within the target group. The above group management method for fault alarm response can continuously monitor whether a fault occurs. When a fault occurs, it can intelligently judge the correlation between the current fault alarm and the historical fault alarm response, and pull a group in time to push the detailed fault information, reducing the communication cost; greatly improving the efficiency and accuracy of fault alarm pushing, thereby enhancing the speed of fault resolution.

[0066] An embodiment of the present invention further provides a group management device for fault alarm response. The group management device for fault alarm response can be configured in the management server, and the group management device for fault alarm response is used to execute any embodiment of the foregoing group management method for fault alarm response. Specifically, please refer to Figure 3 , Figure 3 which is a schematic block diagram of the group management device for fault alarm response provided by the embodiment of the present invention.

[0067] As shown Figure 3 in FIG. 1, the group management device 100 for fault alarm response includes a system monitoring unit 110, an alarm information acquisition unit 120, a target group determination unit 130, a matching judgment unit 140, an addition unit 150, a formation unit 160, and an information push unit 170.

[0068] The system monitoring unit 110 is configured to continuously monitor the service system configured in the management server according to preset monitoring metrics to determine whether a fault occurs.

[0069] In a more specific embodiment, the system monitoring unit 110 includes: an index item value acquisition unit configured to acquire an index item value corresponding to the monitoring metric in the service system; an index item value judgment unit configured to judge whether any of the index item values does not match a preset numerical range in the corresponding monitoring metric to determine whether a fault occurs.

[0070] The alarm information acquisition unit 120 is configured to, if a fault occurs, acquire information related to the fault to generate a corresponding fault alarm information.

[0071] The target group determination unit 130 is configured to, if an alarm handling group corresponding to the fault alarm information has been formed, determine it as the target group.

[0072] The matching judgment unit 140 is configured to, if an alarm handling group corresponding to the fault alarm information has not been formed, judge whether the fault alarm information matches a historical fault alarm response in a preset historical alarm library.

[0073] The addition unit 150 is configured to, if the fault alarm information matches a historical fault alarm response, add the person concerned corresponding to the fault alarm information to the alarm handling group corresponding to the historical fault alarm response and use it as the target group.

[0074] The formation unit 160 is configured to, if the fault alarm information does not match a historical fault alarm response, form a new alarm handling group according to the person concerned corresponding to the fault alarm information and use it as the target group.

[0075] The information push unit 170 is configured to acquire the detailed fault information of the fault alarm information and push it within the target group so that the user terminals corresponding to each person concerned in the target group receive the detailed fault information.

[0076] The group management device for fault alarm response provided in the embodiments of the present invention applies the above-mentioned group management method for fault alarm response to monitor the business systems configured in the management server to determine whether a fault occurs. If a fault occurs, corresponding fault alarm information is generated. If an alarm handling group has been formed, the group is directly determined as the target group. If an alarm handling group has not been formed, it is determined whether the fault alarm information matches the historical fault alarm response. If they match, the concerned persons corresponding to the fault alarm information are added to the alarm handling group corresponding to the historical fault alarm response and used as the target group. If they do not match, a new alarm handling group is created as the target group, and the detailed fault information of the fault alarm information is pushed within the target group. The above-mentioned group management method for fault alarm response can continuously monitor whether a fault occurs. When a fault occurs, it can intelligently judge the correlation between the current fault alarm and the historical fault alarm response, and promptly form a group to push the detailed fault information, reducing the communication cost; greatly improving the efficiency and accuracy of fault alarm pushing, thereby enhancing the speed of fault resolution.

[0077] The above-mentioned group management device for fault alarm response can be implemented in the form of a computer program, and this computer program can run on a computer device as shown in Figure 4 .

[0078] Please refer to Figure 4 . Figure 4 FIG. is a schematic block diagram of the computer device provided in the embodiments of the present invention. This computer device can be a management server used to execute the group management method for fault alarm response to monitor business systems to create groups and push fault alarms.

[0079] Referring to Figure 4 , this computer device 500 includes a processor 502, a memory, and a communication interface 505 connected through a communication bus 501. Among them, the memory can include a storage medium 503 and an internal memory 504.

[0080] The storage medium 503 can store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, the processor 502 can be made to execute the group management method for fault alarm response. Among them, the storage medium 503 can be a volatile storage medium or a non-volatile storage medium.

[0081] The processor 502 is used to provide computing and control capabilities to support the operation of the entire computer device 500.

[0082] The internal memory 504 provides an environment for the operation of the computer program 5032 in the storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can be made to execute the group management method for fault alarm response.

[0083] The communication interface 505 is used for network communication, such as providing data information transmission, etc. Those skilled in the art can understand that Figure 4 The structure shown in is only a block diagram of some structures related to the solution of the present invention, and does not constitute a limitation on the computer device 500 to which the solution of the present invention is applied. The specific computer device 500 may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0084] Wherein, the processor 502 is used to run the computer program 5032 stored in the memory to implement the corresponding functions in the above-mentioned group management method for fault alarm response.

[0085] Those skilled in the art can understand that Figure 4 The embodiments of the computer device shown in do not constitute a limitation on the specific composition of the computer device. In other embodiments, the computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements. For example, in some embodiments, the computer device may only include a memory and a processor. In such an embodiment, the structures and functions of the memory and the processor are the same as those in Figure 4 the embodiment shown, and will not be described in detail here.

[0086] It should be understood that in the embodiments of the present invention, the processor 502 may be a central processing unit (CPU), and the processor 502 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0087] In another embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps included in the above-mentioned group management method for fault alarm response are implemented.

[0088] Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working processes of the devices, apparatuses, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein. Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described according to their functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0089] In several embodiments provided by the present invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, or units with the same function can be aggregated into one unit. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed couplings or direct couplings or communication connections to each other can be indirect couplings or communication connections through some interfaces, devices, or units, or can be electrical, mechanical, or other forms of connection.

[0090] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place, or can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the objectives of the solution of the embodiments of the present invention.

[0091] In addition, the functional units in each embodiment of the present invention can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0092] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. This computer software product is stored in a computer-readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned computer-readable storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), magnetic disks, or optical discs that can store program codes.

[0093] As described above, the above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A group management method for fault alarm response, characterized in that, The method is applied to a management server which establishes network connections with each user terminal to achieve data information transmission. The method includes: Continuously monitor the business systems configured in the management server according to preset monitoring metrics to determine whether a fault occurs; If a fault occurs, obtain information related to the fault to generate corresponding fault alarm information; If the fault alarm information has formed a corresponding alarm handling group, determine it as the target group; If the fault alarm information has not formed a corresponding alarm handling group, determine whether the fault alarm information matches the historical fault alarm responses in a preset historical alarm library; If the fault alarm information matches the historical fault alarm responses, add the person concerned corresponding to the fault alarm information to the alarm handling group corresponding to the historical fault alarm response and use it as the target group; If the fault alarm information does not match the historical fault alarm responses, form a new alarm handling group according to the person concerned corresponding to the fault alarm information and use it as the target group; Obtain the detailed fault information of the fault alarm information and push it within the target group so that the user terminals corresponding to each person concerned in the target group receive the detailed fault information.

2. The group management method for fault alarm response according to claim 1, wherein, The continuously monitoring the business systems configured in the management server according to preset monitoring metrics to determine whether a fault occurs includes: Obtain the item value of the metric corresponding to the monitoring metric in the business system; Determine whether any of the item values does not match the preset numerical range in the corresponding monitoring metric to determine whether a fault occurs.

3. The group management method for fault alarm response according to claim 1, wherein The obtaining information related to the fault to generate corresponding fault alarm information includes: Obtain the processing department corresponding to the fault as the target department; Obtain the person concerned corresponding to the fault within the target department; Obtain the rule identifier corresponding to the fault; Combine the target department, the person concerned and the rule identifier into the fault alarm information corresponding to the fault.

4. The group management method for fault alarm response according to claim 1 or 3, characterized in that, The determining whether the fault alarm information matches the historical fault alarm responses in a preset historical alarm library includes: Screen out the historical fault alarm responses that meet the status screening conditions from the historical alarm library according to the preset status screening conditions; Determine whether the rule identifier and the target department of the fault alarm information match the screened historical fault alarm responses to determine whether the fault alarm information matches the historical fault alarm responses.

5. The group management method for fault alarm response according to claim 1 or 3, characterized in that, The adding the person concerned corresponding to the fault alarm information to the alarm handling group corresponding to the historical fault alarm response and using it as the target group includes: Obtain the target person concerned whose identifier is not included in the group corresponding to the historical fault alarm response among the persons concerned in the processing department corresponding to the fault alarm information; Add the identifier information of the target person concerned to the alarm handling group corresponding to the historical fault alarm response and use it as the target group.

6. The group management method for fault alarm response according to claim 1, wherein After obtaining the detailed fault information of the fault alarm information and pushing it within the target group, it further includes: Add the fault alarm information as a historical fault alarm response to the historical alarm library; Determine whether the fault corresponding to the added historical fault alarm response has been recovered; If the fault corresponding to the historical fault alarm response has been recovered, set the alarm status of the historical fault alarm response to recovered.

7. A group management device for fault alarm response, characterized in that, The device is configured in a management server, and the management server establishes a network connection with each user terminal to implement data information transmission. The device is used to execute the group management method for fault alarm response according to any one of claims 1-6. The device includes: A system monitoring unit for continuously monitoring the service system configured in the management server according to preset monitoring indicators to determine whether a fault occurs; An alarm information acquisition unit for acquiring information related to the fault to generate corresponding fault alarm information if a fault occurs; A target group determination unit for determining a target group if the fault alarm information has formed a corresponding alarm processing group; A matching judgment unit for judging whether the fault alarm information matches the historical fault alarm response in a preset historical alarm library if the fault alarm information has not formed a corresponding alarm processing group; An adding unit for adding the person concerned corresponding to the fault alarm information to the alarm processing group corresponding to the historical fault alarm response and taking it as the target group if the fault alarm information matches the historical fault alarm response; A forming unit for forming a new alarm processing group according to the person concerned corresponding to the fault alarm information and taking it as the target group if the fault alarm information does not match the historical fault alarm response; An information push unit for acquiring the detailed fault information of the fault alarm information and pushing it in the target group so that the user terminals corresponding to each person concerned in the target group receive the detailed fault information.

8. The group management device for fault alarm response according to claim 7, wherein The system monitoring unit includes: An index item value acquisition unit for acquiring the index item value corresponding to the monitoring index in the service system; An index item value judgment unit for judging whether any index item value does not match the preset numerical range in the corresponding monitoring index to judge whether a fault occurs.

9. A computer device, characterized in that, The device includes a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete mutual communication through the communication bus; The memory is used for storing a computer program; The processor, when executing the program stored on the memory, implements the steps of the group management method for fault alarm response according to any one of claims 1-6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the group management method for fault alarm response according to any one of claims 1-6.

Images