CN107168845A - A kind of Fault Locating Method and device - Google Patents
A kind of Fault Locating Method and device Download PDFInfo
- Publication number
- CN107168845A CN107168845A CN201710207391.8A CN201710207391A CN107168845A CN 107168845 A CN107168845 A CN 107168845A CN 201710207391 A CN201710207391 A CN 201710207391A CN 107168845 A CN107168845 A CN 107168845A
- Authority
- CN
- China
- Prior art keywords
- daily record
- target
- server
- service
- key
- 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.)
- Granted
Links
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 embodiments of the invention provide a kind of Fault Locating Method and device, method includes：Target following key is determined, wherein, the target following key is the identification information of the server for tracking response target service requests；Determine that record has the daily record of the target following key in the daily record being locally stored, and identified daily record is defined as target journaling, wherein, each daily record being locally stored has recorded server and has responded the corresponding tracking key of service request；Warning information according to described in the target journaling, positions the server where the service broken down.Fault location is carried out using scheme provided in an embodiment of the present invention, realizes and rapidly failure is positioned.
Description
Technical field
The present invention relates to field of computer technology, more particularly to a kind of Fault Locating Method and device.
Background technology
With the arrival of information age, the demand of user is more and more diversified, and service provider is in order to meet the need of user
Ask, develop a variety of services, cooperated between these services developed, the demand of user could be met by mutually calling.Clothes
Business, which only relies on server, could realize its function, therefore, it can service arrangement at least one server.But with
The quantity for the service of is constantly increasing, and the quantity of server is consequently increased, but the service run in each server has
Failure is likely to occur, and the failure of the service run in server is likely to result in responding the task processing request failure of user,
Accordingly, it would be desirable to failure is positioned, it is determined that the server where the service broken down, while determining the original broken down
Cause, in order to which attendant is according to the reason for failure, is repaired to the service broken down in the server in time.
In the prior art, failure can be positioned by daily record, specific method is：Receive the event of targeted customer
Barrier reports request for repairment；Wherein, the identification information of the troublshooting request bag containing targeted customer；Based on the identification information, in storage
Each server daily record in confirm target journaling, wherein, target journaling for server process targeted customer task handle
Produced during request；The target journaling of acquisition is analyzed, it is determined that the server where the service broken down.Normal conditions
Under can carry out fault location through the above way, but because daily record amount number is various, it is slower to carry out daily record investigation speed one by one,
Accordingly, it is difficult to target journaling be determined in a short time, so as to cause the time of fault location long.
The content of the invention
The purpose of the embodiment of the present invention is to provide a kind of Fault Locating Method and device, to realize rapidly to enter failure
Row positioning.Concrete technical scheme is as follows：
In a first aspect, in order to achieve the above object, the embodiment of the invention discloses a kind of Fault Locating Method, methods described
Including：
Target following key is determined, wherein, the target following key is the server for tracking response target service requests
Identification information；
Determine that record has the daily record of the target following key in the daily record being locally stored, and identified daily record is determined
For target journaling, wherein, each daily record being locally stored has recorded server and has responded the corresponding tracking key of service request；
Warning information according to described in the target journaling, positions the server where the service broken down.
Optionally, the target following key is made up of the numerical value of predetermined number preset kind.
Optionally, the determination target following key, including：
The fault position request for target service requests failure is received, wherein, institute is carried in the fault position request
State the identification information of target service requests；
Inquiry record has the daily record of the identification information of the target service requests in the daily record being locally stored；
According to the tracking key recorded in the daily record inquired, target following key is determined.
Optionally, the determination target following key, including：
Detect in the daily record being locally stored with the presence or absence of the daily record for including default mark；
If it does, according to the tracking key recorded in the daily record comprising the default mark, determining target following key.
Optionally, the warning information according to described in the target journaling, it is determined that where the service broken down
Server, including：
Determine the corresponding alarm time of warning information described in the target journaling；
By service institute of the corresponding server selection of the earliest daily record of alarm time in the target journaling for failure
Server.
Second aspect, in order to achieve the above object, the embodiment of the invention discloses a kind of fault locator, described device
Including：
First determining module, for determining target following key, wherein, the target following key is for tracking response target
The identification information of the server of service request；
Second determining module, for determining that record has the daily record of the target following key in the daily record being locally stored, and
Identified daily record is defined as target journaling, wherein, each daily record being locally stored has recorded server and has responded service
Ask corresponding tracking key；
Locating module, for the warning information according to described in the target journaling, positions the service place broken down
Server.
Optionally, the target following key is made up of the numerical value of predetermined number preset kind.
Optionally, first determining module, including：
Receiving submodule, for receiving the fault position request for target service requests failure, wherein, the failure is determined
The identification information of the target service requests is carried in the request of position；
Submodule is inquired about, has the identification information of the target service requests for inquiring about record in the daily record being locally stored
Daily record；
First determination sub-module, according to the tracking key recorded in the daily record inquired, determines target following key.
Optionally, first determining module, including：
Detection sub-module, for detecting in the daily record being locally stored with the presence or absence of the daily record for including default mark；
Second determination sub-module, in the presence of being in the testing result of the detection sub-module, according to comprising
The tracking key recorded in the daily record of the default mark, determines target following key.
Optionally, the locating module, including：
3rd determination sub-module, for determining the corresponding alarm time of warning information described in the target journaling；
Submodule is positioned, for being by the corresponding server selection of the earliest daily record of alarm time in the target journaling
Server where the service of existing failure.
Fault Locating Method and device provided in an embodiment of the present invention, target journaling, root are quickly determined by tracking key
According to the warning information in target journaling, the server where the service of failure can be positioned, compared to prior art, it is determined that
The time of target journaling is shorter, and rapidly failure can be positioned.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing
There is the accompanying drawing used required in technology description to be briefly described, it should be apparent that, drawings in the following description are only this
Some embodiments of invention, for those of ordinary skill in the art, on the premise of not paying creative work, can be with
Other accompanying drawings are obtained according to these accompanying drawings.
Fig. 1 is a kind of schematic flow sheet of Fault Locating Method provided in an embodiment of the present invention；
Fig. 2 is the schematic diagram that transmits between services of tracking key in the embodiment of the present invention；
Fig. 3 is the schematic diagram in the embodiment of the present invention using Flume collector journals；
Fig. 4 is a kind of structural representation of fault locator provided in an embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete
Site preparation is described, it is clear that described embodiment is only a part of embodiment of the invention, rather than whole embodiments.It is based on
Embodiment in the present invention, it is every other that those of ordinary skill in the art are obtained under the premise of creative work is not made
Embodiment, belongs to the scope of protection of the invention.
Fig. 1 is a kind of schematic flow sheet of Fault Locating Method provided in an embodiment of the present invention, and method includes：
S101：Target following key is determined, wherein, the target following key is the clothes for tracking response target service requests
The identification information of business device.
Specifically, target following key can be made up of the numerical value of predetermined number preset kind.
In embodiments of the present invention, when tracking key (trace ID) is numeric type, it can to track the space that key takes
Compare fixation, generation is easier, specifically, can be using random algorithm generation.Predetermined number can be one or more, tool
Body can be according within the first paragraph time, and the quantity of service request is determined.Preset kind can be integer, long etc., show
Example property, tracking key can be made up of the numerical value of two longs, and the value space of a long is 264, the value of two longs
Space is 2128, then two tracking key identical probability are 1/2128, two tracking key identical probability it is minimum, it is ensured that according to
The daily record accuracy that track key is determined.
In actual applications, service request cooperates by multiple service responses, between service could complete to ask service
The processing asked.Tracking key can be where first service for being handled service request server generate, generation
Key is tracked as the additional parameter of service call, calls the tracking key is all passed into new service as parameter every time.Example
Property, the schematic diagram that tracking key is transmitted between services can be with as shown in Fig. 2 Web (World Wide Web, global wide area network)
Service (service) generation tracking keys 1, and the tracking key 1 is passed into HTTP (Hyper Text Transfer
Protocol, HTTP) Service and RPC (Remote Procedure Call Protocol, remote process
Invocation protocol) Service, HTTP Service by track key 1 pass to DB (Data Base, database) Service, RPC
Service passes to HBase Service by key 1 is tracked.Wherein, HBase is a data distributed, towards row of increasing income
Storehouse.
Tracking key transmits the server that can be understood as in a service and responds the service request between services, then will
Tracking key passes to the server in next service together with other parameters.Certainly, tracking key can also be common component storehouse
Generation, tracking key variable is set in common component storehouse, a tracking key is generated for a service request, and with service
Request is handled in different services, and tracking key can also be transmitted with the component of different services.Key is tracked in common component storehouse
Transmission, it is identical with transmission method of the other specification of the prior art in common component storehouse, herein without repeating.
The first tracking key transmission method is realized fairly simple, but needs extra transmission tracking key.Second of tracking key is passed
Pass method transparent to user, and transmit automatically, but need the support of all common components in common component storehouse.Need explanation
, the storehouse that common component storehouse is made up of common component, common component is can be by the component of outer layer or the group of routine call
Part.
In embodiments of the present invention, target following key can be determined in the following manner：
The first step：The fault position request for target service requests failure is received, wherein, in the fault position request
Carry the identification information of the target service requests.
In embodiments of the present invention, server, which breaks down, to cause service request handling to fail, then will have corresponding
Fault position request.The fault position request can user send or other systems send, can also be out
What the server where the service of existing failure was sent etc., it is not defined herein.Fault position request carries target
The identification information of service request, exemplary, the identification information can include the time, used for sending target service requests
IP (agreement interconnected between Internet Protocol, network) address etc. is used for determining the information of target service requests.
Second step：Inquiry record has the daily record of the identification information of the target service requests in the daily record being locally stored.
In embodiments of the present invention, each server where each service can be exactly with print log, print log
Generation daily record simultaneously saves daily record.When a server print log, there is the server to respond clothes record
The corresponding tracking key of business request is also printed into.Exemplary, the corresponding tracking key of service request 1 is tracking key 1, then server
1 print needle is to the corresponding daily record of service request 1, while tracking key 1 is printed in the daily record.
Fault Locating Method provided in an embodiment of the present invention can apply to Elastic Search.Elastic Search
Be one be based on Lucene (full-text search engine) search server, a offer storage is provided, inquire about, retrieval it is outstanding
Search engine of increasing income, immediate inquiring can also be provided.In actual applications, can be by the disposed server of each service
Daily record all collect and be stored in Elastic Search.
In embodiments of the present invention, it is possible to use log collection instrument carries out the collection of daily record, log collection instrument can be with
For Flume, Logstash etc..Flume is the High Availabitity that Cloudera is provided, highly reliable, distributed magnanimity
The system of log collection, polymerization and transmission.Exemplary, use the schematic diagram of Flume collector journals can be with as shown in figure 3, can
So that Flume is deployed in each service, the Flume disposed in each service carries out the collection of daily record, and by the daily record of collection
Store Elastic Search.Logstash is the log collection processing framework of a lightweight, in that context it may be convenient to scattered
, diversified log collection get up, and carry out customized processing, then by the log transmission being collected into the position specified
Put.
3rd step：According to the tracking key recorded in the daily record inquired, target following key is determined.
In embodiments of the present invention, the identification information of target service requests is not only contained in the daily record inquired, is also wrapped
Contain tracking key, the tracking key can be defined as target following key.
In embodiments of the present invention, target following key can also be determined in the following manner：
The first step：Detect in the daily record being locally stored with the presence or absence of the daily record for including default mark.
In actual applications, Elastic Search store received daily record, it is then detected that in the daily record being locally stored
With the presence or absence of the daily record for including default mark, default mark mentioned here can be the identification information of alarm, exemplary, can
To be error (mistake).If containing default mark in daily record, illustrate that the service run in the corresponding server of the daily record can
It can break down, or be broken down with the service that is run in other servers of the same service request of the server process.
Second step：According to the tracking key recorded in the daily record comprising the default mark, target following key is determined.
If detected and include default mark in multiple daily records, and these daily records would be to for a service request, then might be used
With the tracking key that will directly be recorded in the daily record for including default mark, it is defined as target following key.
If detected and include default mark in multiple daily records, and these daily records would be to for different service request generations
, then it can determine target following key in the daily record for including default mark detected by following two methods：
The first：The daily record of same tracking key can be included by the daily record for including default mark detected
It is divided into a class.Tracking key in one type daily record is defined as target following key, target is determined further according to the target following key
Daily record, and then position the server broken down.Then, other class daily records of target following key are not determined as in tracking key
In, a class daily record is selected, the tracking key in the daily record of selection is defined as target following key.Determination target journaling is repeated,
And then the step of server of positioning failure, it is defined as up to tracking key in the daily record that each class includes default mark
Target following key.
Second：The daily record of same tracking key can be included by the daily record for including default mark detected
Be divided into a class, the tracking key in each class daily record be defined as target following key respectively, for determined in each class daily record with
Track key, performs determine target journaling, and then the step of server of positioning failure according to target following key respectively.
First method is serially to determine target following key, and second method is concurrently to determine target following key,
In practical application, a kind of method therein can be selected to determine target following key.
S102：Record is determined in the daily record being locally stored the daily record of the target following key, and by identified day
Will is defined as target journaling, wherein, each daily record being locally stored recorded server respond service request it is corresponding with
Track key.
It should be noted that in the daily record being locally stored, it is determined that record has all daily records of target following key.It is exemplary
, daily record 1, daily record 2, daily record 3 and daily record 4, which are all recorded, target following key, then daily record 1, daily record 2, daily record 3 and daily record 4 is true
It is set to target journaling.
Those skilled in that art are it is understood that any server in the process of running can be for its fortune
Row state generates daily record, can include in these daily records：The mark of the handled request of server, running status record, processing are asked
No successful mark of Seeking Truth etc.；In addition, the normal operation of service relies on hardware device, the normal operation of a service
A server may be relied on, it is also possible to rely on multiple servers；Based on above-mentioned two aspects situation, service can be learnt
Request is responded by servicing relied on service implement body, then these servers can be during service request be responded
Generate daily record.
Specifically, tracking key is corresponding with service request, so can be in log content while daily record is generated
Middle record tracking key, so each daily record can understand, intuitively corresponding with each service request.Summary situation,
Can realize using tracking key the server for responding the corresponding service request of tracking key is tracked so that can according to
Track key, the disposable server that obtains is directed to the daily record that the service request is produced, and thus positions failure according to the daily record of acquisition, real
Existing one-stop positioning failure, it is convenient and swift.
S103：Warning information according to described in the target journaling, positions the server where the service broken down.
In embodiments of the present invention, the service run in a server is broken down, then meeting in the daily record of the server
There is warning information, alarm letter may also occur in the daily record for the server that same service request is responded together with the server
Breath.Exemplary, server 1, server 2, server 3 and server 4 respond service request A successively, if transported in server 3
Capable service is broken down, then server 3 warning information, server 1 and server occurs for the service request A daily records produced
2 also occur warning information for the service request A daily records produced.Warning information in target journaling is analyzed, can be with
Position the server where the service broken down.
In a preferred embodiment of the invention, the warning information according to described in the target journaling, is determined
Server where the service of existing failure, including：
Determine the corresponding alarm time of warning information described in the target journaling；
By service institute of the corresponding server selection of the earliest daily record of alarm time in the target journaling for failure
Server.
Alarm time mentioned here is the time that warning information is produced, one alarm letter of each alarm time correspondence
Breath.One server breaks down, warning information described in the daily record of the service request of response, and responds the service request
Other servers in the daily record of the service request for can also record warning information.When therefore, it being alerted in target journaling
Between the earliest corresponding server of daily record be defined as the server that breaks down.Exemplary, when alarm time can be alarm
Between stab, determine the alarm time stamp of each daily record in target journaling, identified alarm time stabbed and stabbed according to alarm time
Successively it is ranked up, the alarm time that will come foremost stabs corresponding server, where orientating the service of failure as
Server.
In embodiments of the present invention, alarm time is not only described in target journaling, the reason for also describing failure,
The reason for attendant can be according to breaking down, determines where the service in server specifically goes wrong, and then solves
The problem so that the service in the server can normally be run, and can be handled service request.
Using the embodiment of the present invention, target journaling is quickly determined by tracking key, the alarm letter in target journaling
Breath, can position the server where the service of failure, compared to prior art, determine that the time of target journaling compares
It is short, rapidly failure can be positioned.
Corresponding with the embodiment of the method shown in Fig. 1, Fig. 4 is a kind of fault locator provided in an embodiment of the present invention
Structural representation, device includes the first determining module 201, the second determining module 202 and locating module 203, wherein,
First determining module 201, for determining target following key, wherein, the target following key is for tracking response
The identification information of the server of target service requests；
Second determining module 202, for determining that record has the daily record of the target following key in the daily record being locally stored,
And identified daily record is defined as target journaling, wherein, each daily record being locally stored has recorded server and has responded clothes
The corresponding tracking key of business request；
Locating module 203, for the warning information according to described in the target journaling, positions the service institute broken down
Server.
Specifically, the target following key is made up of the numerical value of predetermined number preset kind.
Specifically, first determining module 201, can include receiving submodule, inquiry submodule and first and determine son
Module (not shown).
Receiving submodule, for receiving the fault position request for target service requests failure, wherein, the failure is determined
The identification information of the target service requests is carried in the request of position；
Submodule is inquired about, has the identification information of the target service requests for inquiring about record in the daily record being locally stored
Daily record；
First determination sub-module, according to the tracking key recorded in the daily record inquired, determines target following key.
Specifically, first determining module 201, can include detection sub-module and the second determination sub-module (in figure not
Show).
Detection sub-module, for detecting in the daily record being locally stored with the presence or absence of the daily record for including default mark；
Second determination sub-module, in the presence of being in the testing result of the detection sub-module, according to comprising
The tracking key recorded in the daily record of the default mark, determines target following key.
Specifically, locating module 203, can include the 3rd determination sub-module and positioning submodule (not shown).
3rd determination sub-module, for determining the corresponding alarm time of warning information described in the target journaling；
Submodule is positioned, for being by the corresponding server selection of the earliest daily record of alarm time in the target journaling
Server where the service of existing failure.
Using the embodiment of the present invention, target journaling is quickly determined by tracking key, the alarm letter in target journaling
Breath, can position the server where the service of failure, compared to prior art, determine that the time of target journaling compares
It is short, rapidly failure can be positioned.
It should be noted that herein, such as first and second or the like relational terms are used merely to a reality
Body or operation make a distinction with another entity or operation, and not necessarily require or imply these entities or deposited between operating
In any this actual relation or order.Moreover, term " comprising ", "comprising" or its any other variant are intended to
Nonexcludability is included, so that process, method, article or equipment including a series of key elements not only will including those
Element, but also other key elements including being not expressly set out, or also include being this process, method, article or equipment
Intrinsic key element.In the absence of more restrictions, the key element limited by sentence "including a ...", it is not excluded that
Also there is other identical element in process, method, article or equipment including the key element.
Each embodiment in this specification is described by the way of related, identical similar portion between each embodiment
Divide mutually referring to what each embodiment was stressed is the difference with other embodiment.It is real especially for system
Apply for example, because it is substantially similar to embodiment of the method, so description is fairly simple, related part is referring to embodiment of the method
Part explanation.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the scope of the present invention.It is all
Any modification, equivalent substitution and improvements made within the spirit and principles in the present invention etc., are all contained in protection scope of the present invention
It is interior.
Claims (10)
1. a kind of Fault Locating Method, it is characterised in that methods described includes：
Target following key is determined, wherein, the target following key is the mark of the server for tracking response target service requests
Know information；
Determine that record has the daily record of the target following key in the daily record being locally stored, and identified daily record is defined as mesh
Daily record is marked, wherein, each daily record being locally stored has recorded server and has responded the corresponding tracking key of service request；
Warning information according to described in the target journaling, positions the server where the service broken down.
2. according to the method described in claim 1, it is characterised in that the target following key is by predetermined number preset kind
Numerical value is constituted.
3. according to the method described in claim 1, it is characterised in that the determination target following key, including：
The fault position request for target service requests failure is received, wherein, the mesh is carried in the fault position request
Mark the identification information of service request；
Inquiry record has the daily record of the identification information of the target service requests in the daily record being locally stored；
According to the tracking key recorded in the daily record inquired, target following key is determined.
4. according to the method described in claim 1, it is characterised in that the determination target following key, including：
Detect in the daily record being locally stored with the presence or absence of the daily record for including default mark；
If it does, according to the tracking key recorded in the daily record comprising the default mark, determining target following key.
5. the method according to claim any one of 1-4, it is characterised in that described according to described in the target journaling
Warning information, it is determined that the server where the service broken down, including：
Determine the corresponding alarm time of warning information described in the target journaling；
Where service by the corresponding server selection of the earliest daily record of alarm time in the target journaling for failure
Server.
6. a kind of fault locator, it is characterised in that described device includes：
First determining module, for determining target following key, wherein, the target following key is for tracking response destination service
The identification information of the server of request；
Second determining module, for determining that record has the daily record of the target following key in the daily record being locally stored, and by institute
The daily record of determination is defined as target journaling, wherein, each daily record being locally stored has recorded server and has responded service request
Corresponding tracking key；
Locating module, for the warning information according to described in the target journaling, positions the clothes where the service broken down
Business device.
7. device according to claim 6, it is characterised in that the target following key is by predetermined number preset kind
Numerical value is constituted.
8. device according to claim 6, it is characterised in that first determining module, including：
Receiving submodule, for receiving the fault position request for target service requests failure, wherein, the fault location please
Seek the middle identification information for carrying the target service requests；
Submodule is inquired about, for inquiring about the day that record has the identification information of the target service requests in the daily record being locally stored
Will；
First determination sub-module, according to the tracking key recorded in the daily record inquired, determines target following key.
9. device according to claim 6, it is characterised in that first determining module, including：
Detection sub-module, for detecting in the daily record being locally stored with the presence or absence of the daily record for including default mark；
Second determination sub-module, in the presence of being in the testing result of the detection sub-module, according to comprising described
The tracking key recorded in the daily record of default mark, determines target following key.
10. the device according to claim any one of 6-9, it is characterised in that the locating module, including：
3rd determination sub-module, for determining the corresponding alarm time of warning information described in the target journaling；
Submodule is positioned, for the corresponding server selection of the earliest daily record of alarm time in the target journaling into event to occur
Server where the service of barrier.
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 true CN107168845A (en) | 2017-09-15 |
| CN107168845B 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) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108768752A (en) * | 2018-06-25 | 2018-11-06 | 华为技术有限公司 | fault locating method, device and system |
| CN109687994A (en) * | 2018-11-30 | 2019-04-26 | 北京奇艺世纪科技有限公司 | A kind of message treatment method, system, device and equipment |
| CN110048899A (en) * | 2019-05-29 | 2019-07-23 | 北京奇艺世纪科技有限公司 | A kind of log detection method, device, terminal and server |
| CN110442498A (en) * | 2019-06-28 | 2019-11-12 | 平安科技（深圳）有限公司 | Localization method, device, storage medium and the computer equipment of abnormal data node |
| 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 |
Citations (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 |
| CN106254145A (en) * | 2016-09-06 | 2016-12-21 | 腾讯科技（深圳）有限公司 | network request tracking processing method and device |
-
2017
- 2017-03-31 CN CN201710207391.8A patent/CN107168845B/en active Active
Patent Citations (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 |
| CN106254145A (en) * | 2016-09-06 | 2016-12-21 | 腾讯科技（深圳）有限公司 | network request tracking processing method and device |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108768752A (en) * | 2018-06-25 | 2018-11-06 | 华为技术有限公司 | fault locating method, device and system |
| 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 |
| CN110048899A (en) * | 2019-05-29 | 2019-07-23 | 北京奇艺世纪科技有限公司 | A kind of log detection method, device, terminal and server |
| CN110048899B (en) * | 2019-05-29 | 2022-03-04 | 北京奇艺世纪科技有限公司 | Log detection method and device, terminal and server |
| CN110442498A (en) * | 2019-06-28 | 2019-11-12 | 平安科技（深圳）有限公司 | Localization method, device, storage medium and the computer equipment of abnormal data node |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107168845B (en) | 2020-12-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107168845A (en) | A kind of Fault Locating Method and device | |
| CN107438079B (en) | Method for detecting unknown abnormal behaviors of website | |
| US11218497B2 (en) | Reporting behavior anomalies | |
| US8504679B2 (en) | Methods, systems and computer program products for managing execution of information technology (IT) processes | |
| CN110245035A (en) | A kind of link trace method and device | |
| CN107087001B (en) | distributed internet important address space retrieval system | |
| CN107769963B (en) | A kind of content distributing network Fault Locating Method and device | |
| CN104468860B (en) | The recognition methods of domain name resolution server danger and device | |
| US8788958B2 (en) | Modeling, monitoring, and analysis of computer services | |
| CN106571960A (en) | Log collection and management system and log collection and management method | |
| CN104993953A (en) | Method for detecting network service state and device detecting network service state | |
| US8141151B2 (en) | Non-intrusive monitoring of services in a service-oriented architecture | |
| CN107181639A (en) | The monitoring method and device of a kind of communications status | |
| CN104636437B (en) | A kind of processing method and processing device of event notification method, monitor | |
| CN103095693B (en) | The method of location database access user's host information and device | |
| US11362912B2 (en) | Support ticket platform for improving network infrastructures | |
| CN108173678B (en) | Client data sending method, client connection abnormity display method and device | |
| CN108063833B (en) | HTTP DNS analysis message processing method and device | |
| CN109359250A (en) | Uniform resource locator processing method, device, server and readable storage medium storing program for executing | |
| CN1963780A (en) | Monotoring device, monotiring method, and monotoring system | |
| JP2011034507A (en) | Behavior history collection device, and behavior history collecting method and program | |
| CN108471359A (en) | A kind of website visiting abnormality monitoring method, device and medium | |
| CN108847952A (en) | The processing method of request link context, apparatus and system | |
| CN103246726A (en) | Method, device and system for searching network information | |
| CN1426555A (en) | Method for monitoring availability of messaging and VOIP network |
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 |