CN113312202B - Fault processing logic generation method, device, equipment and medium based on component - Google Patents
Fault processing logic generation method, device, equipment and medium based on component Download PDFInfo
- Publication number
- CN113312202B CN113312202B CN202110866472.5A CN202110866472A CN113312202B CN 113312202 B CN113312202 B CN 113312202B CN 202110866472 A CN202110866472 A CN 202110866472A CN 113312202 B CN113312202 B CN 113312202B
- Authority
- CN
- China
- Prior art keywords
- fault
- fault processing
- component
- processing logic
- information
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0781—Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to a fault handling logic generation method, device, equipment and medium based on components. The method comprises the following steps: receiving a fault processing logic generation request, and acquiring a pre-generated component based on the fault processing logic generation request; receiving an operation instruction aiming at the component, and connecting the selected component according to the operation instruction; when the component needs to input control parameters, locking the connection operation of the component, outputting a control parameter input prompt, and releasing the connection operation of the component after receiving the input control parameters; and after the connection of the components is completed, the connected components are sent to a back end, so that the back end generates a fault processing logic according to the connected components, and the fault processing logic is used for sending the fault processing logic to a control end, so that the control end controls a corresponding host to execute the fault processing logic according to the fault processing logic. By adopting the method, the fault processing logic can be flexibly generated.
Description
Technical Field
The present application relates to the field of operation and maintenance technologies, and in particular, to a method, an apparatus, a device, and a medium for generating a fault handling logic based on a component.
Background
Along with the development of artificial intelligence technology, intelligent operation and maintenance technology appears, and the intelligent operation and maintenance technology is developed in a superitem operation and maintenance automation and intelligentization direction. The influence of automation on IT operation and maintenance is not only the relation between people and equipment, but also the level of customer service-oriented drive IT operation and maintenance decision, and the composition of an IT operation and maintenance team is also developed from the situation that technicians at all levels account for most of the IT operation and maintenance to the situation that business personnel even users account for most of the IT operation and maintenance.
However, in the conventional technology, the automation operation and maintenance needs to write the corresponding script separately and then use the script after debugging, so that the script needs to be checked again when the script needs to be modified, and the script can be adjusted after the script logic is fully understood, which consumes a lot of time.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method, an apparatus, a device, and a medium for generating a component-based failure handling logic, which are capable of flexibly generating a failure handling logic.
A component-based fault handling logic generation method applied to a front end, the method comprising:
receiving a fault processing logic generation request, and acquiring a pre-generated component based on the fault processing logic generation request;
receiving an operation instruction aiming at the component, and connecting the selected component according to the operation instruction;
when the component needs to input control parameters, locking the connection operation of the component, outputting a control parameter input prompt, and releasing the connection operation of the component after receiving the input control parameters;
and after the connection of the components is completed, the connected components are sent to a back end, so that the back end generates a fault processing logic according to the connected components, and the fault processing logic is used for sending the fault processing logic to a control end, so that the control end controls a corresponding host to execute the fault processing logic according to the fault processing logic.
In one embodiment, the components include at least one of a start component, an end component, a judge component, a job component, a sub-flow component, a parallel component, a merge component, and a control component;
the operation assembly is used for calling an interface of the control end, transmitting fault processing logic and indicating the control end to distribute the fault processing logic to a corresponding host for execution;
the sub-flow components are used to invoke stored fault handling logic.
A fault processing method adopts the fault processing logic generated by the component-based fault processing logic generation method and is applied to a control end, and the fault processing method comprises the following steps:
receiving a fault processing request, wherein the fault processing request carries a fault processing identifier;
inquiring corresponding fault processing information according to the fault processing identifier, and judging whether to perform fusing or not based on the fault processing information;
when it is determined that fusing is not required based on the fault processing information, the control host performs corresponding information detection based on the fault processing logic;
and if the information detects that a fault exists, executing a corresponding fault self-healing processing step based on the fault processing logic.
In one embodiment, the determining whether to perform fusing based on the fault handling information includes:
judging whether the frequency of the fault processing request in a preset time period exceeds a preset frequency or not, or
Judging whether the user authority corresponding to the fault processing request is correct or not, or
And judging whether the fault processing logic, the application and the business owner of the host corresponding to the fault processing request are consistent.
In one embodiment, the control host performs corresponding information detection based on the fault handling logic, including:
and executing corresponding information detection based on the fault processing logic, and judging the branch flow direction in the fault processing logic based on a ternary operator in the fault processing logic so as to determine the flow of the next information detection until the execution of the fault processing logic is completed.
In one embodiment, before the controlling host performs the corresponding information detection based on the fault handling logic, the method further includes:
and calling a preset interface according to the fault processing information to acquire the corresponding host.
An alarm processing method, comprising:
receiving alarm information sent by a monitoring system;
cleaning the alarm information through a preset alarm rule to obtain alarm information to be processed which needs to be automatically processed;
and distributing the alarm information to a corresponding control end so that the control end processes the fault corresponding to the alarm information according to the fault processing method in any embodiment.
In one embodiment, the obtaining of the to-be-processed alarm information that needs to be automatically processed by cleaning the alarm information according to the preset alarm rule includes:
judging whether the alarm information is alarm information of a preset system or not based on a shielding strategy so as to clean the alarm information to obtain alarm information to be processed which needs to be automatically processed; and/or
And cleaning the alarm information according to the processing time interval based on a convergence strategy to obtain the alarm information to be processed which needs to be automatically processed.
A component-based fault handling logic generation apparatus for use in a front end, the apparatus comprising:
the first receiving module is used for receiving a fault processing logic generation request and acquiring a pre-generated component based on the fault processing logic generation request;
the second receiving module is used for receiving an operation instruction aiming at the component and connecting the selected component according to the operation instruction;
the component operation module is used for locking the connection operation of the component when the component needs to input control parameters, outputting a control parameter input prompt, and releasing the connection operation of the component after receiving the input control parameters;
and the logic generation module is used for sending the connected components to a back end after the components are connected, so that the back end generates fault processing logic according to the connected components, and the fault processing logic is used for sending the fault processing logic to a control end, so that the control end controls a corresponding host to execute the fault processing logic according to the fault processing logic.
A computer device comprising a memory storing a computer program and a processor implementing the steps of the method of any of the above embodiments when the processor executes the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any of the above embodiments.
According to the method, the device, the equipment and the medium for generating the fault handling logic based on the component, the fault handling logic is compiled through front-end interactive design, the control layer logic is realized at the rear end, the interface service is provided, the client side on the application host is called, the remote flow control is realized, and then the fault automatic handling is carried out.
Drawings
FIG. 1 is a diagram of an application environment for a component-based fault handling logic generation methodology in one embodiment;
FIG. 2 is a flow diagram that illustrates a method for component-based fault handling logic generation, according to one embodiment;
FIG. 3 is a flow diagram illustrating a method for fault handling in one embodiment;
FIG. 4 is a schematic diagram of failure handling logic in one embodiment;
FIG. 5 is a flowchart illustrating an alarm handling method according to an embodiment;
FIG. 6 is a flow diagram of the multi-terminal processing of the alarm handling method in one embodiment;
FIG. 7 is a flow diagram of an alert processing method in another embodiment;
FIG. 8 is a block diagram of an apparatus for component-based fault handling logic generation in one embodiment;
FIG. 9 is a block diagram showing the structure of a failure processing apparatus according to an embodiment;
FIG. 10 is a block diagram showing the structure of an alarm processing device according to an embodiment;
FIG. 11 is a diagram illustrating an internal structure of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The component-based fault handling logic generation method provided by the application can be applied to the application environment shown in fig. 1. Where the front end 102 communicates with the back end 104 over a network, the back end 104 communicates with the control end 106 over a network, and the control end 106 communicates with the host 108 over a network. The front end 102 receives a fault handling logic generation request, and acquires a pre-generated component based on the fault handling logic generation request; receiving an operation instruction aiming at the components, and connecting the selected components according to the operation instruction; when the component needs to input the control parameters, the connection operation of the component is locked, the control parameter input prompt is output, and after the input control parameters are received, the connection operation of the component is released; after the connection of the components is completed, the connected components are sent to the back end 104, so that the back end 104 generates a fault handling logic according to the connected components, and the fault handling logic is used for sending the fault handling logic to the control end 106, so that the control end 106 controls the corresponding host 108 to execute the fault handling logic according to the fault handling logic. The front end 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the back end 104, the control end 106, and the host 108 may be implemented by independent servers or a server cluster formed by a plurality of servers.
In one embodiment, as shown in fig. 2, a method for generating component-based fault handling logic is provided, which is described by taking the method as an example applied to the front end in fig. 1, and includes the following steps:
s202: and receiving a fault processing logic generation request, and acquiring a pre-generated component based on the fault processing logic generation request.
First, the fault handling logic refers to a control flow for handling a fault, which can detect whether a fault exists in a host and cure the fault existing in the host based on the control flow.
The components comprise at least one of a starting component, an ending component, a judging component, an operation component, a sub-process component, a parallel component, a merging component and a control component, and the components can be dragged on a front-end page for a user to adjust, so that corresponding fault processing logic is generated.
The starting component and the ending component are used as the starting and ending marks of the fault processing logic, and the front end is realized through the identifiers; the judgment component is realized through the judgment of the front end if, if can appear for any number of times, else can appear for 0 time or 1 time; the operation component calls a standard interface of the control end, transmits commands, scripts and the like which need to be executed, the commands, the scripts and the like are distributed to the host computer by the control end to be executed, and the host computer returns an execution result to the control end and the rear-end control logic layer; the sub-process component calls other saved control processes; the parallel component generates a plurality of branches and executes the branches in parallel; merging all the branches of the executed tasks of the components, and entering a subsequent flow after all the branches are converged; the control component may perform operations such as ignore errors, pause, skip, retry, etc.
And drawing the flow in a component dragging mode. If judgment conditions need to be manually added to the judgment component, an operation script needs to be manually input to the operation component, and the merging component requires that all parallel branches return at the same time before the next component can be reached.
S204: and receiving an operation instruction aiming at the components, and connecting the selected components according to the operation instruction.
Specifically, the operation instruction of the component refers to an input instruction for dragging the component to determine the position of the component and modify parameters in the component, and the front end connects the selected component with the processed component according to the operation instruction, so as to form a fault handling logic.
S206: when the component needs to input the control parameters, the connection operation of the component is locked, the control parameter input prompt is output, and after the input control parameters are received, the connection operation of the component is released.
Specifically, the control parameter refers to a parameter that the component needs to correspond to determine the flow direction of the process, for example, determining an if determination condition of the component, an operation script of the operation component, and the like, and before the component is not input to the corresponding control parameter, locking a connection operation, and after a user inputs the control parameter, determining the flow direction, releasing the connection operation, and determining the direction of the fault processing logic.
S208: and after the connection of the components is completed, the connected components are sent to the rear end, so that the rear end generates fault processing logic according to the connected components, and the fault processing logic is used for sending the fault processing logic to the control end, so that the control end controls the corresponding host to execute the fault processing logic according to the fault processing logic.
Specifically, the back-end engineer completes the main business logic of the back-end, provides an interface and data for the front-end, receives scripts and files transmitted by the front-end, executes parameters such as users and variables, calls a control-end interface, and distributes tasks to the host through the control-end. The host task execution result and the standard output are transmitted back to the control end, and are returned to the back end through the control end, and finally returned to the front end. The front end outputs and displays the standard during execution to a user, and transmits the result to the judgment component to determine the flow trend.
The Master, namely the control end and the agent, namely the host, use a Zeromq communication and data transmission mode. When the control end sends the operation to the host, the operation is realized by using a zeromq pub/sub socket, all transmitted data are encrypted, and only the members of the host can decrypt the issued message. When the host transmits data back to the control end, the data is transmitted back by using a req/rep socket of zeromq, and the interface is mainly used for transmitting back the operation result and the standard output when the operation is executed.
In the embodiment, the agent is installed in the host, the master communication with the control end is realized, and the command is remotely executed at the agent end through the master. On a browser, fault processing logic is compiled and a fault automatic processing strategy is formulated through component dragging, script compiling and logic configuration.
According to the fault handling logic generation method based on the components, through the front-end interactive design, the fault handling logic is compiled, the control layer logic is realized at the rear end, the interface service is provided, the client side on the application host is called, the remote flow control is realized, and then the fault automatic handling is carried out.
In addition, scripts are not needed to be carried out on the server, the process is universal, the differentiated information is configured and managed in a zho configuration management center, fault processing is carried out by using process control, and the method is flexible and easy to adjust; resource consumption on the server is reduced, and whether the application is normal or not does not need to be regularly checked.
In an embodiment, as shown in fig. 3, a fault handling method is provided, where the fault handling method uses the fault handling logic generated by the component-based fault handling logic generation method in any of the above embodiments, and is described by taking the method applied to the control end in fig. 1 as an example, and includes the following steps:
s302: and receiving a fault processing request, wherein the fault processing request carries a fault processing identifier.
In particular, the fault handling request may be sent by a service person or automatically generated by the system. The fault processing identifier is an identifier for indicating a fault needing to be processed or an application needing to be detected, and has uniqueness.
S304: and inquiring corresponding fault processing information according to the fault processing identifier, and judging whether to perform fusing or not based on the fault processing information.
Specifically, fusing is to determine whether the number of triggering times exceeds a limit within a specified time period, whether the executing user is unauthorized, whether the business owner is consistent, and the like, and if fusing is triggered, sending a notification, and ending the process. The fusing is to avoid the excessive execution times of the flow, and the override is to judge whether the override is consistent with the business owner by judging whether the script in the fusing is successfully executed.
Specifically, fusing may include: and judging whether the frequency of the fault processing request in a preset time period exceeds a preset frequency, or judging whether the user authority corresponding to the fault processing request is correct, or judging whether the fault processing logic, the application and the business owner of the host corresponding to the fault processing request are consistent.
That is, the fusing may mainly include the following triggering items: and (4) limiting times: whether the triggering times in the specified time period exceed a set value or not can avoid multiple triggering, so that the system has problems, for example, the repeated execution of the fault automatic processing of an application layer caused by host faults, network abnormity and the like can be avoided. Whether the business owner is consistent: the consistency of the business owner of the process, the application and the host must be ensured, so that the process is prevented from being triggered accidentally due to configuration errors. Whether the right is overridden: whether the appointed user has the application start-stop authority, whether the appointed user has the script execution authority, the related path authority and the like can avoid unauthorized operation.
S306: when it is determined that fusing is not required based on the fault handling information, the control host performs corresponding information detection based on the fault handling logic.
Specifically, the information detection may include, but is not limited to, host resource detection, port detection, application detection, and the like.
Specifically, referring to fig. 4, fig. 4 is a schematic diagram of a fault handling logic in an embodiment, in the embodiment, a fusing detection is performed first, and if fusing is triggered, a notification is directly sent, and the process ends.
If the sony end is not triggered, the subsequent information detection is performed, as shown in fig. 4, which includes host resource detection, port detection, and application detection. The method comprises the steps of detecting host resources, checking whether the utilization rate of a host disk exceeds 95% or not, and whether inodes value is 100% or not, if so, sending a notification, and ending the process.
If the host resource detection is passed, continuing the port detection, detecting the port state and the down state of the alarm port, and directly entering the next starting process; the up state enters the next application detection.
And when the port is detected to be in the up state, continuing to perform application detection, detecting whether the application is normal or not by using an application detection script corresponding to the alarm port, and if the application is abnormal, entering the next step and forcibly ending the application process. If the application is normal, a notification is sent, and the process is ended. And in the process of ending the application, stopping the process by using the starting script corresponding to the alarm port. And then starting the process, and starting the process by using a starting script corresponding to the alarm port. This again checks whether the alarm port is back to normal. And if the application is normal, performing application health detection, and if the application health detection is abnormal, sending a notice. If the port detection is normal, whether the application corresponding to the alarm port is normal is detected again. And if the abnormal condition exists, sending a notice. Therefore, a processing record needs to be added at last so as to be convenient for judging next fusing.
S308: and if the information detects that the fault exists, executing a corresponding fault self-healing processing step based on the fault processing logic.
Specifically, referring to fig. 4, when the port detection state is port down, that is, when there is a fault, a process is started, that is, the port is restarted, so as to implement fault self-healing. When the application is detected to be abnormal, the process is ended first, and then the process is started to realize fault self-healing.
In the embodiment, the automatic analysis and automatic processing scheme of the multi-instance application fault is provided, the problem that the multi-instance fault is difficult to self-heal in a complex scene is solved, the resource consumption on the server is reduced, and whether the application is normal or not does not need to be regularly patrolled.
In one embodiment, the control host performs corresponding information detection based on the fault handling logic, including: and executing corresponding information detection based on the fault processing logic, and judging the branch flow direction in the fault processing logic based on a ternary operator in the fault processing logic so as to determine the flow of the next information detection until the execution of the fault processing logic is completed.
Specifically, in the process control of the whole flow, each step requires remote execution of a command and acquisition of an execution result, and the branch flow direction is determined by judging the execution result. And the remote execution command issues a task to the agent by calling the master interface, and returns an execution result through the agent. Branch flow direction determination is determined by a ternary operator. The ternary operator is a fixed format in software programming, and the expression is as follows: operand 1
Operand 2: operand 3, where operand 1 is of the pool type, and operands 2 and 3 are branches, and if operand 1 determines that the result is true, operand 2 is returned, and if the result is false, the operation is returnedAnd (3) counting. Referring to fig. 4, the port detection produces an operation result $ { _ result }, the result variable is of a pool type, if { _ result } = = false, it is determined that the port is in a down state, and the port is taken down in the upper diagram, and the notification is directly sent; if $ { _ result } = = true, it is determined as the port up state, and the port up branch is taken in the upper diagram, and application detection is performed.
In one embodiment, before the control host performs the corresponding information detection based on the fault handling logic, the method further includes: and calling a preset interface according to the fault processing information to acquire the corresponding host.
Specifically, the control end calls a CMDB interface according to a parameter IP transmitted by a process, transmits IP parameters, and acquires a network area, a host type and the like of a host bound by the IP; obtaining the application to which the IP belongs from an application configuration management center, obtaining the application information of multiple instances, and returning a result as a json file with the format:
{
“port1”:
{
“port_check”: “port check command”,
“stop”: “application start command or start scripts”,
“start”: “application start command or start scripts”
},
“port2”:
{
“port_check”: “port check command”,
“stop”: “application start command or start scripts”,
“start”: “application start command or start scripts”
},
...
}
wherein, port1 and port2 are ports monitored after the application is started, port check command is a command for detecting whether the port is started, and application start/stop command or start scripts are start and stop commands or scripts of the application.
In this embodiment, referring to fig. 4, a detailed description is provided for this embodiment, where after receiving a fault processing request, a control end first performs fusing detection according to fault information, if the fusing detection passes, continues to acquire application information, and after the fusing detection passes, performs host resource detection, port detection, application detection, and the like. And when the port detection fails, starting the process to realize self-healing of the port, and when the application detection fails, firstly ending the port process, and then restarting the process, and then carrying out the port detection and the application detection again.
Therefore, resource consumption on the server is reduced, and whether the application is normal or not does not need to be regularly checked.
In one embodiment, as shown in fig. 5, an alarm processing method is provided, which is described by taking the method as an example for being applied to the backend in fig. 1 or another alarm center, and includes the following steps:
s502: and receiving alarm information sent by the monitoring system.
Specifically, the monitoring system includes various monitoring systems for monitoring states of the hosts and the like, and determining whether to generate alarm information according to the states of the hosts, and if so, sending the alarm information to an alarm center. The enterprise level monitoring is various in types, complete in coverage, accurate in positioning and generally adopts a unified alarm outlet. And various monitoring systems uniformly push the generated alarms to an alarm center.
S504: and cleaning the alarm information through a preset alarm rule to obtain the alarm information to be processed which needs to be automatically processed.
Specifically, the preset alarm rule is preset, and the purpose is to identify the alarm information to be processed which needs to be automatically processed. Specifically, the method for cleaning the alarm information by the preset alarm rule to obtain the alarm information to be processed which needs to be automatically processed includes: judging whether the alarm information is the alarm information of a preset system or not based on a shielding strategy so as to clean the alarm information to obtain the alarm information to be processed which needs to be automatically processed; and/or cleaning the alarm information according to the processing time interval based on the convergence strategy to obtain the alarm information to be processed which needs to be automatically processed.
Wherein, the alarm center displays various alarms in a unified way, and performs alarm convergence, assignment, configuration of automatic processing rules and the like.
S506: and distributing the alarm information to the corresponding control end so that the control end processes the fault corresponding to the alarm information according to the fault processing method in any embodiment.
Specifically, the alarm center distributes alarm information to corresponding control terminals, the automation operation and maintenance platform receives the alarm information to be processed, and acquires host and application information such as users, IP addresses, network areas, application deployment paths, log paths, start and stop commands and the like through the CMDB. Through the configured control flow, the operation center is called to perform operation according to the steps, and the flow trend is controlled according to the returned operation result, as shown in fig. 6, the CMDB includes host management, application system management, user management, network device management, and the like. And the automatic operation and maintenance platform acquires the required configuration information from the CMDB. And calling the operation center to perform operation according to the steps according to the control flow. The job center may invoke the host to execute the command and return the result. Which may be shell commands, python, perl scripts, etc. The host application server is provided with an agent of the operation center, and can remotely execute the command on the host through the operation center. The host computer returns the execution result of the command or the script to the operation center. The result of the current operation of the operation center is returned to the automatic operation and maintenance platform, and the automatic operation and maintenance platform returns the result of the automatic processing of the current alarm to the alarm center. And the alarm center updates the alarm state.
The alarm information processing method realizes the cooperative work of the monitoring center, the alarm center, the fault self-healing center, the CMDB, the operation platform and the like, and automatically processes the alarm information.
Referring to fig. 7, fig. 7 is a flowchart of an alarm processing method in another embodiment, after receiving alarm information sent by a monitoring system, an alarm center first processes a format of the alarm information to clean the alarm information, deletes the alarm information whose format does not meet requirements, and then cleans the alarm information by a preset alarm rule, where the following indexes are available for matching: alarm source, alarm index, alarm name, alarm content, alarm level, alarm IP and alarm name. The indexes can be matched in any mode of OR and AND, a single index can be matched in three modes of 'including', 'equal' and 'regular', and after matching is successful, automatic alarm processing can be carried out according to a set flow. When the indexes are matched, the shielding strategy matching and the convergence strategy matching are mainly involved, wherein the shielding strategy can be related to the system, for example, only alarm information of part of the system is processed within a period of time, and the convergence strategy is that only one of the alarm information needs to be processed because the alarm information is usually continuously sent, so that a time interval is set, and only the first alarm information is processed in a certain time interval.
After the alarm information is cleaned, the alarm information is matched with a preset processing strategy, if the alarm information needs to be automatically processed, the alarm information is distributed to a corresponding control end, so that the fault corresponding to the alarm information is processed according to the fault processing method, and after the processing is successful, the alarm state is switched. Similarly, if manual processing is needed, matching the corresponding person according to the allocation strategy, and then performing manual processing, and if the corresponding person is not matched according to the allocation strategy, matching can be performed according to the organization architecture of the system to which the alarm belongs so as to determine that the alarm information is allocated to the specific person.
In addition, in the whole process of processing the alarm information, a uniform interface needs to be provided in each step, a unique identifier needs to be marked from the source, and the identifier needs to be transferred in the whole process until the original link is returned. All interfaces need to communicate some necessary identification information, in addition to the parameters required for each link to operate, which may include: the transaction id is the only transaction id and is generated by the first link; the alarm id is an alarm id; the system name is an application name corresponding to the alarm; the IP address is an IP address corresponding to the alarm; the alarm source is the alert source.
The monitoring system needs to provide an interface for updating the monitoring state; the alarm center needs to provide an interface for receiving the alarm and update the interface of the alarm state; the automatic operation and maintenance platform needs to provide an interface for receiving an alarm, call an interface of a standard flow, and receive an operation result, an operation output and an interface for reporting error information returned by the operation center; the operation center needs to provide an interface for receiving operation and an interface for receiving the operation result of the host command; the host needs to provide an interface for receiving the job; the CMDB requires various host information interfaces, application information interfaces, and the like to be provided.
In the embodiment, the cooperative work of the monitoring center, the alarm center, the fault self-healing center, the CMDB, the operation platform and the like is realized.
It should be understood that, although the steps in the above-described flowcharts are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the above-mentioned flowcharts may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the steps or the stages is not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a part of the steps or the stages in other steps.
In one embodiment, as shown in fig. 8, there is provided a component-based fault handling logic generation apparatus, including: a first receiving module 120, a second receiving module 140, a component operating module 160, and a logic generating module 180, wherein:
a first receiving module 120, configured to receive a fault handling logic generation request, and obtain a pre-generated component based on the fault handling logic generation request;
a second receiving module 140, configured to receive an operation instruction for a component, and connect the selected component according to the operation instruction;
the component operation module 160 is used for locking the connection operation of the component when the component needs to input the control parameters, outputting a control parameter input prompt, and releasing the connection operation of the component after receiving the input control parameters;
the logic generating module 180 is configured to send the connected component to the back end after the component connection is completed, so that the back end generates a fault processing logic according to the connected component, and the fault processing logic is sent to the control end, so that the control end controls the corresponding host to execute the fault processing logic according to the fault processing logic.
In one embodiment, the components include at least one of a start component, an end component, a judge component, a job component, a sub-flow component, a parallel component, a merge component, and a control component;
the operation assembly is used for calling an interface of the control end, transmitting the fault processing logic and indicating the control end to distribute the fault processing logic to the corresponding host for execution;
the sub-flow component is for invoking stored fault handling logic.
In one embodiment, as shown in fig. 9, there is provided a fault handling apparatus, which is applied to a control end and adopts the fault handling logic generated by the component-based fault handling logic generation apparatus, and includes: the third receiving module 220, the fusing judgment module 240, the information detection module 260 and the self-healing processing module 280, wherein:
a third receiving module 220, configured to receive a fault handling request, where the fault handling request carries a fault handling identifier;
a fusing judgment module 240, configured to query corresponding fault processing information according to the fault processing identifier, and judge whether to perform fusing based on the fault processing information;
an information detection module 260, configured to, when it is determined that fusing is not required based on the fault handling information, perform corresponding information detection based on the fault handling logic by the control host;
and the self-healing processing module 280 is configured to, if the information detection has a fault, execute a corresponding fault self-healing processing step based on the fault processing logic.
In one embodiment, the fusing determination module 240 is further configured to determine whether the number of times of the fault processing request in the preset time period exceeds a preset number of times, or determine whether a user right corresponding to the fault processing request is correct, or determine whether a fault processing logic, an application, and a service owner to which the host belongs, corresponding to the fault processing request, are consistent.
In one embodiment, the information detection module 260 is further configured to perform corresponding information detection based on the fault handling logic, and determine a branch flow direction in the fault handling logic based on a ternary operator in the fault handling logic to determine a flow of a next information detection until the fault handling logic is completed.
In one embodiment, the fault handling apparatus further includes:
and the host acquisition module is used for calling the preset interface according to the fault processing information to acquire the corresponding host.
In one embodiment, as shown in fig. 10, there is provided an alert processing apparatus including: a fourth receiving module 320, a cleaning module 340, and an alert processing module 360, wherein:
a fourth receiving module 320, configured to receive alarm information sent by the monitoring system;
the cleaning module 340 is configured to clean the alarm information according to a preset alarm rule to obtain to-be-processed alarm information that needs to be automatically processed;
the alarm processing module 360 is configured to allocate the alarm information to the corresponding control end, so that the control end processes the fault corresponding to the alarm information according to the fault processing apparatus in any of the above embodiments.
In one embodiment, the cleaning module 340 includes:
the shielding strategy cleaning unit is used for judging whether the alarm information is the alarm information of a preset system or not based on the shielding strategy so as to clean the alarm information to obtain the alarm information to be processed which needs to be automatically processed; and/or
And the convergence strategy cleaning unit is used for cleaning the alarm information according to the processing time interval based on the convergence strategy to obtain the alarm information to be processed which needs to be automatically processed.
For specific limitations of the device for generating fault handling logic based on components, the device for processing fault, and the alarm device, reference may be made to the above limitations of the method for generating fault handling logic based on components, the method for processing fault, and the alarm method, which are not described herein again. The modules in the component-based fault handling logic generation apparatus, the fault handling apparatus and the alarm apparatus may be implemented in whole or in part by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 11. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a component-based fault handling logic generation method, a fault handling method, and an alarm method.
Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program: receiving a fault processing logic generation request, and acquiring a pre-generated component based on the fault processing logic generation request; receiving an operation instruction aiming at the components, and connecting the selected components according to the operation instruction; when the component needs to input the control parameters, the connection operation of the component is locked, the control parameter input prompt is output, and after the input control parameters are received, the connection operation of the component is released; and after the connection of the components is completed, the connected components are sent to the rear end, so that the rear end generates fault processing logic according to the connected components, and the fault processing logic is used for sending the fault processing logic to the control end, so that the control end controls the corresponding host to execute the fault processing logic according to the fault processing logic.
In one embodiment, the components involved in the execution of the computer program by the processor include at least one of a start component, an end component, a judge component, a job component, a sub-flow component, a parallel component, a merge component, and a control component; the operation assembly is used for calling an interface of the control end, transmitting the fault processing logic and indicating the control end to distribute the fault processing logic to the corresponding host for execution; the sub-flow component is for invoking stored fault handling logic.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program: receiving a fault processing request, wherein the fault processing request carries a fault processing identifier; inquiring corresponding fault processing information according to the fault processing identifier, and judging whether to perform fusing or not based on the fault processing information; when it is determined that fusing is not required based on the fault processing information, the control host performs corresponding information detection based on the fault processing logic; and if the information detects that the fault exists, executing a corresponding fault self-healing processing step based on the fault processing logic.
In one embodiment, determining whether to fuse based on fault handling information implemented when a processor executes a computer program comprises: and judging whether the frequency of the fault processing request in a preset time period exceeds a preset frequency, or judging whether the user authority corresponding to the fault processing request is correct, or judging whether the fault processing logic, the application and the business owner of the host corresponding to the fault processing request are consistent.
In one embodiment, a control host implemented when a processor executes a computer program performs corresponding information detection based on fault handling logic, comprising: and executing corresponding information detection based on the fault processing logic, and judging the branch flow direction in the fault processing logic based on a ternary operator in the fault processing logic so as to determine the flow of the next information detection until the execution of the fault processing logic is completed.
In one embodiment, before the control host implemented when the processor executes the computer program performs corresponding information detection based on the fault handling logic, the method further includes: and calling a preset interface according to the fault processing information to acquire the corresponding host.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program: receiving alarm information sent by a monitoring system; cleaning the alarm information through a preset alarm rule to obtain to-be-processed alarm information needing automatic processing; and distributing the alarm information to the corresponding control end so that the control end processes the fault corresponding to the alarm information according to the fault processing method in any embodiment.
In one embodiment, the method for cleaning the alarm information according to the preset alarm rule to obtain the alarm information to be processed, which is implemented when the processor executes the computer program, includes: judging whether the alarm information is the alarm information of a preset system or not based on a shielding strategy so as to clean the alarm information to obtain the alarm information to be processed which needs to be automatically processed; and/or cleaning the alarm information according to the processing time interval based on the convergence strategy to obtain the alarm information to be processed which needs to be automatically processed.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving a fault processing logic generation request, and acquiring a pre-generated component based on the fault processing logic generation request; receiving an operation instruction aiming at the components, and connecting the selected components according to the operation instruction; when the component needs to input the control parameters, the connection operation of the component is locked, the control parameter input prompt is output, and after the input control parameters are received, the connection operation of the component is released; and after the connection of the components is completed, the connected components are sent to the rear end, so that the rear end generates fault processing logic according to the connected components, and the fault processing logic is used for sending the fault processing logic to the control end, so that the control end controls the corresponding host to execute the fault processing logic according to the fault processing logic.
In one embodiment, the components involved in the execution of the computer program by the processor include at least one of a start component, an end component, a judge component, a job component, a sub-flow component, a parallel component, a merge component, and a control component; the operation assembly is used for calling an interface of the control end, transmitting the fault processing logic and indicating the control end to distribute the fault processing logic to the corresponding host for execution; the sub-flow component is for invoking stored fault handling logic.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving a fault processing request, wherein the fault processing request carries a fault processing identifier; inquiring corresponding fault processing information according to the fault processing identifier, and judging whether to perform fusing or not based on the fault processing information; when it is determined that fusing is not required based on the fault processing information, the control host performs corresponding information detection based on the fault processing logic; and if the information detects that the fault exists, executing a corresponding fault self-healing processing step based on the fault processing logic.
In one embodiment, determining whether to fuse based on fault handling information implemented when the computer program is executed by a processor includes: and judging whether the frequency of the fault processing request in a preset time period exceeds a preset frequency, or judging whether the user authority corresponding to the fault processing request is correct, or judging whether the fault processing logic, the application and the business owner of the host corresponding to the fault processing request are consistent.
In one embodiment, a control host implemented when the computer program is executed by a processor performs corresponding information detection based on fault handling logic, comprising: and executing corresponding information detection based on the fault processing logic, and judging the branch flow direction in the fault processing logic based on a ternary operator in the fault processing logic so as to determine the flow of the next information detection until the execution of the fault processing logic is completed.
In one embodiment, before the control host implemented when the computer program is executed by the processor performs the corresponding information detection based on the fault handling logic, the method further includes: and calling a preset interface according to the fault processing information to acquire the corresponding host.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving alarm information sent by a monitoring system; cleaning the alarm information through a preset alarm rule to obtain to-be-processed alarm information needing automatic processing; and distributing the alarm information to the corresponding control end so that the control end processes the fault corresponding to the alarm information according to the fault processing method in any embodiment.
In one embodiment, the method for cleaning the alarm information according to the preset alarm rule to obtain the alarm information to be processed, which is implemented when the computer program is executed by the processor, includes: judging whether the alarm information is the alarm information of a preset system or not based on a shielding strategy so as to clean the alarm information to obtain the alarm information to be processed which needs to be automatically processed; and/or cleaning the alarm information according to the processing time interval based on the convergence strategy to obtain the alarm information to be processed which needs to be automatically processed.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A fault handling method is applied to a control end, and is characterized in that the fault handling method comprises the following steps:
a control terminal receives a fault processing request, wherein the fault processing request carries a fault processing identifier, and the fault processing identifier is an identifier for indicating a fault needing to be processed;
the control terminal inquires corresponding fault processing information according to the fault processing identifier and judges whether to perform fusing or not based on the fault processing information;
when the control end judges that fusing is not needed based on the fault processing information, a CMDB interface is called according to a parameter IP transmitted by a process, IP parameters are transmitted, a network area where a host bound by the IP is located and a host type are obtained, an application to which the IP belongs is obtained from an application configuration management center, the host is controlled to execute corresponding information detection on the corresponding application based on fault processing logic, so that the front end receives a fault processing logic generation request, and a pre-generated component is obtained based on the fault processing logic generation request; the front end receives an operation instruction aiming at the component and connects the selected component according to the operation instruction; when the component needs to input control parameters, the front end locks the connection operation of the component, outputs a control parameter input prompt, and releases the connection operation of the component after receiving the input control parameters; after the components are connected, the front end sends the connected components to the rear end so that the rear end generates fault processing logic according to the connected components, the fault processing logic is used for sending the fault processing logic to the control end so that the control end controls a corresponding host to execute the fault processing logic according to the fault processing logic, and the information detection sequentially comprises host resource detection, port detection and application detection;
and if the information detection has a fault, the control end executes a corresponding fault self-healing processing step based on the fault processing logic, wherein the fault self-healing processing step is port restarting.
2. The fault handling method according to claim 1, wherein the control terminal determining whether to perform fusing based on the fault handling information includes:
the control terminal judges whether the frequency of the fault processing request in a preset time period exceeds a preset frequency or not, or
The control terminal judges whether the user authority corresponding to the fault processing request is correct or not, or
And the control terminal judges whether the fault processing logic, the application and the business owner of the host corresponding to the fault processing request are consistent.
3. The fault handling method according to claim 1, wherein the control-side control host performs corresponding information detection based on the fault handling logic, and includes:
and the control end executes corresponding information detection on the basis of the fault processing logic, and judges the branch flow direction in the fault processing logic on the basis of a ternary operator in the fault processing logic so as to determine the flow of the next information detection until the fault processing logic is executed.
4. The fault handling method of claim 1, wherein the components include at least one of a start component, an end component, a judge component, a job component, a sub-flow component, a parallel component, a merge component, and a control component;
the operation assembly is used for calling an interface of the control end, transmitting fault processing logic and indicating the control end to distribute the fault processing logic to a corresponding host for execution;
the sub-flow components are used to invoke stored fault handling logic.
5. An alarm processing method, characterized in that the alarm processing method comprises:
receiving alarm information sent by a monitoring system;
cleaning the alarm information through a preset alarm rule to obtain alarm information to be processed which needs to be automatically processed;
distributing the alarm information to a corresponding control end so that the control end processes the fault corresponding to the alarm information according to the fault processing method in any one of claims 1 to 4.
6. The method according to claim 5, wherein the cleaning of the alarm information by the preset alarm rule to obtain the alarm information to be processed which needs to be automatically processed comprises:
judging whether the alarm information is alarm information of a preset system or not based on a shielding strategy so as to clean the alarm information to obtain alarm information to be processed which needs to be automatically processed; and/or
And cleaning the alarm information according to the processing time interval based on a convergence strategy to obtain the alarm information to be processed which needs to be automatically processed.
7. A fault handling apparatus, wherein the fault handling apparatus is applied to a control terminal, and the fault handling apparatus comprises:
a third receiving module, configured to receive a fault handling request, where the fault handling request carries a fault handling identifier, and the fault handling identifier is an identifier used to indicate a fault to be handled;
the fusing judgment module is used for inquiring corresponding fault processing information according to the fault processing identifier and judging whether fusing is carried out or not based on the fault processing information;
the information detection module is used for calling a CMDB interface according to a parameter IP transmitted by a flow when the condition that fusing is not needed is judged based on the fault processing information, transmitting IP parameters, acquiring a network area where a host bound by the IP is located and a host type, acquiring an application to which the IP belongs from an application configuration management center, and controlling the host to execute corresponding information detection on the corresponding application based on the fault processing logic so that a front end receives a fault processing logic generation request and acquires a pre-generated component based on the fault processing logic generation request; the front end receives an operation instruction aiming at the component and connects the selected component according to the operation instruction; when the component needs to input control parameters, the front end locks the connection operation of the component, outputs a control parameter input prompt, and releases the connection operation of the component after receiving the input control parameters; after the components are connected, the front end sends the connected components to the rear end so that the rear end generates fault processing logic according to the connected components, the fault processing logic is used for sending the fault processing logic to the control end so that the control end controls a corresponding host to execute the fault processing logic according to the fault processing logic, and the information detection sequentially comprises host resource detection, port detection and application detection;
and the self-healing processing module is used for executing a corresponding fault self-healing processing step based on the fault processing logic if the information detection has a fault, wherein the fault self-healing processing step is a restarting port.
8. An alert processing apparatus, characterized in that the alert processing apparatus comprises:
the fourth receiving module is used for receiving the alarm information sent by the monitoring system;
the cleaning module is used for cleaning the alarm information through a preset alarm rule to obtain to-be-processed alarm information needing automatic processing;
an alarm processing module, configured to allocate the alarm information to a corresponding control end, so that the control end processes the fault corresponding to the alarm information according to the fault processing apparatus in claim 7.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 4 or 5 to 6.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 4 or 5 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110866472.5A CN113312202B (en) | 2021-07-29 | 2021-07-29 | Fault processing logic generation method, device, equipment and medium based on component |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110866472.5A CN113312202B (en) | 2021-07-29 | 2021-07-29 | Fault processing logic generation method, device, equipment and medium based on component |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113312202A CN113312202A (en) | 2021-08-27 |
| CN113312202B true CN113312202B (en) | 2021-11-12 |
Family
ID=77382376
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110866472.5A Active CN113312202B (en) | 2021-07-29 | 2021-07-29 | Fault processing logic generation method, device, equipment and medium based on component |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113312202B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112749064A (en) * | 2021-01-21 | 2021-05-04 | 北京明略昭辉科技有限公司 | Method and system for predicting and self-healing fault of software application service |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080126987A1 (en) * | 2006-09-19 | 2008-05-29 | International Business Machines Corporation | Graphical representation of compatible workflow steps |
| JP5712533B2 (en) * | 2010-09-15 | 2015-05-07 | 株式会社リコー | Information processing apparatus, job display program, and recording medium recording the program |
| GB2546253B (en) * | 2016-01-06 | 2020-04-22 | Ge Aviat Systems Ltd | Fusion of aviation-related data for comprehensive aircraft system health monitoring |
| CN111585782A (en) * | 2020-03-18 | 2020-08-25 | 国网江苏省电力有限公司信息通信分公司 | Comprehensive centralized alarm automatic processing system and method |
| CN111865665B (en) * | 2020-06-23 | 2023-10-13 | 广州衡昊数据科技有限公司 | Network equipment fault self-healing method and device |
| CN111831191A (en) * | 2020-07-22 | 2020-10-27 | 平安证券股份有限公司 | Workflow configuration method and device, computer equipment and storage medium |
| CN112051993B (en) * | 2020-08-17 | 2023-10-24 | 腾讯科技（深圳）有限公司 | Method, device, medium and equipment for generating state machine template and processing task |
| CN112527544B (en) * | 2020-11-23 | 2022-04-29 | 聚好看科技股份有限公司 | Server, and method and device for triggering fusing |
-
2021
- 2021-07-29 CN CN202110866472.5A patent/CN113312202B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112749064A (en) * | 2021-01-21 | 2021-05-04 | 北京明略昭辉科技有限公司 | Method and system for predicting and self-healing fault of software application service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113312202A (en) | 2021-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113169952B (en) | Container cloud management system based on block chain technology | |
| CN112840326A (en) | Test engine for automated operations management | |
| CN104205060B (en) | Be provided for the monitoring based on application and the recovery of the supervisory routine of HA cluster | |
| JP4945935B2 (en) | Autonomous operation management system, autonomous operation management method and program | |
| US20200007464A1 (en) | Method and management system of distributed computation | |
| WO2016183553A1 (en) | Query dispatch and execution architecture | |
| EP3509270B1 (en) | Data backup method and device, storage medium and electronic apparatus | |
| CN106911648B (en) | Environment isolation method and equipment | |
| CN112835782B (en) | Interface access test method and system | |
| CN108418859B (en) | Method and device for writing data | |
| CN107729213B (en) | Background task monitoring method and device | |
| JP2000148683A (en) | On-line system, data transmission managing method for the on-line system, and recording medium where program for managing data transmission is recorded | |
| CN114172785B (en) | Alarm information processing method, device, equipment and storage medium | |
| CN113312202B (en) | Fault processing logic generation method, device, equipment and medium based on component | |
| CN113296795A (en) | Application deployment method, device, equipment, storage medium and program product | |
| CN109118352A (en) | Remaining sum monitoring method, device, computer equipment and storage medium | |
| CN110704196B (en) | Resource data transfer method, device and block chain system | |
| US5668994A (en) | Conversation management routine for co-operative processing applications | |
| US9189370B2 (en) | Smart terminal fuzzing apparatus and method using multi-node structure | |
| CN116521460A (en) | Screen unlocking method and device for test equipment, electronic equipment and storage medium | |
| CN111694724A (en) | Testing method and device of distributed table system, electronic equipment and storage medium | |
| CN114816662A (en) | Container arrangement method and system applied to Kubernetes | |
| CN105790975A (en) | Service processing operation execution method and device | |
| CN109034768B (en) | Financial reconciliation method, apparatus, computer device and storage medium | |
| CN114691395A (en) | Fault processing method and device, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |