CN106445784B - Information monitoring method and device - Google Patents
Information monitoring method and device Download PDFInfo
- Publication number
- CN106445784B CN106445784B CN201610857573.5A CN201610857573A CN106445784B CN 106445784 B CN106445784 B CN 106445784B CN 201610857573 A CN201610857573 A CN 201610857573A CN 106445784 B CN106445784 B CN 106445784B
- Authority
- CN
- China
- Prior art keywords
- code
- monitored
- monitored code
- monitoring
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses an information monitoring method and device, which improve the implantation efficiency of monitoring codes. The method comprises the following steps: presetting a configuration file, wherein the configuration file comprises the name and the path of a monitored code; acquiring the monitored code according to the name and the path of the monitored code, and implanting the monitoring code into the monitored code; and if the monitored code is executed, running the monitoring code to generate monitored information of the monitored code, so as to realize monitoring of the monitored code.
Description
Technical Field
The invention relates to the field of computers, in particular to an information monitoring method and device.
Background
A distributed system is a computer system consisting of a number of interconnected processing resources that cooperate to perform the same task under the control of the entire system, relying minimally on centralized programs, data, or hardware. These processing resources are referred to as nodes, which may be clients or servers.
The distributed monitoring system is a system for monitoring each node in the distributed system. The distributed monitoring system generally includes an information acquisition system and an information analysis system. The information acquisition system is arranged in each node and used for acquiring calling relationship state information among methods in each node and sending the information to the information analysis system in a log form for analysis. The code for collecting the calling relation is called monitoring code, and the method in the node is called monitored code.
The traditional information acquisition system manually adds monitoring codes to monitored codes of nodes, and when the number of monitored codes of the nodes is large and/or the number of the nodes is large, the method is obviously very inefficient.
Disclosure of Invention
In order to solve the technical problems in the prior art, the invention provides an information monitoring method and device, which improve the implantation efficiency of monitoring codes.
The embodiment of the invention provides an information monitoring method, which comprises the following steps:
presetting a configuration file, wherein the configuration file comprises the name and the path of a monitored code;
acquiring the monitored code according to the name and the path of the monitored code, and implanting the monitoring code into the monitored code;
and if the monitored code is executed, running the monitoring code to generate monitored information of the monitored code, so as to realize monitoring of the monitored code.
Preferably, the implanting of the monitoring code into the monitored code includes:
inserting a start statement of a monitoring code before a first statement of the monitored code, and inserting an end statement of the monitoring code after a tail statement of the monitored code.
Preferably, if the monitored code is executed, the running the monitoring code to generate the monitored information of the monitored code includes:
and if the monitored code is called, running the monitoring code to generate called information of the monitored code.
Preferably, the monitored code comprises a first monitored code and a second monitored code;
if the monitored code is called, running the monitoring code to generate called information of the monitored code comprises: if the first monitored code is executed, running the monitoring code of the first monitored code to generate a monitoring log of the first monitored code, wherein the monitoring log of the first monitored code comprises the unique identifier of the first monitored code, and the starting execution time and the ending execution time of the first monitored code;
if the second monitored code is called by the first monitored code, running the monitoring code of the second monitored code to generate a monitoring log of the second monitored code, wherein the monitoring log of the second monitored code comprises the unique identifier of the second monitored code, the starting execution time and the ending execution time of the second monitored code and the unique identifier of the first monitored code.
Preferably, the method further comprises:
and establishing a calling relationship between the first monitored code and the second monitored code according to the monitoring log of the first monitored code and the monitoring log of the second monitored code.
Preferably, the first monitored code and the second monitored code are in the same monitored device or in different monitored devices.
Preferably, if the first monitored code and the second monitored code are in the same monitored device, the first monitored code and the second monitored code are executed in the same thread;
the monitoring log of the first monitored code and the monitoring log of the second monitored code further comprise: and the thread identifier corresponds to the same thread.
Preferably, if the first monitored code and the second monitored code are in different monitored devices, the first monitored code and the second monitored code are executed in different threads;
the monitoring log of the first monitored code and the monitoring log of the second monitored code further comprise: the same thread identification corresponding to the different thread.
Preferably, the path of the monitored code includes:
a packet path of the monitored code and/or a class path of the monitored code.
An embodiment of the present invention further provides an information monitoring apparatus, where the apparatus includes: the system comprises a configuration file setting unit, a code implanting unit and a monitored information generating unit;
the configuration file setting unit is used for presetting a configuration file, wherein the configuration file comprises the name and the path of a monitored code;
the code implanting unit is used for acquiring the monitored code according to the name and the path of the monitored code and implanting the monitoring code into the monitored code;
the monitored information generating unit is used for running the monitoring code if the monitored code is executed so as to generate monitored information of the monitored code and realize monitoring of the monitored code.
Compared with the mode of manually implanting the monitoring codes into the monitored codes one by one in the prior art, the embodiment can achieve the purpose of automatically implanting the monitoring codes into the monitored codes as long as the names and the paths of the monitored codes are configured in the configuration file, and the implantation efficiency of the monitoring codes is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a first embodiment of an information monitoring method according to the present invention;
fig. 2 is a block diagram of a first embodiment of an information monitoring apparatus according to the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The first embodiment of the method comprises the following steps:
referring to fig. 1, the figure is a flowchart of an information monitoring method according to a first embodiment of the present invention.
The information monitoring method provided by the embodiment comprises the following steps:
step S101: presetting a configuration file, wherein the configuration file comprises a path of a monitored code.
The configuration file is provided with the name and the path of the monitored code, and the path of the monitored code refers to the place where the monitored code is stored in the monitored system. If the monitored code is written by a java program, the path of the monitored code may be a packet path of the monitored code and/or a class path of the monitored code.
For example, the class path of the monitored code included in the configuration file may be:
regClazz＝com.sohu.ott.api.service.AlbumService,com.sohu.ott.*
the monitored code name included in the configuration file may be:
regMethod＝com.sohu.ott.solr.provider.service.impl.SolrV3ServiceImpl.queryByAlbumId
step S102: and acquiring the monitored code according to the name and the path of the monitored code, and implanting the monitoring code into the monitored code.
In this embodiment, the monitored code may be obtained according to the path and the name of the monitored code. And when the monitored code is acquired, automatically implanting the monitoring code into the monitored code.
Specifically, in practical applications, the monitoring code may have a Start statement and an end statement, that is, a Start statement and an end statement, so that in the implanting process, the Start statement of the monitoring code may be inserted before the first statement of the monitored code, and the end statement of the monitoring code may be inserted after the last statement of the monitored code, so that the monitoring code may monitor all conditions of the monitored code.
Compared with the mode of manually implanting the monitoring codes into the monitored codes one by one in the prior art, the embodiment can achieve the purpose of automatically implanting the monitoring codes into the monitored codes as long as the names and the paths of the monitored codes are configured in the configuration file, and the implantation efficiency of the monitoring codes is improved.
Step S103: and if the monitored code is executed, running the monitoring code to generate monitored information of the monitored code, so as to realize monitoring of the monitored code.
In this embodiment, if the monitored code is executed, the monitoring code is run to generate monitored information of the monitored code. The monitored information for the monitored code may be of a wide variety. For example, the monitored code may be monitored for successful execution; or, the time difference between the start execution time and the end execution time of the monitored code can be obtained by monitoring the start execution time and the end execution time of the monitored code, so as to judge whether the monitored code has an execution overtime condition; alternatively, other abnormal conditions of the monitored code during the execution process can be monitored, such as network abnormality, database abnormality, null pointer abnormality, custom abnormality and the like.
When the monitored codes are multiple, the mutual calling relation among the monitored codes can be monitored through the monitoring codes.
Specifically, assume that the monitored code includes a first monitored code and a second monitored code. When the first monitored code is executed, running the monitoring code of the first monitored code to generate a monitoring log of the first monitored code, wherein the monitoring log of the first monitored code comprises the unique identifier of the first monitored code, and the starting execution time and the ending execution time of the first monitored code.
If the second monitored code is called by the first monitored code, running the monitoring code of the second monitored code to generate a monitoring log of the second monitored code, wherein the monitoring log of the second monitored code comprises the unique identifier of the second monitored code, the starting execution time and the ending execution time of the second monitored code and the unique identifier of the first monitored code.
Then, a call relationship between the first monitored code and the second monitored code may be established according to the monitoring log of the first monitored code and the monitoring log of the second monitored code.
Specifically, because the first monitored code calls the second monitored code, the start execution time of the first monitored code is earlier than the start execution time of the second monitored code, and the end execution time of the first monitored code is later than the end execution time of the second monitored code. And determining the calling relation of the second monitored code called by the first monitored code according to the rule and the unique identification of the first monitored code stored in the monitoring log of the second monitored code.
And determining the calling relation of the third monitored code called by the second monitored code according to the rule that the starting execution time of the second monitored code is earlier than the starting execution time of the third monitored code and the ending execution time of the second monitored code is later than the ending execution time of the third monitored code and the unique identifier of the second monitored code stored in the monitoring log of the third monitored code, under the assumption that the monitored code also comprises the third monitored code and the third monitored code is called by the second monitored code.
And so on.
In practical applications, the first monitored code and the second monitored code may be in the same monitored device or in different monitored devices.
If the first monitored code and the second monitored code are in the same monitored device X, and the second monitored code is called by the first monitored code, the first monitored code and the second monitored code may be executed in the same thread, in which the first monitored code is executed first, and then the second monitored code is executed.
One call chain may correspond to one thread, and the call chain refers to a chain formed by each monitored code having a call relation. For example, in a first thread, the first monitored code calls the second monitored code during execution, the second monitored code calls a third monitored code during execution, and the first monitored code, the second monitored code, and the third monitored code form a call chain.
For another example, in a second thread, the first monitored code successively calls the second monitored code and a fourth monitored code in the execution process, and then the first monitored code, the second monitored code and the fourth monitored code form a call chain.
In order to distinguish different call chains, each call chain corresponds to a unique thread identifier. The thread identification may be generated by the execution of monitoring code corresponding to the first monitored code established by the thread.
For example, in the above two examples, the monitored code executed by the first thread is the first monitored code, and then the thread identifier a corresponding to the first thread may be generated by the monitoring code corresponding to the first monitored code.
In addition to storing the thread identifier a in the monitoring log M1 of the first monitored code corresponding to the first thread, the thread identifier a may be stored in the monitoring log N1 of the second monitored object when the first monitored code calls the second monitored code to generate the monitoring log N1 of the second monitored code corresponding to the first thread. Similarly, the monitoring log of the third monitored code may also store the thread identifier a.
The monitored code executed by the first thread in the second thread is also the first monitored code, and then the thread identification B corresponding to the second thread can be generated by the monitoring code corresponding to the first monitored code.
In addition to storing the thread identifier B in the monitoring log M2 of the first monitored code corresponding to the second thread, the thread identifier B may be stored in the monitoring log N2 of the second monitored object when the first monitored code calls the second monitored code to generate the monitoring log N2 of the second monitored code corresponding to the second thread. Similarly, the monitoring log of the fourth monitored code may also store the thread identifier B.
Therefore, when all the monitoring logs of the monitored device X are sorted, the monitoring logs with the same thread identifier can be classified into one class, and then the call chain is formed according to the initial execution time and the ending execution time of the monitored code recorded in the monitoring logs.
And if the first monitored code and the second monitored code are in different monitored devices, executing the first monitored code and the second monitored code in different threads. In order to obtain the calling information of the first monitored code calling the second monitored code, the first monitored code and the second monitored code can be connected in series through the same thread identifier.
Specifically, it is assumed that the first monitored code is executed in a thread of monitored device Y1, and the second monitored code is executed in a thread of monitored device Y2. When the first monitored code executes, the monitoring code of the first monitored code executes, and generates the unique identifier of the first monitored code, the thread identifier C of the thread of the monitored device Y1, and the start execution time and the end execution time of the first monitored code.
When the first monitored code needs to call a second monitored code in the execution process, the monitored device Y1 sends the thread identifier C corresponding to the first monitored code to the monitored device Y2, so that the second monitored code is stored in the monitoring log of the second monitored code when executed in the thread of the monitored device Y2. The first monitored device Y1 and the second monitored device Y2 can communicate with each other and also communicate with each other by means of middleware.
Thus, when all the monitoring logs of the monitored devices Y1 and Y2 are sorted, the first monitored code and the second monitored code can be associated according to the thread identifier C, and then a call chain for the first monitored code to call the second monitored code is obtained according to the start execution time and the end execution time recorded in the respective monitoring logs of the first monitored code and the second monitored code.
After the monitored device generates the call chains, the call chains may be uploaded to a data analysis device, and the data analysis device may count the number of times of generation of requests corresponding to the same call chain and/or the average execution time of each call chain in a certain period of time, so as to perform further analysis.
In addition to the statistics with the call chain as the dimension, the statistics with the monitored code as the dimension may also be performed, that is, the number of times that the monitored code is called to execute, the number of times that the monitored code is not called to execute, and the like may be counted.
Based on the information monitoring method provided by the above embodiment, the embodiment of the invention also provides an information monitoring device, and the working principle of the information monitoring device is described in detail below with reference to the accompanying drawings.
Apparatus embodiment one
Referring to fig. 2, the figure is a block diagram of a first embodiment of an information monitoring apparatus according to the present invention.
The information monitoring device provided by the embodiment comprises:
a configuration file setting unit 101, a code implanting unit 102, and a monitored information generating unit 103;
the configuration file setting unit 101 is configured to set a configuration file in advance, where the configuration file includes a name and a path of a monitored code;
the code implanting unit 102 is configured to obtain the monitored code according to the name and the path of the monitored code, and implant the monitoring code into the monitored code;
the monitored information generating unit 103 is configured to run the monitoring code if the monitored code is executed, so as to generate monitored information of the monitored code, and implement monitoring on the monitored code.
Compared with the mode of manually implanting the monitoring codes into the monitored codes one by one in the prior art, the embodiment can achieve the purpose of automatically implanting the monitoring codes into the monitored codes as long as the names and the paths of the monitored codes are configured in the configuration file, and the implantation efficiency of the monitoring codes is improved.
Optionally, the code implanting unit 102 is specifically configured to insert a start statement of a monitor code before a first statement of the monitored code, and insert an end statement of the monitor code after a last statement of the monitored code.
Optionally, the monitored information generating unit 103 is specifically configured to run the monitoring code if the monitored code is called, so as to generate called information of the monitored code.
Optionally, the monitored code includes a first monitored code and a second monitored code;
if the monitored code is called, the monitored information generating unit 103 is specifically configured to:
if the first monitored code is executed, running the monitoring code of the first monitored code to generate a monitoring log of the first monitored code, wherein the monitoring log of the first monitored code comprises the unique identifier of the first monitored code, and the starting execution time and the ending execution time of the first monitored code;
if the second monitored code is called by the first monitored code, running the monitoring code of the second monitored code to generate a monitoring log of the second monitored code, wherein the monitoring log of the second monitored code comprises the unique identifier of the second monitored code, the starting execution time and the ending execution time of the second monitored code and the unique identifier of the first monitored code.
Optionally, the apparatus further comprises: and the call relation establishing unit is used for establishing the call relation between the first monitored code and the second monitored code according to the monitoring log of the first monitored code and the monitoring log of the second monitored code.
Optionally, the first monitored code and the second monitored code are in the same monitored device or in different monitored devices.
Optionally, if the first monitored code and the second monitored code are in the same monitored device, the first monitored code and the second monitored code are executed in the same thread;
the monitoring log of the first monitored code and the monitoring log of the second monitored code further comprise: and the thread identifier corresponds to the same thread.
Optionally, if the first monitored code and the second monitored code are in different monitored devices, the monitoring log of the first monitored code and the monitoring log of the second monitored code further include: and (4) global identification.
Optionally, the path of the monitored code includes:
a packet path of the monitored code and/or a class path of the monitored code.
When introducing elements of various embodiments of the present invention, the articles "a," "an," "the," and "said" are intended to mean that there are one or more of the elements. The terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements other than the listed elements.
It should be noted that, as one of ordinary skill in the art would understand, all or part of the processes of the above method embodiments may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when executed, the computer program may include the processes of the above method embodiments. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the units and modules described as separate components may or may not be physically separate. In addition, some or all of the units and modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is directed to embodiments of the present invention, and it is understood that various modifications and improvements can be made by those skilled in the art without departing from the spirit of the invention.
Claims (7)
1. An information monitoring method is suitable for an information acquisition system, and is characterized by comprising the following steps:
presetting a configuration file, wherein the configuration file comprises the name and the path of a monitored code; wherein the monitored code is a method inside a node in the information acquisition system;
acquiring the monitored code according to the name and the path of the monitored code, and implanting the monitoring code into the monitored code; the monitoring code is a calling relation code for acquiring methods inside nodes in the information acquisition system;
if the monitored code is executed, running the monitoring code to generate monitored information of the monitored code, and monitoring the monitored code; the monitored information is state information of calling relations among methods in nodes in the information acquisition system;
wherein, if the monitored code is executed, running the monitoring code to generate monitored information of the monitored code includes:
if the monitored code is called, running the monitoring code to generate called information of the monitored code;
if the monitored code includes a first monitored code and a second monitored code, if the monitored code is called, running the monitoring code to generate called information of the monitored code includes:
if the first monitored code is executed, running the monitoring code of the first monitored code to generate a monitoring log of the first monitored code, wherein the monitoring log of the first monitored code comprises the unique identifier of the first monitored code, and the starting execution time and the ending execution time of the first monitored code;
if the second monitored code is called by the first monitored code, running the monitoring code of the second monitored code to generate a monitoring log of the second monitored code, wherein the monitoring log of the second monitored code comprises the unique identifier of the second monitored code, the starting execution time and the ending execution time of the second monitored code and the unique identifier of the first monitored code;
and establishing a calling relationship between the first monitored code and the second monitored code according to the monitoring log of the first monitored code and the monitoring log of the second monitored code.
2. The method of claim 1, wherein said embedding a monitoring code into the monitored code comprises:
inserting a start statement of a monitoring code before a first statement of the monitored code, and inserting an end statement of the monitoring code after a tail statement of the monitored code.
3. The method of claim 1, wherein the first monitored code and the second monitored code are in the same monitored device or in different monitored devices.
4. The method of claim 3, wherein if the first monitored code and the second monitored code are in the same monitored device, the first monitored code and the second monitored code are executed in the same thread;
the monitoring log of the first monitored code and the monitoring log of the second monitored code further comprise: and the thread identifier corresponds to the same thread.
5. The method of claim 3, wherein the first monitored code and the second monitored code execute in different threads if the first monitored code and the second monitored code are in different monitored devices;
the monitoring log of the first monitored code and the monitoring log of the second monitored code further comprise: the same thread identification corresponding to the different thread.
6. The method of claim 1, wherein the path of the monitored code comprises:
a packet path of the monitored code and/or a class path of the monitored code.
7. An information monitoring device adapted for use in an information acquisition system, the device comprising: the system comprises a configuration file setting unit, a code implanting unit and a monitored information generating unit;
the configuration file setting unit is used for presetting a configuration file, wherein the configuration file comprises the name and the path of a monitored code; wherein the monitored code is a method inside a node in the information acquisition system;
the code implanting unit is used for acquiring the monitored code according to the name and the path of the monitored code and implanting the monitoring code into the monitored code; the monitoring code is a calling relation code for acquiring a method inside a node in the information acquisition system;
the monitored information generating unit is used for running the monitoring code if the monitored code is executed so as to generate monitored information of the monitored code and realize monitoring of the monitored code; the monitored information is state information of calling relations among methods in nodes in the information acquisition system;
the monitored information generating unit is used for running the monitoring code to generate the called information of the monitored code if the monitored code is called;
if the monitored code includes a first monitored code and a second monitored code, the monitored information generating unit is configured to:
if the first monitored code is executed, running the monitoring code of the first monitored code to generate a monitoring log of the first monitored code, wherein the monitoring log of the first monitored code comprises the unique identifier of the first monitored code, and the starting execution time and the ending execution time of the first monitored code;
if the second monitored code is called by the first monitored code, running the monitoring code of the second monitored code to generate a monitoring log of the second monitored code, wherein the monitoring log of the second monitored code comprises the unique identifier of the second monitored code, the starting execution time and the ending execution time of the second monitored code and the unique identifier of the first monitored code;
and establishing a calling relationship between the first monitored code and the second monitored code according to the monitoring log of the first monitored code and the monitoring log of the second monitored code.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610857573.5A CN106445784B (en) | 2016-09-27 | 2016-09-27 | Information monitoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610857573.5A CN106445784B (en) | 2016-09-27 | 2016-09-27 | Information monitoring method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106445784A CN106445784A (en) | 2017-02-22 |
| CN106445784B true CN106445784B (en) | 2020-08-28 |
Family
ID=58170577
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610857573.5A Active CN106445784B (en) | 2016-09-27 | 2016-09-27 | Information monitoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106445784B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108664372A (en) * | 2018-05-08 | 2018-10-16 | 平安科技（深圳）有限公司 | Monitoring device, method and the computer readable storage medium of test process |
| CN109542718B (en) * | 2018-10-22 | 2023-02-07 | 中国平安人寿保险股份有限公司 | Service call monitoring method and device, storage medium and server |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040078681A1 (en) * | 2002-01-24 | 2004-04-22 | Nick Ramirez | Architecture for high availability using system management mode driven monitoring and communications |
| CN100435111C (en) * | 2005-10-13 | 2008-11-19 | 同济大学 | Parallel adjusting and performance analyzing method of supporting multi-language multi-platform under isomerized environment |
| US8352791B2 (en) * | 2010-06-04 | 2013-01-08 | GM Global Technology Operations LLC | Configurable test suite |
| US20120151450A1 (en) * | 2010-12-09 | 2012-06-14 | Microsoft Corporation | Platform-Agnostic Diagnostic Data Collection and Display |
| CN102354298A (en) * | 2011-07-27 | 2012-02-15 | 哈尔滨工业大学 | Software testing automation framework (STAF)-based fault injection automation testing platform and method for high-end fault-tolerant computer |
| CN102457578B (en) * | 2011-12-16 | 2015-10-07 | 中标软件有限公司 | A kind of distributed network monitoring method based on case mechanism |
| CN104391795B (en) * | 2014-12-03 | 2017-05-10 | 北京京东尚科信息技术有限公司 | Method and system for automatically testing coverage rate in distributed system |
-
2016
- 2016-09-27 CN CN201610857573.5A patent/CN106445784B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN106445784A (en) | 2017-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107688496B (en) | Task distributed processing method and device, storage medium and server | |
| CN107332876B (en) | Method and device for synchronizing block chain state | |
| CN108268372B (en) | Mock test processing method and device, storage medium and computer equipment | |
| CN108563502B (en) | Task scheduling method and device | |
| CN108062243B (en) | Execution plan generation method, task execution method and device | |
| CN110535928B (en) | Event pushing method for JAVA intelligent contract of block chain | |
| CN107689982A (en) | Multi-data source method of data synchronization, application server and computer-readable recording medium | |
| CN110009347B (en) | Block chain transaction information auditing method and device | |
| CN106445784B (en) | Information monitoring method and device | |
| CN111158800B (en) | Method and device for constructing task DAG based on mapping relation | |
| CN102385536A (en) | Method and system for realization of parallel computing | |
| CN113835844A (en) | Management method and device of container cluster and cloud computing platform | |
| CN105635231A (en) | Calling method and apparatus of distributed system | |
| CN108063814B (en) | Load balancing method and device | |
| CN110990381B (en) | Processing method and device of server, storage medium and electronic device | |
| CN110888892A (en) | Block synchronization method, device and storage medium | |
| CN114063606B (en) | PLC protocol fuzzy test method and device, electronic equipment and storage medium | |
| CN106936643B (en) | Equipment linkage method and terminal equipment | |
| CN110365520B (en) | Method, device and equipment for polling nodes in distributed system | |
| CN114422576A (en) | Session cleaning method and device, computer equipment and readable storage medium | |
| CN110580172B (en) | Configuration rule verification method and device, storage medium and electronic device | |
| CN111159006B (en) | Automatic testing method and device | |
| CN110874303B (en) | Data acquisition method, device and equipment | |
| CN113760518A (en) | Information processing method, device and storage medium | |
| CN111858043B (en) | Service request processing method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |