CDN performance monitoring method

Abstract

The invention discloses a CDN performance monitoring method. The monitoring method comprises the following steps of user request log collection, CDN hit rate and average time consumption analysis, CDN node performance analysis using different network operators, IOS and Android CDN request time consumption comparative analysis, same-city request CDN node distribution city analysis and timed task monitoring performance trend. The method has the advantages that storage records such as user request time consumption, request addresses, whether the CDN cache is hit or not, CDN node related information and the like are extracted by collecting user request logs, analyzing requests and returning information, related performance is counted from different dimensions, a timed task is added, performance indexes are monitored and focused on, and the user experience is improved. Once the performance is obviously changed and fluctuated, an alarm can be given in time to notify a related person in charge to follow up and check problems in time, so that the service stability and the user experience are ensured, reliable and stable performance can be provided for the service of the user, and the user experience is ensured.

Description

Technical Field

[0001] The present invention relates to a monitoring method, in particular to a CDN performance monitoring method, and belongs to the technical field of routing control applications. Background Art

[0002] CDN, or content distribution network, is an intelligent virtual network built on the basis of the existing network. It relies on edge servers deployed in various places, and through the load balancing, content distribution, scheduling and other functional modules of the central platform, it enables users to obtain the required content nearby, reduce network latency, and improve the response speed and availability of users' website access. With the rapid development of the Internet, in today's information age, the content distribution network (CDN) is a vital part of the network architecture. The stability and efficiency of its performance are crucial to improving user experience, carrying the content loading speed of various company applications and websites and reducing the pressure on the source server.

[0003] However, the services of CDN operators are not absolutely stable. For example, if the performance of some CDN node servers declines, or the operator adjusts the service nodes (increases or decreases), it is possible to have an impact on the performance of the service and affect the user experience. When the service request time increases and the performance declines, it may be a problem with the service itself, or it may be affected by the decline in CDN service performance. At present, it is impossible to analyze and determine whether the increase in service response time is a problem with the service itself or a problem with the CDN service. Therefore, a system is needed that can analyze and monitor information related to CDN service responses. It can monitor the overall CDN service response time, CDN service response time in each city dimension, cache hit rate in the national dimension, cache hit rate in the city dimension, the proportion of CDN node network service providers, the average response time of each network service provider, etc. Without a complete CDN monitoring system, performance degradation problems cannot be discovered in a timely manner, and there is no data to support the proof that the performance degradation is caused by the decline in the service performance of the CDN operator. Summary of the invention

[0004] The purpose of the present invention is to provide a method for CDN performance monitoring in order to solve the above problems.

[0005] The present invention achieves the above-mentioned purpose through the following technical scheme, a method for monitoring CDN performance, the monitoring method comprising the following steps:

[0006] (1) User request log collection;

[0007] (2) Analysis of CDN hit rate and average time consumption;

[0008] (3) Performance analysis of CDN nodes using different network operators;

[0009] (4) Comparative analysis of the time consumption of CDN requests for iOS and Android;

[0010] (5) Analysis of the distribution of CDN nodes in the same city;

[0011] (6) Scheduled tasks to monitor performance trends.

[0012] In the technical solution, step (1) completely records all data from the user initiating the request to the end of the response, including the user request URL, the user's IP address, the user's city, and whether the CDN cache is hit.

[0013] In the technical solution, when the request hits the CDN cache in step (1), the city where the CDN node is located, the network information used by the CDN node, etc. are analyzed through the request response header X-Cache-Lookup return value (such as: HIT from KS-CLOUD-BJ-CTT-11-07, HIT represents hit CDN, BJ is the city code, and CTT is the network operator code), which is used for statistical monitoring of CDN performance in various dimensions.

[0014] In the technical solution, in step (2), the overall CDN hit rate, average time consumption and the average time consumption of the CDN hit rate of each city are counted by city dimension.

[0015] In the technical solution, in step (3), statistics are collected to compare the average response time of each network operator in each time period in multiple cities.

