CN112434831A - Troubleshooting method and device, storage medium and computer equipment - Google Patents
Troubleshooting method and device, storage medium and computer equipment Download PDFInfo
- Publication number
- CN112434831A CN112434831A CN202011423588.3A CN202011423588A CN112434831A CN 112434831 A CN112434831 A CN 112434831A CN 202011423588 A CN202011423588 A CN 202011423588A CN 112434831 A CN112434831 A CN 112434831A
- Authority
- CN
- China
- Prior art keywords
- node
- troubleshooting
- operation information
- decision
- type
- 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
- 238000013024 troubleshooting Methods 0.000 title claims abstract description 262
- 238000000034 method Methods 0.000 title claims abstract description 147
- 238000013515 script Methods 0.000 claims description 23
- 238000004590 computer program Methods 0.000 claims description 7
- 238000012423 maintenance Methods 0.000 abstract description 14
- 238000010586 diagram Methods 0.000 description 5
- 230000006399 behavior Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000004886 process control Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04845—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range for image manipulation, e.g. dragging, rotation, expansion or change of colour
-
- 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/067—Enterprise or organisation modelling
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The embodiment of the invention provides a troubleshooting method and device, a storage medium and computer equipment, and belongs to the field of troubleshooting. The method comprises the following steps: determining a fault scene name according to a fault triggering condition; acquiring a troubleshooting process table corresponding to the failure scene name, wherein the troubleshooting process table comprises: node ID of each node, node type of each node, downstream node of each node and initial node mark in the troubleshooting process; acquiring operation information of each node according to the fault scene name, the node ID of each node and the node type of each node; and executing troubleshooting according to the troubleshooting flow table and the operation information of each node. The troubleshooting method can save labor, improve troubleshooting efficiency and facilitate subsequent operation and maintenance configuration and reuse.
Description
Technical Field
The present invention relates to the field of troubleshooting, and in particular, to a troubleshooting method, device, storage medium, and computer device.
Background
At present, aiming at a Hadoop ecological technology stack (hereinafter referred to as a "technology stack"), a troubleshooting script aiming at a certain fault scene is often written aiming at the fault scene. A fault scenario corresponds to a fixed troubleshooting script. The troubleshooting method is tightly coupled with the fault scene, when the fault scene changes, workers often need to rewrite the troubleshooting script aiming at the changed scene, the reusability of the script is poor, and the configuration and the later operation and maintenance are inconvenient. Moreover, rewriting the troubleshooting script requires that a worker has certain knowledge reserves, so that the threshold is high, a large amount of manpower is consumed, and the efficiency is low.
Disclosure of Invention
The embodiment of the invention provides a troubleshooting method, a troubleshooting device, a storage medium and computer equipment, and aims to solve the problems that in the prior art, troubleshooting scripts are poor in reusability, inconvenient to configure and high in labor cost.
In one aspect, an embodiment of the present invention provides a troubleshooting method, where the method includes:
determining a fault scene name according to a fault triggering condition;
acquiring a troubleshooting process table corresponding to the failure scene name, wherein the troubleshooting process table comprises: node ID of each node, node type of each node, downstream node of each node and initial node mark in the troubleshooting process;
acquiring operation information of each node according to the fault scene name, the node ID of each node and the node type of each node;
and executing troubleshooting according to the troubleshooting flow table and the operation information of each node.
In an implementation manner of this embodiment, the obtaining the operation information of each node according to the fault scenario name, the node ID of each node, and the node type of each node includes:
determining an operation information table corresponding to each node according to the node type of each node, wherein the operation information table stores operation information of nodes of which the node types belong to the node types corresponding to the operation information table in various fault scenes;
and acquiring the operation information of each node in the fault scene corresponding to the fault scene name from the operation information table corresponding to each node according to the node ID of each node and the fault scene name.
In an implementation manner of this embodiment, the node types include: a command node, a method node, a decision node and a result node;
the node types of the downstream node of the command node and the downstream node of the method node are decision nodes;
the decision value of the decision node is a binary value, when the decision value of the decision node is a first decision value, the downstream node of the decision node is a first downstream node of the decision node, and when the decision value of the decision node is a second decision value, the downstream node of the decision node is a second downstream node of the decision node.
In one implementation of the present embodiment,
if the node type is a command node, the obtained operation information of the node comprises: the target host name, the target index and the target index analysis script of the node;
if the node type is a method node, the obtained operation information of the node comprises the following steps: a target log path of the node, a time range of the target log, a target keyword and a target log analysis script;
if the node type is a decision node, the obtained operation information of the node comprises: judging threshold values and judging rules of the nodes;
if the node type is a result node, the obtained operation information of the node comprises: and describing the result of the node.
In an implementation manner of this embodiment, the performing troubleshooting according to the troubleshooting flow table and the operation information of each node includes:
generating a workflow dictionary according to the troubleshooting flow table;
generating a node operation information dictionary according to the operation information of each node;
and performing troubleshooting according to the workflow dictionary and the node operation information dictionary.
In an implementation manner of this embodiment, the method further includes:
acquiring a troubleshooting flow chart;
acquiring node IDs of all nodes, types of all nodes, downstream nodes of all nodes and initial nodes in the troubleshooting flow chart;
generating a troubleshooting flow table corresponding to the troubleshooting flow chart according to the node ID of each node, the node type of each node, the downstream node of each node and the initial node;
acquiring operation information bound to each node in the troubleshooting flow chart;
and storing the operation information bound by each node and the fault scene name of the fault troubleshooting flow table into an operation information table corresponding to the node type according to the node type of each node.
In another aspect, an embodiment of the present invention provides a troubleshooting apparatus, where the apparatus includes:
the scene name determining module is used for determining the name of the fault scene according to the fault triggering condition;
a flow table obtaining module, configured to obtain a troubleshooting flow table corresponding to the failure scene name, where the troubleshooting flow table includes: node ID of each node, node type of each node, downstream node of each node and initial node mark in the troubleshooting process;
the operation information acquisition module is used for acquiring the operation information of each node according to the fault scene name, the node ID of each node and the node type of each node;
and the troubleshooting module is used for executing troubleshooting according to the troubleshooting flow table and the operation information of each node.
In an implementation manner of this embodiment, the operation information obtaining module includes:
the operation information table determining unit is used for determining an operation information table corresponding to each node according to the node type of each node, wherein the operation information table stores the operation information of the node of which the node type belongs to the node type corresponding to the operation information table in various fault scenes;
and the operation information acquisition unit is used for acquiring the operation information of each node in the fault scene corresponding to the fault scene name from the operation information table corresponding to each node according to the node ID of each node and the fault scene name.
In an implementation manner of this embodiment, the node types include: a command node, a method node, a decision node and a result node;
the node types of the downstream node of the command node and the downstream node of the method node are decision nodes;
the decision value of the decision node is a binary value, when the decision value of the decision node is a first decision value, the downstream node of the decision node is a first downstream node of the decision node, and when the decision value of the decision node is a second decision value, the downstream node of the decision node is a second downstream node of the decision node.
In one implementation of the present embodiment,
if the node type is a command node, the obtained operation information of the node comprises: the target host name, the target index and the target index analysis script of the node;
if the node type is a method node, the obtained operation information of the node comprises the following steps: a target log path of the node, a time range of the target log, a target keyword and a target log analysis script;
if the node type is a decision node, the obtained operation information of the node comprises: judging threshold and judging method of the node;
if the node type is a result node, the obtained operation information of the node comprises: and describing the result of the node.
In an implementation manner of this embodiment, the checking module includes:
the workflow dictionary generating unit is used for generating a workflow dictionary according to the troubleshooting flow table;
the node detailed information dictionary generating unit is used for generating a node operation information dictionary according to the operation information of each node;
and the execution unit is used for executing troubleshooting according to the workflow dictionary and the node operation information dictionary.
In an implementation manner of this embodiment, the apparatus further includes:
the flow chart acquisition module is used for acquiring a troubleshooting flow chart;
a node obtaining module, configured to obtain a node ID of each node, a type of each node, a downstream node of each node, and an initial node in the troubleshooting flowchart;
a flow table generating module, configured to generate a troubleshooting flow table corresponding to the troubleshooting flow chart according to the node ID of each node, the node type of each node, the downstream node of each node, and the initial node;
the operation information acquisition module is used for acquiring operation information bound by each node in the troubleshooting flow chart;
and the operation information storage module is used for storing the operation information bound by each node and the fault scene name of the fault troubleshooting flow table into an operation information table corresponding to the node type according to the node type of each node.
In still another aspect, an embodiment of the present invention provides a computer-readable storage medium, on which computer instructions are stored, where the computer instructions are executable by a processor to implement the troubleshooting method described in any one implementation manner of the foregoing embodiment.
In another aspect, an embodiment of the present invention provides a computer device, including:
a memory having a computer program stored thereon;
a processor for executing the computer program to implement the troubleshooting method described in any one of the implementation manners of the above embodiments.
Compared with the prior art, the troubleshooting method, the troubleshooting device, the storage medium and the computer equipment provided by the embodiment of the invention have the following beneficial technical effects:
in the embodiment of the invention, the execution sequence of each node in the troubleshooting process is defined by the troubleshooting process table, the troubleshooting process is controlled, the specific operation information of each node is stored by the operation information table, and the specific operation executed by each node during troubleshooting is controlled, so that the troubleshooting process and the specific operation of each node are decoupled. When a fault occurs, the present embodiment may automatically acquire the troubleshooting flow table according to the fault triggering condition, acquire the operation information of each node according to the node ID of each node in the troubleshooting flow table, and then automatically perform troubleshooting according to the troubleshooting flow table and the operation information of each node. By the method, the configuration of the troubleshooting process and the operation information of each node is facilitated, the later operation and maintenance are facilitated, and the information multiplexing is realized. Compared with manual troubleshooting, the troubleshooting process table for abstracting various fault scenes and the operation information of each node under various fault scenes are stored persistently, when a fault occurs, the fault scene can be automatically determined according to fault triggering conditions, then the troubleshooting operation under the fault scene is automatically executed, labor cost can be saved, and troubleshooting efficiency is improved.
Drawings
In order to more clearly illustrate the technical solution in the embodiments of the present invention, the drawings required to be used in the embodiments will be briefly described below. The drawings in the following description are only drawings of some embodiments of the invention, and other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a method flowchart of a troubleshooting method according to embodiment 1 of the present invention;
FIG. 2 is a method flowchart of a troubleshooting method according to embodiment 2 of the present invention;
FIG. 3 is a method flowchart of a troubleshooting method according to embodiment 3 of the present invention;
fig. 4 is an example of a troubleshooting flowchart according to embodiment 3 of the present invention;
fig. 5 is a block schematic diagram of a troubleshooting apparatus according to embodiment 4 of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It is to be understood that the following examples are illustrative only and are not intended to limit the scope of the present invention.
[ example 1 ]
The embodiment provides a troubleshooting method. Fig. 1 is a method flowchart of a troubleshooting method according to embodiment 1 of the present invention. As shown in fig. 1, the troubleshooting method described in this embodiment may include the following processing:
s101: and determining the name of the fault scene according to the fault triggering condition.
S102: acquiring a troubleshooting process table corresponding to the failure scene name, wherein the troubleshooting process table comprises: node ID of each node, node type of each node, downstream node of each node and initial node mark in the troubleshooting process.
S103: and acquiring the operation information of each node according to the fault scene name, the node ID of each node and the node type of each node.
S104: and executing troubleshooting according to the troubleshooting flow table and the operation information of each node.
In this embodiment, the troubleshooting process and the specific operation of each node in the troubleshooting process are separated, when a fault occurs, the troubleshooting process is automatically obtained according to the fault trigger condition, then the specific operation information of each node in the troubleshooting process is obtained, and then the fault is troubleshot according to the troubleshooting process and the specific operation information of each node in the process. By the method, the troubleshooting process and the specific operation of each node can be decoupled, and configuration and later operation and maintenance are facilitated. Meanwhile, compared with manual troubleshooting, the fault scene is automatically determined according to the fault triggering condition, the fault troubleshooting operation under the fault scene is automatically executed, the labor cost can be saved, and the fault troubleshooting efficiency is improved.
Specifically, the process of manually troubleshooting the operation and maintenance personnel generally includes sequentially checking the relevant index items and logs of the fault scene, comparing the index values with normal values to determine whether the index values exceed a normal range, narrowing the troubleshooting range according to the index analysis result, determining and analyzing a target log, and obtaining the fault reason.
According to the behavior principle, the computer system is utilized to simulate the manual failure analysis behavior, and the failure troubleshooting can be automatically executed. The operation and maintenance personnel can pre-configure the troubleshooting process, store the troubleshooting process into the troubleshooting process table, and then store the troubleshooting process table into the troubleshooting rule base, so that the troubleshooting process is persisted. Table 1 shows a schematic diagram of a troubleshooting flow chart according to an embodiment of the present invention. As shown in table 1, one troubleshooting flow table may correspond to one failure scenario, and the table name of the troubleshooting flow table may represent the name of the failure scenario corresponding to the troubleshooting flow table. In the troubleshooting-flow table, a row may represent a node in the troubleshooting-flow, and the table field of the table may include: node ID, node type, whether it is the original node, downstream node 1_ ID, downstream node 2_ ID.
TABLE 1
Fault scenario 1
| Node ID | Node type | Whether it is the initial node | Downstream node 1_ ID | Downstream node 2_ ID |
| 1 | command | 1 | 2 | 5 |
| 2 | method | 0 | 3 | -1 |
| 3 | decision | 0 | 4 | -1 |
| 4 | result | 0 | -1 | -1 |
As shown in table 1, the troubleshooting flow table may include 4 types of nodes, which are a command node, a method node, a decision node, and a result node. In table 1, when the node ID is-1, it indicates that the node is empty, i.e., there is no node. For example, the ID of the downstream node 2 of the command node or method node may be-1, indicating that the downstream node 2 of the node is empty, and the command node or method node has only the downstream node 1 and no downstream node 2. The downstream node of the command node may be only one, with the node type being the decision node. The downstream nodes of the decision node may be two, namely, the downstream node 1 and the downstream node 2, and the node types of the downstream node 1 and the downstream node 2 may be command nodes or method nodes. The decision value of the decision node is a binary value, and the flow trend of troubleshooting can be determined according to the decision value of the decision node, for example, if the decision value is true, the downstream node is determined to be the downstream node 1 of the decision node, and if the decision value is false, the downstream node is determined to be the downstream node 2 of the decision node.
Table 2 is an operation information table corresponding to a command node according to the embodiment of the present invention, table 3 is an operation information table corresponding to a method node according to the embodiment of the present invention, table 4 is an operation information table corresponding to a decision node according to the embodiment of the present invention, and table 5 is an operation information table corresponding to a result node according to the embodiment of the present invention. The table name of the operation information table may represent a node type corresponding to the operation information table, and one node type may correspond to one operation information table. One row in the table represents detailed operational information for one node in a certain fault scenario. Each node of the present embodiment is described in detail below with reference to tables 2, 3, 4, and 5.
TABLE 2
command
TABLE 3
method
TABLE 4
decision
TABLE 5
result
The command node can respectively set index items of the anti-counterfeiting operating system and each technical component of the Hadoop through an operating system command, a Hadoop client command and a Curl command. The operation and maintenance personnel can configure the target host name of the node operation, the name of the target index to be obtained, and the specific operation instruction or script for obtaining the target index (i.e. target index analysis script, such as iostat-xmd 10001000 (an operating system command), curr https:// ip: htpport/_ cluster/hierarchy (a REST interface command), hbase hbck-h (a command of a Hadoop client command line tool)), and the specific operation information of the corresponding node, and then store the specific operation information of the node into the operation information table corresponding to the command node. Therefore, the operation information table corresponding to the command node can store the operation information of the node with the node type being the command node under various fault scenes. During execution, the operation information of the command node in the fault scenario corresponding to the fault scenario name may be obtained from the operation information table corresponding to the command node according to the node ID and the fault scenario name of the command node, and a command return value of the command node, such as a value of the target index item, may be output to a downstream node of the command node after executing an operation according to the operation information.
The method node can perform analysis operations such as reading and text processing on various logs. The operation and maintenance personnel can configure specific operation information of nodes such as a target log storage path, a target time range of log analysis, a target keyword, a target analysis script, a corresponding fault scene name and the like for the method node, and then store the operation information of the node into an operation information table corresponding to the method node, so that the operation information of the node with the node type as the method node under various fault scenes can be stored in the operation information table corresponding to the method node. During execution, the operation information of the method node under the fault scenario corresponding to the fault scenario name can be acquired from the operation information table corresponding to the method node according to the node ID and the fault scenario name of the method node, and the analysis result of the method node is output to the downstream node of the method node after the operation is executed according to the operation information, such as the number of times that the target keyword appears in the log within a specific time range.
The decision node can judge the operation result of the upstream node and the set threshold value and output the judgment result to the downstream node. In this embodiment, the decision node only performs boolean judgment, and the output result is a binarization result, such as true or false. The operation and maintenance personnel can configure specific operation information of the nodes such as the judgment rule and the fault scene name corresponding to the judgment threshold value for the decision node, and then store the specific operation information of the node into an operation information table corresponding to the decision node. Therefore, the operation information table corresponding to the decision node can store the operation information of the node with the node type as the decision node under various fault scenes. During execution, the operation information of the decision node under the fault scenario corresponding to the fault scenario name can be obtained from the operation information table corresponding to the decision node according to the node ID and the fault scenario name of the decision node, and a downstream node is determined from two downstream nodes of the decision node according to an execution result after the operation information is executed.
The result node may represent a troubleshooting result. The operation and maintenance personnel can configure specific operation information of the result node, such as result description, corresponding fault scene name and the like, for the result node, and then store the specific operation information of the node into an operation information table corresponding to the result node. During execution, the operation information of the result node can be acquired from the operation information table corresponding to the result node according to the node ID and the fault scene name of the result node, so as to output a result description corresponding to the result node.
In this embodiment, the troubleshooting process and the operation information of the nodes are persisted, the troubleshooting process table defines the execution sequence of each node in the troubleshooting process, and the troubleshooting process is controlled. The specific operation information of each node is stored by the operation information table, and the specific operation executed by each node during troubleshooting is controlled, so that the troubleshooting process and the specific operation of the node are decoupled. When troubleshooting is performed, the embodiment may determine a failure scene name according to the failure trigger condition, determine a troubleshooting flow table according to the failure scene name, further obtain specific operation information of each node from an operation information table corresponding to each node type according to the ID and the failure scene name of each node in the troubleshooting flow table, and then perform troubleshooting operation. By the method, the operation information of each node is convenient to configure and maintain, and the operation of each node is convenient to multiplex. In addition, the troubleshooting processes of various fault scenes can be formed by combining four types of nodes, namely a command node, a method node, a decision node and a result node, and the normalization and the variability of the troubleshooting processes are convenient to realize.
[ example 2 ]
In order to simplify the program logic of troubleshooting and improve the program execution efficiency, a troubleshooting flow table corresponding to a failure scene and operation information of each node in the troubleshooting flow can be acquired, the troubleshooting flow table stored in a database and the operation information of each node are converted into a dictionary structure stored in a memory, and then troubleshooting is executed according to the dictionary structure in the memory. Fig. 2 shows a flow chart of a troubleshooting method according to embodiment 2 of the present invention. As shown in fig. 2, the troubleshooting method according to this embodiment may include the following steps:
s201: and determining the name of the fault scene according to the fault triggering condition.
The fault scene name and the corresponding fault condition may be bound in advance. When the fault triggering condition is detected, the corresponding fault scene name can be determined according to the fault triggering condition. The troubleshooting of the embodiment supports triggering types such as artificial triggering, alarm triggering or periodic triggering. The fault condition may be input manually, generated based on an alarm, or generated periodically.
S202: acquiring a troubleshooting process table corresponding to the failure scene name, wherein the troubleshooting process table comprises: node ID of each node, node type of each node, downstream node of each node and initial node mark in the troubleshooting process.
The troubleshooting process table can adopt a two-dimensional table, and the name of the fault scene is used as the table name. The troubleshooting flow tables corresponding to various fault scenes can be stored in a relational database MySQL in advance so as to facilitate the identification of computer programs and the recursive operation.
S203: and acquiring the operation information of each node according to the fault scene name, the node ID of each node and the node type of each node.
The operation information table corresponding to each node can be determined according to the node type of each node, one node type corresponds to one operation information table, and the operation information of the node of which the node type belongs to the node type corresponding to the operation information table in various fault scenes is stored in one operation information table. The operation information of each node in the fault scenario corresponding to the fault scenario name can be acquired from the operation information table corresponding to the node type of each node according to the node ID of each node and the fault scenario name.
S204: and generating a workflow dictionary according to the troubleshooting flow table.
The generated Workflow Dictionary (Workflow _ Dictionary) may adopt a recursively nested data structure, and command nodes or method nodes and decision nodes are sequentially nested in a loop. The dictionary structure of the command or method node only has one key-value pair, and the dictionary of the precision node has two key-value pairs.
Specifically, when the workflow dictionary is generated according to the troubleshooting flow table, the troubleshooting flow table named by the failure scene name corresponding to the failure trigger condition may be read from the database. The initial node (e.g., the node whose initial node is labeled 1) is then found from the troubleshooting flow table, and the initial node ID is then written into the json string at the first level of the workflow dictionary. Then, the ID (decision node) of the downstream node of the initial node may be written into the json character string of the second level of the workflow dictionary, the node ID of the node whose decision is true after the decision node is written into the json character string of the first key-value pair of the third level of the workflow dictionary, and the node ID of the node whose decision is false after the decision node is written into the json character string of the second key-value pair of the third level of the workflow dictionary. By analogy, a workflow dictionary is recursively generated. An example of a generated workflow dictionary may be in the form of:
s205: and generating a node operation information dictionary according to the operation information of each node.
The generated node operation information Dictionary (node detail _ Dictionary) may adopt a two-layer nested structure, the outer-layer Dictionary may represent all nodes in a troubleshooting process, and the inner-layer Dictionary may represent specific operation information of each node.
Specifically, when the node operation information dictionary is generated according to the operation information of each node, key value pairs in the dictionary may be sequentially generated according to the operation information of each node in the troubleshooting flow table corresponding to the failure scene name, a key (key) in the key value pair may take an attribute name of a node in the operation information table, such as a node ID, a target host, a target index, and the like, and a value (value) may take a corresponding attribute value, thereby storing detailed information of each node in the troubleshooting flow table. An example of the generated node operation information dictionary may be in the form of:
s206: and performing troubleshooting according to the workflow dictionary and the node operation information dictionary.
During execution, the workflow dictionary can be relied on to perform the process control of troubleshooting, and the information dictionary is relied on to operate the node to acquire the specific troubleshooting command, method, judgment threshold and other information of the node, so that troubleshooting is performed.
Specifically, when performing automatic troubleshooting, the workflow dictionary may be traversed to obtain a node ID of the initial node, such as command _ node ID _1, and then the node ID (command _ node ID _1) of the node may be utilized, and then the node operation information dictionary may be traversed to obtain specific operation information of the node, and further, the specific operation information of the node may be utilized to perform specific troubleshooting operations. After the troubleshooting operation is executed, an operation result returned by the troubleshooting operation can be obtained and output to a lower node of the node in the workflow dictionary, for example, the determination _ node _2, then the node operation information dictionary can be traversed through the node ID (the determination _ node _2) of the lower node, specific operation information of the lower node is obtained, further, the judgment can be performed by using the specific operation information of the lower node, if the judgment result is true, the first group of key value pairs in a secondary dictionary of the determination node in the workflow dictionary is continuously traversed, otherwise, the second group of key value pairs is traversed, and the recursive traversal execution is performed according to the rule.
In this embodiment, the troubleshooting flow chart and the node operation information stored in the database are converted into the workflow dictionary and the node operation information dictionary in the memory, and troubleshooting is performed according to the workflow dictionary and the node operation information dictionary in the memory, so that program logic of troubleshooting can be simplified, and program execution efficiency can be improved.
[ example 3 ]
In order to facilitate operation and maintenance personnel to configure troubleshooting processes and operation information in various fault scenes and reduce the threshold of troubleshooting configuration, the embodiment provides a visual configuration module for a user to configure a troubleshooting flow chart, and then converts the troubleshooting flow chart configured by the user into the troubleshooting flow chart and node operation information for persistent storage. Fig. 3 is a method flow diagram of a troubleshooting method according to embodiment 3 of the present invention. As shown in fig. 3, in addition to the troubleshooting method described in embodiment 1 or embodiment 2, the troubleshooting method of this embodiment further includes:
s301: and acquiring a troubleshooting flow chart.
Fig. 4 shows a schematic diagram of a troubleshooting flowchart according to embodiment 3 of the present invention.
The embodiment may provide a troubleshooting flowchart configuration module for operation and maintenance personnel to configure the troubleshooting flowchart. Specifically, a troubleshooting-flow-chart configuration interface may be provided, and a configuration selection area and a drawing area may be provided at the troubleshooting-flow-chart configuration interface. In the configuration selection area, graphs of four node types such as command nodes, method nodes, decision nodes and result nodes can be provided for users to select. After the user selects a node type of graph, the graph can be dragged to the flow chart drawing area, and the node ID of the node can be configured. In addition, the configuration selection area may also provide an attribute information list corresponding to the node of each node type, such as an attribute information list of a target host, an operation instruction list, and the like, so that a user may select the attribute information bound to the node. For example, if the user selects a command node, the configuration selection area may provide an optional host list, an optional metrics list, and an optional metrics analysis script list for the command node. The user may select attribute information from the configuration selection area to bind with the drawn node. For example, a user may select a graphic of a command node, drag and drop the graphic into a drawing area, and select a target host, a target index analysis script from a list of attribute information of the command node provided in a configuration selection area to bind with the node drawn thereby.
S302: and acquiring the node ID of each node, the type of each node, the downstream node of each node and the initial node in the troubleshooting flow chart.
In the troubleshooting flowchart drawn by the user, the node IDs, the node types, the downstream nodes, and the initial nodes of all the nodes in the troubleshooting flowchart can be detected.
S303: and generating a troubleshooting flow table corresponding to the troubleshooting flow chart according to the node ID of each node, the node type of each node, the downstream node of each node and the initial node.
The method includes the steps of taking a node ID as a row, taking the node ID, the node type, the downstream node and the initial node identifier as table fields, storing a troubleshooting process in a troubleshooting flow chart (only including the node ID of each node, the sequence among the nodes, the node type and the like included in the troubleshooting flow, and not including specific operation information of the nodes) as a two-dimensional troubleshooting flow chart, marking the detected initial node with an initial node identifier, and taking a fault scene name corresponding to the troubleshooting flow chart as a table name of the troubleshooting flow chart.
S304: and acquiring the operation information bound by each node in the troubleshooting flow chart.
S305: and storing the operation information bound by each node and the fault scene name of the fault troubleshooting flow table into an operation information table corresponding to the node type according to the node type of each node.
The node types in the troubleshooting flow chart comprise: command node, method node, decision node, result node. If the node type of the node is a command node, the operation information bound with the node comprises: the target host name, the target index and the target index analysis script of the node; if the node type of the node is the method node, the operation information bound with the node comprises: a target log path of the node, a time range of the target log, a target keyword and a target log analysis script; if the node type of the node is a decision node, the operation information bound with the node comprises: judging threshold values and judging rules of the nodes; if the node type of the node is a result node, the operation information bound with the node comprises: and describing the result of the node.
If the node type of the node is the command node, the operation information and the fault scene name of the node can be stored in the operation information table corresponding to the command node. If the node type of the node is the method node, the operation information and the fault scene name of the node can be stored in an operation information table corresponding to the method node. If the node type of the node is a decision node, the operation information and the fault scene name of the node can be stored in an operation information table corresponding to the decision node. If the node type of the node is the result node, the operation information and the fault scene name of the node can be stored in the operation information table corresponding to the result node.
The embodiment provides a troubleshooting flow chart configuration module, which can facilitate operation and maintenance personnel to configure troubleshooting flow charts suitable for human reading and understanding, and the embodiment converts and stores information in the troubleshooting flow charts convenient for human reading into a troubleshooting flow chart and an operation information table which can be identified by a computer and are convenient for the computer to execute automatic operation. And then executing troubleshooting operation according to the troubleshooting flow table and the operation information table. Compared with the method for executing the troubleshooting operation directly according to the troubleshooting flowchart, the method for executing the troubleshooting operation in the embodiment converts the information in the troubleshooting flowchart into the information in the troubleshooting flowchart and the operation information table in advance to store the information, and then executes the troubleshooting according to the troubleshooting flowchart and the operation information table, so that the execution efficiency of the troubleshooting operation can be improved. Moreover, by providing a troubleshooting flow chart configuration module, the embodiment facilitates operation and maintenance personnel to visually configure the troubleshooting method.
[ example 4 ]
The present embodiment provides a troubleshooting apparatus. Fig. 5 shows a block schematic diagram of a troubleshooting apparatus according to embodiment 4 of the present invention. As shown in fig. 5, the troubleshooting apparatus 10 provided in the present embodiment may include:
a scene name determining module 11, configured to determine a fault scene name according to a fault triggering condition;
a flow table obtaining module 12, configured to obtain a troubleshooting flow table corresponding to the failure scene name, where the troubleshooting flow table includes: node ID of each node, node type of each node, downstream node of each node and initial node mark in the troubleshooting process;
an operation information obtaining module 13, configured to obtain operation information of each node according to the fault scene name, the node ID of each node, and the node type of each node;
and the troubleshooting module 14 is configured to perform troubleshooting according to the troubleshooting flow table and the operation information of each node.
In an implementation manner of this embodiment, the operation information obtaining module includes:
the operation information table determining unit is used for determining an operation information table corresponding to each node according to the node type of each node, wherein the operation information table stores the operation information of the node of which the node type belongs to the node type corresponding to the operation information table in various fault scenes;
and the operation information acquisition unit is used for acquiring the operation information of each node in the fault scene corresponding to the fault scene name from the operation information table corresponding to each node according to the node ID of each node and the fault scene name.
In an implementation manner of this embodiment, the node types include: a command node, a method node, a decision node and a result node;
the node types of the downstream node of the command node and the downstream node of the method node are decision nodes;
the decision value of the decision node is a binary value, when the decision value of the decision node is a first decision value, the downstream node of the decision node is a first downstream node of the decision node, and when the decision value of the decision node is a second decision value, the downstream node of the decision node is a second downstream node of the decision node.
In one implementation of the present embodiment,
if the node type is a command node, the obtained operation information of the node comprises: the target host name, the target index and the target index analysis script of the node;
if the node type is a method node, the obtained operation information of the node comprises the following steps: a target log path of the node, a time range of the target log, a target keyword and a target log analysis script;
if the node type is a decision node, the obtained operation information of the node comprises: judging threshold and judging method of the node;
if the node type is a result node, the obtained operation information of the node comprises: and describing the result of the node.
In an implementation manner of this embodiment, the checking module includes:
the workflow dictionary generating unit is used for generating a workflow dictionary according to the troubleshooting flow table;
the node detailed information dictionary generating unit is used for generating a node operation information dictionary according to the operation information of each node;
and the execution unit is used for executing troubleshooting according to the workflow dictionary and the node operation information dictionary.
In an implementation manner of this embodiment, the apparatus further includes:
the flow chart acquisition module is used for acquiring a troubleshooting flow chart;
a node obtaining module, configured to obtain a node ID of each node, a type of each node, a downstream node of each node, and an initial node in the troubleshooting flowchart;
a flow table generating module, configured to generate a troubleshooting flow table corresponding to the troubleshooting flow chart according to the node ID of each node, the node type of each node, the downstream node of each node, and the initial node;
the operation information acquisition module is used for acquiring operation information bound by each node in the troubleshooting flow chart;
and the operation information storage module is used for storing the operation information bound by each node and the fault scene name of the fault troubleshooting flow table into an operation information table corresponding to the node type according to the node type of each node.
The troubleshooting device provided in this embodiment can be used for implementing the troubleshooting method described in the above embodiment, and for the specific working process and the processing flow, reference is made to the corresponding process in the foregoing troubleshooting method embodiment, which is not described herein again.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention can be implemented by combining software and a hardware platform. With this understanding in mind, all or part of the technical solutions of the present invention that contribute to the background can be embodied in the form of a software product, which can be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
[ example 5 ]
The present embodiment provides a computer-readable storage medium, such as a hard disk, an optical disk, a flash memory, a floppy disk, a magnetic tape, etc., on which computer-readable instructions are stored, which can be executed by a processor to implement the process of the troubleshooting method described in the above embodiment.
[ example 6 ]
The present embodiment provides a computer device, including:
a memory having a computer program stored thereon,
a processor which can execute the computer program to realize the processing of the troubleshooting method described in the above embodiment.
The terms and expressions used in the present specification are used as terms of illustration only and are not meant to be limiting. It will be appreciated by those skilled in the art that changes could be made to the details of the above-described embodiments without departing from the underlying principles thereof. The scope of the invention is, therefore, indicated by the appended claims, in which all terms are intended to be interpreted in their broadest reasonable sense unless otherwise indicated.
Claims (14)
1. A troubleshooting method, characterized in that the troubleshooting method comprises:
determining a fault scene name according to a fault triggering condition;
acquiring a troubleshooting process table corresponding to the failure scene name, wherein the troubleshooting process table comprises: node ID of each node, node type of each node, downstream node of each node and initial node mark in the troubleshooting process;
acquiring operation information of each node according to the fault scene name, the node ID of each node and the node type of each node;
and executing troubleshooting according to the troubleshooting flow table and the operation information of each node.
2. The troubleshooting method of claim 1, wherein obtaining the operation information of each node according to the failure scene name, the node ID of each node, and the node type of each node comprises:
determining an operation information table corresponding to each node according to the node type of each node, wherein the operation information table stores operation information of nodes of which the node types belong to the node types corresponding to the operation information table in various fault scenes;
and acquiring the operation information of each node in the fault scene corresponding to the fault scene name from the operation information table corresponding to each node according to the node ID of each node and the fault scene name.
3. The troubleshooting method of claim 1, wherein the node type comprises: a command node, a method node, a decision node and a result node;
the node types of the downstream node of the command node and the downstream node of the method node are decision nodes;
the decision value of the decision node is a binary value, when the decision value of the decision node is a first decision value, the downstream node of the decision node is a first downstream node of the decision node, and when the decision value of the decision node is a second decision value, the downstream node of the decision node is a second downstream node of the decision node.
4. The troubleshooting method of claim 3,
if the node type is a command node, the obtained operation information of the node comprises: the target host name, the target index and the target index analysis script of the node;
if the node type is a method node, the obtained operation information of the node comprises the following steps: a target log path of the node, a time range of the target log, a target keyword and a target log analysis script;
if the node type is a decision node, the obtained operation information of the node comprises: judging threshold values and judging rules of the nodes;
if the node type is a result node, the obtained operation information of the node comprises: and describing the result of the node.
5. The troubleshooting method according to claim 1, wherein the performing troubleshooting according to the troubleshooting flow table and the operation information of the respective nodes includes:
generating a workflow dictionary according to the troubleshooting flow table;
generating a node operation information dictionary according to the operation information of each node;
and performing troubleshooting according to the workflow dictionary and the node operation information dictionary.
6. The troubleshooting method according to claim 1, wherein the troubleshooting method further comprises:
acquiring a troubleshooting flow chart;
acquiring node IDs of all nodes, types of all nodes, downstream nodes of all nodes and initial nodes in the troubleshooting flow chart;
generating a troubleshooting flow table corresponding to the troubleshooting flow chart according to the node ID of each node, the node type of each node, the downstream node of each node and the initial node;
acquiring operation information bound to each node in the troubleshooting flow chart;
and storing the operation information bound by each node and the fault scene name of the fault troubleshooting flow table into an operation information table corresponding to the node type according to the node type of each node.
7. A troubleshooting device, characterized in that the troubleshooting device comprises:
the scene name determining module is used for determining the name of the fault scene according to the fault triggering condition;
a flow table obtaining module, configured to obtain a troubleshooting flow table corresponding to the failure scene name, where the troubleshooting flow table includes: node ID of each node, node type of each node, downstream node of each node and initial node mark in the troubleshooting process;
the operation information acquisition module is used for acquiring the operation information of each node according to the fault scene name, the node ID of each node and the node type of each node;
and the troubleshooting module is used for executing troubleshooting according to the troubleshooting flow table and the operation information of each node.
8. The troubleshooting apparatus according to claim 7, wherein the operation information obtaining module includes:
the operation information table determining unit is used for determining an operation information table corresponding to each node according to the node type of each node, wherein the operation information table stores the operation information of the node of which the node type belongs to the node type corresponding to the operation information table in various fault scenes;
and the operation information acquisition unit is used for acquiring the operation information of each node in the fault scene corresponding to the fault scene name from the operation information table corresponding to each node according to the node ID of each node and the fault scene name.
9. The troubleshooting apparatus of claim 7, wherein the node type comprises: a command node, a method node, a decision node and a result node;
the node types of the downstream node of the command node and the downstream node of the method node are decision nodes;
the decision value of the decision node is a binary value, when the decision value of the decision node is a first decision value, the downstream node of the decision node is a first downstream node of the decision node, and when the decision value of the decision node is a second decision value, the downstream node of the decision node is a second downstream node of the decision node.
10. The troubleshooting device of claim 9,
if the node type is a command node, the obtained operation information of the node comprises: the target host name, the target index and the target index analysis script of the node;
if the node type is a method node, the obtained operation information of the node comprises the following steps: a target log path of the node, a time range of the target log, a target keyword and a target log analysis script;
if the node type is a decision node, the obtained operation information of the node comprises: judging threshold and judging method of the node;
if the node type is a result node, the obtained operation information of the node comprises: and describing the result of the node.
11. The troubleshooting device of claim 7, wherein the troubleshooting module comprises:
the workflow dictionary generating unit is used for generating a workflow dictionary according to the troubleshooting flow table;
the node detailed information dictionary generating unit is used for generating a node operation information dictionary according to the operation information of each node;
and the execution unit is used for executing troubleshooting according to the workflow dictionary and the node operation information dictionary.
12. The troubleshooting device of claim 7, further comprising:
the flow chart acquisition module is used for acquiring a troubleshooting flow chart;
a node obtaining module, configured to obtain a node ID of each node, a type of each node, a downstream node of each node, and an initial node in the troubleshooting flowchart;
a flow table generating module, configured to generate a troubleshooting flow table corresponding to the troubleshooting flow chart according to the node ID of each node, the node type of each node, the downstream node of each node, and the initial node;
the operation information acquisition module is used for acquiring operation information bound by each node in the troubleshooting flow chart;
and the operation information storage module is used for storing the operation information bound by each node and the fault scene name of the fault troubleshooting flow table into an operation information table corresponding to the node type according to the node type of each node.
13. A computer-readable storage medium having stored thereon computer instructions executable by a processor to perform the troubleshooting method of any one of claims 1-6.
14. A computer device, comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program to implement the troubleshooting method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011423588.3A CN112434831A (en) | 2020-12-08 | 2020-12-08 | Troubleshooting method and device, storage medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011423588.3A CN112434831A (en) | 2020-12-08 | 2020-12-08 | Troubleshooting method and device, storage medium and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112434831A true CN112434831A (en) | 2021-03-02 |
Family
ID=74690921
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011423588.3A Pending CN112434831A (en) | 2020-12-08 | 2020-12-08 | Troubleshooting method and device, storage medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112434831A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407374A (en) * | 2021-06-22 | 2021-09-17 | 未鲲(上海)科技服务有限公司 | Fault processing method and device, fault processing equipment and storage medium |
| CN115222371A (en) * | 2022-09-08 | 2022-10-21 | 联信弘方(北京)科技股份有限公司 | Problem troubleshooting method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017041406A1 (en) * | 2015-09-08 | 2017-03-16 | 中兴通讯股份有限公司 | Failure positioning method and device |
| CN108153603A (en) * | 2017-12-08 | 2018-06-12 | 上海陆家嘴国际金融资产交易市场股份有限公司 | Database server fault handling method, device and storage medium |
| CN109213773A (en) * | 2017-07-06 | 2019-01-15 | 阿里巴巴集团控股有限公司 | A kind of diagnostic method, device and the electronic equipment of online failure |
| CN109508902A (en) * | 2018-12-14 | 2019-03-22 | 安徽中船璞华科技有限公司 | Intelligent troubleshooting terminal based on fault tree models |
| CN110674096A (en) * | 2019-08-28 | 2020-01-10 | 北京浪潮数据技术有限公司 | Node troubleshooting method, device and equipment and computer readable storage medium |
| CN110908910A (en) * | 2019-11-25 | 2020-03-24 | 腾讯科技（深圳）有限公司 | Block chain-based test monitoring method and device and readable storage medium |
| CN111881278A (en) * | 2020-07-27 | 2020-11-03 | 珠海格力电器股份有限公司 | Fault confirmation method and device, storage medium, electronic device and air conditioner |
-
2020
- 2020-12-08 CN CN202011423588.3A patent/CN112434831A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017041406A1 (en) * | 2015-09-08 | 2017-03-16 | 中兴通讯股份有限公司 | Failure positioning method and device |
| CN109213773A (en) * | 2017-07-06 | 2019-01-15 | 阿里巴巴集团控股有限公司 | A kind of diagnostic method, device and the electronic equipment of online failure |
| CN108153603A (en) * | 2017-12-08 | 2018-06-12 | 上海陆家嘴国际金融资产交易市场股份有限公司 | Database server fault handling method, device and storage medium |
| CN109508902A (en) * | 2018-12-14 | 2019-03-22 | 安徽中船璞华科技有限公司 | Intelligent troubleshooting terminal based on fault tree models |
| CN110674096A (en) * | 2019-08-28 | 2020-01-10 | 北京浪潮数据技术有限公司 | Node troubleshooting method, device and equipment and computer readable storage medium |
| CN110908910A (en) * | 2019-11-25 | 2020-03-24 | 腾讯科技（深圳）有限公司 | Block chain-based test monitoring method and device and readable storage medium |
| CN111881278A (en) * | 2020-07-27 | 2020-11-03 | 珠海格力电器股份有限公司 | Fault confirmation method and device, storage medium, electronic device and air conditioner |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407374A (en) * | 2021-06-22 | 2021-09-17 | 未鲲(上海)科技服务有限公司 | Fault processing method and device, fault processing equipment and storage medium |
| CN115222371A (en) * | 2022-09-08 | 2022-10-21 | 联信弘方(北京)科技股份有限公司 | Problem troubleshooting method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110245496B (en) | Source code vulnerability detection method and detector and training method and system thereof | |
| US20190079993A1 (en) | Method and system for implementing efficient classification and exploration of data | |
| Ferreira et al. | Approaching process mining with sequence clustering: Experiments and findings | |
| CN107111625B (en) | Method and system for efficient classification and exploration of data | |
| US10261967B2 (en) | Data extraction | |
| KR20150091521A (en) | Method and device for mining data regular expression | |
| CN106682514B (en) | System calling sequence feature pattern set generation method based on subgraph mining | |
| CN112434831A (en) | Troubleshooting method and device, storage medium and computer equipment | |
| CN110489317B (en) | Cloud system task operation fault diagnosis method and system based on workflow | |
| CN115169810A (en) | Artificial intelligence system construction method and device for power grid regulation | |
| CN111008521A (en) | Method and device for generating wide table and computer storage medium | |
| CN112949973A (en) | AI-combined robot process automation RPA process generation method | |
| CN116560984A (en) | Test case clustering grouping method based on call dependency graph | |
| CN113409016A (en) | Information processing method, server and medium applied to big data cloud office | |
| CN112288397A (en) | Flow template configuration method, flow execution method and device and electronic equipment | |
| CN108629124B (en) | Method for automatically generating simulation parameter data based on active graph path | |
| CN107920067B (en) | Intrusion detection method on active object storage system | |
| JP2018133044A (en) | Webapi execution flow generation device and webapi execution flow generation method | |
| CN116302984A (en) | Root cause analysis method and device for test task and related equipment | |
| CN114185938B (en) | Project traceability analysis method and system based on digital finance and big data traceability | |
| CN115098362A (en) | Page testing method and device, electronic equipment and storage medium | |
| CN114465875A (en) | Fault processing method and device | |
| CN110597572B (en) | Service call relation analysis method and computer system | |
| CN113849392A (en) | Method and device for analyzing function call | |
| CN111338609A (en) | Information acquisition method and device, storage medium and terminal |
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 |