CN110460487B - Service node monitoring method and system and service node - Google Patents
Service node monitoring method and system and service node Download PDFInfo
- Publication number
- CN110460487B CN110460487B CN201910555191.0A CN201910555191A CN110460487B CN 110460487 B CN110460487 B CN 110460487B CN 201910555191 A CN201910555191 A CN 201910555191A CN 110460487 B CN110460487 B CN 110460487B
- Authority
- CN
- China
- Prior art keywords
- url
- check
- information
- service node
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 77
- 238000000034 method Methods 0.000 title claims abstract description 65
- 238000012795 verification Methods 0.000 claims abstract description 143
- 238000012545 processing Methods 0.000 claims abstract description 66
- 238000007405 data analysis Methods 0.000 claims description 47
- 238000007726 management method Methods 0.000 claims description 23
- 230000008569 process Effects 0.000 claims description 16
- 238000004364 calculation method Methods 0.000 claims description 5
- 238000012423 maintenance Methods 0.000 description 16
- 230000006872 improvement Effects 0.000 description 11
- 230000000694 effects Effects 0.000 description 7
- 238000012384 transportation and delivery Methods 0.000 description 4
- 238000013024 troubleshooting Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention relates to the technical field of networks, and discloses a service node monitoring method and system and a service node. The monitoring method of the service node comprises the following steps: receiving check information sent by at least one service node; the check information comprises a URL and a check value corresponding to the URL; for each piece of verification information, acquiring a credible verification value corresponding to the URL in the verification information, and marking the verification information if the verification value corresponding to the URL in the verification information is inconsistent with the credible verification value corresponding to the URL; and processing the file in the service node which sends the marked check information. According to the invention, whether the files in the service nodes need to be processed can be judged according to the verification information sent by each service node, so that the automatic monitoring and processing of the files in the service nodes are realized, and the risk of file downloading failure of a user is reduced.
Description
Technical Field
The embodiment of the invention relates to the technical field of networks, in particular to a service node monitoring method and system and a service node.
Background
A Content Delivery Network (CDN) is a Content Delivery Network constructed on a Network, and users can obtain required Content nearby by using functional modules of load balancing, Content Delivery, scheduling and the like of a central platform by means of edge service nodes deployed in various places, so that Network congestion is reduced, and the access response speed and hit rate of the users are increased.
The inventor finds that at least the following problems exist in the prior art: at present, an edge service node in a CDN network can only provide a cache service for a user, and when problems such as hijacking tampering and a disk error occur, a cache error occurs, and a file with the cache error is returned to the user, which results in a failure of the user to download the file.
Disclosure of Invention
An object of embodiments of the present invention is to provide a method and a system for monitoring a service node, and a service node, which can determine whether a file in the service node needs to be processed according to check information sent by each service node, so as to implement automatic monitoring and processing of the file in the service node, and reduce a risk of failure in downloading the file by a user.
In order to solve the above technical problem, an embodiment of the present invention provides a monitoring method for a service node, which is applied to a monitoring system for a service node, and the method includes: receiving check information sent by at least one service node; the check information comprises a URL and a check value corresponding to the URL; for each piece of verification information, acquiring a credible verification value corresponding to the URL in the verification information, and marking the verification information if the verification value corresponding to the URL in the verification information is inconsistent with the credible verification value corresponding to the URL; and processing the file in the service node which sends the marked check information.
The embodiment of the invention also provides a monitoring method of the service node, which is applied to the service node and comprises the following steps: when an access request comprising a URL is received, generating verification information, wherein the verification information comprises a URL and a verification value corresponding to the URL; and sending the verification information to a monitoring system of the service node so that the monitoring system can acquire a trusty verification value corresponding to the URL in the verification information, if the verification value corresponding to the URL in the verification information is inconsistent with the trusty verification value corresponding to the URL, marking the verification information, and processing a file in the service node which sends the marked verification information.
The embodiment of the present invention further provides a monitoring system for a service node, including: the content management system comprises a storage component, a content management component and a data analysis component which is respectively connected with the storage component and the content management component; the storage component is used for receiving the check information sent by at least one service node; the check information comprises a URL and a check value corresponding to the URL; the data analysis component is used for acquiring a credible check value corresponding to the URL in the check information for each check information, and marking the check information if the check value corresponding to the URL in the check information is inconsistent with the credible check value corresponding to the URL; the content management component is used for processing files in the service node which sends the marked check information.
Compared with the prior art, the embodiment of the invention receives the check information which is sent by each service node and comprises the URL and the check value corresponding to the URL; for each received check message, acquiring a trusted check value corresponding to a URL in the check message, if the check value corresponding to the URL in the check message is inconsistent with the trusted check value corresponding to the URL, indicating that a file corresponding to the URL in the check message may have an error, marking the check message, and processing the file in the service node which sends the marked check message; whether the files in the service nodes need to be processed or not can be judged according to the verification information sent by each service node, so that the files in the service nodes are automatically monitored and processed, and the risk of file downloading failure of a user is reduced; and the automatic monitoring and processing of the files in the service node can be completed under the condition that the source station does not need to provide the check value corresponding to the URL.
In addition, acquiring a trusted verification value corresponding to the URL includes: judging whether the file corresponding to the URL in the verification information exceeds preset time or not; if the file corresponding to the URL in the verification information does not exceed the preset time, acquiring a trusted verification value corresponding to the locally cached URL; and if the file corresponding to the URL in the verification information exceeds the preset time, obtaining a credible verification value corresponding to the URL according to the file corresponding to the URL in the source station corresponding to the acquired URL. In this embodiment, whether the file corresponding to the URL in the verification information exceeds the preset time is determined, so that it is possible to avoid repeatedly acquiring the file corresponding to the URL from the source station and calculating the trusted verification value corresponding to the URL on the basis of ensuring the accuracy of the acquired trusted verification value corresponding to the URL, and performance consumption is reduced.
In addition, the verification information also comprises expiration information representing whether the file corresponding to the URL in the verification information exceeds the preset time; judging whether the file corresponding to the URL in the verification information exceeds the preset time, specifically: and judging whether the file corresponding to the URL exceeds the preset time or not according to the expiration information of the file corresponding to the URL in the verification information. The embodiment provides a specific implementation mode for judging whether the file corresponding to the URL exceeds the preset time according to the expiration information of the file corresponding to the URL in the verification information.
In addition, before processing the file in the service node sending the marked check information, the method further comprises the following steps: for each URL, determining whether the URL meets a preset condition according to the number of pieces of check information including the URL and the number of pieces of marked check information including the URL; processing the file in the service node sending the marked check information, specifically: and for each marked check information, if the URL in the check information meets the preset condition, processing the file in the service node sending the check information. In this embodiment, whether the URL satisfies the preset condition can be determined according to the number of the verification information including the URL and the number of the marked verification information including the URL, and it can be avoided that large-scale file processing of the service node is generated when the number of the marked verification information including a certain URL is too large, thereby avoiding causing large-scale source return downloading and further not affecting the service quality of the service node.
In addition, the preset condition is that a quotient of the number of the marked check information including the URL divided by the number of the check information including the URL is less than a preset duty threshold. The present embodiment provides a specific content of the preset condition.
In addition, processing the file in the service node sending the marked check information specifically includes: and for each marked check information, processing a file corresponding to the URL in the check information in the service node sending the check information. This embodiment provides a specific implementation of processing files in a service node that sends marked check information.
In addition, before generating the verification information, the method further includes: judging whether the file corresponding to the URL exceeds preset time or not; if the file corresponding to the URL does not exceed the preset time, acquiring a check value corresponding to the locally cached URL, and generating overdue information representing that the file corresponding to the URL does not exceed the preset time; if the file corresponding to the URL exceeds the preset time, obtaining a check value corresponding to the URL according to the file corresponding to the URL in the source station corresponding to the acquired URL, and generating overdue information representing that the file corresponding to the URL exceeds the preset time; the verification information also includes expiration information. In the embodiment, before the service node generates the verification information, whether the file corresponding to the URL exceeds the preset time is judged, so that repeated acquisition of the verification value corresponding to the URL can be avoided, and the performance consumption of the service node is reduced.
In addition, the service node is an edge node of the content distribution network; judging whether the file corresponding to the URL exceeds the preset time or not, including: judging whether the file corresponding to the locally cached URL exceeds preset time or not; if the file corresponding to the locally cached URL does not exceed the preset time, judging that the file corresponding to the URL does not exceed the preset time; if the file corresponding to the locally cached URL exceeds the preset time, determining whether the file corresponding to the URL exceeds the preset time through the source station corresponding to the URL; if the source station corresponding to the URL determines that the file corresponding to the URL does not exceed the preset time, judging that the file corresponding to the URL does not exceed the preset time; and if the source station corresponding to the URL determines that the file corresponding to the URL exceeds the preset time, judging that the file corresponding to the URL exceeds the preset time. In this embodiment, when the service node is an edge node of the content delivery network, a specific implementation manner for determining whether a file corresponding to the locally cached URL exceeds a preset time is provided.
In addition, the edge node corresponds to an intermediate node of a content distribution network; before determining whether the file corresponding to the URL exceeds the preset time through the source station corresponding to the URL, the method further includes: determining whether the file corresponding to the URL exceeds preset time or not through the intermediate node; if the file corresponding to the URL does not exceed the preset time through the intermediate node corresponding to the edge node, the check value corresponding to the URL is obtained again from the intermediate node; if the intermediate node determines that the file corresponding to the URL exceeds the preset time, the step of determining whether the file corresponding to the URL exceeds the preset time through the source station corresponding to the URL is carried out; determining whether the file corresponding to the URL exceeds the preset time through the source station corresponding to the URL, specifically: and determining whether the file corresponding to the URL exceeds the preset time or not from the intermediate node to the source station. In this embodiment, before determining whether the file corresponding to the URL exceeds the preset time by the source station corresponding to the URL, it is first determined whether the file corresponding to the URL exceeds the preset time by the corresponding intermediate node, so that it is avoided that whether the file corresponding to the URL exceeds the preset time by the source station corresponding to the URL each time, and the pressure of the source station is reduced.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings, which correspond to the figures in which like reference numerals refer to similar elements and which are not to scale unless otherwise specified.
Fig. 1 is a block schematic diagram of a monitoring system of a service node to which a monitoring method of the service node according to a first embodiment of the present invention is applied;
fig. 2 is a detailed flowchart of a monitoring method of a service node according to a first embodiment of the present invention;
fig. 3 is a detailed flowchart of a monitoring method of a service node according to a second embodiment of the present invention;
fig. 4 is a detailed flowchart of a monitoring method of a service node according to a third embodiment of the present invention;
fig. 5 is a detailed flowchart of a monitoring method of a service node according to a fourth embodiment of the present invention;
fig. 6 is a detailed flowchart of a monitoring method of a service node according to a fifth embodiment of the present invention;
fig. 7 is a specific flowchart of a monitoring method of a service node according to a sixth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present application in various embodiments of the present invention. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments.
Referring to fig. 1, the monitoring system of the service node includes a storage component 1, a content management component 2, and a data analysis component 3 respectively connected to the storage component 1 and the content management component 2. It should be noted that the monitoring method of the service node in this embodiment is used to monitor a node in the CDN network, and in this embodiment and the following embodiments, the CDN network includes an edge node and an intermediate node corresponding to the edge node as an example for description, but is not limited to this, and the CDN network may also include only the edge node.
Fig. 2 shows a specific flow of the monitoring method for a service node according to this embodiment.
specifically, the service node 4 may be an edge node or an intermediate node of the CDN network, and when the service node 4 is an edge node, the edge node obtains a file corresponding to a URL when receiving an access request of a user via a URL sent by an electronic device, and calculates a check value of the file as a check value corresponding to the URL, so that check information including the URL and the check value corresponding to the URL can be generated; when the service node 4 is an intermediate node, the intermediate node acquires a file corresponding to the URL when receiving an access request including the URL of an edge node corresponding thereto, and calculates a check value of the file as a check value corresponding to the URL, thereby being capable of generating check information including the URL and the check value corresponding to the URL. After generating the check information, the service node 4 sends the check information to the storage component 1 of the monitoring system, the storage component 1 receives and stores the check information, and the storage component 1 may be a data storage center server. The service node 4 is provided with a log collector, which can collect access log information of the service node 4 at regular time, the access log information is check information, the access log information includes, in addition to a check value corresponding to the URL and the URL, an IP address, an access time, a port, a source station address corresponding to the URL, and the like of the service node 4, and the format of the access log information may be { IP, port, URL, access time, a check value corresponding to the URL, and a source station address }.
In one example, the check value corresponding to the URL is the MD5 value of the file corresponding to the URL.
And 102, for each piece of verification information, acquiring a trusty verification value corresponding to the URL in the verification information, and if the verification value corresponding to the URL in the verification information is inconsistent with the trusty verification value corresponding to the URL, marking the verification information.
Specifically, the data analysis component 3 may obtain the check information sent by each service node 4 in the storage component 1, and in an example, the check information sent by each service node 4 in one period may be obtained according to a preset period, for example, every five minutes, and then the data analysis component 3 obtains the check information sent by each service node 4 in the five minutes. For each check message, the data analysis component 3 first obtains a trusty check value corresponding to the URL in the check message, where the trusty check value is calculated according to a file corresponding to the URL in the source station; comparing the check value corresponding to the URL in the check information with the trusted check value corresponding to the URL, determining whether the two are consistent, and if the two are consistent, indicating that the check value corresponding to the URL is consistent with the check value corresponding to the URL of the source station, that is, the file cached in the service node 4 that sends the check information is consistent with the file in the source station; otherwise, it indicates that the check value corresponding to the URL is inconsistent with the source station, that is, the file cached in the service node 4 that sends the check information is inconsistent with the source station, and the file cached in the service node 4 that sends the check information has a problem, and marks the check information. In addition, after the data analysis component 3 marks the check information, an alarm message can be sent to the operation and maintenance personnel of the service node 4 sending the check information, so that the operation and maintenance personnel can perform troubleshooting in time.
Specifically, for each marked check information, the content management component 2 determines the service node 4 sending the check information according to the IP address in the check information, and processes the file in the service node 4; for example, a file processing task is sent to the service node 4 sending the verification information, and the service node 4 processes the cached file when receiving the file processing task; for example, deleting or moving all files corresponding to the cached URLs to a specific directory location, or retrieving all files corresponding to the URLs in the source station.
In one example, for each marked check information, processing a file corresponding to a URL in the check information in the service node 4 sending the check information, for example, for each marked check information, the content management component 2 sends a file processing task to the service node 4 sending the check information, the file processing task includes an IP and a URL of the service node 4, and when receiving the file processing task, the service node 4 processes the file corresponding to the URL in the file processing task, for example, deleting the file corresponding to the URL in the cached file processing task or re-acquiring the file corresponding to the URL in the source station; in addition, the files corresponding to the URLs in the cached file processing tasks can be moved to a specific directory location for operation and maintenance personnel to check and analyze.
Compared with the prior art, the embodiment receives the check information which is sent by each service node and comprises the URL and the check value corresponding to the URL; for each received check message, acquiring a trusted check value corresponding to a URL in the check message, if the check value corresponding to the URL in the check message is inconsistent with the trusted check value corresponding to the URL, indicating that a file corresponding to the URL in the check message may have an error, marking the check message, and processing the file in the service node which sends the marked check message; whether the files in the service nodes need to be processed or not can be judged according to the verification information sent by each service node, so that the automatic monitoring and processing of the files in the service nodes are realized, and the risk of file downloading failure of a user is reduced; and the automatic monitoring and processing of the files in the service node can be completed without the source station providing the credible check value corresponding to the URL.
A second embodiment of the present invention relates to a monitoring method for a service node, and the present embodiment is an improvement on the first embodiment, and the main improvement is that: and judging whether the file corresponding to the URL in the verification information exceeds the preset time.
Fig. 3 shows a specific flow of the monitoring method for a service node according to this embodiment.
Wherein, steps 201 and 203 are substantially the same as steps 101 and 103, and are not described herein again, and the main difference is that step 202 includes the following substeps:
Specifically, the data analysis component 3 may obtain check information sent by each service node 4 in the storage component 1, and for each check information, the data analysis component 3 first determines whether a file corresponding to a URL in the check information exceeds a preset time, that is, determines whether the file corresponding to the URL is expired, and if the file corresponding to the URL is not expired, the substep 2022 is performed; if the file corresponding to the URL is expired, go to substep 2023.
In an example, the verification information further includes expiration information representing whether the file corresponding to the URL in the verification information exceeds the preset time, so that the data analysis component 3 may determine whether the file corresponding to the URL exceeds the preset time according to the expiration information of the file corresponding to the URL in the verification information.
In this embodiment, when receiving an access request including a URL, the service node 4 first determines whether a file corresponding to the URL exceeds a preset time, that is, determines whether a file corresponding to the locally cached URL is expired; if the file corresponding to the locally cached URL is not expired, the check value corresponding to the URL may be obtained from the last access log information (check information); if the file corresponding to the locally cached URL is expired, the file corresponding to the URL needs to be obtained again from the source station, and the check value of the file needs to be calculated again; the service node 4 adds an expiration information representing whether the file corresponding to the URL in the verification information exceeds a preset time in the generated access log information, for example, the expiration information is a flag bit, 1 indicates that the file is expired, and 0 indicates that the file is not expired. It should be noted that, if the service node 4 receives the access request of the URL for the first time, it needs to obtain the file corresponding to the URL from the source station, calculate the check value of the file, and generate an access log information; the file corresponding to the URL has an effective time, which may be set by the source station or by the service node 4 that receives the file, so that the service node 4 may determine whether the file is expired according to the effective time of the file.
Specifically, the data analysis component 3 prestores the trusty check values corresponding to the URLs, and when the monitoring system is established, the monitoring system can acquire files corresponding to the URLs from a source station in advance and calculate the trusty check values corresponding to the URLs according to the files corresponding to the URLs; or the operation and maintenance personnel directly stores the credible check value corresponding to each URL in the monitoring system. When the data analysis component 3 determines that the file corresponding to the URL in the verification information is not expired, it may indicate that the trusted verification value corresponding to the URL cached by the data analysis component 3 is still unexpired, and directly obtain the trusted verification value corresponding to the URL from the local cache.
And a substep 2023 of obtaining a trusted check value corresponding to the URL according to the file corresponding to the URL in the source station corresponding to the obtained URL.
Specifically, the data analysis component 3 prestores the trusty check values corresponding to the URLs, and when the monitoring system is established, the monitoring system can acquire files corresponding to the URLs from a source station in advance and calculate the trusty check values corresponding to the URLs according to the files corresponding to the URLs; or the operation and maintenance personnel directly stores the credible check value corresponding to each URL in the monitoring system. When the data analysis component 3 determines that the file corresponding to the URL in the verification information is expired, it may indicate that the trusted verification value corresponding to the URL cached by the data analysis component 3 is expired, re-acquire the file corresponding to the URL from the source station corresponding to the URL, re-calculate the verification value of the file, serve as the trusted verification value corresponding to the URL, and update the cached trusted verification value corresponding to the URL.
In the substep 2024, if the check value corresponding to the URL in the check information is not consistent with the trusted check value corresponding to the URL, the check information is marked.
Specifically, the data analysis component 3 compares the check value corresponding to the URL in the check information with the trusted check value corresponding to the URL, determines whether the two are consistent, and if the two are consistent, indicates that the check value corresponding to the URL is consistent with that in the source station, that is, the file cached in the service node 4 that sends the check information is consistent with that in the source station; otherwise, it indicates that the check value corresponding to the URL is inconsistent with the source station, that is, the file cached in the service node 4 that sends the check information is inconsistent with the source station, and the file cached in the service node 4 that sends the check information has a problem, and marks the check information. In addition, after the data analysis component 3 marks the check information, an alarm message can be sent to the operation and maintenance personnel of the service node 4 sending the check information, so that the operation and maintenance personnel can perform troubleshooting in time.
Compared with the first embodiment, the embodiment judges whether the file corresponding to the URL in the verification information exceeds the preset time, so that the repeated acquisition of the file corresponding to the URL from the source station and the calculation of the trusted verification value corresponding to the URL can be avoided on the basis of ensuring the accuracy of the acquired trusted verification value corresponding to the URL, and the performance consumption is reduced.
The third embodiment of the present invention relates to a monitoring method for a service node, which is an improvement on the first embodiment, and the main improvement is that: whether the URL satisfies the preset condition can be determined according to the number of pieces of check information including the URL and the number of pieces of marked check information including the URL.
Fig. 4 shows a specific flow of the monitoring method for a service node according to this embodiment.
Step 301 and step 302 are substantially the same as step 201 and step 202, and are not described herein again, the main difference is that step 303 is added, specifically as follows:
Specifically, the data analysis component 3 may count the check information corresponding to each URL, and determine, for each URL, whether the URL meets a preset condition according to the number of the check information including the URL and the number of the marked check information including the URL, where the preset condition may be that a quotient obtained by dividing the number of the marked check information including the URL by the number of the check information including the URL is smaller than a preset ratio threshold, that is, when the quotient is smaller than the preset ratio threshold, it is determined that the URL meets the preset condition, which indicates that only a part of files corresponding to the URL in the service node 4 have a cache error, and the process proceeds to step 304 to process the files in the service node that sends the marked check information including the URL meeting the preset condition; otherwise, it indicates that a cache error condition occurs in the file corresponding to the URL in most of the service nodes 4, and it may be that there is a problem in the link between the data analysis component 3 and the source station, at this time, an alarm message is sent to the operation and maintenance personnel, and if the operation and maintenance personnel confirm that there is no problem in the link between the data analysis component 3 and the source station, or after correcting the file corresponding to the URL in the source station, the operation and maintenance personnel then enter step 304 to process the file in the service node that sends the marked verification information including the URL that meets the preset condition.
And a substep 304, for each marked check information, if the URL in the check information meets a preset condition, processing the file in the service node sending the check information.
Specifically, substantially the same as step 103 in the first embodiment, the main difference is that when the URL in the marked check information satisfies the preset condition, the file in the service node 4 that sends the check information is processed, and the details are not repeated.
Compared with the first embodiment, the embodiment can determine whether the URL meets the preset condition according to the number of the check information comprising the URL and the number of the marked check information comprising the URL, and can avoid the file processing of large-scale service nodes when the number of the marked check information comprising a certain URL is too large, thereby avoiding the large-scale source return downloading and further not influencing the service quality of the service nodes.
A fourth embodiment of the present invention relates to a monitoring method for a service node, which is applied to a service node, where the service node may be an edge node or an intermediate node of a CDN network.
Fig. 5 shows a specific flow of the monitoring method for a service node according to this embodiment.
Specifically, when the service node is an edge node, the edge node acquires a file corresponding to a URL when receiving an access request of the URL sent by a user through the electronic device, and calculates a check value of the file as a check value corresponding to the URL, so that check information including the URL and the check value corresponding to the URL can be generated; when the service node is an intermediate node, the intermediate node acquires a file corresponding to the URL when receiving an access request including the URL of the edge node corresponding to the service node, and calculates a check value of the file as a check value corresponding to the URL, so that check information including the URL and the check value corresponding to the URL can be generated. The service node 4 is provided with a log collector, which can collect access log information of the service node 4 at regular time, the access log information is check information, the access log information includes, in addition to a check value corresponding to the URL and the URL, an IP address, an access time, a port, a source station address corresponding to the URL, and the like of the service node 4, and the format of the access log information may be { IP, port, URL, access time, a check value corresponding to the URL, and a source station address }.
Specifically, after generating the check information, the service node 4 sends the check information to the monitoring system of the service node, please refer to fig. 1, where the storage component 1 of the monitoring system of the service node is configured to receive and store the check information, and the storage component 1 may be a data storage center server. The data analysis component 3 may obtain the check information sent by each service node 4 in the storage component 1, and in an example, the check information sent by each service node 4 in one period may be obtained according to a preset period, for example, every five minutes, the data analysis component 3 obtains the check information sent by each service node 4 in the five minutes. For each check message, the data analysis component 3 first obtains a trusty check value corresponding to the URL in the check message, where the trusty check value is calculated according to a file corresponding to the URL in the source station; comparing the check value corresponding to the URL in the check information with the trusted check value corresponding to the URL, determining whether the two are consistent, and if the two are consistent, indicating that the check value corresponding to the URL is consistent with the source station, that is, indicating that the file cached in the service node 4 that sent the check information is consistent with the source station; otherwise, it indicates that the check value corresponding to the URL is inconsistent with the source station, that is, the file cached in the service node 4 that sends the check information is inconsistent with the source station, and the file cached in the service node 4 that sends the check information has a problem, and marks the check information. In addition, after the data analysis component 3 marks the check information, an alarm message can be sent to the operation and maintenance personnel of the service node 4 sending the check information, so that the operation and maintenance personnel can perform troubleshooting in time.
For each marked check information, the content management component 2 determines the service node 4 sending the check information according to the IP address in the check information, and processes the file in the service node 4; for example, a file processing task is sent to the service node 4 sending the verification information, and the service node 4 processes the cached file when receiving the file processing task; for example, deleting or moving all files corresponding to the cached URLs to a specific directory location, or retrieving all files corresponding to the URLs in the source station.
In one example, for each marked check information, processing a file corresponding to a URL in the check information in the service node 4 sending the check information, for example, for each marked check information, the content management component 2 sends a file processing task to the service node 4 sending the check information, the file processing task includes an IP and a URL of the service node 4, and when receiving the file processing task, the service node 4 processes the file corresponding to the URL in the file processing task, for example, deleting the file corresponding to the URL in the cached file processing task or re-acquiring the file corresponding to the URL in the source station; in addition, the files corresponding to the URLs in the cached file processing tasks can be moved to a specific directory folder for operation and maintenance personnel to check and analyze.
Since the first embodiment corresponds to the present embodiment, the present embodiment can be implemented in cooperation with the first embodiment. The related technical details mentioned in the first embodiment are still valid in this embodiment, and the technical effects that can be achieved in the first embodiment can also be achieved in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the first embodiment.
Compared with the prior art, in the embodiment, when a service node receives an access request including a URL, the service node generates check information including the URL and a check value corresponding to the URL, and sends the check information to a monitoring system of the service node, the monitoring system of the service node obtains a trusted check value corresponding to the URL in the check information for each piece of received check information, if the check value corresponding to the URL in the check information is not consistent with the trusted check value corresponding to the URL, it is indicated that a file corresponding to the URL in the check information may have an error, the check information is marked, and the file in the service node sending the marked check information is processed; whether the files in the service nodes need to be processed or not can be judged according to the verification information sent by each service node, so that the automatic monitoring and processing of the files in the service nodes are realized, and the risk of file downloading failure of a user is reduced; and the automatic monitoring and processing of the files in the service node can be completed under the condition that the source station does not need to provide the check value corresponding to the URL.
A fifth embodiment of the present invention relates to a method for monitoring a service node, which is an improvement over the fourth embodiment, and the main improvement is that: the judgment of whether the file corresponding to the URL exceeds the preset time is added.
Fig. 6 shows a specific flow of the monitoring method for a service node according to this embodiment.
Specifically, when receiving an access request including a URL, the service node 4 first determines whether a file corresponding to the URL exceeds a preset time, that is, determines whether a file corresponding to the locally cached URL is expired; the method comprises the steps that a file corresponding to a URL has an effective time, and the effective time of the file is set when a service node 4 acquires and caches the file corresponding to the URL for the first time; the valid time may be set by the source station, or may be set by the service node 4 that receives the file, so that the service node 4 may determine whether the file corresponding to the URL is expired according to the cached valid time of the file corresponding to the URL when receiving the access request of the URL again; if not, go to step 502; if yes, go to step 503. It should be noted that, if the service node 4 receives the access request of the URL for the first time, it needs to obtain the file corresponding to the URL from the source station, calculate the check value of the file, and generate an access log information.
Specifically, when determining that the file corresponding to the URL cached locally is not expired, the service node 4 acquires the check value corresponding to the URL from the previous access log information (check information) and generates expiration information indicating that the file corresponding to the URL does not exceed a preset time, where the expiration information may be a flag bit, for example, 0 indicating that the file is not expired.
Specifically, when determining that the file corresponding to the locally cached URL is expired, the service node 4 needs to obtain the file corresponding to the URL from the source station again, and recalculate the check value of the file as the check value corresponding to the URL; and then generating expiration information representing that the file corresponding to the URL exceeds a preset time, where the expiration information may be a flag bit, for example, 1 indicates that the file has expired.
Specifically, the service node 4 adds expiration information representing whether the file corresponding to the URL in the verification information exceeds the preset time to the generated access log information (verification information), and the format of the access log information is { IP, port, URL, access time, verification value corresponding to the URL, source address, expiration information }.
And 505, sending the verification information to a monitoring system of the service node, so that the monitoring system can acquire a trusty verification value corresponding to the URL in the verification information, if the verification value corresponding to the URL in the verification information is not consistent with the trusty verification value corresponding to the URL, marking the verification information, and processing a file in the service node which sends the marked verification information.
Specifically, this step is substantially the same as step 402 in the fourth embodiment, and the main difference is that: the verification information further includes expiration information representing whether the file corresponding to the URL in the verification information exceeds the preset time, so that the data analysis component 3 can judge whether the file corresponding to the URL exceeds the preset time according to the expiration information of the file corresponding to the URL in the verification information. The data analysis component 3 acquires files corresponding to all URLs from a source station in advance, calculates check values corresponding to all URLs, and when the files corresponding to the URLs in the check information are judged to be not expired, the files corresponding to the URLs cached by the data analysis component 3 can be indicated to be still unexpired, and a trusted check value corresponding to the URLs is directly acquired from a local cache; when the file corresponding to the URL in the verification information is determined to be expired, it may be indicated that the file corresponding to the URL cached by the data analysis component 3 is expired, the file corresponding to the URL is re-acquired from the source station corresponding to the URL, the verification value of the file is re-calculated, and the trusted verification value of the URL is updated.
Since the second embodiment corresponds to the present embodiment, the present embodiment can be implemented in cooperation with the second embodiment. The related technical details mentioned in the second embodiment are still valid in this embodiment, and the technical effects that can be achieved in the second embodiment can also be achieved in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the second embodiment.
Compared with the fourth embodiment, the service node determines whether the file corresponding to the URL exceeds the preset time before generating the verification information, so that the situation that the verification value corresponding to the URL is obtained according to the file corresponding to the URL in the source station corresponding to the acquired URL repeatedly can be avoided, and the performance consumption of the service node is reduced.
A sixth embodiment of the present invention relates to a method for monitoring a service node, which is a refinement of the fifth embodiment, and the main refinement is as follows: when the service node is an edge node of the content distribution network, a specific implementation mode for judging whether the file corresponding to the locally cached URL exceeds the preset time is provided.
Fig. 7 shows a specific flow of the monitoring method for a service node according to this embodiment. In this embodiment, the service node 4 is an edge node of a content distribution network, and the edge node corresponds to an intermediate node of the content distribution network.
Step 602 to step 605 are substantially the same as step 502 to step 505, and are not described herein again, the main difference is that step 601 includes the following sub-steps:
Specifically, when an edge node receives an access request of a certain URL for the first time, the edge node and an intermediate node corresponding to the edge node do not have a file corresponding to the URL, the intermediate node obtains a source station corresponding to the URL from a source station corresponding to the URL to obtain the file corresponding to the URL for caching, and sends the cached file to the edge node, and the edge node caches the file and generates access log information; in addition, when the intermediate node acquires the file corresponding to the URL, the intermediate node also calculates the check value of the file and generates access log information.
When the edge node receives the access request of the URL again, it determines whether the file corresponding to the locally cached URL exceeds a preset time, that is, it determines whether the file corresponding to the URL is expired, and if it determines that the file corresponding to the URL is expired, it goes to substep 6012; otherwise, it indicates that the file corresponding to the locally cached URL is not expired, step 602 is entered, and a check value corresponding to the locally cached URL is obtained, that is, the check value in the last access log information is used as the check value corresponding to the URL in the current access log information, and expiration information indicating that the file corresponding to the URL does not exceed the preset time is added to the current access log information.
Sub-step 6012, determining whether the file corresponding to the URL exceeds a preset time through an intermediate node. If yes, go to substep 6013; if not, go to substep 6014.
Specifically, the edge node determines whether the file corresponding to the URL exceeds a preset time through the intermediate node corresponding to the edge node, the intermediate node determines whether the file corresponding to the locally cached URL exceeds the preset time, that is, determines whether the file corresponding to the URL is expired, and if it is determined that the file corresponding to the URL is expired, the sub-step 6013 is performed; if the file corresponding to the URL is determined not to be expired, then sub-step 6014 is performed.
Sub-step 6013, determining whether the file corresponding to the URL exceeds a preset time by the intermediate node to the source station. If yes, go to step 603; if not, go to step 602.
Specifically, the intermediate node determines whether the file corresponding to the URL exceeds a preset time to a source station corresponding to the URL, if it is determined that the file corresponding to the URL has exceeded the preset time by the source station, the intermediate node acquires the file corresponding to the URL from the source station again to cache the file, and sends the file acquired again to the edge node, the edge node caches the file, and recalculates a check value of the file, takes the recalculated check value as the check value corresponding to the URL in the access log information generated this time, and adds expiration information representing that the file corresponding to the URL does not exceed the preset time in the access log information this time. In addition, when caching the file corresponding to the newly acquired URL, the intermediate node also calculates a check value of the file, uses the recalculated check value as the check value corresponding to the URL in the access log information generated this time, and adds expiration information representing that the file corresponding to the URL does not exceed the preset time in the access log information this time.
Specifically, when the edge node determines that the file corresponding to the URL does not exceed the preset time through the intermediate node corresponding to the edge node, the intermediate node sends the file corresponding to the URL, which is locally cached by the intermediate node, to the edge node, the edge node caches the file, recalculates the check value of the file, uses the recalculated check value as the check value corresponding to the URL in the access log information generated this time, and adds the expiration information representing that the file corresponding to the URL exceeds the preset time into the access log information this time.
Since the second embodiment corresponds to the present embodiment, the present embodiment can be implemented in cooperation with the second embodiment. The related technical details mentioned in the second embodiment are still valid in this embodiment, and the technical effects that can be achieved in the second embodiment can also be achieved in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the second embodiment.
Compared with the fifth embodiment, the present embodiment provides a specific implementation manner for determining whether a file corresponding to a locally cached URL exceeds a preset time when a service node is an edge node of a content distribution network.
Referring to fig. 1, the monitoring system of the service node includes a storage component 1, a content management component 2, and a data analysis component 3 respectively connected to the storage component 1 and the content management component 2. It should be noted that the monitoring system of the service node in this embodiment is used to monitor the node in the CDN network, and in this embodiment and the following embodiments, the CDN network includes an edge node and an intermediate node corresponding to the edge node as an example for description, but is not limited to this, and the CDN network may also include only the edge node.
The storage component 1 is used for receiving check information sent by at least one service node; the check information includes the URL and a check value corresponding to the URL. Specifically, the service node 4 may be an edge node or an intermediate node of the CDN network, and when the service node 4 is an edge node, the edge node obtains a file corresponding to a URL when receiving an access request of a user via a URL sent by the electronic device, and calculates a check value of the file as a check value corresponding to the URL, so that check information including the URL and the check value corresponding to the URL can be generated; when the service node 4 is an intermediate node, the intermediate node acquires a file corresponding to the URL when receiving an access request including the URL of an edge node corresponding thereto, and calculates a check value of the file as a check value corresponding to the URL, thereby being capable of generating check information including the URL and the check value corresponding to the URL. After generating the check information, the service node 4 sends the check information to the storage component 1 of the monitoring system of the service node, the storage component 1 receives and stores the check information, and the storage component 1 may be a data storage center server. The service node 4 is provided with a log collector, which can collect access log information of the service node 4 at regular time, the access log information is check information, the access log information includes, in addition to a check value corresponding to the URL and the URL, an IP address, an access time, a port, a source station address corresponding to the URL, and the like of the service node 4, and the format of the access log information may be { IP, port, URL, access time, a check value corresponding to the URL, and a source station address }.
In one example, the check value corresponding to the URL is the MD5 value of the file corresponding to the URL.
The data analysis component 3 is configured to, for each piece of verification information, obtain a trusted verification value corresponding to the URL in the verification information, and mark the verification information if the verification value corresponding to the URL in the verification information is inconsistent with the trusted verification value corresponding to the URL. Specifically, the data analysis component 3 may obtain the check information sent by each service node 4 in the storage component 1, and in an example, the check information sent by each service node 4 in one period may be obtained according to a preset period, for example, every five minutes, the data analysis component 3 obtains the check information sent by each service node 4 in the five minutes. For each check message, the data analysis component 3 first obtains a trusty check value corresponding to the URL in the check message, where the trusty check value is calculated according to a file corresponding to the URL in the source station; comparing the check value corresponding to the URL in the check information with the trusted check value corresponding to the URL, determining whether the two are consistent, and if the two are consistent, indicating that the check value corresponding to the URL is consistent with the source station, that is, indicating that the file cached in the service node 4 that sent the check information is consistent with the source station; otherwise, it indicates that the check value corresponding to the URL is inconsistent with the source station, that is, the file cached in the service node 4 that sends the check information is inconsistent with the source station, and the file cached in the service node 4 that sends the check information has a problem, and marks the check information. In addition, after the data analysis component 3 marks the check information, an alarm message can be sent to the operation and maintenance personnel of the service node 4 sending the check information, so that the operation and maintenance personnel can perform troubleshooting in time.
The content management component 2 is used to process the file in the service node that sends the marked check information. Specifically, for each marked check information, the content management component 2 determines the service node 4 sending the check information according to the IP address in the check information, and processes the file in the service node 4; for example, a file processing task is sent to the service node 4 sending the verification information, and the service node 4 processes the cached file when receiving the file processing task; for example, deleting or moving all files corresponding to the cached URLs to a specific directory location, or retrieving all files corresponding to the URLs in the source station.
In one example, for each marked check information, processing a file corresponding to a URL in the check information in the service node 4 sending the check information, for example, for each marked check information, the content management component 2 sends a file processing task to the service node 4 sending the check information, the file processing task includes an IP and a URL of the service node 4, and when receiving the file processing task, the service node 4 processes the file corresponding to the URL in the file processing task, for example, deleting the file corresponding to the URL in the cached file processing task or re-acquiring the file corresponding to the URL in the source station; in addition, the files corresponding to the URLs in the cached file processing tasks can be moved to a specific directory location for operation and maintenance personnel to check and analyze.
Since the first and fourth embodiments correspond to the present embodiment, the present embodiment can be implemented in cooperation with the first and fourth embodiments. The related technical details mentioned in the first embodiment and the fourth embodiment are still valid in this embodiment, and the technical effects achieved in the first embodiment and the fourth embodiment can also be achieved in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the first embodiment and the fourth embodiment.
Compared with the prior art, the embodiment receives the check information which is sent by each service node and comprises the URL and the check value corresponding to the URL; for each received check message, acquiring a trusted check value corresponding to a URL in the check message, if the check value corresponding to the URL in the check message is inconsistent with the trusted check value corresponding to the URL, indicating that a file corresponding to the URL in the check message may have an error, marking the check message, and processing the file in the service node which sends the marked check message; whether the files in the service nodes need to be processed or not can be judged according to the verification information sent by each service node, so that the automatic monitoring and processing of the files in the service nodes are realized, and the risk of file downloading failure of a user is reduced; and moreover, the automatic monitoring and processing of the files in the service nodes can be completed without the source station of each service node providing the check value corresponding to the URL.
An eighth embodiment of the present invention relates to a monitoring system for a service node, and the eighth embodiment is an improvement of the seventh embodiment, and the main improvement is that: and judging whether the file corresponding to the URL in the verification information exceeds the preset time.
The data analysis component 3 is configured to, when the file corresponding to the URL in the verification information does not exceed the preset time, obtain a trusted verification value corresponding to the locally cached URL.
And the data analysis component 3 is used for obtaining a credible check value corresponding to the URL according to the file corresponding to the URL in the source station corresponding to the acquired URL when the file corresponding to the URL in the check information exceeds the preset time.
In one example, the verification information further includes expiration information representing whether a file corresponding to the URL in the verification information exceeds a preset time; the data analysis component 3 is used for judging whether the file corresponding to the URL exceeds the preset time according to the expiration information of the file corresponding to the URL in the verification information.
Since the second, fourth and fifth embodiments correspond to the present embodiment, the present embodiment can be implemented in cooperation with the second, fourth and fifth embodiments. The related technical details mentioned in the second, fourth, and fifth embodiments are still valid in this embodiment, and the technical effects achieved in the second, fourth, and fifth embodiments can also be achieved in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the second embodiment, the fourth embodiment, and the fifth embodiment.
Compared with the seventh embodiment, the embodiment judges whether the file corresponding to the URL in the verification information exceeds the preset time, so that the file corresponding to the URL is prevented from being repeatedly acquired from the source station and the trusted verification value corresponding to the URL is calculated on the basis of ensuring the accuracy of the acquired trusted verification value corresponding to the URL, and the performance consumption is reduced.
A ninth embodiment of the present invention relates to a monitoring system for a service node, and the ninth embodiment is an improvement on the seventh embodiment, and the main improvement is that: whether the URL satisfies the preset condition can be determined according to the number of pieces of check information including the URL and the number of pieces of marked check information including the URL.
The data analysis component 3 is further configured to determine, for each URL, whether the URL satisfies a preset condition according to the number of pieces of check information including the URL and the number of pieces of marked check information including the URL; the preset condition is that a quotient of the number of the marked check information including the URL divided by the number of the check information including the URL is less than a preset duty threshold.
The data analysis component 3 is configured to, for each marked check information, process a file in a service node that sends the check information if a URL in the check information satisfies a preset condition.
Since the third embodiment corresponds to the present embodiment, the present embodiment can be implemented in cooperation with the third embodiment. The related technical details mentioned in the third embodiment are still valid in this embodiment, and the technical effects that can be achieved in the third embodiment can also be achieved in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the third embodiment.
Compared with the seventh embodiment, the present embodiment can determine whether the URL satisfies the preset condition according to the number of the check information including the URL and the number of the marked check information including the URL, and can avoid the file processing of a large-scale service node when the number of the marked check information including a certain URL is too large, thereby avoiding the large-scale source return downloading and further not affecting the service quality of the service node. This embodiment mode can also be an improvement on the eighth embodiment mode, and can achieve the same technical effects.
A tenth embodiment of the present invention is directed to a service node, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of monitoring a service node of any one of the fourth to sixth embodiments.
Where the memory and processor are connected by a bus, the bus may comprise any number of interconnected buses and bridges, the buses connecting together one or more of the various circuits of the processor and the memory. The bus may also connect various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor is transmitted over a wireless medium via an antenna, which further receives the data and transmits the data to the processor.
The processor is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And the memory may be used to store data used by the processor in performing operations.
An eleventh embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The computer program realizes the above-described method embodiments when executed by a processor.
That is, as can be understood by those skilled in the art, all or part of the steps in the method according to the above embodiments may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps in the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.
Claims (13)
1. A monitoring method of a service node is applied to a monitoring system of the service node, and the method comprises the following steps:
receiving check information sent by at least one service node; the check information comprises a URL and a check value corresponding to the URL, and the check value is obtained by calculation according to a file corresponding to the URL;
for each piece of check information, obtaining a trusty check value corresponding to the URL in the check information from a pre-stored trusty check value corresponding to each URL, marking the check information if the check value corresponding to the URL in the check information is not consistent with the trusty check value corresponding to the URL, and calculating the trusty check value according to a file corresponding to the corresponding URL;
processing a file in the service node which sends the marked check information;
wherein the processing the file in the service node sending the marked checking information includes:
for each URL, determining whether the quotient of the number of the marked check information of the URL divided by the number of the marked check information of the URL is less than a preset duty ratio threshold value according to the number of the check information including the URL and the number of the marked check information including the URL;
and processing the file in the service node which sends the verification information under the condition that the quotient value is smaller than the preset ratio threshold value.
2. The method for monitoring a service node according to claim 1, wherein the obtaining a trusted verification value corresponding to the URL in the verification information includes:
judging whether the file corresponding to the URL in the verification information exceeds preset time or not;
if the file corresponding to the URL in the verification information does not exceed the preset time, acquiring the credible verification value corresponding to the URL cached locally;
and if the file corresponding to the URL in the verification information exceeds the preset time, obtaining the credible verification value corresponding to the URL according to the obtained file corresponding to the URL in the source station corresponding to the URL.
3. The method for monitoring a service node according to claim 2, wherein the check information further includes expiration information indicating whether the file corresponding to the URL in the check information exceeds the preset time;
the judging whether the file corresponding to the URL in the verification information exceeds a preset time specifically includes:
and judging whether the file corresponding to the URL exceeds preset time or not according to the overdue information of the file corresponding to the URL in the verification information.
4. The method for monitoring a service node according to claim 1, wherein the processing of the file in the service node that sends the marked verification information specifically includes:
and for each marked check information, processing a file corresponding to the URL in the check information in the service node sending the check information.
5. A monitoring method for a service node is applied to the service node, and the method comprises the following steps:
when an access request comprising a URL is received, generating check information, wherein the check information comprises a URL and a check value corresponding to the URL, and the check value is obtained by calculation according to a file corresponding to the URL;
sending the check information to a monitoring system of a service node, so that the monitoring system can obtain a trusty check value corresponding to the URL in the check information from pre-stored trusty check values corresponding to the URLs, if the check value corresponding to the URL in the check information is not consistent with the trusty check value corresponding to the URL, marking the check information, and processing a file in the service node sending the marked check information, wherein the trusty check value is obtained by calculation according to the file corresponding to the URL;
wherein the processing the file in the service node sending the marked checking information includes:
for each URL, determining whether the quotient of the number of the marked check information of the URL divided by the number of the marked check information of the URL is less than a preset duty ratio threshold value according to the number of the check information including the URL and the number of the marked check information including the URL;
and processing the file in the service node which sends the verification information under the condition that the quotient value is smaller than the preset ratio threshold value.
6. The method for monitoring a service node according to claim 5, wherein before the generating the check information, the method further comprises:
judging whether the file corresponding to the URL exceeds preset time or not;
if the file corresponding to the URL does not exceed the preset time, acquiring the check value corresponding to the locally cached URL, and generating expiration information representing that the file corresponding to the URL does not exceed the preset time;
if the file corresponding to the URL exceeds the preset time, obtaining the check value corresponding to the URL according to the obtained file corresponding to the URL in the source station corresponding to the URL, and generating expiration information representing that the file corresponding to the URL exceeds the preset time; the verification information further includes the expiration information.
7. The method of claim 6, wherein the service node is an edge node of a content distribution network;
the judging whether the file corresponding to the URL exceeds the preset time includes:
judging whether the locally cached file corresponding to the URL exceeds preset time or not;
if the file corresponding to the locally cached URL does not exceed the preset time, judging that the file corresponding to the URL does not exceed the preset time; if the locally cached file corresponding to the URL exceeds the preset time, determining whether the file corresponding to the URL exceeds the preset time through the source station corresponding to the URL;
if the source station corresponding to the URL determines that the file corresponding to the URL does not exceed the preset time, judging that the file corresponding to the URL does not exceed the preset time; and if the source station corresponding to the URL determines that the file corresponding to the URL exceeds the preset time, judging that the file corresponding to the URL exceeds the preset time.
8. The method of claim 7, wherein the edge node corresponds to an intermediate node of the content distribution network;
before the determining, by the source station corresponding to the URL, whether the file corresponding to the URL exceeds the preset time, the method further includes: determining whether the file corresponding to the URL exceeds the preset time through the intermediate node;
if the intermediate node corresponding to the edge node determines that the file corresponding to the URL does not exceed the preset time, the check value corresponding to the URL is obtained from the intermediate node again; if the intermediate node determines that the file corresponding to the URL exceeds the preset time, entering a step of determining whether the file corresponding to the URL exceeds the preset time through a source station corresponding to the URL;
determining whether the file corresponding to the URL exceeds the preset time by the source station corresponding to the URL, specifically:
and determining whether the file corresponding to the URL exceeds the preset time or not from the intermediate node to the source station.
9. A monitoring system for a service node, comprising: the content management system comprises a storage component, a content management component and a data analysis component which is respectively connected with the storage component and the content management component;
the storage component is used for receiving check information sent by at least one service node; the check information comprises a URL and a check value corresponding to the URL, and the check value is obtained by calculation according to a file corresponding to the URL;
the data analysis component is used for acquiring a credible check value corresponding to the URL in the check information from a credible check value corresponding to each prestored URL for each check information, if the check value corresponding to the URL in the check information is not consistent with the credible check value corresponding to the URL, marking the check information, and calculating the credible check value according to a file corresponding to the corresponding URL;
the data analysis component is further used for determining whether the quotient of the number of the marked check information of the URL divided by the number of the marked check information of the URL is smaller than a preset ratio threshold value or not according to the number of the check information of the URL and the number of the marked check information of the URL;
under the condition that the quotient value is smaller than the preset ratio threshold value, instructing the content management component to process the file in the service node which sends the verification information;
the content management component is used for processing files in the service nodes which send the marked check information.
10. The monitoring system of a service node according to claim 9, wherein the data analysis component is configured to determine whether a file corresponding to the URL in the verification information exceeds a preset time;
the data analysis component is used for acquiring the credible check value corresponding to the locally cached URL when the file corresponding to the URL in the check information does not exceed the preset time;
the data analysis component is used for obtaining the credible check value corresponding to the URL according to the obtained file corresponding to the URL in the source station corresponding to the URL when the file corresponding to the URL in the check information exceeds the preset time.
11. The monitoring system of service nodes according to claim 10, wherein the check information further includes expiration information indicating whether the file corresponding to the URL in the check information exceeds the preset time;
and the data analysis component is used for judging whether the file corresponding to the URL exceeds preset time or not according to the overdue information of the file corresponding to the URL in the verification information.
12. The system for monitoring service nodes according to claim 9, wherein the content management component is specifically configured to, for each marked check information, process a file corresponding to the URL in the check information in the service node that sent the check information.
13. A serving node, comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of monitoring of a service node of any of claims 5 to 8.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910555191.0A CN110460487B (en) | 2019-06-25 | 2019-06-25 | Service node monitoring method and system and service node |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910555191.0A CN110460487B (en) | 2019-06-25 | 2019-06-25 | Service node monitoring method and system and service node |
Publications (2)
Publication Number | Publication Date |
---|---|
CN110460487A CN110460487A (en) | 2019-11-15 |
CN110460487B true CN110460487B (en) | 2022-04-05 |
Family
ID=68480852
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201910555191.0A Active CN110460487B (en) | 2019-06-25 | 2019-06-25 | Service node monitoring method and system and service node |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110460487B (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112306753B (en) * | 2020-10-30 | 2024-07-23 | 联想(北京)有限公司 | Data restoration method, device and system |
CN114285639B (en) * | 2021-12-24 | 2023-11-24 | 云盾智慧安全科技有限公司 | Website safety protection method and device |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102255695B (en) * | 2011-07-22 | 2013-09-04 | 乐视网信息技术(北京)股份有限公司 | Data check method and system applied to peer-to-peer (p2p) network delivery system |
CN103379139B (en) * | 2012-04-17 | 2017-07-25 | 百度在线网络技术(北京)有限公司 | Method of calibration, system and the device of distributed caching content |
CN103377251B (en) * | 2012-04-27 | 2017-05-10 | 百度在线网络技术(北京)有限公司 | File comparison method and device for HDFS (Hadoop Distributed File System) |
CA2999150A1 (en) * | 2015-09-18 | 2017-03-23 | First Data Corporation | System for validating a biometric input |
CN107026828B (en) * | 2016-02-02 | 2020-02-21 | 中国移动通信集团辽宁有限公司 | Anti-stealing-link method based on Internet cache and Internet cache |
CN108282543A (en) * | 2018-03-05 | 2018-07-13 | 北京云端智度科技有限公司 | A kind of CDN node content authentication method and system |
CN108924595A (en) * | 2018-08-15 | 2018-11-30 | 广东南方新媒体股份有限公司 | Realize the method and system of TS slice door chain |
CN109492436A (en) * | 2018-11-29 | 2019-03-19 | 深圳市网心科技有限公司 | A kind of file verification method and relevant apparatus |
-
2019
- 2019-06-25 CN CN201910555191.0A patent/CN110460487B/en active Active
Also Published As
Publication number | Publication date |
---|---|
CN110460487A (en) | 2019-11-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110909013B (en) | Service list generation method, device, equipment and computer readable storage medium | |
CN113472852A (en) | CDN node back-source method, device and equipment | |
EP3832452A1 (en) | Log printing method and system, server | |
CN110460487B (en) | Service node monitoring method and system and service node | |
US8069236B2 (en) | Flow control of events based on threshold, grace period, and event signature | |
CN110460486B (en) | Service node monitoring method and system | |
CN110138808B (en) | Anti-hijack downloading method and system based on CDN | |
CN107395451B (en) | Processing method, device and equipment for internet traffic abnormity and storage medium | |
CN112783541A (en) | Equipment upgrading method and device and server | |
CN112600952A (en) | Method and system for accelerating distribution of mobile terminal network | |
CN110889143A (en) | File verification method and device | |
CN109194706B (en) | Network resource dial testing method and terminal | |
CN104410962A (en) | A terminal user network traffic monitoring method and device | |
CN112422604B (en) | File uploading method, device and system and computer equipment | |
CN116719639A (en) | Link dynamic adjustment and data processing method, device, computer equipment and medium | |
WO2022062807A1 (en) | Device control method, server, and storage medium | |
CN111372277A (en) | Data distribution method, device and storage medium | |
CN112131198B (en) | Log analysis method and device and electronic equipment | |
CN117714295A (en) | Network link generation method, server and storage medium | |
CN115296979A (en) | Fault processing method, device, equipment and storage medium | |
CN115333917A (en) | CDN anomaly detection method and device | |
CN111401672B (en) | Block chain-based validity verification method, device and system | |
CN112436974A (en) | CDN data resource consistency detection method and device and computer equipment | |
CN110881213A (en) | Method and system for transmitting network test process information | |
CA2475207C (en) | System, method and terminal for measuring the quality of service in a telecommunications 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 |