CN113468024A - Visual on-duty emergency disposal interaction method and device - Google Patents
Visual on-duty emergency disposal interaction method and device Download PDFInfo
- Publication number
- CN113468024A CN113468024A CN202110834979.2A CN202110834979A CN113468024A CN 113468024 A CN113468024 A CN 113468024A CN 202110834979 A CN202110834979 A CN 202110834979A CN 113468024 A CN113468024 A CN 113468024A
- Authority
- CN
- China
- Prior art keywords
- information
- alarm information
- fault
- alarm
- technical support
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Operations Research (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Mathematical Physics (AREA)
- Alarm Systems (AREA)
Abstract
The invention relates to the field of big data, in particular to a visual on-duty emergency disposal interaction method and device. The method comprises the steps of obtaining and displaying first alarm information of faults; generating shared alarm information according to the first alarm information; sending the sharing alarm information to a technical support terminal; receiving a request for acquiring second alarm information sent by the technical support terminal; acquiring second alarm information according to the second alarm information acquisition request and the application permission of the fault; sending the second alarm information to a technical support terminal; receiving the technical support terminal to generate a fault processing scheme according to the shared alarm information and the second alarm information; executing the fault handling scheme to resolve the fault.
Description
Technical Field
The text relates to the technical field of information security, can be used in the financial field, and particularly relates to a visual on-duty emergency disposal method and device.
Background
With the increase of banking service types, the probability of failure of the banking service system may increase, and the operation of the banking service system becomes more and more complex. When a fault occurs, different from a fault emergency flow that a system, a network and equipment have clear categories and fixed means, a unified and standardized emergency flow is lacked when an application program fails, and meanwhile, in the face of a variety of application systems, a person on duty cannot know all the faults, so that the flow for processing the fault is relatively complex, and the time spent on processing the fault is relatively long. Therefore, the failure of the bank application program system puts higher requirements on operators on duty and manual intervention, and puts a severe test on the daily operation of the bank system.
In the prior art, a method for solving fault handling of a financial system generally includes that an on-duty person manually analyzes each fault alarm, contacts a business support person for an alarm which is uncertain whether to be handled or not in a manner of dialing a telephone, finds a solution under the guidance of the business support person, and opens a corresponding tool to perform a series of operations, so as to remove the fault. The fault processing method is long in time consumption and tedious in procedure, and faults cannot be solved at the highest speed.
Aiming at the problems of complex flow and long time consumption of bank application program fault processing, a visual emergency disposal interaction system and method are urgently needed to be researched, when an application program fails, the emergency disposal scheme of the fault can be determined and quickly processed through interaction of a system and business support personnel, and therefore bank business stop caused by the fault and adverse effects on customer experience are avoided.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments herein provide a visual emergency treatment interaction method, device, computer device, and storage medium, which solve the problems in the prior art that the flow for processing the failure of the bank application is tedious and the time is long.
An embodiment herein provides a visual emergency treatment method, including:
acquiring and displaying first alarm information of a fault;
generating shared alarm information according to the first alarm information;
sending the sharing alarm information to a technical support terminal;
receiving a request for acquiring second alarm information sent by the technical support terminal;
acquiring second alarm information according to the second alarm information acquisition request and the application permission of the fault;
sending the second alarm information to a technical support terminal;
receiving the technical support terminal to generate a fault processing scheme according to the shared alarm information and the second alarm information;
executing the fault handling scheme to resolve the fault.
According to an aspect of an embodiment herein, the first alarm information is alarm information related to the fault, including at least: server information, alarm events, error reporting information, and application responsible personnel information.
According to an aspect of an embodiment herein, the generating shared alert information based on the first alert information includes: acquiring the total information of server information, alarm events and error reporting information in the first alarm information; and performing screen capture on the display interface of the full information, and taking a screen capture image as the shared alarm information.
According to one aspect of embodiments herein, the full amount of information for the server information includes server address, server name, server network information; the total information of the alarm event comprises the number, the name and the danger level of the alarm event; the total information of the error reporting information comprises error reporting starting time, error reporting duration and specific contents of error reporting.
According to an aspect of embodiments herein, in obtaining the full amount of information of the server information, the alarm event, and the error information in the first alarm information, further comprises: and acquiring the full information or partial full information of the server information, the alarm event and the error reporting information in the first alarm information according to the common grade corresponding to the fault.
According to an aspect of the embodiment herein, sending the shared alarm information to a technical support terminal further includes querying an address of the technical support terminal according to the application responsible person information in the first alarm information, and sending the shared alarm information to the technical support terminal.
According to an aspect of an embodiment herein, generating shared alert information based on the first alert information further includes, before determining key information of the first alert information; matching key information of the first alarm information in a preset scene library; when the matching is successful, generating a fault processing scheme aiming at the fault; and when the matching fails, generating shared alarm information according to the first alarm information.
According to an aspect of an embodiment herein, the obtaining the second alarm information according to the request for obtaining the second alarm information and the service authority of the fault further includes: acquiring fault information according to the demand information in the second alarm information request; and comparing the authority information of the application responsible personnel in the second alarm information request with the application authority of the fault information, and taking the fault information which is in accordance with the authority of the application responsible personnel in the second alarm information request as the second alarm information.
According to an aspect of embodiments herein, the failed application authority includes: and fault information related to various faults, wherein each fault information has a corresponding safety level.
According to an aspect of an embodiment herein, the receiving a fault handling scheme generated by the technical support terminal according to the shared alarm information and the second alarm information includes: determining key information of the shared alarm information and the second alarm information; matching the key information in a preset scene library; and when the matching is successful, generating a fault processing scheme aiming at the fault.
According to an aspect of embodiments herein, the fault handling scheme comprises one or a combination of: repairing, deleting, recovering, backing up, stopping running and alarming.
Embodiments herein also provide a visual emergency treatment device on duty, including:
the first alarm information acquisition unit is used for acquiring and displaying first alarm information of a fault;
the shared alarm information generating unit is used for generating shared alarm information according to the first alarm information;
the sharing alarm information sending unit is used for sending the sharing alarm information to a technical support terminal;
the second alarm information request receiving unit is used for receiving a request for acquiring second alarm information sent by the technical support terminal;
the second alarm information acquisition unit is used for acquiring second alarm information according to the second alarm information acquisition request and the application permission of the fault;
the second alarm information sending unit is used for sending the second alarm information to the technical support terminal;
a fault processing scheme receiving unit, configured to receive a fault processing scheme generated by the technical support terminal according to the shared alarm information and the second alarm information;
an execution unit to execute the failure handling scheme to resolve the failure.
Embodiments herein also provide a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the above-mentioned method when executing the computer program.
Embodiments herein also provide a computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, implement the above-described method.
By utilizing the embodiment of the invention, when the application program fails, the emergency handling scheme of the failure can be timely and accurately determined and quickly processed through the interaction of the system and the service support personnel, so that the failure is prevented from causing the stop of banking services and adverse effects on customer experience.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic network structure diagram illustrating a visual on-duty emergency handling interaction system according to an embodiment of the present disclosure;
fig. 2 is a flowchart illustrating a visual on-duty emergency treatment interaction method according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram illustrating a visual on-duty emergency treatment interaction device according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram illustrating a specific structure of a visual on-duty emergency treatment interaction device according to an embodiment of the present disclosure;
FIG. 5 is a flow diagram illustrating an automatic generation of a fault handling scheme according to an embodiment of the disclosure;
FIG. 6 is a flow chart illustrating a method of generating shared alert information according to an embodiment herein;
fig. 7 is a flowchart illustrating a process of acquiring second alarm information according to a first embodiment of the present disclosure;
FIG. 8 is a flowchart illustrating a method for generating a fault handling scenario based on shared alert information and second alert information according to an embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure.
Description of the symbols of the drawings:
101. an emergency disposition interactive system;
102. a server on duty;
103. a technical support terminal;
301. a first alarm information acquisition unit;
3011. a display module;
302. a shared alarm information generation unit;
303. a shared alarm information sending unit;
304. a second alarm information request receiving unit;
305. a second alarm information acquisition unit;
306. a second alarm information sending unit;
307. a failure handling scheme receiving unit;
308. an execution unit;
3021. a determination module;
3022. a matching module;
3071. a fault handling scheme display module;
902. a computer device;
904. a processor;
906. a memory;
908. a drive mechanism;
910. an input/output module;
912. an input device;
914. an output device;
916. a presentation device;
918. a graphical user interface;
920. a network interface;
922. a communication link;
924. a communication bus.
Detailed Description
In order to make the technical solutions in the present specification better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments, but not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments herein without making any creative effort, shall fall within the scope of protection.
It should be noted that the terms "first," "second," and the like in the description and claims herein and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments herein described are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or device.
The present specification provides method steps as described in the examples or flowcharts, but may include more or fewer steps based on routine or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual system or apparatus product executes, it can execute sequentially or in parallel according to the method shown in the embodiment or the figures.
It should be noted that the visual on-duty emergency handling interaction method and apparatus may be used in the financial field, and may also be used in any field other than the financial field.
Fig. 1 is a schematic network structure diagram of a visual on-duty emergency disposal interaction system according to an embodiment of the present disclosure, and a visual on-duty emergency disposal interaction method implemented by combining an emergency disposal interaction system 101, an on-duty server 102, and a technical support terminal 103 is described in the present disclosure. The emergency disposal interaction system 101, the duty server 102 and the technical support terminal 103 may perform data interaction therebetween.
In some embodiments of the present description, the emergency treatment interaction system 101 may be an electronic device with a network interaction function, or may be software running in the electronic device and providing service logic for data processing and network interaction. The emergency treatment interactive system 101 may autonomously fail and generate failure alarm information during a normal operation process. The emergency treatment interaction system 101 may send alarm information of the fault to the on-duty server 102.
In some embodiments of the present disclosure, the on-duty server 102 may be an electronic device with a network interaction function, or may be software running in the electronic device and providing service logic for data processing and network interaction. The on-duty server 102 includes a first obtaining unit configured to obtain first alarm information about a fault, a shared alarm information generating unit 302 configured to generate shared alarm information according to the first alarm information, a shared alarm information sending unit 303 configured to send the shared alarm information to a technical support terminal, a second alarm information request receiving unit 304 configured to receive a request for obtaining second alarm information sent by the technical support terminal 103, and a second alarm information sending unit 306 configured to send the second alarm information to the technical support terminal 103.
In some embodiments of the present description, the technical support terminal 103 may be a desktop computer, a tablet computer, a laptop computer, a smartphone, a digital assistant, a smart wearable device, or the like. The technical support terminal 103 is not limited to the electronic device having a certain entity, and may be software running in the electronic device.
Fig. 2 is a flowchart of a visual on-duty emergency treatment interaction method according to an embodiment of the present disclosure, where a flowchart of generating a fault handling scheme using alarm information is described in the present diagram, where the method specifically includes the following steps:
at step 208, the fault handling scheme is executed to resolve the fault.
As one embodiment herein, the first alarm information is alarm information related to the failure, and the first alarm information includes at least: server information, alarm events, error reporting information, application principal information, and the like.
In this step, the fault is an abnormal event occurring in an application program of the banking system, and the first alarm information of the fault is randomly generated by the application program of the system. The first alarm information of the fault is a set of at least one alarm information of the fault, the form of the first alarm information comprises an alarm log, an alarm list and the like, and the first alarm information can be composed of codes, characters, letters, numbers and the like.
In this step, the server information includes a server address, a server name, a server memory, and a normal operation time of the server. The alarm event comprises: alarm starting time, alarm event name, alarm equipment, alarm service department, alarm service type, alarm danger level, etc. The error reporting information comprises: the starting time of error reporting, the content of error reporting, the business department of error reporting, the business type of error reporting, etc. The application principal information includes: the application responsible personnel ID, the department to which the application responsible personnel belong, the authority level of the application responsible personnel, the online time of the application responsible personnel, the contact address of the application responsible personnel, the corresponding terminal address of the application responsible personnel and the like. The contact address of the application responsible person comprises a mobile phone number, a mailbox address, an instant messaging software user name and the like of the application responsible person.
In this step, the first alarm information further includes a history alarm information event, a normal operation time of the history alarm information from the current first alarm information, and the like.
In this step, after the attendant server obtains the first alarm information generated by the system application, based on a Web front end technology, the first alarm information is displayed in a page form on a display device with a display function through a Java script plug-in (JavaScript), Web Real-Time Communication (WebTRC) transmission, and a full duplex Communication protocol (WebSocket) based on a transmission control protocol, where the display device includes but is not limited to: computer display, monitor screen, mobile device display, etc.
As one embodiment herein, generating shared alert information based on the first alert information includes:
acquiring the total information of server information, alarm events and error reporting information in the first alarm information;
and performing screen capture on the display interface of the full information, and taking a screen capture image as the shared alarm information.
In this step, the total information in the first alarm information is information of all dimensions of the first alarm information. The system cannot generate a fault processing scheme through the first alarm information, and needs to acquire full information of more contents related to the first alarm information according to the first alarm information. Therefore, the content of the shared alarm information is more comprehensive than that of the first alarm information. The display interface of the full information is stored as a screen capture image, and the shared alarm information is stored in a uniform picture format, so that when the display interface of the full information is displayed across terminals, the format is stable when a plurality of display interfaces of a plurality of display terminals are displayed, and abnormal conditions such as messy codes, line feed, character string disconnection and the like can not occur.
As one embodiment herein, the full amount of information of the server information includes server address, server name, server network information;
the total information of the alarm event comprises the number, the name and the danger level of the alarm event;
the total information of the error reporting information comprises error reporting starting time, error reporting duration and specific contents of error reporting.
In this step, the total information of the alarm event further includes information such as a start time of the alarm event, a device that issues the alarm, an application that issues the alarm, and a network environment where the alarm is located. The total information of the error reporting information also comprises an error reporting service type, historical error reporting information and the like.
As an embodiment herein, the obtaining of the full amount of information of the service information, the alarm time and the error information in the first alarm information further includes: and acquiring the information or partial full information of the server information, the alarm event and the error report information in the first alarm information according to the common grade corresponding to the fault.
In this step, the common level corresponding to the fault indicates the frequency of occurrence of the fault within a period of time, and the common level corresponding to the fault may also reflect the safety level and/or the importance level corresponding to the fault. The emergency disposal system can specify that the fault with high common grade is a fault with high frequency and small processing difficulty in historical time; the common faults with low grade are faults which have low frequency and high processing difficulty in historical time. The higher the common grade corresponding to the fault is, the more common the fault is, the smaller the processing difficulty is and the shorter the processing time is; the lower the common grade corresponding to the fault is, the less frequent the fault is, the greater the processing difficulty is and the longer the processing time is.
In the embodiment of the present disclosure, the full amount information or the partial full amount information of the server information, the alarm event, and the error report information in the first alarm information may also be obtained according to the degree of harm, the degree of urgency, and the like corresponding to the fault.
In this step, for a common fault with a low grade, the processing difficulty is high, and the technical support end needs to obtain more information for assisting the service support personnel in fault diagnosis, so that the full amount of information such as server information, alarm events, error reporting information and the like in the first alarm information needs to be obtained, so that the technical support can judge the fault reason according to sufficient alarm information; for the common faults with higher grades, the processing difficulty is lower, the information needed by the business support terminal to assist the business support personnel in fault diagnosis is less, and partial full information, namely partial information, is enough to assist the business support personnel in judging and solving the faults.
In this step, the corresponding level of the fault may be represented by a combination of numbers, letters, and the like.
Taking a banking business as an example for explanation, in the business process, two application faults of 'availability disconnection' and 'interface messy codes' occur, the common grade corresponding to the fault 'availability disconnection' is 3 grade, which indicates that the fault is common, and the on-duty server can process partial full information of the server ID, the alarm event name, the error reporting information and the like in the first alarm information or the basic content of the alarm information; for another example, the common level corresponding to the "interface messy code" of the fault is level 1, which indicates that the "interface messy code" fault is rare, the processing difficulty is high, and the on-duty server needs to acquire the total information of the server in the first alarm information, the total information of the alarm event, and the total information of the error report information to process the relevant fault.
As an embodiment herein, sending the shared alarm information to a technical support terminal further includes: and inquiring the address of the technical support terminal according to the information of the application responsible personnel in the first alarm information, and sending the shared alarm information to the technical support terminal.
In this step, the server may obtain a plurality of first alarm messages at a time. As described in the foregoing embodiment, the first alarm information includes application responsible person information. The first alarm information can be processed by at least one corresponding application responsible person, and the application responsible person can process the at least one first alarm information. In this step, the technical support terminal to which the first alarm information is to be sent may be determined according to the application responsible person information in the first alarm information. Wherein, the address of the technical support terminal can be determined according to the ID of the application responsible person. For example, the address of the corresponding technical support terminal a is determined according to the ID of the application responsible person a in the first alarm information X, the address of the corresponding technical support terminal B is determined according to the ID of the application responsible person B in the first alarm information Y, and the address of the corresponding technical support terminal C is determined according to the ID of the application responsible person C in the first alarm information Z. Therefore, when sending the shared alarm information to the technical support terminal, the server needs to determine the information of the responsible person applied in the at least one piece of first alarm information, determine the address of the technical support terminal, and send the shared alarm information to the technical support terminal.
As an embodiment herein, before generating shared alert information according to the first alert information, the method further includes: determining key information of the first alarm information; matching key information of the first alarm information in a preset scene library; when the matching is successful, generating a fault processing scheme aiming at the fault; and when the matching fails, generating shared alarm information according to the first alarm information.
Before generating the shared alarm information in this step, the system firstly judges whether a fault processing scheme aiming at the fault can be directly generated according to the first alarm information, and if the fault processing scheme cannot be generated according to the first alarm information, the subsequent steps are executed.
In this step, the system may identify key information of the first alarm information by means of keyword extraction, text recognition, image recognition, and the like, where the key information may be one of an alarm name, application principal information, an alarm event, a server address, and the like, or any combination thereof.
In this step, the system presets a preset scene library, in which key information of the historical alarm information and a historical fault processing method corresponding to the key information are stored, for example, a fault processing method corresponding to a "telephone line disconnection" name including the key information alarm in the preset scene library is "connected telephone line"; for another example, the preset scene library includes a fault handling method corresponding to the key information alarm event interface messy code, such as restarting corresponding equipment/software.
In the step, a fault processing scheme of a fault can be matched and generated according to existing key information in a preset scene library; and when the key information cannot be matched in the preset scene library, indicating that a fault processing scheme corresponding to the current fault is not stored in the preset scene library, generating shared alarm information according to the first alarm information, and executing subsequent steps.
As an embodiment herein, the acquiring the second alarm information according to the request for acquiring the second alarm information and the service authority of the fault further includes:
acquiring fault information according to the demand information in the second alarm information request;
comparing the authority information of the application responsible personnel in the second alarm information request with the application authority of the fault information,
and taking the fault information which is in accordance with the authority of the application responsible personnel in the second alarm information request as the second alarm information.
In this step, the system cannot match a fault handling scheme of the fault in the preset scene library, and the service support terminal provides a request for acquiring the second alarm information to the system according to the received shared alarm information. The second alarm information and the first alarm information can be different service information based on the same equipment, the same software and the same application; or different service information based on different devices, different software, and different applications. The second alarm information request may be made by an application responsible person of the service support terminal based on the authority information thereof.
The requirement information in the second alarm information request comprises application responsible personnel information, a server address of the second alarm information and the like. Based on business safety consideration, the application responsible personnel cannot provide a second alarm information request which exceeds the authority range of the application responsible personnel. For example, the application principal with a low privilege level cannot access the relevant information of the high privilege range server. Therefore, the authority information of the application responsible person in the second alarm information request needs to be compared with the application authority of the fault information. If the authority information of the application responsible personnel is higher than the application authority of the fault information required in the second alarm information request, the system can acquire the fault information required in the second alarm information request, and the fault information conforming to the authority of the application responsible personnel in the second alarm information request is used as the second alarm information. And if the authority information of the application responsible personnel is lower than the application authority of the fault information, the second alarm information request cannot be acquired. For example, when the application responsible person performs fault diagnosis, more information about the fault needs to be obtained, so the second alarm information request includes a requirement for obtaining more information about the fault, but the authority of the application responsible person cannot obtain the address information of a certain server, and the second alarm information request includes a requirement for obtaining the address information of the server, the system sends the fault information meeting the authority of the application responsible person to the technical support terminal of the application responsible person according to the application authority corresponding to the relevant fault information about the fault, and does not obtain the server address information and feed the server address information back to the technical support terminal of the application responsible person.
As one embodiment herein, the failed application authority includes: the fault information related to various faults and each fault information have corresponding safety levels.
In this step, different application authorities for the fault correspond to different security levels. The safety level of the failure information is different from the common level corresponding to the failure described in the previous embodiment. And the system determines whether the authority information of the application responsible personnel sends the requirement of a second alarm information request according to the safety level corresponding to the fault.
As an embodiment herein, the receiving a fault handling scheme generated by the technical support terminal according to the shared alarm information and the second alarm information includes:
determining key information of the shared alarm information and the second alarm information by the technical support terminal 103; matching the key information in a preset scene library; and when the matching is successful, generating a fault processing scheme aiming at the fault.
In this step, the technical support terminal 103 receives the second alarm information, and the technical support terminal 103 determines the key information of the shared alarm information and the second alarm information through keyword extraction, text recognition, image recognition and the like. Specific methods for determining key information of the shared alert information and the second alert information can be seen in the foregoing description of the embodiments regarding determining key information of the first alert information. The technical support terminal 103 matches the key information of the shared alarm information and the second alarm information in a preset scene library. And when a fault processing scheme corresponding to the key information is matched in a preset scene library, generating a fault processing scheme aiming at the fault.
As an embodiment herein, the fault handling scheme includes one or a combination of the following: repairing, deleting, recovering, backing up, stopping running and alarming.
In this step, the failure handling scheme for the failure includes repairing application data, deleting application data, restoring history settings, backing up application data, stopping running the current device/software, executing an alarm, and the like.
Fig. 3 is a schematic structural diagram of a visual on-duty emergency handling interaction device according to an embodiment of the present disclosure, in which a basic structure of the visual on-duty emergency handling device is described, where functional units and modules may be implemented in a software manner, or may also be implemented in a general chip or a specific chip, and a part or all of the functional units and modules may be on an on-duty server, or a part of the functional units and modules may also be on a technical support terminal 103, and the emergency handling interaction is implemented through cooperation with the on-duty server 102, where the device specifically includes:
and the first alarm information acquisition unit 301 is used for acquiring and displaying the first alarm information of the fault.
And a shared alarm information generating unit 302, configured to generate shared alarm information according to the first alarm information.
And a shared alarm information sending unit 303, configured to send the shared alarm information to a technical support terminal.
A second alarm information request receiving unit 304, configured to receive a request for obtaining second alarm information sent by the technical support terminal.
And a second alarm information obtaining unit 305, configured to obtain the second alarm information according to the second alarm information obtaining request and the application permission of the fault.
And a second alarm information sending unit 306, configured to send the second alarm information to the technical support terminal.
And a fault processing scheme receiving unit 307, configured to receive a fault processing scheme generated by the technical support terminal according to the shared alarm information and the second alarm information.
An execution unit 308 to execute the failure handling scheme to resolve the failure.
Through the setting of the embodiment, the key information of the first alarm information, the key information of the shared alarm information and the key information of the second alarm information are combined, the shared alarm information is displayed on the display interface, the fault processing scheme corresponding to the fault is generated, the step that an operator on duty displays the fault to the service support terminal is reduced, the time for fault processing is reduced, the application authority of the operator in charge of application is compared with the application authority of the fault information, the safety of the application operation and the fault maintenance process is guaranteed to the maximum extent, and the fault can be solved more accurately.
As an embodiment herein, referring to a specific structural schematic diagram of the visual on-duty emergency treatment interaction device shown in fig. 4, the first alarm information acquiring unit 301 is further configured to display the first alarm information on a display interface after acquiring the first alarm information about the fault.
As an embodiment herein, the first alarm information acquisition unit 301 further includes:
and the display module 3011 is configured to collectively display the acquired first alarm information on a display interface according to a predetermined rule.
The shared alarm information generating unit 302 is configured to determine key information of first alarm information before generating shared alarm information, and match the key information of the first alarm information in a preset scene library.
As an embodiment herein, the shared alarm information generation unit 302 further includes:
a determining module 3021, configured to identify and determine key information in the first alarm information;
the matching module 3022 is configured to match the key information of the first alarm information in a preset scene.
The failure handling scheme receiving unit 307 is further configured to display the received failure handling scheme on a display interface.
As an embodiment herein, the failure handling scheme unit 307 further comprises:
and the failure handling scheme display module 3071 is configured to display the failure handling scheme generated by the service support terminal on the display interface.
Fig. 5 is a flow chart illustrating an automatic generation of a fault handling scheme according to an embodiment of the present disclosure.
the first alarm information comprises server information, alarm events, error reporting information, application responsible personnel information and the like. The server information includes: server address, server name, server memory, server normal operation time length and the like; the alarm event includes: alarm IP, alarm starting time, alarm ending time, alarm times, alarm event names, alarm equipment, alarm service departments, alarm service types, alarm danger levels and the like; the error reporting information comprises: error reporting starting time, error reporting content, error reporting service department, error reporting service type and the like; the application responsible person information includes: the application responsible person ID, the department to which the application responsible person belongs, the application responsible person authority level, the application responsible person duty time, the application responsible person contact address and the like.
In this step, the key information indicates information having representative meanings in a plurality of fields of the first alarm information, including keywords, key sentences, and the like. The first alarm information contains a variety of information and complex content, and key information in the first alarm information needs to be extracted and determined so as to determine a fault and generate a corresponding fault processing scheme.
In an exemplary embodiment of the present description, the first alarm information is as shown in the following table (see table 1 below):
| main field | Description of the invention | Examples of the invention |
| Application abbreviation | Alarm application English name | F-CCIS |
| Using Chinese names | Alarm application Chinese name | Remote bank center |
| Alarm IP | Alarm server ip | 84.XX.XX.XX |
| Alarm start time | Alarm start time | YYYY-MM-DD HH:MM:SS |
| Alarm end time | Alarm end time | YYYY-MM-DD HH:MM:SS |
| Number of alarms | Counting the number of alarm times | 1 |
| Alarm type | Type of alarm | Class of non-/recoverable |
| Details of the alarm | And (4) alarming related content. | Xxx availability |
| Support manager | Support manager corresponding to application | Zhang San |
| Contact means | Contact mobile phone | 1XXXXXXXXX |
TABLE 1
In this step, the emergency disposal system first presets the key information deemed necessary by the system, and in this step, the key information can be adjusted and set manually in real time according to the actual service conditions. Taking a bank system as an example, the emergency system presets key information as follows: alarm IP address, alarm details, alarm application, error reporting application name, etc. Or, the preset key information of the emergency system comprises: server IP address, alarm issuing equipment/software, etc.
And then, when the application fails, according to the generated first alarm information, the system identifies and determines key information of the first alarm information from the first alarm information according to the preset information. And extracting and identifying key information in the alarm information for each piece of first alarm information in a mode of keyword extraction, text identification, graphic image identification and the like. Taking banking as an example, the system presets key information as 'alarm application' and 'alarm detail'. When the application of the telephone bank breaks down, the first alarm information displays various information such as server information, alarm event information, application responsible personnel information and the like on a display interface, and the system identifies and determines that the key information of the first alarm information is as follows through text identification: the alarm application 'telephone bank' and the alarm IP '192.12.168.22' simply and accurately express the key content of the first alarm information and accurately position the problem generation server where the alarm application program is located.
The key information of the first alarm information may be stored in a memory or a preset scene library for application in a subsequent step.
502, matching key information of the first alarm information in a preset scene library;
in the step, according to the history faults and the records of alarm information corresponding to the faults, the emergency treatment system stores certain faults which are high in occurrence frequency and single and fixed in fault treatment scheme and first alarm information of the faults in a preset scene library. As shown in step 502, the preset scene library also stores the key information preset by the system, so that the preset scene library stores at least one piece of key information of at least one fault and a fault handling scheme corresponding to the key information. When the application fails, the emergency system matches the key information of the first alarm information determined in step 501 in a preset scene library.
Taking banking business as an example, when the application fails, determining that key information in the first alarm information is' alarm application: telephone bank "; the preset scene library stores key information of alarm information corresponding to fault availability disconnection: the "alarm application" is "telephone banking" and the "alarm IP" is "192.12.168.22". Therefore, the key information of the first alarm information can be matched with the key information of the 'usability disconnection' fault in the preset scene library.
And 503, when the matching is successful, generating a fault processing scheme aiming at the fault.
In this step, according to the key information of the first alarm information determined in step 501, a fault processing scheme corresponding to the fault is matched in a preset scene library. Taking banking as an example, the preset scene library stores key information of alarm information corresponding to failure availability disconnection: the ' alarm application ' is ' telephone bank ' and ' alarm IP ' is ' 192.12.168.22 ', and a fault processing scheme ' step 1 cd/aproot/abc sh stop.sh corresponding to the ' availability disconnection ' fault is stored; step 2sh start.sh; step 3, sqlplus sqlplus XXXX @ XXXX; step 4update XX from XX where XX XXX "etc. When the 'availability disconnection' fault occurs in the actual application, the emergency system can match the key information 'alarm application' and 'alarm IP' of the first alarm information in a preset scene library and match the key information 'alarm application' and 'alarm IP' to a corresponding fault processing scheme.
Fig. 6 is a flowchart illustrating a method for generating shared alarm information according to an embodiment of the present disclosure.
In this step, according to the history of the alarm information, the history occurrence frequency of some fault alarm information is low, and the faults are rare, so that the preset scene library does not store the alarm information of the fault and the fault processing scheme corresponding to the fault. The emergency disposal system cannot match a fault handling scheme matched with the corresponding fault in the preset scene library according to the key information of the first alarm information. Therefore, the system needs to acquire the full amount of information of the server information, the alarm event and the error information in the first alarm information, and acquire all information in the first alarm information as much as possible.
In this step, the common level corresponding to the fault indicates the degree of frequency of occurrence of the fault in the historical time, and the common level corresponding to the fault may also reflect the safety level and/or the importance level corresponding to the fault. The emergency disposal system can specify that the fault with high common grade is a fault with high frequency and small processing difficulty in historical time; the common faults with low grade are faults which have low frequency and high processing difficulty in historical time.
Taking a banking business fault as an example, the common grade of the 'telephone disconnection' fault is 5, which means that the 'telephone disconnection' fault has high occurrence frequency in historical time, the fault is common and the processing difficulty is small; the common grade of the interface messy code fault is 1, which indicates that the frequency of the interface messy code fault in the historical time is low, the fault is not common, and the processing difficulty is high.
For the common faults with higher grades, partial full information in the first alarm information needs to be acquired; for a fault with a low common grade, the processing difficulty is high, the first alarm information may not be enough to solve the fault, and therefore, the full amount of information in the first alarm information needs to be acquired. Wherein the common grade corresponding to the fault is represented by letters, numbers or characters.
In this step, the full information of the first alarm information may be displayed on one or more display interfaces, and the screenshot image is stored in the storage device as shared alarm information, so that an application responsible person can conveniently view the shared alarm information at a technical support terminal. The full information can also be generated by shooting a video, intercepting an image of a fixed frame and recording an alarm log. The present embodiment does not limit the form of the total amount of information.
And step 604, sending the sharing alarm information to a technical support terminal.
In this step, the on-duty server 102 obtains the address of the technical support terminal 103 according to the information query of the application responsible person in the first alarm information, and sends the shared alarm information to the technical support terminal 103. Specifically, the first alarm information includes information of an application responsible person, and specifically includes: the application responsible personnel ID, the department to which the application responsible personnel belong, the authority level of the application responsible personnel, the online time of the application responsible personnel, the contact address of the application responsible personnel, the corresponding terminal address of the application responsible personnel and the like. And determining the address of the technical support terminal to receive the shared alarm information according to the address of the corresponding terminal of the application responsible personnel. And the shared alarm information is displayed on a technical support terminal interface for application responsible personnel to check.
Fig. 7 is a flowchart illustrating a method for obtaining second warning information according to an embodiment of the present disclosure.
In the foregoing step, the emergency handling system cannot obtain the fault handling scheme of the fault according to the first alarm information in the preset database, so after receiving the shared alarm information in fig. 6, the service support terminal 103 generates a second alarm information request, and sends a request for obtaining the second alarm information to the on-duty server 102. The second alarm information request comprises the following requirement information: authority information of the application responsible person (e.g., ID of the application responsible person, position level of the application responsible person, device access authority, application access authority, etc.), failure information (e.g., failed application authority, failed device, failed network, failed application, etc.), device and/or application requesting access (e.g., device and/or application requesting access correlated to device and/or application of the first alert information, device and/or application requesting access not correlated to the first alert device and/or application).
Wherein, the second alarm information request is input from the technical support terminal 103 by the application responsible person and is sent to the on-duty server 102 by the technical support terminal. The input of the application responsible person at the technical support terminal 103 includes, but is not limited to: manual input of instructions, voice input of sentences, selection of corresponding keys on the technical support terminal 103, and the like.
In this step, the requirement information in the second alarm information request includes fault information, and the fault information is determined by the application responsible person at the technical support terminal 103. The fault information includes: failure application authority, failure occurrence address, failure occurrence type, failure device, failure network, failure application, other devices that may be related to failure occurrence, other networks related to failure occurrence, other applications related to failure occurrence, and the like, or any combination thereof.
The on-duty server 102 obtains the fault information determined by the application responsible personnel from the requirement information in the second alarm information request.
And 703, comparing the authority information of the application responsible personnel in the second alarm information request with the application authority of the fault information.
In this step, whether the behavior of the application responsible person sending the second alarm information request is reasonable is determined by comparing the application authority of the fault information with the authority information of the application responsible person, so as to subsequently judge whether to acquire the second alarm information.
In this step, the application authority of the failure information indicates the security level of the plurality of parties involved in the network, device, application, etc. related to the failure, and the application authority of the failure information is preset by the system. Wherein the application authority of the fault is distinguished by the divided grades. For example, the application authority security level of the faulty devices a-D is level 1; the safety level of the application authority of the fault equipment E-H is 2 level; the safety level of the application authority of the fault equipment I-M is 3 levels, wherein the levels 1, 2 and 3 represent the fault application authority levels from low to high respectively. Or the application authority level of the fault application O-Q is 3 level; the application authority level of the fault application sink R-T is 4 level and the like. Wherein, the application authority of the fault information is different from the common level corresponding to the fault in fig. 6.
Referring to step 701, the authority information of the application responsible person includes an ID of the application responsible person, a post level of the application responsible person, a device access authority, an application access authority, and the like, and the authority information of the application responsible person is preset by the system. Wherein, the post level and the access authority of the application responsible personnel are distinguished by the divided levels. For example, the authority of the application responsible person A is of a low level; the authority of the application responsible personnel B is in a middle level; the authority of the application responsible person is high level. Or the authority of the application responsible person A is level 1; the authority of the application responsible personnel B is level 2; the authority of the application responsible personnel C is grade 3, wherein the grades 1, 2 and 3 represent the authority grades from low to high respectively.
The application responsible personnel with the lower authority level can only access the fault information related to the fault of the lower application authority and process the fault, and the application responsible personnel with the higher authority level can access the fault information related to the fault of all the application authorities and process the fault. In this step, the authority information of the application responsible person and the application authority of the fault information may have other corresponding manners, which is not limited herein.
In the second alarm information acquisition request, whether the second alarm information is acquired or not can be determined by comparing the authority level of the application responsible person in the second alarm information request with the application authority of the fault information.
By determining that the authority of the application responsible person conforms to the application authority of the fault information, the on-duty server 102 acquires the fault information conforming to the authority of the application responsible person in the second alarm information request as second alarm information. If the authority of the application responsible person does not accord with the application authority of the fault information, the step is not executed, the step 701 is returned, and the second alarm information request is fetched again.
Fig. 8 is a flowchart illustrating a method for generating a fault handling scheme according to shared alarm information and second alarm information, which may be executed by the technical support terminal 103 in an embodiment of the present disclosure, and the method specifically includes:
The specific content of the key information of the shared alarm information and the second alarm information determined in this step may be searched elsewhere herein, and refer to the related description of step 501 in fig. 5 specifically.
the specific content of the step of matching the key information of the shared alarm information and the second alarm information in the preset scene may be found elsewhere herein, specifically referring to the related description of step 502 in fig. 5.
And 803, when the matching is successful, generating a fault processing scheme aiming at the fault.
The specific content of the key information of the step of matching the shared alarm information and the second alarm information in the preset scene can be found elsewhere herein, and the related description of step 503 in fig. 5 is specifically referred to.
When the matching fails, the application responsible personnel inputs a manually set fault handling scheme at the service support terminal 103 and sends the fault handling scheme to the on-duty server 102 through the technical support terminal. Wherein, the application responsible personnel sends the fault processing scheme to the on-duty server 102 by manually inputting the instruction of the fault processing scheme, inputting the utterance sentence by voice, and the like at the technical support terminal 103.
Fig. 9 is a schematic mechanical diagram of a computer device provided in an embodiment of the present disclosure. The computer device 902 may include one or more processors 904, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 902 may also include any memory 906 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 906 may include any one or more of the following in combination: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 902. In one case, when the processor 904 executes the associated instructions, which are stored in any memory or combination of memories, the computer device 902 can perform any of the operations of the associated instructions. The computer device 902 also includes one or more drive mechanisms 908, such as a hard disk drive mechanism, an optical disk drive mechanism, etc., for interacting with any memory.
The duty server 102 and the technical support terminal 103 in the embodiment of the present disclosure may be computer devices described in fig. 9.
Corresponding to the methods in fig. 1-2 and 5-8, the embodiments herein also provide a computer-readable storage medium having stored thereon a computer program, which, when executed by a processor, performs the steps of the above-described method.
Embodiments herein also provide computer readable instructions, wherein a program therein causes a processor to perform the methods as shown in fig. 1-2 and fig. 5-8 when the instructions are executed by the processor.
It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.
It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments herein.
In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The principles and embodiments of this document are explained herein using specific examples, which are presented only to aid in understanding the methods and their core concepts; meanwhile, for the general technical personnel in the field, according to the idea of this document, there may be changes in the concrete implementation and the application scope, in summary, this description should not be understood as the limitation of this document.
Claims (14)
1. A visual on-duty emergency treatment interaction method is characterized by comprising the following steps:
acquiring and displaying first alarm information of a fault;
generating shared alarm information according to the first alarm information;
sending the sharing alarm information to a technical support terminal;
receiving a request for acquiring second alarm information sent by the technical support terminal;
acquiring second alarm information according to the second alarm information acquisition request and the application permission of the fault;
sending the second alarm information to a technical support terminal;
receiving the technical support terminal to generate a fault processing scheme according to the shared alarm information and the second alarm information;
executing the fault handling scheme to resolve the fault.
2. The visual emergency treatment on duty interaction method according to claim 1, wherein the first alarm information is alarm information related to the fault, and includes at least: server information, alarm events, error reporting information, and application responsible personnel information.
3. The visual emergency treatment on duty interaction method of claim 2, wherein the generating shared alarm information according to the first alarm information comprises:
acquiring the total information of server information, alarm events and error reporting information in the first alarm information;
and performing screen capture on the display interface of the full information, and taking a screen capture image as the shared alarm information.
4. The visual on-duty emergency treatment interaction method of claim 3,
the total information of the server information comprises a server address, a server name and server network information;
the total information of the alarm event comprises the number, the name and the danger level of the alarm event;
the total information of the error reporting information comprises error reporting starting time, error reporting duration and specific contents of error reporting.
5. The visual emergency treatment on duty interaction method of claim 3, wherein in obtaining the full amount of information of server information, alarm events and error reporting information in the first alarm information further comprises:
and acquiring the full information or partial full information of the server information, the alarm event and the error reporting information in the first alarm information according to the common grade corresponding to the fault.
6. The visual on-duty emergency treatment interaction method of claim 2, wherein sending the shared alert information to a technical support terminal further comprises,
and inquiring the address of the technical support terminal according to the information of the application responsible personnel in the first alarm information, and sending the shared alarm information to the technical support terminal.
7. The visual emergency treatment on duty interaction method of claim 1, wherein generating shared alarm information according to the first alarm information further comprises:
determining key information of the first alarm information;
matching key information of the first alarm information in a preset scene library;
when the matching is successful, generating a fault processing scheme aiming at the fault;
and when the matching fails, generating shared alarm information according to the first alarm information.
8. The visual on-duty emergency treatment interaction method of claim 1, wherein the application authority of the fault comprises: and fault information related to various faults, wherein each fault information has a corresponding safety level.
9. The visual on-duty emergency treatment interaction method of claim 8, wherein the obtaining the second alarm information according to the request for obtaining the second alarm information and the service authority of the fault further comprises:
acquiring the fault information according to the demand information in the second alarm information request;
comparing the authority information of the application responsible personnel in the second alarm information request with the application authority of the fault information;
and taking the fault information which is in accordance with the authority of the application responsible personnel in the second alarm information request as the second alarm information.
10. The visual on-duty emergency treatment interaction method of claim 1, wherein the receiving the fault handling scheme generated by the technical support terminal according to the shared alarm information and the second alarm information comprises:
determining key information of the shared alarm information and the second alarm information by the technical support terminal;
and matching the key information in a preset scene library, judging whether the matching is successful, and generating a fault processing scheme aiming at the fault when the matching is successful.
11. The visual on-duty emergency treatment interaction method of claim 1, wherein the fault handling scheme comprises one or a combination of: repairing, deleting, recovering, backing up, stopping running and alarming.
12. A visual emergency disposal device on duty, comprising:
the first alarm information acquisition unit is used for acquiring and displaying first alarm information of a fault;
the shared alarm information generating unit is used for generating shared alarm information according to the first alarm information;
the sharing alarm information sending unit is used for sending the sharing alarm information to a technical support terminal;
the second alarm information request receiving unit is used for receiving a request for acquiring second alarm information sent by the technical support terminal;
the second alarm information acquisition unit is used for acquiring second alarm information according to the second alarm information acquisition request and the application permission of the fault;
the second alarm information sending unit is used for sending the second alarm information to the technical support terminal;
a fault processing scheme receiving unit, configured to receive a fault processing scheme generated by the technical support terminal according to the shared alarm information and the second alarm information;
an execution unit to execute the failure handling scheme to resolve the failure.
13. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the visual on-duty emergency treatment interaction method of any one of claims 1 to 11 when executing the computer program.
14. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the visual on-duty emergency treatment interaction method of any one of the preceding claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110834979.2A CN113468024A (en) | 2021-07-23 | 2021-07-23 | Visual on-duty emergency disposal interaction method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110834979.2A CN113468024A (en) | 2021-07-23 | 2021-07-23 | Visual on-duty emergency disposal interaction method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113468024A true CN113468024A (en) | 2021-10-01 |
Family
ID=77882078
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110834979.2A Pending CN113468024A (en) | 2021-07-23 | 2021-07-23 | Visual on-duty emergency disposal interaction method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113468024A (en) |
-
2021
- 2021-07-23 CN CN202110834979.2A patent/CN113468024A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020088326A1 (en) | Interface operation and maintenance method and apparatus | |
| CN106548402B (en) | Resource transfer monitoring method and device | |
| CN112115026B (en) | Server cluster monitoring method and device, electronic equipment and readable storage medium | |
| CN112631913B (en) | Method, device, equipment and storage medium for monitoring operation faults of application program | |
| CN107800783B (en) | Method and device for remotely monitoring server | |
| CN112636957A (en) | Early warning method and device based on log, server and storage medium | |
| US10915510B2 (en) | Method and apparatus of collecting and reporting database application incompatibilities | |
| CN111339540A (en) | Computer accounting data anti-theft device and control method thereof | |
| RU2688254C1 (en) | Self-service device network monitoring system | |
| CN113595886A (en) | Instant messaging message processing method and device, electronic equipment and storage medium | |
| CN113468024A (en) | Visual on-duty emergency disposal interaction method and device | |
| CN117173839A (en) | Intelligent early warning method and system for monitoring financial machines | |
| CN114884696A (en) | Fraud early warning method, device, equipment and storage medium | |
| CN112180783B (en) | Information monitoring management method and device based on Internet | |
| CN113676356A (en) | Alarm information processing method and device, electronic equipment and readable storage medium | |
| US20120173495A1 (en) | Computer Readable Medium, Systems, and Methods of Detecting a Discrepancy in a Chain-of-title of an Asset | |
| CN110362464B (en) | Software analysis method and equipment | |
| CN111835566A (en) | System fault management method, device and system | |
| CN111242770B (en) | Risk equipment identification method and device, electronic equipment and readable storage medium | |
| CN111045723B (en) | Method and device for notifying code change between associated systems | |
| US20240184643A1 (en) | Proactive monitoring of file status updates in transaction systems | |
| KR101883407B1 (en) | detecting methods and systems of prevention check for information system using agentless | |
| CN114924900A (en) | Abnormal information processing method and device and electronic equipment | |
| CN117097692A (en) | Session storage system | |
| CN116302652A (en) | System alarm information processing method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |