CN114726714A - WebRPA operation and maintenance method and system - Google Patents
WebRPA operation and maintenance method and system Download PDFInfo
- Publication number
- CN114726714A CN114726714A CN202210151001.0A CN202210151001A CN114726714A CN 114726714 A CN114726714 A CN 114726714A CN 202210151001 A CN202210151001 A CN 202210151001A CN 114726714 A CN114726714 A CN 114726714A
- Authority
- CN
- China
- Prior art keywords
- log
- webrpa
- state
- running
- component
- 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
- 238000012423 maintenance Methods 0.000 title claims abstract description 31
- 238000000034 method Methods 0.000 title claims abstract description 21
- 238000004806 packaging method and process Methods 0.000 claims abstract description 15
- 238000013024 troubleshooting Methods 0.000 abstract description 11
- 230000008859 change Effects 0.000 description 5
- 230000002159 abnormal effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 230000007547 defect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Abstract
The invention provides a WebRPA operation and maintenance method and a system in the technical field of WebRPA operation and maintenance, wherein the method comprises the following steps: step S10, sequentially packaging the WebRPA into a plurality of elements based on the operation logic; step S20, operating WebRPA and first state data before operation, generating a log to start operation and reporting to a log server based on the first state data; step S30, opening a Web page through WebRPA and operating each element in sequence; step S40, recording element before-operation state logs, element operation results and element after-operation state logs of each element operation, generating element operation logs based on the element before-operation state logs and the element after-operation state logs and reporting the element operation logs to a log server; step S50, after the WebRPA finishes running, recording second state data of the WebRPA, generating a running ending log based on the second state data and reporting the running ending log to the log server; step S60, the log server performs operation and maintenance based on the start operation log, the component operation log, and the end operation log. The invention has the advantages that: the efficiency of WebRPA troubleshooting has greatly been promoted.
Description
Technical Field
The invention relates to the technical field of WebRPA operation and maintenance, in particular to a WebRPA operation and maintenance method and a WebRPA operation and maintenance system.
Background
With the development of the technology, the WebRPA is not limited to local scheduling any more, and can also be used for cloud scheduling to help a user to run some repetitive tasks regularly to achieve unattended operation, for example, in the cross-border e-commerce industry, many sellers have access to the WebRPA cloud scheduling to assist in operation.
Due to the variability of Web pages, the WebRPA cannot be perfectly adapted to all scenes when being programmed, so that a plurality of conditions of WebRPA operation failure inevitably occur, and great trouble is brought to users. When the WebRPA fails to operate, troubleshooting needs to be carried out in time to locate the failure reason, and further the WebRPA operation success rate is improved. However, when the conventional WebRPA runs, only the relevant logs at the beginning of the task, at the end of the task and when the operation is abnormal are recorded, and the abnormal context and the relevant data of the data stream change in the running process are lacked, so that when a fault is eliminated, the operation and maintenance personnel can only see the representation of the operation failure, the root cause cannot be deeply analyzed from the whole task flow of the WebRPA, and a great amount of time and energy is consumed for fault elimination and repair.
Therefore, how to provide a WebRPA operation and maintenance method and system to improve efficiency of WebRPA troubleshooting becomes a technical problem to be solved urgently.
Disclosure of Invention
The invention aims to provide a WebRPA operation and maintenance method and a WebRPA operation and maintenance system, so that the efficiency of WebRPA troubleshooting is improved.
In a first aspect, the present invention provides a WebRPA operation and maintenance method, including the following steps:
step S10, sequentially packaging the WebRPA into a plurality of elements based on the operation logic;
step S20, operating the WebRPA, recording first state data before the WebRPA is operated, and generating a log to start operating and reporting to a log server based on the first state data;
step S30, opening a Web page through the WebRPA, and sequentially operating all elements on the Web page;
step S40, recording element running state logs, element running results and element running state logs of each element in real time, generating element running logs based on the element running state logs and the element running state logs, and reporting the element running logs to a log server;
step S50, after the WebRPA finishes running, recording second state data of the WebRPA, and generating a running ending log based on the second state data and reporting the log to a log server;
and step S60, the log server operates and maintains WebRPA based on the starting operation log, the element operation log and the ending operation log.
Further, in step S10, the component at least carries a component ID, a component name, an operation sequence, a component parameter, and a component variable.
Further, the step S20 is specifically:
manually operating the WebRPA, or periodically operating the WebRPA through a cloud scheduling service, recording first state data before the WebRPA is operated, and generating a log to start operation based on the first state data and reporting the log to a log server in real time;
the first state data includes at least an operation ID, a start operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
Further, the step S40 specifically includes:
step S41, WebRPA records the state log before the operation of each element in real time;
the element pre-operation state log at least comprises an element ID, an element name, a start operation time, a pre-operation element parameter and a pre-operation element variable;
step S42, WebRPA obtains the component operation result fed back in the operation of each component in real time;
the element operation result at least comprises a state identifier and feedback data; the state identification is successful operation or failure operation; when the state identification is successful, the feedback data is operation data; when the state identification is operation failure, the feedback data at least comprises a fault code, a fault reason and fault detailed information;
step S43, WebRPA generates the element operation state log after the element operation based on the element operation result;
the element running state log at least comprises an element ID, an element name, a finished running time, a running element parameter, a running element variable, a state identifier and feedback data;
and step S44, the WebRPA generates an element operation log based on the state log before the element operation and the state log after the element operation, and reports the element operation log to a log server in real time.
Further, in step S50, the second state data at least includes an operation ID, an end operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
In a second aspect, the present invention provides a WebRPA operation and maintenance system, including the following modules:
the component packaging module is used for sequentially packaging the WebRPA into a plurality of components based on the operation logic;
a running start log reporting module, configured to run the WebRPA, record first state data of the WebRPA before running, and generate a running start log reporting log server based on the first state data;
the component operation module is used for opening a Web page through the WebRPA and sequentially operating each component on the Web page;
the device comprises an element running log reporting module, a log server and a state logging module, wherein the element running log reporting module is used for recording element running state logs, element running results and element running state logs of each element in real time, generating element running logs based on the element running state logs and reporting the element running logs to the log server;
a log reporting end module, configured to record second state data of the WebRPA after the WebRPA finishes running, and generate a log reporting end server based on the second state data;
and the WebRPA operation and maintenance module is used for the log server to operate and maintain the WebRPA based on the starting operation log, the element operation log and the ending operation log.
Further, in the component packaging module, the component at least carries a component ID, a component name, an operation sequence, a component parameter, and a component variable.
Further, the starting running log reporting module specifically includes:
manually operating the WebRPA, or periodically operating the WebRPA through a cloud scheduling service, recording first state data before the WebRPA is operated, and generating a log to start operation based on the first state data and reporting the log to a log server in real time;
the first state data includes at least an operation ID, a start operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
Further, the element operation log reporting module specifically includes:
the device comprises a pre-element running state log recording unit, a pre-element running state log recording unit and a pre-element running state log recording unit, wherein the pre-element running state log recording unit is used for recording a pre-element running state log of each element in real time by WebRPA;
the element pre-operation state log at least comprises an element ID, an element name, a start operation time, a pre-operation element parameter and a pre-operation element variable;
the WebRPA is used for acquiring the component operation result fed back in the operation of each component in real time;
the element operation result at least comprises a state identifier and feedback data; the state identification is successful operation or failure operation; when the state identification is successful, the feedback data is operation data; when the state identification is operation failure, the feedback data at least comprises a fault code, a fault reason and fault detailed information;
the device comprises an element running state log generating unit, a state log generating unit and a state log generating unit, wherein the element running state log generating unit is used for generating an element running state log after the element runs by WebRPA based on the element running result;
the element running state log at least comprises an element ID, an element name, a finished running time, a running element parameter, a running element variable, a state identifier and feedback data;
and the element running log generating unit is used for generating an element running log by the WebRPA based on the state log before the element runs and the state log after the element runs, and reporting the element running log to the log server in real time.
Further, in the end run log reporting module, the second state data at least includes a run ID, an end run time, a run parameter, a run variable, a run environment, and a run source.
The invention has the advantages that:
the method comprises the steps of respectively recording a starting operation log and an ending operation log before and after the WebRPA is operated and reporting the logs to a log server, sequentially packaging the WebRPA into a plurality of elements based on operation logic, recording a state log before the element is operated before each element is operated, acquiring an element operation result in the operation of each element, generating an element operation post-state log based on the element operation result after each element is operated, generating an element operation log based on the element operation pre-state log and the element operation post-state log and reporting the log server, so that the log server not only stores the starting operation log and the ending operation log of the WebRPA, but also stores the element operation logs of each element, and can deeply analyze the root cause of a fault from the whole task flow of the WebRPA by combining the starting operation log, the element operation log and the ending operation log, thereby overcoming the defects of lack of abnormal context and related data of data stream change in the operation process in the prior art, finally, the efficiency of WebRPA troubleshooting is greatly improved.
Drawings
The invention will be further described with reference to the following examples with reference to the accompanying drawings.
FIG. 1 is a flowchart of a WebRPA operation and maintenance method of the present invention.
Fig. 2 is a schematic structural diagram of a WebRPA operation and maintenance system according to the present invention.
FIG. 3 is a schematic flow diagram of the present invention.
Detailed Description
The technical scheme in the embodiment of the application has the following general idea: the WebRPA is sequentially packaged into a plurality of elements based on the operation logic, the element operation logs of the elements are respectively recorded and reported to the log server, the start operation log and the end operation log are respectively recorded and reported to the log server before and after the WebRPA is operated, and the root cause of the fault is deeply analyzed from the whole task flow of the WebRPA by combining the start operation log, the element operation log and the end operation log stored in the log server, so that the efficiency of WebRPA fault troubleshooting is improved.
Referring to fig. 1 to fig. 3, a preferred embodiment of a WebRPA operation and maintenance method according to the present invention includes the following steps:
step S10, sequentially packaging the WebRPA into a plurality of elements based on the operation logic, namely abstracting the WebRPA into an element with single responsibility based on the operation logic, wherein one WebRPA consists of a plurality of elements, and the operation of the WebRPA sequentially operates each element according to certain conditions until all the elements are operated;
step S20, operating (triggering) the WebRPA, recording first state data before the WebRPA is operated, and generating a start operation log based on the first state data to report to a log server;
step S30, opening a Web page through the WebRPA, and sequentially operating all elements on the Web page;
step S40, recording element running state logs, element running results and element running state logs of each element in real time, generating element running logs based on the element running state logs and the element running state logs, and reporting the element running logs to a log server; by the aid of the element operation logs, the context of the fault and the change condition of the data stream can be quickly known, so that the root cause of the fault can be quickly found, and troubleshooting difficulty is reduced;
step S50, after the WebRPA finishes running, recording second state data of the WebRPA, and generating a running ending log based on the second state data and reporting the log to a log server;
step S60, the log server operates and maintains WebRPA based on the starting operation log, the element operation log and the ending operation log; in specific implementation, the operation condition of each element can be counted based on the element operation log, and the elements with higher operation failure rate are subjected to targeted optimization.
In step S10, the component at least carries a component ID, a component name, an operation sequence, a component parameter, and a component variable; the element ID is the number of the element, and the operation sequence is the execution sequence of each element.
The step S20 specifically includes:
manually operating the WebRPA, or periodically operating the WebRPA through a cloud scheduling service, recording first state data before the WebRPA is operated, and generating a log to start operation based on the first state data and reporting the log to a log server in real time;
the first state data at least comprises an operation ID, a starting operation time, operation parameters, operation variables, an operation environment and an operation source; the running ID is an identification of the running times of the WebRPA, the running environment is a running browser version and an operating system installed by a browser, and the running source is an installation path of the WebRPA.
The step S40 specifically includes:
step S41, WebRPA records the state log before the operation of each element in real time;
the element pre-operation state log at least comprises an element ID, an element name, a start operation time, a pre-operation element parameter and a pre-operation element variable;
step S42, WebRPA obtains the component operation result fed back in the operation of each component in real time;
the element operation result at least comprises a state identifier and feedback data; the state identification is successful operation or failure operation; when the state identification is successful, the feedback data is operation data; when the state identification is operation failure, the feedback data at least comprises fault codes, fault reasons and fault detailed information;
step S43, WebRPA generates the element operation state log after the element operation based on the element operation result;
the element running state log at least comprises an element ID, an element name, a finished running time, a running element parameter, a running element variable, a state identifier and feedback data;
and step S44, the WebRPA generates an element operation log based on the state log before the element operation and the state log after the element operation, and reports the element operation log to a log server in real time. The element operation logs of all the elements are reported to the log server in real time, and not all the elements are reported uniformly after operation is finished, so that the timeliness of troubleshooting positioning is effectively improved.
In step S50, the second state data at least includes an operation ID, an end operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
The invention relates to a preferred embodiment of a WebRPA operation and maintenance system, which comprises the following modules:
the WebRPA packaging module is used for sequentially packaging the WebRPA into a plurality of elements based on the operation logic, namely abstracting the WebRPA into an element with single responsibility based on the operation logic, one WebRPA consists of a plurality of elements, and the WebRPA is operated, namely, each element is sequentially operated according to a certain condition until all the elements are operated;
a running start log reporting module, configured to run (trigger) the WebRPA, record first state data before the WebRPA runs, and generate a running start log reporting log server based on the first state data;
the component operation module is used for opening a Web page through the WebRPA and sequentially operating each component on the Web page;
the device comprises an element running log reporting module, a log server and a state logging module, wherein the element running log reporting module is used for recording element running state logs, element running results and element running state logs of each element in real time, generating element running logs based on the element running state logs and reporting the element running logs to the log server; by the aid of the element operation logs, the context of the fault and the change condition of the data stream can be quickly known, so that the root cause of the fault can be quickly found, and troubleshooting difficulty is reduced;
a log reporting end module, configured to record second state data of the WebRPA after the WebRPA finishes running, and generate a log reporting end server based on the second state data;
the WebRPA operation and maintenance module is used for the log server to operate and maintain the WebRPA based on the starting operation log, the element operation log and the ending operation log; in specific implementation, the operation condition of each element can be counted based on the element operation log, and the elements with higher operation failure rate are subjected to targeted optimization.
In the component packaging module, the component at least carries a component ID, a component name, an operation sequence, a component parameter and a component variable; the element ID is the number of the element, and the operation sequence is the execution sequence of each element.
The starting operation log reporting module specifically comprises:
manually operating the WebRPA, or periodically operating the WebRPA through a cloud scheduling service, recording first state data before the WebRPA is operated, and generating a log to start operation based on the first state data and reporting the log to a log server in real time;
the first state data at least comprises an operation ID, a starting operation time, operation parameters, operation variables, an operation environment and an operation source; the running ID is an identification of the running times of the WebRPA, the running environment is a running browser version and an operating system installed by a browser, and the running source is an installation path of the WebRPA.
The element operation log reporting module specifically includes:
the device comprises a pre-element running state log recording unit, a pre-element running state log recording unit and a pre-element running state log recording unit, wherein the pre-element running state log recording unit is used for recording a pre-element running state log of each element in real time by WebRPA;
the element pre-operation state log at least comprises an element ID, an element name, a start operation time, a pre-operation element parameter and a pre-operation element variable;
the WebRPA is used for acquiring the component operation result fed back in the operation of each component in real time;
the element operation result at least comprises a state identifier and feedback data; the state identification is successful operation or failure operation; when the state identification is successful, the feedback data is operation data; when the state identification is operation failure, the feedback data at least comprises a fault code, a fault reason and fault detailed information;
the device comprises an element running state log generating unit, a state log generating unit and a state log generating unit, wherein the element running state log generating unit is used for generating an element running state log after the element runs by WebRPA based on the element running result;
the element running state log at least comprises an element ID, an element name, a finished running time, a running element parameter, a running element variable, a state identifier and feedback data;
and the element running log generating unit is used for generating an element running log by the WebRPA based on the state log before the element runs and the state log after the element runs, and reporting the element running log to the log server in real time. The element operation logs of all the elements are reported to the log server in real time, and the element operation logs are not reported uniformly after all the elements are operated, so that the timeliness of troubleshooting and positioning is effectively improved.
In the end operation log reporting module, the second state data at least includes an operation ID, an end operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
In summary, the invention has the advantages that:
the method comprises the steps of respectively recording a starting operation log and an ending operation log before and after the WebRPA is operated and reporting the logs to a log server, sequentially packaging the WebRPA into a plurality of elements based on operation logic, recording a state log before the element is operated before each element is operated, acquiring an element operation result in the operation of each element, generating an element operation post-state log based on the element operation result after each element is operated, generating an element operation log based on the element operation pre-state log and the element operation post-state log and reporting the log server, so that the log server not only stores the starting operation log and the ending operation log of the WebRPA, but also stores the element operation logs of each element, and can deeply analyze the root cause of a fault from the whole task flow of the WebRPA by combining the starting operation log, the element operation log and the ending operation log, thereby overcoming the defects of lack of abnormal context and related data of data stream change in the operation process in the prior art, finally, the efficiency of WebRPA troubleshooting is greatly improved.
Although specific embodiments of the invention have been described above, it will be understood by those skilled in the art that the specific embodiments described are illustrative only and are not limiting upon the scope of the invention, and that equivalent modifications and variations can be made by those skilled in the art without departing from the spirit of the invention, which is to be limited only by the appended claims.
Claims (10)
1. A WebRPA operation and maintenance method is characterized in that: the method comprises the following steps:
step S10, sequentially packaging the WebRPA into a plurality of elements based on the operation logic;
step S20, operating the WebRPA, recording first state data before the WebRPA is operated, and generating a log to start operating and reporting to a log server based on the first state data;
step S30, opening a Web page through the WebRPA, and sequentially operating all elements on the Web page;
step S40, recording element running state logs, element running results and element running state logs of each element in real time, generating element running logs based on the element running state logs and the element running state logs, and reporting the element running logs to a log server;
step S50, after the WebRPA finishes running, recording second state data of the WebRPA, and generating a running ending log based on the second state data and reporting the log to a log server;
and step S60, the log server operates and maintains WebRPA based on the starting operation log, the element operation log and the ending operation log.
2. The WebRPA operation and maintenance method of claim 1, wherein: in step S10, the component at least carries a component ID, a component name, an operation sequence, a component parameter, and a component variable.
3. The WebRPA operation and maintenance method of claim 1, wherein: the step S20 specifically includes:
manually operating the WebRPA, or periodically operating the WebRPA through a cloud scheduling service, recording first state data before the WebRPA is operated, and generating a log to start operation based on the first state data and reporting the log to a log server in real time;
the first state data includes at least an operation ID, a start operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
4. The WebRPA operation and maintenance method of claim 1, wherein: the step S40 specifically includes:
step S41, WebRPA records the state log before the operation of each element in real time;
the element pre-operation state log at least comprises an element ID, an element name, a start operation time, a pre-operation element parameter and a pre-operation element variable;
step S42, WebRPA obtains the component operation result fed back in the operation of each component in real time;
the element operation result at least comprises a state identifier and feedback data; the state identification is successful operation or failure operation; when the state identification is successful, the feedback data is operation data; when the state identification is operation failure, the feedback data at least comprises a fault code, a fault reason and fault detailed information;
step S43, WebRPA generates the element operation state log after the element operation based on the element operation result;
the element running state log at least comprises an element ID, an element name, a finished running time, a running element parameter, a running element variable, a state identifier and feedback data;
and step S44, the WebRPA generates an element operation log based on the state log before the element operation and the state log after the element operation, and reports the element operation log to a log server in real time.
5. The WebRPA operation and maintenance method of claim 1, wherein: in step S50, the second state data at least includes an operation ID, an end operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
6. A WebRPA operation and maintenance system is characterized in that: the system comprises the following modules:
the component packaging module is used for sequentially packaging the WebRPA into a plurality of components based on the operation logic;
a running start log reporting module, configured to run the WebRPA, record first state data of the WebRPA before running, and generate a running start log reporting log server based on the first state data;
the component operation module is used for opening a Web page through the WebRPA and sequentially operating each component on the Web page;
the device comprises an element running log reporting module, a log server and a state logging module, wherein the element running log reporting module is used for recording element running state logs, element running results and element running state logs of each element in real time, generating element running logs based on the element running state logs and reporting the element running logs to the log server;
a log reporting end module, configured to record second state data of the WebRPA after the WebRPA finishes running, and generate a log reporting end server based on the second state data;
and the WebRPA operation and maintenance module is used for the log server to operate and maintain the WebRPA based on the starting operation log, the element operation log and the ending operation log.
7. The WebRPA operation and maintenance system of claim 6, wherein: in the component packaging module, the component at least carries a component ID, a component name, an operation sequence, a component parameter and a component variable.
8. The WebRPA operation and maintenance system of claim 6, wherein: the starting operation log reporting module specifically comprises:
manually operating the WebRPA, or periodically operating the WebRPA through a cloud scheduling service, recording first state data before the WebRPA is operated, and generating a log to start operation based on the first state data and reporting the log to a log server in real time;
the first state data includes at least an operation ID, a start operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
9. The WebRPA operation and maintenance system of claim 6, wherein: the element operation log reporting module specifically includes:
the device comprises a pre-element running state log recording unit, a pre-element running state log recording unit and a pre-element running state log recording unit, wherein the pre-element running state log recording unit is used for recording a pre-element running state log of each element in real time by WebRPA;
the element pre-operation state log at least comprises an element ID, an element name, a start operation time, a pre-operation element parameter and a pre-operation element variable;
the WebRPA is used for acquiring the component operation result fed back in the operation of each component in real time;
the element operation result at least comprises a state identifier and feedback data; the state identification is successful in operation or failed in operation; when the state identification is successful, the feedback data is operation data; when the state identification is operation failure, the feedback data at least comprises a fault code, a fault reason and fault detailed information;
the device comprises an element running state log generating unit, a state log generating unit and a state log generating unit, wherein the element running state log generating unit is used for generating an element running state log after the element runs by WebRPA based on the element running result;
the element running state log at least comprises an element ID, an element name, a finished running time, a running element parameter, a running element variable, a state identifier and feedback data;
and the element running log generating unit is used for generating an element running log based on the state log before the element runs and the state log after the element runs by the WebRPA and reporting the element running log to the log server in real time.
10. The WebRPA operation and maintenance system of claim 6, wherein: in the end operation log reporting module, the second state data at least includes an operation ID, an end operation time, an operation parameter, an operation variable, an operation environment, and an operation source.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210151001.0A CN114726714A (en) | 2022-02-18 | 2022-02-18 | WebRPA operation and maintenance method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210151001.0A CN114726714A (en) | 2022-02-18 | 2022-02-18 | WebRPA operation and maintenance method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114726714A true CN114726714A (en) | 2022-07-08 |
Family
ID=82236543
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210151001.0A Pending CN114726714A (en) | 2022-02-18 | 2022-02-18 | WebRPA operation and maintenance method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114726714A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106254144A (en) * | 2016-09-06 | 2016-12-21 | 华为技术有限公司 | Fault location platform, Fault Locating Method and device |
| WO2018010176A1 (en) * | 2016-07-15 | 2018-01-18 | 华为技术有限公司 | Method and device for acquiring fault information |
| CN108768752A (en) * | 2018-06-25 | 2018-11-06 | 华为技术有限公司 | fault locating method, device and system |
| US10372595B1 (en) * | 2016-12-15 | 2019-08-06 | EMC IP Holding Company LLC | System and method to diagnose applications by accessing log files associated with different subsystems of a data center via a common interface |
| CN112214459A (en) * | 2020-10-12 | 2021-01-12 | 成都精灵云科技有限公司 | Resource processing flow log collection system based on event mechanism |
| CN112527619A (en) * | 2020-12-20 | 2021-03-19 | 大唐互联科技(武汉)有限公司 | Analysis link calling method and system based on directed acyclic graph structure |
-
2022
- 2022-02-18 CN CN202210151001.0A patent/CN114726714A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018010176A1 (en) * | 2016-07-15 | 2018-01-18 | 华为技术有限公司 | Method and device for acquiring fault information |
| CN106254144A (en) * | 2016-09-06 | 2016-12-21 | 华为技术有限公司 | Fault location platform, Fault Locating Method and device |
| US10372595B1 (en) * | 2016-12-15 | 2019-08-06 | EMC IP Holding Company LLC | System and method to diagnose applications by accessing log files associated with different subsystems of a data center via a common interface |
| CN108768752A (en) * | 2018-06-25 | 2018-11-06 | 华为技术有限公司 | fault locating method, device and system |
| CN112214459A (en) * | 2020-10-12 | 2021-01-12 | 成都精灵云科技有限公司 | Resource processing flow log collection system based on event mechanism |
| CN112527619A (en) * | 2020-12-20 | 2021-03-19 | 大唐互联科技(武汉)有限公司 | Analysis link calling method and system based on directed acyclic graph structure |
Non-Patent Citations (1)
| Title |
|---|
| 徐萌飞，王军玲: "控制系统软件的日志功能设计", 船电技术, vol. 31, no. 7, pages 8 - 12 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110287052B (en) | Root cause task determination method and device for abnormal task | |
| CN109271272B (en) | Big data assembly fault auxiliary repair system based on unstructured log | |
| CN101620565B (en) | Method for automatically testing functions of terminal system | |
| US7421621B1 (en) | Application integration testing | |
| CN109474488A (en) | Interface test method, device and computer equipment | |
| CN101620564A (en) | Method for automatically testing recording playback mode of terminal system | |
| WO2002052411A9 (en) | Computer software run-time analysis systems and methods | |
| US20200117587A1 (en) | Log File Analysis | |
| CN113946499A (en) | Micro-service link tracking and performance analysis method, system, equipment and application | |
| US20050154734A1 (en) | Method and system for monitoring and reporting backup results | |
| CN112561370A (en) | Software version management method and device, computer equipment and storage medium | |
| CN115114064A (en) | Micro-service fault analysis method, system, equipment and storage medium | |
| CN114172921A (en) | Log auditing method and device for scheduling recording system | |
| CN114726714A (en) | WebRPA operation and maintenance method and system | |
| CN112527619A (en) | Analysis link calling method and system based on directed acyclic graph structure | |
| CN116467188A (en) | Universal local reproduction system and method under multi-environment scene | |
| CN116483730A (en) | Service system automatic test method based on domestic software and hardware and open source test tool | |
| CN115185489B (en) | Time sequence data algorithm configuration system and method | |
| CN114546758A (en) | WebRPA operation and maintenance method and system based on Chrome plug-in | |
| CN115168175A (en) | Program error solving method, device, electronic equipment and storage medium | |
| CN113392006A (en) | Method and equipment for monitoring automatic test logs by using capsules | |
| CN111061580A (en) | Computer system emergency plan drilling method, server and system | |
| Nieminen et al. | Adaptable design for root cause analysis of a model-based software testing process | |
| CN116450305B (en) | SOAR platform assembly execution method and device based on distributed task scheduling | |
| Fisher et al. | Monitoring of the National Ignition Facility Integrated Computer Control System |
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 |