[0016] In the technical solution, if the performance of a certain network used in step (3) is poor in the city, the information can be fed back to the CDN service provider to appropriately adjust the proportion of network usage by CDN nodes to improve response performance.

[0017] In the technical solution, in step (4), the average response time trends of IOS and Android in each time period are statistically compared. If there is a large difference in the average time consumption of the two ends, the cause can be promptly identified and the end with poor performance can be improved.

[0018] In the present technical solution, user requests in the same city in step (5) will hit CDN nodes in multiple cities. Theoretically, the closer the city where the CDN node is located is to the user, the faster it should be and the priority access should be given. Through statistical analysis of the current existing data and based on the current statistical data support, it can be suggested that CDN operators adjust the CDN distribution strategy and try to distribute user requests to the CDN node closest to the user.

[0019] In the present technical solution, in step (6), CDN performance trends are regularly monitored from various dimensions, the overall CDN hit rate and performance trends are monitored, more important cities are selected to detect hit rates and performance trends by city, various performance monitoring is performed according to the network operator dimension, and comparative performance monitoring is performed on both IOS and Android terminals.

[0020] In the present technical solution, in step (6), comparative analysis is performed from multiple dimensions such as month-on-month and year-on-year, and if fluctuations exceed the set threshold, an alarm is promptly issued to notify the relevant person in charge to follow up and investigate, so as to ensure the stability of service performance.

[0021] The beneficial effects of the present invention are as follows: the monitoring method collects user request logs, parses requests and return information to extract user request time, request address, whether it hits the CDN cache, CDN node related information and other storage records, and counts relevant performance from different dimensions, such as: overall CDN hit rate and performance trend, CDN hit rate and performance trend in each city, the proportion of network service providers used by users in each city to request CDN, statistics on the cities to which CDN nodes hit in the same city belong, performance trend comparison of different operating systems on mobile phones in the national and city dimensions, etc., analyzes and monitors CDN performance from multiple dimensions, and monitors key performance indicators by adding scheduled tasks. Once significant performance changes and fluctuations are found, timely alarms can be issued to notify relevant persons in charge to follow up and investigate the problem in a timely manner to ensure service stability and user experience. User request logs can be collected, and the value of the HTTP cache protocol X-Cache-Status in the log response header information can be analyzed to determine whether the CDN hits the cache, the city where the CDN node is located, the network used, and other information. Then, CDN performance trends are counted from different dimensions, and scheduled tasks are used to monitor performance trend changes. CDN service performance degradation can be discovered in a timely manner, and the person in charge can be notified to contact the CDN operator to investigate the cause, so as to provide reliable and stable performance for their own services and ensure user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 The present invention is a flow chart of the method. DETAILED DESCRIPTION

[0023] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0024] Embodiment 1:

[0025] A method for monitoring CDN performance, the monitoring method comprising the following steps:

[0026] (1) User request log collection;

[0027] (2) Analysis of CDN hit rate and average time consumption;

[0028] (3) Performance analysis of CDN nodes using different network operators;

[0029] (4) Comparative analysis of the time consumption of CDN requests for iOS and Android;

[0030] (5) Analysis of the distribution of CDN nodes in the same city;

[0031] (6) Scheduled tasks to monitor performance trends.

[0032] In the technical solution, step (1) completely records all data from the user initiating the request to the end of the response, including the user request URL, the user's IP address, the user's city, and whether the CDN cache is hit.

[0033] In the technical solution, when the request hits the CDN cache in step (1), the city where the CDN node is located, the network information used by the CDN node, etc. are analyzed through the request response header X-Cache-Lookup return value (such as: HIT from KS-CLOUD-BJ-CTT-11-07, HIT represents hit CDN, BJ is the city code, and CTT is the network operator code), which is used for statistical monitoring of CDN performance in various dimensions.

[0034] In the technical solution, in step (2), the overall CDN hit rate, average time consumption and the average time consumption of the CDN hit rate of each city are counted by city dimension.

