CN107168845B - Fault positioning method and device - Google Patents
Fault positioning method and device Download PDFInfo
- Publication number
- CN107168845B CN107168845B CN201710207391.8A CN201710207391A CN107168845B CN 107168845 B CN107168845 B CN 107168845B CN 201710207391 A CN201710207391 A CN 201710207391A CN 107168845 B CN107168845 B CN 107168845B
- Authority
- CN
- China
- Prior art keywords
- target
- log
- determining
- tracking key
- server
- 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/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3471—Address tracing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Telephonic Communication Services (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides a fault positioning method and a device, wherein the method comprises the following steps: determining a target tracking key, wherein the target tracking key is used for tracking identification information of a server responding to a target service request; determining logs recorded with the target tracking key in locally stored logs, and determining the determined logs as target logs, wherein each locally stored log records a tracking key corresponding to a service request responded by a server; and positioning the server where the service with the fault is located according to the alarm information recorded in the target log. By applying the scheme provided by the embodiment of the invention to carry out fault location, the fault can be quickly located.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a fault positioning method and device.
Background
With the arrival of the information age, the demands of users are more and more diversified, service operators develop various services in order to meet the demands of the users, and the developed services are matched with each other and are mutually called to meet the demands of the users. A service can only rely on a server to perform its function, and thus, the service can be deployed on at least one server. However, as the number of services is continuously increased, the number of servers is also increased, but the services running in each server may have a fault, and the fault of the services running in the server may cause a failure in responding to a task processing request of a user, so that the fault needs to be located, the server where the service with the fault is located needs to be determined, and the reason of the fault needs to be determined at the same time, so that a maintenance worker can timely repair the service with the fault in the server according to the reason of the fault.
In the prior art, a fault can be located through a log, and the specific method is as follows: receiving a fault repair request of a target user; the fault repair request comprises identification information of a target user; confirming a target log in the stored logs of each server based on the identification information, wherein the target log is generated when the server processes a task processing request of a target user; and analyzing the obtained target log, and determining the server where the service with the fault is located. Usually, fault location can be performed by the above method, but because the number of logs is large, the speed of performing log checking one by one is slow, and therefore, it is difficult to determine a target log in a short time, and the time for fault location is long.
Disclosure of Invention
The embodiment of the invention aims to provide a fault positioning method and a fault positioning device so as to quickly position a fault. The specific technical scheme is as follows:
in a first aspect, to achieve the above object, an embodiment of the present invention discloses a fault location method, where the method includes:
determining a target tracking key, wherein the target tracking key is used for tracking identification information of a server responding to a target service request;
determining logs recorded with the target tracking key in locally stored logs, and determining the determined logs as target logs, wherein each locally stored log records a tracking key corresponding to a service request responded by a server;
and positioning the server where the service with the fault is located according to the alarm information recorded in the target log.
Optionally, the target tracking key is composed of a preset number of preset types of numerical values.
Optionally, the determining a target tracking key includes:
receiving a fault positioning request aiming at target service request failure, wherein the fault positioning request carries identification information of the target service request;
inquiring a log recorded with identification information of the target service request in a locally stored log;
and determining a target tracking key according to the tracking key recorded in the inquired log.
Optionally, the determining a target tracking key includes:
detecting whether a log containing a preset identifier exists in locally stored logs or not;
and if the preset mark exists, determining a target tracking key according to the tracking key recorded in the log containing the preset mark.
Optionally, the determining, according to the alarm information recorded in the target log, a server where the failed service is located includes:
determining alarm time corresponding to the alarm information recorded in the target log;
and positioning the server corresponding to the log with the earliest alarm time in the target logs as the server where the service with the fault is located.
In a second aspect, in order to achieve the above object, an embodiment of the present invention discloses a fault location apparatus, including:
the system comprises a first determining module, a first judging module and a second determining module, wherein the first determining module is used for determining a target tracking key, and the target tracking key is used for tracking identification information of a server responding to a target service request;
the second determining module is used for determining the log recorded with the target tracking key in the locally stored logs and determining the determined log as the target log, wherein each locally stored log records the tracking key corresponding to the service request responded by the server;
and the positioning module is used for positioning the server where the service with the fault is located according to the alarm information recorded in the target log.
Optionally, the target tracking key is composed of a preset number of preset types of numerical values.
Optionally, the first determining module includes:
the receiving submodule is used for receiving a fault positioning request aiming at target service request failure, wherein the fault positioning request carries identification information of the target service request;
the query submodule is used for querying a log recorded with the identification information of the target service request in a locally stored log;
and the first determining submodule determines a target tracking key according to the searched tracking key recorded in the log.
Optionally, the first determining module includes:
the detection submodule is used for detecting whether a log containing a preset identifier exists in the locally stored log;
and the second determining submodule is used for determining a target tracking key according to the tracking key recorded in the log containing the preset identifier under the condition that the detection result of the detection submodule is present.
Optionally, the positioning module includes:
a third determining submodule, configured to determine an alarm time corresponding to the alarm information recorded in the target log;
and the positioning submodule is used for positioning the server corresponding to the log with the earliest alarm time in the target logs as the server where the service with the fault is positioned.
According to the fault positioning method and device provided by the embodiment of the invention, the target log is quickly determined through the tracking key, the server where the service with the fault is located can be positioned according to the alarm information in the target log, compared with the prior art, the time for determining the target log is shorter, and the fault can be quickly positioned.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings 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 of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a fault location method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating the transfer of tracking keys between services according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of the collection of logs using flash in an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a fault location device according to an embodiment of the present invention.
Detailed Description
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.
Fig. 1 is a schematic flow chart of a fault location method provided in an embodiment of the present invention, where the method includes:
s101: and determining a target tracking key, wherein the target tracking key is used for tracking the identification information of the server responding to the target service request.
Specifically, the target tracking key may be composed of a preset number of preset types of numerical values.
In the embodiment of the present invention, when the trace key (trace ID) is a numerical type, the space occupied by the trace key may be relatively fixed, and the generation may be relatively easy, and specifically, the generation may be performed by using a random algorithm. The preset number may be one or more, and may be specifically determined according to the number of service requests in the first period of time. The preset type may be integer, long integer, etc., and the tracking key may be composed of two long integers, one long integer having a value space of 264The value space of the two long integers is 2128Then the probability of the two tracking keys being the same is 1/2128And the probability that the two tracking keys are the same is extremely low, so that the log accuracy determined according to the tracking keys is ensured.
In practical application, a service request is responded by a plurality of services, and the services cooperate with each other to complete the processing of the service request. The trace key may be generated by the server where the first service to process the service request is located, as an additional parameter to the service invocation, each invocation passing the trace key as a parameter to the new service. As an example, a schematic diagram of the trace key passing between services may be as shown in fig. 2, where a Web (World Wide Web) Service generates a trace key 1 and passes the trace key 1 to an HTTP (Hyper Text Transfer Protocol) Service and an RPC (Remote Procedure Call Protocol) Service, the HTTP Service passes the trace key 1 to a DB (Data Base) Service, and the RPC Service passes the trace key 1 to the HBase Service. Among them, HBase is a distributed, column-oriented open-source database.
Passing the tracking key between services may be understood as a server in one service responding to the service request and then passing the tracking key along with other parameters to a server in the next service. Of course, the tracking key may also be generated by a common component library, a tracking key variable is set in the common component library, one tracking key is generated for one service request, and as the service request is processed in different services, the tracking key is also transmitted with components of different services. The tracking key is transferred in the common component library, which is the same as the transfer method of other parameters in the common component library in the prior art, and is not described herein again.
The first trace key transfer method is simpler to implement, but requires additional transfer of trace keys. The second method of tracking key delivery is transparent to the user and is automatic, but requires support of all common components in the common component library. It should be noted that the common component library is a library composed of common components, and the common components are components that can be called by the components or programs in the outer layer.
In the embodiment of the present invention, the target tracking key may be determined by:
the first step is as follows: receiving a fault positioning request aiming at target service request failure, wherein the fault positioning request carries identification information of the target service request.
In the embodiment of the invention, if the server fails to cause the failure of the service request processing, a corresponding fault location request is generated. The fault location request may be sent by a user, may be sent by another system, may be sent by a server where a service with a fault is located, and the like, and is not limited herein. The fault location request carries identification information of the target service request, and the identification information may include, for example, a time when the target service request is sent, an IP (Internet Protocol) address used, and the like, to determine the target service request.
The second step is that: and inquiring a log recorded with the identification information of the target service request in a locally stored log.
In the embodiment of the invention, each server where each service is located can print the log, and the log printing is to generate and store the log. When a server prints a log, a trace key corresponding to a service request responded by the server is recorded. Illustratively, if the tracking key corresponding to the service request 1 is the tracking key 1, the server 1 prints a log corresponding to the service request 1, and simultaneously prints the tracking key 1 into the log.
The fault positioning method provided by the embodiment of the invention can be applied to Elastic Search. The Elastic Search is a Search server based on Lucene (full text Search engine), and not only is an excellent open source Search engine for providing storage, query and retrieval, but also can provide instant query. In practical applications, the logs on the servers deployed by each service may be collected and stored in an Elastic Search.
In the embodiment of the present invention, the log collection tool may be used to collect logs, and the log collection tool may be flash, Logstash, or the like. Flume is a highly available, highly reliable, distributed system of mass log collection, aggregation and transmission provided by Cloudera. For example, a schematic diagram of collecting logs by using flash may be as shown in fig. 3, where flash may be deployed in each service, and the flash deployed in each service collects logs and stores the collected logs in an Elastic Search. The Logstash is a lightweight log collection processing framework, can conveniently collect scattered and diversified logs, performs user-defined processing, and then transmits the collected logs to a designated position.
The third step: and determining a target tracking key according to the tracking key recorded in the inquired log.
In the embodiment of the invention, the inquired log not only contains the identification information of the target service request, but also contains the tracking key, and the tracking key can be determined as the target tracking key.
In the embodiment of the present invention, the target tracking key may also be determined by:
the first step is as follows: and detecting whether a log containing a preset identifier exists in the locally stored log.
In practical applications, the Elastic Search stores the received log, and then detects whether there is a log containing a preset identifier in the locally stored log, where the preset identifier may be identification information of an alarm, and may be an error (for example). If the log contains the preset identifier, it indicates that the service running in the server corresponding to the log may have a fault, or the service running in another server that processes the same service request as the server has a fault.
The second step is that: and determining a target tracking key according to the tracking key recorded in the log containing the preset identifier.
If it is detected that the plurality of logs contain the preset identifier and the log pairs aim at one service request, the tracking key recorded in the log containing the preset identifier can be directly determined as the target tracking key.
If a plurality of logs containing preset identifications are detected and the logs are generated for different service requests, the target tracking key can be determined in the detected logs containing the preset identifications by the following two methods:
the first method comprises the following steps: the logs including the same tracking key in the detected logs including the preset identifier can be classified into one type. And determining a tracking key in one type of logs as a target tracking key, and determining a target log according to the target tracking key so as to position a server with a fault. Then, in other logs of which the tracking key is not determined as the target tracking key, one log is selected, and the tracking key in the selected log is determined as the target tracking key. And repeating the steps of determining the target log and further positioning the server with the fault until the tracking key in each type of log containing the preset identifier is determined as the target tracking key.
And the second method comprises the following steps: the method includes the steps that logs containing the same tracking key in detected logs containing preset marks are classified into one type, the tracking key in each type of logs is determined as a target tracking key, the target logs are determined according to the target tracking key aiming at the tracking key determined in each type of logs, and then a server with a fault is located.
The first method is to determine the target tracking key in series, the second method is to determine the target tracking key in parallel, and in practical application, one of the methods can be selected to determine the target tracking key.
S102: and determining the log recorded with the target tracking key in the locally stored logs, and determining the determined log as the target log, wherein each locally stored log records the tracking key corresponding to the service request responded by the server.
It should be noted that, of the locally stored logs, all logs in which the target tracking key is recorded are determined. Illustratively, the target tracking key is recorded in log 1, log 2, log 3 and log 4, and then log 1, log 2, log 3 and log 4 are determined as target logs.
It will be understood by those skilled in the art that any one server may generate logs for its operating status during operation, and these logs may include: the identification of the processing request of the server, the running state record, the identification of whether the processing request is successful or not and the like; in addition, the normal operation of the service is dependent on hardware equipment, and the normal operation of one service may be dependent on one server or a plurality of servers; based on the above two aspects, it can be known that the service request is specifically responded by the server on which the service is supported, and then the servers can generate logs in the process of responding to the service request.
In particular, the tracking key corresponds to the service request, so that the tracking key can be recorded in the log content while the log is generated, and each log can clearly and intuitively correspond to each service request. By combining the above conditions, the server responding to the service request corresponding to the tracking key can be tracked by adopting the tracking key, so that the log generated by the server aiming at the service request can be acquired at one time according to the tracking key, the fault can be positioned according to the acquired log, the fault can be positioned in one-stop mode, and the method is convenient and quick.
S103: and positioning the server where the service with the fault is located according to the alarm information recorded in the target log.
In the embodiment of the invention, when a service running in one server fails, the alarm information can appear in the log of the server, and the alarm information can also appear in the log of the server which responds to the same service request together with the server. Illustratively, the server 1, the server 2, the server 3 and the server 4 respond to the service request a in sequence, and if the service running in the server 3 fails, the server 3 generates alarm information for the log of the service request a, and the server 1 and the server 2 generate alarm information for the log of the service request a. The alarm information in the target log is analyzed, and the server where the service with the fault is located can be located.
In a preferred embodiment of the present invention, determining a server where a failed service is located according to alarm information recorded in the target log includes:
determining alarm time corresponding to the alarm information recorded in the target log;
and positioning the server corresponding to the log with the earliest alarm time in the target logs as the server where the service with the fault is located.
The alarm time is the time when the alarm information is generated, and each alarm time corresponds to one alarm information. When one server fails, the log of the service request in response records the alarm information, and the log of the service request by the other server in response to the service request also records the alarm information. Therefore, the server corresponding to the log with the earliest alarm time in the target log can be determined as the failed server. For example, the alarm time may be an alarm timestamp, the alarm timestamp of each log in the target log is determined, the determined alarm timestamps are sorted according to the sequence of the alarm timestamps, and the server corresponding to the alarm timestamp arranged at the top is positioned as the server where the failed service is located.
In the embodiment of the invention, the target log not only records the alarm time, but also records the reason of the fault, and a maintainer can determine where the service in the server is in the specific problem according to the reason of the fault, so that the problem is solved, the service in the server can normally run, and the service request can be processed.
By applying the embodiment of the invention, the target log is quickly determined through the tracking key, and the server where the service with the fault is located can be positioned according to the alarm information in the target log.
Corresponding to the method embodiment shown in fig. 1, fig. 4 is a schematic structural diagram of a fault location apparatus provided in an embodiment of the present invention, and the apparatus includes a first determining module 201, a second determining module 202, and a locating module 203, wherein,
a first determining module 201, configured to determine a target tracking key, where the target tracking key is identification information of a server for tracking and responding to a target service request;
a second determining module 202, configured to determine, in a locally stored log, a log in which the target tracking key is recorded, and determine the determined log as a target log, where each locally stored log records a tracking key corresponding to a service request responded by a server;
and the positioning module 203 is configured to position a server where the failed service is located according to the alarm information recorded in the target log.
Specifically, the target tracking key is composed of a preset number of preset types of numerical values.
Specifically, the first determining module 201 may include a receiving sub-module, a querying sub-module, and a first determining sub-module (not shown in the figure).
The receiving submodule is used for receiving a fault positioning request aiming at target service request failure, wherein the fault positioning request carries identification information of the target service request;
the query submodule is used for querying a log recorded with the identification information of the target service request in a locally stored log;
and the first determining submodule determines a target tracking key according to the searched tracking key recorded in the log.
Specifically, the first determining module 201 may include a detecting sub-module and a second determining sub-module (not shown in the figure).
The detection submodule is used for detecting whether a log containing a preset identifier exists in the locally stored log;
and the second determining submodule is used for determining a target tracking key according to the tracking key recorded in the log containing the preset identifier under the condition that the detection result of the detection submodule is present.
Specifically, the positioning module 203 may include a third determining sub-module and a positioning sub-module (not shown).
A third determining submodule, configured to determine an alarm time corresponding to the alarm information recorded in the target log;
and the positioning submodule is used for positioning the server corresponding to the log with the earliest alarm time in the target logs as the server where the service with the fault is positioned.
By applying the embodiment of the invention, the target log is quickly determined through the tracking key, and the server where the service with the fault is located can be positioned according to the alarm information in the target log.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (6)
1. A method of fault location, the method comprising:
determining a target tracking key, wherein the target tracking key is used for tracking identification information of a server responding to a target service request;
determining logs recorded with the target tracking key in locally stored logs, and determining the determined logs as target logs, wherein each locally stored log records a tracking key corresponding to a service request responded by a server;
positioning a server where the service with the fault is located according to the alarm information recorded in the target log;
the target tracking key determination method comprises the following steps:
receiving a fault positioning request aiming at target service request failure, wherein the fault positioning request carries identification information of the target service request;
inquiring a log recorded with identification information of the target service request in a locally stored log;
determining a target tracking key according to the tracking key recorded in the inquired log;
alternatively, the first and second electrodes may be,
detecting whether a log containing a preset identifier exists in locally stored logs or not; the preset identification is identification information of an alarm;
and if the preset mark exists, determining a target tracking key according to the tracking key recorded in the log containing the preset mark.
2. The method of claim 1, wherein the target tracking key is comprised of a preset number of preset types of numeric values.
3. The method according to any one of claims 1-2, wherein the determining the server where the failed service is located according to the alarm information recorded in the target log comprises:
determining alarm time corresponding to the alarm information recorded in the target log;
and positioning the server corresponding to the log with the earliest alarm time in the target logs as the server where the service with the fault is located.
4. A fault locating device, characterized in that the device comprises:
the system comprises a first determining module, a first judging module and a second determining module, wherein the first determining module is used for determining a target tracking key, and the target tracking key is used for tracking identification information of a server responding to a target service request;
the second determining module is used for determining the log recorded with the target tracking key in the locally stored logs and determining the determined log as the target log, wherein each locally stored log records the tracking key corresponding to the service request responded by the server;
the positioning module is used for positioning a server where the service with the fault is located according to the alarm information recorded in the target log;
the first determining module includes:
the receiving submodule is used for receiving a fault positioning request aiming at target service request failure, wherein the fault positioning request carries identification information of the target service request;
the query submodule is used for querying a log recorded with the identification information of the target service request in a locally stored log;
the first determining sub-module is used for determining a target tracking key according to the searched tracking key recorded in the log;
alternatively, the first and second electrodes may be,
the detection submodule is used for detecting whether a log containing a preset identifier exists in the locally stored log; the preset identification is identification information of an alarm;
and the second determining submodule is used for determining a target tracking key according to the tracking key recorded in the log containing the preset identifier under the condition that the detection result of the detection submodule is present.
5. The apparatus of claim 4, wherein the target tracking key is comprised of a preset number of preset types of numeric values.
6. The apparatus of any of claims 4-5, wherein the positioning module comprises:
a third determining submodule, configured to determine an alarm time corresponding to the alarm information recorded in the target log;
and the positioning submodule is used for positioning the server corresponding to the log with the earliest alarm time in the target logs as the server where the service with the fault is positioned.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710207391.8A CN107168845B (en) | 2017-03-31 | 2017-03-31 | Fault positioning method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710207391.8A CN107168845B (en) | 2017-03-31 | 2017-03-31 | Fault positioning method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107168845A CN107168845A (en) | 2017-09-15 |
| CN107168845B true CN107168845B (en) | 2020-12-25 |
Family
ID=59849801
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710207391.8A Active CN107168845B (en) | 2017-03-31 | 2017-03-31 | Fault positioning method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107168845B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108768752B (en) * | 2018-06-25 | 2021-12-03 | 华为技术有限公司 | Fault positioning method, device and system |
| CN109687994A (en) * | 2018-11-30 | 2019-04-26 | 北京奇艺世纪科技有限公司 | A kind of message treatment method, system, device and equipment |
| CN110048899B (en) * | 2019-05-29 | 2022-03-04 | 北京奇艺世纪科技有限公司 | Log detection method and device, terminal and server |
| CN110442498B (en) * | 2019-06-28 | 2022-11-25 | 平安科技（深圳）有限公司 | Abnormal data node positioning method and device, storage medium and computer equipment |
| CN110677304A (en) * | 2019-10-11 | 2020-01-10 | 广州趣丸网络科技有限公司 | Distributed problem tracking system and equipment |
| CN111061584A (en) * | 2019-11-21 | 2020-04-24 | 浪潮电子信息产业股份有限公司 | Fault diagnosis method, device, equipment and readable storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105577454A (en) * | 2016-03-03 | 2016-05-11 | 上海新炬网络信息技术有限公司 | Method for quickly positioning service fault based on log |
| CN106100913A (en) * | 2016-08-25 | 2016-11-09 | 北京票之家科技有限公司 | Error message alignment system and method |
| CN106254145B (en) * | 2016-09-06 | 2019-07-19 | 腾讯科技（深圳）有限公司 | Network request tracking processing method and device |
-
2017
- 2017-03-31 CN CN201710207391.8A patent/CN107168845B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107168845A (en) | 2017-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107168845B (en) | Fault positioning method and device | |
| US10476905B2 (en) | Security actions for computing assets based on enrichment information | |
| JP4318643B2 (en) | Operation management method, operation management apparatus, and operation management program | |
| WO2013186870A1 (en) | Service monitoring system and service monitoring method | |
| US20070118528A1 (en) | Apparatus and method for blocking phishing web page access | |
| JP5353540B2 (en) | Operation history collection device, operation history collection method, and program | |
| CN105119783B (en) | Method and device for detecting network request data | |
| CN100440160C (en) | Monotoring device, monotiring method, and monotoring system | |
| CN111897625B (en) | Resource event backtracking method, system and electronic equipment based on Kubernetes cluster | |
| CN108900374B (en) | Data processing method and device applied to DPI equipment | |
| CN112181931A (en) | Big data system link tracking method and electronic equipment | |
| CN112711496A (en) | Log information full link tracking method and device, computer equipment and storage medium | |
| CN111078447A (en) | Method, device, equipment and medium for positioning abnormity in micro-service architecture | |
| CA3139971A1 (en) | Problem positioning method and device | |
| CN109086094B (en) | Method, system, device and storage medium for self-starting of application service | |
| CN112714118B (en) | Network traffic detection method and device | |
| KR101770066B1 (en) | Method and system for real time tracking and analysing business transaction using application call log in distributed system | |
| CN105183648A (en) | Visualized automatic dial testing method and system | |
| CN108024090B (en) | Abnormity positioning method and device for video monitoring platform | |
| JP5707263B2 (en) | Fault location diagnostic system and fault location diagnostic method | |
| CN116760571A (en) | Asset identification method, device, electronic equipment and storage medium | |
| KR101288535B1 (en) | Method for monitoring communication system and apparatus therefor | |
| CN108255868B (en) | Method and device for checking links in website | |
| CN110968779A (en) | Processing method and device for crawling webpage information | |
| CN113037564B (en) | Network fault diagnosis method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |