CN109640127A - The Fault Locating Method and device of content distributing network - Google Patents
The Fault Locating Method and device of content distributing network Download PDFInfo
- Publication number
- CN109640127A CN109640127A CN201811648385.7A CN201811648385A CN109640127A CN 109640127 A CN109640127 A CN 109640127A CN 201811648385 A CN201811648385 A CN 201811648385A CN 109640127 A CN109640127 A CN 109640127A
- Authority
- CN
- China
- Prior art keywords
- time
- failure
- log
- occurs
- fault
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/24—Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
- H04N21/2404—Monitoring of server processing errors or hardware failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
- H04N21/4425—Monitoring of client processing errors or hardware failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
- H04N21/6473—Monitoring network processes errors
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
Abstract
This application discloses the Fault Locating Methods of CDN a kind of, it include: the log for obtaining CDN server, the log includes response time and time source information of CDN server, wherein the response time of CDN server includes processing request time, reads document time and written document time；The processing request time in log is read, based on processing request time determines whether that CDN server performance fault occurs；The reading document time and time source information in log are read, with source information is returned determines whether that disk input and output failure or time source failure occurs based on document time is read；The written document time in log is read, determines whether that client performance failure or network failure occurs based on the written document time.Based on Fault Locating Method disclosed in the present application, when there is the excessively slow problem of speed of download, the failure for leading to the problem can be accurately located.The fault locator of CDN is also disclosed in the application.
Description
Technical field
The application belongs to the Fault Locating Method and device of network communication technology field more particularly to content distributing network.
Background technique
CDN (Content Delivery Network, content distributing network) can avoid having on internet as far as possible can
The bottleneck and link that can influence data transmission bauds and stability, make content transmission faster, it is more stable.
When user requests video content or other content to CDN, CDN scheduler is according to the relevant information of user
User selects most suitable CDN server to provide download service.In actual moving process, user downloads number from CDN server
According to will appear the excessively slow problem of speed of download, which may be caused by various faults, only accurately to leading to the problem
Failure is positioned, and could targetedly be improved, to provide quality services for user.
Therefore, when user the excessively slow problem of speed of download occurs from CDN server downloading data, how to be accurately located
The failure for leading to the problem is that those skilled in the art are urgently to be resolved.
Summary of the invention
In view of this, a kind of Fault Locating Method and device for being designed to provide CDN of the application, so as under appearance
When carrying the excessively slow problem of speed, the failure for leading to the problem can be accurately located.
To achieve the above object, the application provides the following technical solutions:
A kind of Fault Locating Method of content distributing network, which comprises
The log of content distribution network CDN service device is obtained, the log includes response time and the Hui Yuan of CDN server
Information, wherein described time source information is used to indicate the CDN server and whether occurs Hui Yuan, when the response of the CDN server
Between include processing request time, read document time and written document time；
The processing request time in the log is read, determines whether that CDN service occurs based on the processing request time
Device performance fault；
It reads the reading document time in the log and returns source information, be based on the reading document time and described time source information
Determine whether that disk input and output failure occurs or returns source failure；
The written document time in the log is read, determines whether that client performance event occurs based on the written document time
Barrier or network failure.
Optionally, described to determine whether that CDN clothes occur based on the processing request time in above-mentioned Fault Locating Method
Business device performance fault, comprising:
Compare the processing request time and first time threshold；
In the case where the processing request time is greater than or equal to first time threshold, determines and CDN server occurs
It can failure.
Optionally, described to be determined based on the reading document time and described time source information in above-mentioned Fault Locating Method
Disk input and output failure whether occurs or returns source failure, comprising:
Hui Yuan does not occur in described time source information characterization, and the document time of reading is greater than or equal to second time threshold
In the case of, it determines and disk input and output failure occurs；
In the case where Hui Yuan occurs for described time source information characterization and time source speed is less than or equal to First Speed threshold value,
Source failure occurs back for determination.
Optionally, described to determine whether that client occurs based on the written document time in above-mentioned Fault Locating Method
Performance fault or network failure, comprising:
The speed of download of client is calculated according to transmission total bytes and the written document time；
In the case where the speed of download of the client is less than or equal to second speed threshold value, determines and client occurs
It can failure or network failure.
Optionally, the log further includes HTTP status code, in above-mentioned Fault Locating Method, further includes:
The HTTP status code in the log is extracted, in the case where the HTTP status code exception, determination is configured
Failure or application layer failure.
On the other hand, the application also provides a kind of fault locator of content distributing network, comprising:
Log acquisition unit, for obtaining the log of content distribution network CDN service device, the log includes CDN service
The response time of device and time source information, wherein described time source information is used to indicate whether the CDN server occurs Hui Yuan, institute
The response time for stating CDN server includes processing request time, reads document time and written document time；
Fisrt fault analytical unit, for reading the processing request time in the log, when based on processing request
Between determine whether occur CDN server performance fault；
Second accident analysis unit is based on the reading for reading the reading document time in the log and returning source information
Document time and described time source information determine whether that disk input and output failure occurs or return source failure；
Third accident analysis unit, it is true based on the written document time for reading the written document time in the log
It is fixed that client performance failure or network failure whether occurs.
Optionally, in above-mentioned fault locator, the Fisrt fault analytical unit is specifically used for:
Compare the processing request time and first time threshold, when the processing request time is greater than or equal to first
Between in the case where threshold value, determine and CDN server performance fault occur.
Optionally, in above-mentioned fault locator, the second accident analysis unit is specifically used for:
Hui Yuan does not occur in described time source information characterization, and the document time of reading is greater than or equal to second time threshold
In the case of, it determines and disk input and output failure occurs；Hui Yuan occurs in described time source information characterization, and returns source speed and is less than or waits
In the case where First Speed threshold value, source failure occurs back for determination.
Optionally, in above-mentioned fault locator, the third accident analysis unit is specifically used for:
The speed of download of client is calculated according to transmission total bytes and the written document time；Under the client
Speed is carried less than or equal in the case where second speed threshold value, determines and client performance failure or network failure occurs.
Optionally, the log further includes HTTP status code, in above-mentioned fault locator, further includes:
4th accident analysis unit, it is abnormal in the HTTP status code for extracting the HTTP status code in the log
In the case where, it determines and config failure or application layer failure occurs.
It can be seen that the application's has the beneficial effect that
The response time of CDN server is split as processing and asked by the Fault Locating Method and device of CDN disclosed in the present application
Seeking time reads document time and written document time, and each user is requested, and CDN server records above-mentioned thin in log
The temporal information of granularity.When needing to carry out fault location to CDN, the log of CDN server is read, reading place from the log
Request time is managed, document time is read, returns source information and written document time, determines whether that CDN clothes occur based on processing request time
Business device performance fault determines whether that disk input and output failure or time source event occurs based on reading document time and time source information
Barrier determines whether that client performance failure or network failure occurs based on the written document time, to be accurately located the event of CDN
Barrier.
Detailed description of the invention
In order to illustrate the technical solutions in the embodiments of the present application or in the prior art more clearly, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is the application
Some embodiments for those of ordinary skill in the art without creative efforts, can also basis
These attached drawings obtain other attached drawings.
Fig. 1 is a kind of flow chart of the Fault Locating Method of CDN disclosed in the present application；
Fig. 2 is the composition of the response time of the CDN server disclosed in the present application in the case where Hui Yuan occurs for CDN server
Schematic diagram；
Fig. 3 is the flow chart of the Fault Locating Method of another kind CDN disclosed in the present application；
Fig. 4 is the flow chart of the Fault Locating Method of another CDN disclosed in the present application；
Fig. 5 is a kind of structural schematic diagram of the fault locator of CDN disclosed in the present application；
Fig. 6 is the structural schematic diagram of the fault locator of another CDN disclosed in the present application.
Specific embodiment
The application discloses the Fault Locating Method and fault locator of a kind of CDN, so as to speed of download occur excessively slow
The problem of when, the failure for leading to the problem can be accurately located.
To keep the purposes, technical schemes and advantages of the embodiment of the present application clearer, below in conjunction with the embodiment of the present application
In attached drawing, the technical scheme in the embodiment of the application is clearly and completely described, it is clear that described embodiment is
Some embodiments of the present application, instead of all the embodiments.Based on the embodiment in the application, those of ordinary skill in the art
Every other embodiment obtained without making creative work, shall fall in the protection scope of this application.
Referring to Fig. 1, Fig. 1 is a kind of flow chart of the Fault Locating Method of CDN disclosed in the present application.The Fault Locating Method
Include:
Step S101: the log of CDN server is obtained.
Wherein, the log of CDN server includes response time and time source information of CDN server.
In the prior art, when the speed of download to user counts, the formula of use are as follows: speed of download=transmission
Total bytes/response time.Wherein, the response time in the formula are as follows: receive first that user requests from CDN server
Time of the byte until all bytes are sent to client.
In this application, when the response time of CDN server includes processing request time, reads document time and written document
Between.That is, being split as processing request time by the response time of CDN server in the application, reading document time and writing text
The part time.
The processing request time of CDN server refers to: from CDN server receive user request first character section to
CDN server responds user and requests to carry out the time before file polling.Time loss of the CDN server in this stage is to solve
User's request is analysed, security verification is carried out, carries out logic flow verifying, extracting parameter, carries out Resource orientation operation.CDN service
Device is mainly related to the CPU of CDN server, internal memory performance and software processing capability in the time loss in this stage.
The reading document time of CDN server refers to the process of: CDN server obtains the time consumed by file from disk.
The characteristics of according to practical business, the reading document time of CDN server are divided into two kinds of situations:
The first situation, user requests the file of downloading to be stored in local disk, correspondingly, the reading file of CDN server
Time is: requesting the file of downloading to read in the time consumed by memory from local disk by user, when can be described as local reading file
Between.Time loss of the CDN server in this stage be magnetic disc i/o read operation performance (time is generally extremely short, be Millisecond
Not).
Second situation: user requests the file of downloading to be not stored in local disk, and CDN server needs to carry out Hui Yuancao
Work, that is, CDN server needs to request the file of downloading from other CDN servers downloading user, when can be described as back source reading file
Between.Time loss of the CDN server in this stage is back source procedure.
The written document time of CDN server refers to: CDN server sends the file to the time consumed by client.CDN
Server can call write function by the file buffer area recurrent wrIting socket in batches, be sent out file by the buffer area socket
Client is given, time loss of the CDN server in this stage mainly receives the speed and Network status of data with client
It is related.
The source information of returning of CDN server is used to indicate whether CDN server occurs Hui Yuan.
What needs to be explained here is that in the case where user requests the file of downloading to be stored in local disk, i.e. CDN service
In the case that Hui Yuan does not occur for device, document time+written document is read in response time=processing request time+local of CDN server
Time；In the case where user requests the file of downloading to be not stored in local disk, i.e., there is a situation where go back to source for CDN server
Under, the composition of the response time of CDN server is as shown in Figure 2.
Step S102: reading the processing request time in log, based on processing request time determines whether that CDN service occurs
Device performance fault.
The processing request time of CDN server is mainly related to the performance of CDN server, therefore, based on CDN server
Processing request time is able to determine whether that CDN server performance fault occurs.
Step S103: reading the reading document time and time source information in log, true based on reading document time and time source information
It is fixed that disk input and output failure whether occurs or returns source failure.
In the case that user requests the file of downloading to be stored in local disk, i.e., there is a situation where go back to source for CDN server
Under, the reading document time of CDN server is mainly related to the read operation performance of magnetic disc i/o, and user requests the file of downloading not deposited
Storage in the case where local disk, that is, CDN server occur Hui Yuan in the case where, the reading document time of CDN server mainly with
It is related to return source procedure, therefore, returning source information and reading document time based on CDN server is able to determine whether that generation disk is defeated
Enter to export failure or returns source failure.
Step S104: reading the written document time in log, determines whether that client performance occurs based on the written document time
Failure or network failure.
The written document time of CDN server is mainly related to the speed of client reception data and Network status, therefore,
The written document time based on CDN server is able to determine whether that client performance failure or network failure occurs.
In the Fault Locating Method of CDN disclosed in the present application, when the response time of CDN server is split as processing request
Between, read document time and written document time, each user is requested, CDN server records above-mentioned fine granularity in log
Temporal information.When needing to carry out fault location to CDN, the log of CDN server is read, reading process is asked from the log
Seeking time reads document time, returns source information and written document time, based on processing request time determines whether that CDN server occurs
Performance fault with source information is returned determines whether that disk input and output failure or time source failure, base occurs based on document time is read
Determine whether that client performance failure or network failure occurs in the written document time, to be accurately located the failure of CDN.
It should be noted that in specific implementation, step S102, the execution of step S103 and step S104 are sequentially and unlimited
It is set to shown in Fig. 1, step S102, the execution sequence between step S103 and step S104 can be arbitrary.
For example, after step slol, successively executing step S103, step S104 and step S102.Such as: in step
After S101, multiple steps for being performed simultaneously in step S102, step S103 and step S104.That is, in step S101
Later, malfunction elimination item by item is carried out to CDN according to predefined sequence, to comprehensively determine the failure that CDN occurs.
Optionally, in some cases, certain steps step S102, in step S103 and step S104 can not be held
Row.Such as: after step slol, step S102 is first carried out, if it is determined that CDN server performance fault occurs, then can
No longer to execute step S103 and step S104.
As a preferred embodiment, the log of CDN server further includes HTTP status code.
Correspondingly, on the basis of Fault Locating Method shown in Fig. 1, it can be with setting steps S105: extracting in log
HTTP status code determines and config failure or application layer failure occurs in the case where HTTP status code exception.
In implementation, if the first place of HTTP status code is 4 or 5, show that HTTP status code is abnormal, then it is determined that matching
Set failure or application layer failure.That is, if HTTP status code is 4XY or 5XY (wherein X and Y be 0~9 between
Number), so that it may it determines and config failure or application layer failure occurs.Such as HTTP status code is 404,505 etc., so that it may really
Surely config failure or application layer failure occurs.
It should be noted that in specific implementation, the step S102, execution of step S103, step S104 and step S105
Sequence is not limited to shown in Fig. 3, and step S102, the execution sequence between step S103, step S104 and step S105 can be with
It is arbitrary.That is, after step slol, malfunction elimination item by item is carried out to CDN according to predefined sequence, thus entirely
Determine to face the failure that CDN occurs.
The CDN Fault Locating Method disclosed above to the application is described in more details below.
As an example, step S102 determines whether that CDN server performance fault, packet occurs based on processing request time
It includes:
Compare processing request time and first time threshold.
In the case where handling request time more than or equal to first time threshold, determines and the event of CDN server performance occurs
Barrier.
If the processing request time of CDN server is greater than or equal to preset first time threshold, show CDN server
Performance it is poor, it is thus determined that occur CDN server performance fault.In implementation, which is configurable to 5ms.
As an example, step S103 is based on reading document time and return source information to determine whether that disk input and output occur
Failure returns source failure, comprising:
In the case where Hui Yuan does not occur for time source information characterization and reading document time is greater than or equal to second time threshold,
It determines and disk input and output failure occurs.
It is returning source information characterization generation Hui Yuan and is returning source speed less than or equal in the case where First Speed threshold value, determining
Source failure occurs back.
Determine whether CDN server occurs Hui Yuan according to source information is returned.
If Hui Yuan does not occur for CDN server, i.e. user requests the file of downloading to be stored in local disk, then comparing
The reading document time (specifically local to read document time) and second time threshold of CDN server, if the reading text of CDN server
The part time is greater than or equal to second time threshold, shows that the input and output performance of local disk is poor, determines and disk input occurs
Export failure.In implementation, which is configurable to 1ms.
If Hui Yuan occurs for CDN server, source speed is calculated back ,=returning source total bytes/returns wherein returning source speed
Source time shows back that source procedure goes wrong if returning source speed is less than or equal to preset First Speed threshold value, determines and occurs
Return source failure.
As an example, step S104 determines whether that client performance failure or network occurs based on the written document time
Failure, comprising:
The speed of download of client is calculated according to transmission total bytes and written document time.
In the case where the speed of download of client is less than or equal to second speed threshold value, determines and client performance event occurs
Barrier or network failure.
In technical solution disclosed in the present application, the step S102, sequence between step S103, step S104 and step S105
It can be arbitrary, one of them preferred scheme is illustrated below with reference to Fig. 4, comprising:
Step S401: the log of CDN server is read.
Step S402: HTTP status code is read from log, judges whether HTTP status code is normal, if HTTP status code
It is abnormal, S403 is thened follow the steps, if HTTP status code is normal, thens follow the steps S404.
Step S403: it determines and config failure or application layer failure occurs.
Step S404: reading the processing request time of CDN server from log, judges to handle whether request time is less than
First time threshold thens follow the steps S405 if processing request time is greater than or equal to first time threshold, if processing is asked
Seeking time is less than first time threshold, thens follow the steps S406.
Step S405: it determines and CDN server performance fault occurs.
Step S406: reading back source information from log, judges whether CDN server occurs Hui Yuan according to source information is returned,
In case of Hui Yuan, S407 is thened follow the steps, if Hui Yuan does not occur, thens follow the steps S412.
Step S407: calculating the speed of download of client, judges whether the speed of download of client is greater than second speed threshold
Value thens follow the steps S408, if the speed of download of client is small if the speed of download of client is greater than second speed threshold value
In or equal to second speed threshold value, S409 is thened follow the steps.
Step S408: it determines and non-downloading service failure occurs.
Step S409: calculate CDN server returns source speed, judges back whether source speed is greater than First Speed threshold value, such as
Fruit returns source speed and is less than or equal to First Speed threshold value, thens follow the steps S410, if returning source speed is greater than First Speed threshold value,
Then follow the steps S411.
Step S410: source failure occurs back for determination.
Step S411: it determines and client performance failure or network failure occurs.
Step S412: the reading document time (specially local to read document time) of CDN server, judgement are read from log
It reads whether document time is less than second time threshold, if reading document time is greater than or equal to second time threshold, executes step
Rapid S413 thens follow the steps S414 if reading document time is less than second time threshold.
Step S413: it determines and disk input and output failure occurs.
Step S414: calculating the speed of download of client, judges whether the speed of download of client is greater than second speed threshold
Value thens follow the steps S408, if the speed of download of client is small if the speed of download of client is greater than second speed threshold value
In or equal to second speed threshold value, S411 is thened follow the steps.
The application Fault Locating Method of CDN disclosed above, correspondingly, the fault location dress of CDN is also disclosed in the application
It sets.Hereinafter with regard to fault locator description with above in connection with Fault Locating Method description, can be with cross-reference.
Referring to Fig. 5, Fig. 5 is a kind of structural schematic diagram of the fault locator of CDN disclosed in the present application.The fault location
Device includes log acquisition unit 100, Fisrt fault analytical unit 200, the second accident analysis unit 300 and third accident analysis
Unit 400.
Wherein:
Log acquisition unit 100, for obtaining the log of content distribution network CDN service device.Log includes CDN server
Response time and return source information, wherein the response time of CDN server includes processing request time, reads document time and to write
Document time.
Fisrt fault analytical unit 200 is determined for reading the processing request time in log based on processing request time
Whether CDN server performance fault is occurred.
Second accident analysis unit 300, for reading the reading document time in log and returning source information, when based on reading file
Between and return source information determine whether occur disk input and output failure or return source failure.
Third accident analysis unit 400 is determined whether for reading the written document time in log based on the written document time
Client performance failure or network failure occurs.
The fault locator of CDN disclosed in the present application, when the response time of CDN server is split as processing request
Between, read document time and written document time, each user is requested, CDN server records above-mentioned fine granularity in log
Temporal information.When needing to carry out fault location to CDN, the log of CDN server is read, reading process is asked from the log
Seeking time reads document time, returns source information and written document time, based on processing request time determines whether that CDN server occurs
Performance fault with source information is returned determines whether that disk input and output failure or time source failure, base occurs based on document time is read
Determine whether that client performance failure or network failure occurs in the written document time, to be accurately located the failure of CDN.
As a preferred embodiment, the log of CDN server further includes HTTP status code.
Correspondingly, the 4th accident analysis unit 500 can also be arranged, such as on the basis of Fault Locating Method shown in Fig. 1
Shown in Fig. 6.Wherein, the 4th accident analysis unit 500 is used for: the HTTP status code in log is extracted, it is abnormal in HTTP status code
In the case where, it determines and config failure or application layer failure occurs.
As an example, in the fault locator of the application CDN disclosed above, Fisrt fault analytical unit
200 are specifically used for:
Compare processing request time and first time threshold, is greater than or equal to first time threshold in processing request time
In the case of, it determines and CDN server performance fault occurs.
As an example, in the fault locator of the application CDN disclosed above, the second accident analysis unit
300 are specifically used for:
In the case where Hui Yuan does not occur for time source information characterization and reading document time is greater than or equal to second time threshold,
It determines and disk input and output failure occurs；Hui Yuan occurs returning source information characterization, and returns source speed and is less than or equal to First Speed
In the case where threshold value, source failure occurs back for determination.
As an example, in the fault locator of the application CDN disclosed above, third accident analysis unit
400 are specifically used for:
The speed of download of client is calculated according to transmission total bytes and written document time；It is small in the speed of download of client
In or in the case where being equal to second speed threshold value, determine and client performance failure or network failure occur.
It should be noted that the Fault Locating Method of the application CDN disclosed above, executing subject can be CDN service
Device or CDN scheduler.The fault locator of the application CDN disclosed above, can be arranged in CDN server or CDN
In scheduler.
Finally, it is to be noted that, herein, relational terms such as first and second and the like be used merely to by
One entity or operation are distinguished with another entity or operation, without necessarily requiring or implying these entities or operation
Between there are any actual relationship or orders.Moreover, the terms "include", "comprise" or its any other variant meaning
Covering non-exclusive inclusion, so that the process, method, article or equipment for including a series of elements not only includes that
A little elements, but also including other elements that are not explicitly listed, or further include for this process, method, article or
The intrinsic element of equipment.In the absence of more restrictions, the element limited by sentence "including a ...", is not arranged
Except there is also other identical elements in the process, method, article or apparatus that includes the element.
Each embodiment in this specification is described in a progressive manner, the highlights of each of the examples are with other
The difference of embodiment, the same or similar parts in each embodiment may refer to each other.For failure disclosed in embodiment
For positioning device, since it is corresponding with Fault Locating Method disclosed in embodiment, so be described relatively simple, correlation
Place is referring to method part illustration.
The foregoing description of the disclosed embodiments makes professional and technical personnel in the field can be realized or use the application.
Various modifications to these embodiments will be readily apparent to those skilled in the art, as defined herein
General Principle can be realized in other embodiments without departing from the spirit or scope of the application.Therefore, the application
It is not intended to be limited to the embodiments shown herein, and is to fit to and the principles and novel features disclosed herein phase one
The widest scope of cause.
Claims (10)
1. a kind of Fault Locating Method of content distributing network, which is characterized in that the described method includes:
The log of content distribution network CDN service device is obtained, the log includes response time and the Hui Yuanxin of CDN server
Breath, wherein described time source information is used to indicate whether the CDN server occurs Hui Yuan, the response time of the CDN server
Including processing request time, read document time and written document time；
The processing request time in the log is read, determines whether that CDN server occurs based on the processing request time
It can failure；
It reads the reading document time in the log and returns source information, determined based on the reading document time and described time source information
Disk input and output failure whether occurs or returns source failure；
Read the written document time in the log, based on the written document time determine whether occur client performance failure or
Person's network failure.
2. Fault Locating Method according to claim 1, which is characterized in that described to be determined based on the processing request time
Whether CDN server performance fault is occurred, comprising:
Compare the processing request time and first time threshold；
In the case where the processing request time is greater than or equal to first time threshold, determines and the event of CDN server performance occurs
Barrier.
3. Fault Locating Method according to claim 1, which is characterized in that described based on the reading document time and described
Source information is returned to determine whether that disk input and output failure occurs or return source failure, comprising:
Hui Yuan does not occur in described time source information characterization, and the case where the readings document time is more than or equal to second time threshold
Under, it determines and disk input and output failure occurs；
Hui Yuan occurs in described time source information characterization and returns source speed less than or equal in the case where First Speed threshold value, determines
Source failure occurs back.
4. Fault Locating Method according to claim 1, which is characterized in that described to be based on the written document time determination
No generation client performance failure or network failure, comprising:
The speed of download of client is calculated according to transmission total bytes and the written document time；
In the case where the speed of download of the client is less than or equal to second speed threshold value, determines and client performance event occurs
Barrier or network failure.
5. Fault Locating Method according to claim 1, which is characterized in that the log further includes HTTP status code, institute
State Fault Locating Method further include:
The HTTP status code in the log is extracted, in the case where the HTTP status code exception, determines and config failure occurs
Or application layer failure.
6. a kind of fault locator of content distributing network characterized by comprising
Log acquisition unit, for obtaining the log of content distribution network CDN service device, the log includes CDN server
Response time and time source information, wherein described time source information is used to indicate whether the CDN server occurs Hui Yuan, the CDN
The response time of server includes processing request time, reads document time and written document time；
Fisrt fault analytical unit, it is true based on the processing request time for reading the processing request time in the log
It is fixed that CDN server performance fault whether occurs；
Second accident analysis unit is based on the reading file for reading the reading document time in the log and returning source information
Time and described time source information determine whether that disk input and output failure occurs or return source failure；
Third accident analysis unit is based on the written document time determination for reading the written document time in the log
No generation client performance failure or network failure.
7. fault locator according to claim 6, which is characterized in that the Fisrt fault analytical unit is specifically used
In:
Compare the processing request time and first time threshold, is greater than or equal to first time threshold in the processing request time
In the case where value, determines and CDN server performance fault occurs.
8. fault locator according to claim 6, which is characterized in that the second accident analysis unit is specifically used
In:
Hui Yuan does not occur in described time source information characterization, and the case where the readings document time is more than or equal to second time threshold
Under, it determines and disk input and output failure occurs；Hui Yuan occurs in described time source information characterization, and returns source speed and is less than or equal to the
In the case where one threshold speed, source failure occurs back for determination.
9. fault locator according to claim 6, which is characterized in that the third accident analysis unit is specifically used
In:
The speed of download of client is calculated according to transmission total bytes and the written document time；In the downloading speed of the client
In the case that degree is less than or equal to second speed threshold value, determines and client performance failure or network failure occurs.
10. fault locator according to claim 6, which is characterized in that the log further includes HTTP status code, institute
State fault locator further include:
4th accident analysis unit, for extracting the HTTP status code in the log, in the feelings of the HTTP status code exception
Under condition, determines and config failure or application layer failure occurs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811648385.7A CN109640127A (en) | 2018-12-30 | 2018-12-30 | The Fault Locating Method and device of content distributing network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811648385.7A CN109640127A (en) | 2018-12-30 | 2018-12-30 | The Fault Locating Method and device of content distributing network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109640127A true CN109640127A (en) | 2019-04-16 |
Family
ID=66055257
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811648385.7A Pending CN109640127A (en) | 2018-12-30 | 2018-12-30 | The Fault Locating Method and device of content distributing network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109640127A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110912926A (en) * | 2019-12-04 | 2020-03-24 | 湖南快乐阳光互动娱乐传媒有限公司 | Data resource back-source method and device |
| CN112217672A (en) * | 2020-09-30 | 2021-01-12 | 安徽极玩云科技有限公司 | Service processing system for CDN platform |
Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102624584A (en) * | 2012-03-01 | 2012-08-01 | 中兴通讯股份有限公司 | Link detection method and link detection device |
| CN102647299A (en) * | 2012-04-24 | 2012-08-22 | 网宿科技股份有限公司 | Hierarchical alarm analysis method and hierarchical alarm analysis system based on content delivery network |
| CN103974139A (en) * | 2014-05-20 | 2014-08-06 | 北京速能数码网络技术有限公司 | Method and device for detecting network faults of terminal and system |
| US20140379908A1 (en) * | 2010-12-21 | 2014-12-25 | Guest Tek Interactive Entertainment Ltd. | Client in distributed computing system that monitors service time reported by server in order to detect performance problems and automatically issue alerts |
| CN104917651A (en) * | 2015-06-09 | 2015-09-16 | 北京齐尔布莱特科技有限公司 | Method and device for monitoring network anomalies |
| CN105049503A (en) * | 2015-07-07 | 2015-11-11 | 深信服网络科技（深圳）有限公司 | Server dispatching method and load balancing device |
| CN105721953A (en) * | 2016-04-28 | 2016-06-29 | 乐视控股（北京）有限公司 | Stream media video start playing abnormity analyzing method and system |
| CN105978703A (en) * | 2015-08-12 | 2016-09-28 | 乐视云计算有限公司 | Video fault feedback method, client and server |
| CN106130786A (en) * | 2016-07-26 | 2016-11-16 | 腾讯科技（深圳）有限公司 | The detection method of a kind of network failure and device |
| CN106411659A (en) * | 2016-11-29 | 2017-02-15 | 福建中金在线信息科技有限公司 | Business data monitoring method and apparatus |
| CN106446300A (en) * | 2016-12-01 | 2017-02-22 | 郑州云海信息技术有限公司 | Transaction processing method and system based on shared storage pool |
| CN106911511A (en) * | 2017-03-10 | 2017-06-30 | 网宿科技股份有限公司 | The means of defence and system of a kind of CDN client source station |
| CN107493183A (en) * | 2016-06-13 | 2017-12-19 | 中国移动通信集团北京有限公司 | A kind of Fault Locating Method and device |
| CN107797893A (en) * | 2016-09-07 | 2018-03-13 | 华为数字技术（成都）有限公司 | A kind of method and apparatus for the duration for calculating hard disk processing read write command |
| CN107911240A (en) * | 2017-11-14 | 2018-04-13 | 北京知道创宇信息技术有限公司 | A kind of fault detection method and device |
| CN108011752A (en) * | 2017-11-21 | 2018-05-08 | 江苏天联信息科技发展有限公司 | Fault locating analysis method and device, computer-readable recording medium |
| CN108199914A (en) * | 2017-12-27 | 2018-06-22 | 杭州迪普科技股份有限公司 | Server-side condition detection method and device |
| CN108234207A (en) * | 2017-12-29 | 2018-06-29 | 北京奇虎科技有限公司 | A kind of Fault Locating Method and device based on content distributing network CDN |
| CN108737469A (en) * | 2017-04-20 | 2018-11-02 | 北京雷石天地电子技术有限公司 | A kind of method and apparatus hard disk praameter monitoring and fed back |
| CN108880847A (en) * | 2017-05-16 | 2018-11-23 | 北京微影时代科技有限公司 | A kind of method and device of positioning failure |
| CN109062723A (en) * | 2018-08-22 | 2018-12-21 | 郑州云海信息技术有限公司 | The treating method and apparatus of server failure |
-
2018
- 2018-12-30 CN CN201811648385.7A patent/CN109640127A/en active Pending
Patent Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140379908A1 (en) * | 2010-12-21 | 2014-12-25 | Guest Tek Interactive Entertainment Ltd. | Client in distributed computing system that monitors service time reported by server in order to detect performance problems and automatically issue alerts |
| CN102624584A (en) * | 2012-03-01 | 2012-08-01 | 中兴通讯股份有限公司 | Link detection method and link detection device |
| CN102647299A (en) * | 2012-04-24 | 2012-08-22 | 网宿科技股份有限公司 | Hierarchical alarm analysis method and hierarchical alarm analysis system based on content delivery network |
| CN103974139A (en) * | 2014-05-20 | 2014-08-06 | 北京速能数码网络技术有限公司 | Method and device for detecting network faults of terminal and system |
| CN104917651A (en) * | 2015-06-09 | 2015-09-16 | 北京齐尔布莱特科技有限公司 | Method and device for monitoring network anomalies |
| CN105049503A (en) * | 2015-07-07 | 2015-11-11 | 深信服网络科技（深圳）有限公司 | Server dispatching method and load balancing device |
| CN105978703A (en) * | 2015-08-12 | 2016-09-28 | 乐视云计算有限公司 | Video fault feedback method, client and server |
| CN105721953A (en) * | 2016-04-28 | 2016-06-29 | 乐视控股（北京）有限公司 | Stream media video start playing abnormity analyzing method and system |
| CN107493183A (en) * | 2016-06-13 | 2017-12-19 | 中国移动通信集团北京有限公司 | A kind of Fault Locating Method and device |
| CN106130786A (en) * | 2016-07-26 | 2016-11-16 | 腾讯科技（深圳）有限公司 | The detection method of a kind of network failure and device |
| CN107797893A (en) * | 2016-09-07 | 2018-03-13 | 华为数字技术（成都）有限公司 | A kind of method and apparatus for the duration for calculating hard disk processing read write command |
| CN106411659A (en) * | 2016-11-29 | 2017-02-15 | 福建中金在线信息科技有限公司 | Business data monitoring method and apparatus |
| CN106446300A (en) * | 2016-12-01 | 2017-02-22 | 郑州云海信息技术有限公司 | Transaction processing method and system based on shared storage pool |
| CN106911511A (en) * | 2017-03-10 | 2017-06-30 | 网宿科技股份有限公司 | The means of defence and system of a kind of CDN client source station |
| CN108737469A (en) * | 2017-04-20 | 2018-11-02 | 北京雷石天地电子技术有限公司 | A kind of method and apparatus hard disk praameter monitoring and fed back |
| CN108880847A (en) * | 2017-05-16 | 2018-11-23 | 北京微影时代科技有限公司 | A kind of method and device of positioning failure |
| CN107911240A (en) * | 2017-11-14 | 2018-04-13 | 北京知道创宇信息技术有限公司 | A kind of fault detection method and device |
| CN108011752A (en) * | 2017-11-21 | 2018-05-08 | 江苏天联信息科技发展有限公司 | Fault locating analysis method and device, computer-readable recording medium |
| CN108199914A (en) * | 2017-12-27 | 2018-06-22 | 杭州迪普科技股份有限公司 | Server-side condition detection method and device |
| CN108234207A (en) * | 2017-12-29 | 2018-06-29 | 北京奇虎科技有限公司 | A kind of Fault Locating Method and device based on content distributing network CDN |
| CN109062723A (en) * | 2018-08-22 | 2018-12-21 | 郑州云海信息技术有限公司 | The treating method and apparatus of server failure |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110912926A (en) * | 2019-12-04 | 2020-03-24 | 湖南快乐阳光互动娱乐传媒有限公司 | Data resource back-source method and device |
| CN112217672A (en) * | 2020-09-30 | 2021-01-12 | 安徽极玩云科技有限公司 | Service processing system for CDN platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10515000B2 (en) | Systems and methods for performance testing cloud applications from multiple different geographic locations | |
| US7685270B1 (en) | Method and apparatus for measuring latency in web services | |
| US9104572B1 (en) | Automated root cause analysis | |
| EP1386240B1 (en) | Synthetic transaction monitor | |
| US9811445B2 (en) | Methods and systems for the use of synthetic users to performance test cloud applications | |
| US10116534B2 (en) | Systems and methods for WebSphere MQ performance metrics analysis | |
| US20060085420A1 (en) | Method and apparatus for monitoring real users experience with a website | |
| US20070271375A1 (en) | Method and apparatus for monitoring real users experience with a website capable of using service providers and network appliances | |
| US20150170070A1 (en) | Method, apparatus, and system for monitoring website | |
| US20040039550A1 (en) | System load testing coordination over a network | |
| CN109309596B (en) | Pressure testing method and device and server | |
| US8589537B2 (en) | Methods and computer program products for aggregating network application performance metrics by process pool | |
| CN108696399B (en) | Business service test method and device | |
| US10216608B1 (en) | Load testing with automated service dependency discovery | |
| WO2017131774A1 (en) | Log event summarization for distributed server system | |
| CN104468399B (en) | Data transmission method and device and server | |
| Jayathilaka et al. | Detecting performance anomalies in cloud platform applications | |
| US9652488B2 (en) | Computer product, verification support method, and verification support apparatus | |
| CN107924345A (en) | Data storage area for the polymerization measurement result of measurement | |
| US20130060835A1 (en) | Techniques for gauging performance of services | |
| CN109640127A (en) | The Fault Locating Method and device of content distributing network | |
| CN113676372A (en) | Communication performance testing method, device and storage medium | |
| CN108924159A (en) | The verification method and device in a kind of message characteristic identification library | |
| US9378230B1 (en) | Ensuring availability of data in a set being uncorrelated over time | |
| CN105184559B (en) | A kind of payment system and method |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190416 |
|
| RJ01 | Rejection of invention patent application after publication |