[0035] In the technical solution, in step (3), statistics are collected to compare the average response time of each network operator in each time period in multiple cities.

[0036] In the technical solution, if the performance of a certain network used in step (3) is poor in the city, the information can be fed back to the CDN service provider to appropriately adjust the proportion of network usage by CDN nodes to improve response performance.

[0037] In the technical solution, in step (4), the average response time trends of IOS and Android in each time period are statistically compared. If there is a large difference in the average time consumption of the two ends, the cause can be promptly identified and the end with poor performance can be improved.

[0038] In the present technical solution, in step (5), user requests from the same city will hit CDN nodes in multiple cities. The city where the CDN node is located is closer to the user, but it is not the priority access. Through statistical analysis of the current existing data and based on the current statistical data support, it is recommended that CDN operators adjust the CDN distribution strategy and try to distribute user requests to the CDN node closest to the user.

[0039] In the present technical solution, in step (6), CDN performance trends are regularly monitored from various dimensions, the overall CDN hit rate and performance trends are monitored, more important cities are selected to detect hit rates and performance trends by city, various performance monitoring is performed according to the network operator dimension, and comparative performance monitoring is performed on both IOS and Android terminals.

[0040] In the present technical solution, in step (6), comparative analysis is performed from multiple dimensions such as month-on-month and year-on-year, and if fluctuations exceed the set threshold, an alarm is promptly issued to notify the relevant person in charge to follow up and investigate, so as to ensure the stability of service performance.

[0041] The above method is suitable for CDN performance monitoring. The statistical receiving data processing time is long and the efficiency of CDN performance monitoring is low.

[0042] Embodiment 2:

[0043] A method for monitoring CDN performance, the monitoring method comprising the following steps:

[0044] (1) User request log collection;

[0045] (2) Analysis of CDN hit rate and average time consumption;

[0046] (3) Performance analysis of CDN nodes using different network operators;

[0047] (4) Comparative analysis of the time consumption of CDN requests for iOS and Android;

[0048] (5) Analysis of the distribution of CDN nodes in the same city;

[0049] (6) Scheduled tasks to monitor performance trends.

[0050] In the technical solution, step (1) completely records all data from the user initiating the request to the end of the response, including the user request URL, the user's IP address, the user's city, and whether the CDN cache is hit.

[0051] In the technical solution, when the request hits the CDN cache in step (1), the city where the CDN node is located, the network information used by the CDN node, etc. are analyzed through the request response header X-Cache-Lookup return value (such as: HIT from KS-CLOUD-BJ-CTT-11-07, HIT represents hit CDN, BJ is the city code, and CTT is the network operator code), which is used for statistical monitoring of CDN performance in various dimensions.

[0052] In the technical solution, in step (2), the overall CDN hit rate, average time consumption and the average time consumption of the CDN hit rate of each city are counted by city dimension.

[0053] In the technical solution, in step (3), statistics are collected to compare the average response time of each network operator in each time period in multiple cities.

[0054] In the technical solution, if the performance of a certain network used in step (3) is poor in the city, the information can be fed back to the CDN service provider to appropriately adjust the proportion of network usage by CDN nodes to improve response performance.

[0055] In the technical solution, in step (4), the average response time trends of IOS and Android in each time period are statistically compared. If there is a large difference in the average time consumption of the two ends, the cause can be promptly identified and the end with poor performance can be improved.

[0056] In the technical solution, in step (5), user requests from the same city will hit CDN nodes in multiple cities. The city where the CDN node is located is closer to the user and has priority access. Through statistical analysis of currently available data and based on the support of currently available statistical data, it is ensured that user requests from the same city will hit the CDN node in the city where they are located first.

[0057] In the present technical solution, in step (6), CDN performance trends are regularly monitored from various dimensions, the overall CDN hit rate and performance trends are monitored, more important cities are selected to detect hit rates and performance trends by city, various performance monitoring is performed according to the network operator dimension, and comparative performance monitoring is performed on both IOS and Android terminals.

[0058] In the present technical solution, in step (6), comparative analysis is performed from multiple dimensions such as month-on-month and year-on-year, and if fluctuations exceed the set threshold, an alarm is promptly issued to notify the relevant person in charge to follow up and investigate, so as to ensure the stability of service performance.

[0059] The above method is suitable for CDN performance monitoring. The statistical receiving data processing time is short and the CDN performance monitoring efficiency is high.

[0060] It will be apparent to those skilled in the art that the invention is not limited to the details of the exemplary embodiments described above and that the invention can be implemented in other specific forms without departing from the spirit or essential features of the invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description, and it is intended that all variations falling within the meaning and scope of the equivalent elements of the claims be included in the invention. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

[0061] In addition, it should be understood that although the present specification is described according to implementation modes, not every implementation mode contains only one independent technical solution. This description of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment may also be appropriately combined to form other implementation modes that can be understood by those skilled in the art.

Claims

1. A method for monitoring CDN performance, characterized in that: The monitoring method comprises the following steps: (1) User request log collection; (2) Analysis of CDN hit rate and average time consumption; (3) Performance analysis of CDN nodes using different network operators; (4) Comparative analysis of the time consumption of CDN requests for iOS and Android; (5) Analysis of the distribution of CDN nodes in the same city; (6) Scheduled tasks to monitor performance trends.

2. The CDN performance monitoring method according to claim 1, characterized in that: In the step (1), all data from the user initiating the request to the end of the response is completely recorded, including the user request URL, the user's IP address, the user's city, and whether the CDN cache is hit.

3. The CDN performance monitoring method according to claim 1, characterized in that: In step (1), when the request hits the CDN cache, the city where the CDN node is located, the network information used by the CDN node, etc. are analyzed through the request response header X-Cache-Lookup return value (such as: HIT from KS-CLOUD-BJ-CTT-11-07, HIT represents hit CDN, BJ is the city code, and CTT is the network operator code), which is used for statistical monitoring of CDN performance in various dimensions.

4. The CDN performance monitoring method according to claim 1, characterized in that: In the step (2), the overall CDN hit rate, average time consumption and the average time consumption of the CDN hit rate of each city are counted by city dimension.

5. The CDN performance monitoring method according to claim 1, characterized in that: In the step (3), statistics are collected to compare the average response time of each network operator in each time period in multiple cities.

6. The CDN performance monitoring method according to claim 1, characterized in that: In the step (3), if the performance of a certain network used in the city is poor, the performance can be fed back to the CDN service provider to appropriately adjust the proportion of network usage by CDN nodes to improve response performance.

7. The CDN performance monitoring method according to claim 1, characterized in that: In the step (4), the average response time trends of IOS and Android in each time period are statistically compared. If there is a large difference in the average time consumption of the two ends, the cause can be promptly identified and the end with poor performance can be improved.

8. The CDN performance monitoring method according to claim 1, characterized in that: In step (5), user requests in the same city will hit CDN nodes in multiple cities. In theory, the closer the city where the CDN node is located is to the user, the faster it should be and the priority access should be given. Through statistical analysis of the current existing data and based on the current statistical data support, it is recommended that CDN operators adjust their CDN distribution strategies and try to distribute user requests to the CDN nodes closest to the users.

9. The CDN performance monitoring method according to claim 1, characterized in that: In the step (6), CDN performance trends are monitored regularly from various dimensions, the overall CDN hit rate and performance trends are monitored, more important cities are selected to detect hit rates and performance trends by city, various performance monitoring is performed according to the network operator dimension, and IOS and Android dual-end comparative performance monitoring is performed.

10. The CDN performance monitoring method according to claim 1, characterized in that: In the step (6), a comparative analysis is performed from multiple dimensions such as month-on-month and year-on-year, and if fluctuations exceed the set threshold, an alarm is promptly issued to notify the relevant person in charge to follow up and investigate, so as to ensure the stability of service performance.

Images