Quality monitoring method and device, equipment, storage medium and computer program product

By evaluating the quality of the traffic data of the Internet online system through quality verification rules based on traffic element configuration, the problem of poor quality monitoring effect in the existing technology is solved, and fine-grained quality monitoring of complex scenarios is realized, and monitoring effect is improved.

CN118972288APending Publication Date: 2024-11-15BEIJING DIDI INFINITY TECH & DEV CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310545482.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-15
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The quality monitoring method of existing online Internet systems mainly relies on fixed quality monitoring thresholds set by experience, resulting in weak ability to discover problems, unable to meet the quality monitoring requirements of complex scenarios, and unable to achieve fine-grained quality verification, resulting in monitoring effects. Difference.

Method used

By obtaining the traffic data of the target monitoring time period, determining the quality verification rules based on the configuration of each traffic element, performing quality verification on the traffic data, supporting the quality monitoring requirements of complex scenarios, and achieving fine-grained quality verification.

Benefits of technology

It improves the quality monitoring effect of traffic data, enhances the ability to discover problems, meets the quality monitoring requirements of complex scenarios, and avoids poor monitoring effects caused by fixed quality monitoring thresholds in traditional technologies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118972288A_ABST
    Figure CN118972288A_ABST
Patent Text Reader

Abstract

The embodiment of the invention relates to a quality monitoring method and device, equipment, a storage medium and a computer program product. The method comprises the following steps: acquiring traffic data corresponding to a target monitoring time period, wherein the traffic data comprises a plurality of traffic elements; determining a quality verification rule corresponding to the traffic data, and performing quality verification on the traffic data by using the quality verification rule to obtain a quality monitoring result corresponding to the target monitoring time period; wherein the quality verification rule is configured based on each traffic element. By adopting the method, the monitoring effect of quality monitoring can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of Internet technology, and in particular, to a quality monitoring method, apparatus, device, storage medium, and computer program product. Background Art

[0002] The quality assurance method of the Internet online system is mainly achieved through monitoring and alarm. The monitoring and alarm method refers to the quality monitoring of the flow data of the target system. When the flow data is abnormal, the person in charge of the system is notified through some notification method.

[0003] In the related art, a quality monitoring threshold is usually set. The quality monitoring threshold is generally a specific value set based on experience. The flow data is compared with the quality monitoring threshold to monitor whether the flow data is abnormal.

[0004] However, the above quality monitoring method has the problem of poor monitoring effect. Summary of the invention

[0005] The embodiments of the present disclosure provide a quality monitoring method, apparatus, device, storage medium and computer program product, which can improve the monitoring effect of quality monitoring.

[0006] In a first aspect, an embodiment of the present disclosure provides a quality monitoring method, the method comprising:

[0007] Acquire flow data corresponding to a target monitoring time period, wherein the flow data includes a plurality of flow elements;

[0008] Determine a quality verification rule corresponding to the flow data, and use the quality verification rule to perform quality verification on the flow data to obtain a quality monitoring result corresponding to the target monitoring time period;

[0009] Wherein, the quality verification rule is configured based on each of the traffic elements.

[0010] In one embodiment, the amount of the flow data is multiple, and the quality verification of the flow data using the quality verification rule to obtain the quality monitoring result corresponding to the target monitoring time period includes:

[0011] Classify the traffic data according to the preset business scenarios to obtain target traffic data corresponding to the business scenarios;

[0012] The quality verification rule is used to perform quality verification on each of the target flow data to obtain the quality monitoring result.

[0013] In one embodiment, the flow data are classified according to preset business scenarios to obtain target flow data corresponding to each business scenario, including:

[0014] Determine a set of traffic elements corresponding to each of the business scenarios;

[0015] For each of the business scenarios, the traffic elements in the traffic element set are matched with the traffic elements included in each of the traffic data, and the traffic data with successful matching is used as the intermediate traffic data corresponding to the traffic element set;

[0016] The target flow data corresponding to the business scenario is obtained according to each successfully matched intermediate flow data.

[0017] In one embodiment, obtaining the target flow data corresponding to the business scenario according to each successfully matched intermediate flow data includes:

[0018] Each of the intermediate flow data is divided equally to obtain the target flow data corresponding to the business scenario, and the number of the target flow data is multiple.

[0019] In one embodiment, the quality verification of each target flow data using the quality verification rule to obtain the quality monitoring result includes:

[0020] For each of the business scenarios, the target quality verification rules corresponding to the business scenario are used to perform quality verification on the target traffic data corresponding to the business scenario to obtain the quality monitoring result.

[0021] In one of the embodiments, the target quality verification rule corresponding to the business scenario is used to perform quality verification on the target flow data corresponding to the business scenario to obtain the quality monitoring result, including:

[0022] Dividing the target quality verification rule into equal parts to obtain a plurality of sub-verification rules;

[0023] Performing quality verification on each of the sub-verification rules and the target flow data respectively to obtain verification results of each of the sub-verification rules;

[0024] Each of the verification results is used as the quality monitoring result corresponding to the business scenario.

[0025] In one embodiment, the quality verification of each of the sub-verification rules is performed on the target flow data to obtain the verification results of each of the sub-verification rules, including:

[0026] Performing a hash operation on the sub-check rule and the target traffic data to obtain a target hash value;

[0027] Searching in the cache whether there is a historical hash value that is the same as the target hash value;

[0028] If the historical hash value does not exist, the sub-verification rule is used to perform quality verification on the target traffic data to obtain a verification result of the sub-verification rule.

[0029] In one embodiment, the method further comprises:

[0030] If the historical Hash value exists, the verification result associated with the historical Hash value is used as the verification result of the sub-verification rule.

[0031] In one embodiment, the method further comprises:

[0032] The verification result of the target Hash value corresponding to the sub-verification rule is stored in a cache.

[0033] In one of the embodiments, for each of the business scenarios, using the target quality verification rule corresponding to the business scenario, performing quality verification on the target flow data corresponding to the business scenario to obtain the quality monitoring result includes:

[0034] According to the verification priority corresponding to the business scenario, using the target quality verification rule corresponding to the business scenario, performing quality verification on the target flow data corresponding to the business scenario to obtain the quality monitoring result;

[0035] Among them, the verification priorities of different business scenarios corresponding to the same calling interface are continuous in time sequence.

[0036] In one embodiment, obtaining the flow data corresponding to the target monitoring time period includes:

[0037] Recording initial traffic data within the target monitoring time period;

[0038] The initial flow data is converted into a flow format to obtain the flow data corresponding to the target monitoring time period.

[0039] In one embodiment, the method further comprises:

[0040] If the quality monitoring result is that the quality verification fails, a quality monitoring alarm message is output.

[0041] In a second aspect, an embodiment of the present disclosure provides a quality monitoring device, the device comprising:

[0042] An acquisition module, used to acquire flow data corresponding to a target monitoring time period, wherein the flow data includes a plurality of flow elements;

[0043] A monitoring module, used to determine a quality verification rule corresponding to the flow data, and perform quality verification on the flow data using the quality verification rule to obtain a quality monitoring result corresponding to the target monitoring time period;

[0044] Wherein, the quality verification rule is configured based on each of the traffic elements.

[0045] In a third aspect, an embodiment of the present disclosure provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in the first aspect when executing the computer program.

[0046] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method described in the first aspect above.

[0047] In a fifth aspect, an embodiment of the present disclosure provides a computer program product, including a computer program, which implements the method described in the first aspect when executed by a processor.

[0048] The quality monitoring method, apparatus, device, storage medium and computer program product provided by the embodiments of the present disclosure obtain the flow data corresponding to the target monitoring time period, and the flow data includes multiple flow elements. Then, the quality verification rules corresponding to the flow data are determined, and the quality verification rules are used to perform quality verification on the flow data to obtain the quality monitoring result corresponding to the target monitoring time period. The quality verification rules are configured based on each flow element. In this way, the embodiments of the present disclosure configure quality verification rules based on each flow element included in the flow data to perform quality verification on the flow data. The quality verification rules can cover any flow element, so as to support the quality monitoring requirements of complex scenarios and realize fine-grained quality verification, avoiding the problem of poor monitoring effect caused by the traditional technology that only sets a fixed quality monitoring threshold based on experience, and its ability to discover problems is weak, that is, the quality verification ability is weak, and it cannot meet the quality monitoring requirements of complex scenarios. The embodiments of the present disclosure improve the quality monitoring effect of flow data. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 An application environment diagram of a quality monitoring method in an embodiment;

[0050] Figure 2 A flow chart of a quality monitoring method in one embodiment;

[0051] Figure 3A schematic diagram of a process for obtaining a quality monitoring result corresponding to a target monitoring time period in another embodiment;

[0052] Figure 4 A schematic diagram of a process for obtaining target traffic data corresponding to a business scenario in another embodiment;

[0053] Figure 5 A schematic diagram of a process for obtaining a quality monitoring result corresponding to a target monitoring time period in another embodiment;

[0054] Figure 6 A flow chart of a quality monitoring method according to another embodiment;

[0055] Figure 7 A flow chart of a quality monitoring method according to another embodiment;

[0056] Figure 8 is a structural block diagram of a quality monitoring device in one embodiment;

[0057] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure more clear, the embodiments of the present disclosure are further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the embodiments of the present disclosure and are not used to limit the embodiments of the present disclosure.

[0059] First of all, before specifically introducing the technical solution of the embodiments of the present disclosure, the technical background or technical evolution context on which the embodiments of the present disclosure are based is introduced.

[0060] The quality assurance measures of Internet online systems are usually divided into two stages: offline and online. In the online stage, common quality assurance measures mainly include automation and monitoring and alarm methods. The monitoring and alarm method has become one of the most effective means because of its low construction cost and strong response capability.

[0061] The monitoring alarm method refers to quality monitoring of the flow data of the target system. Abnormal flow data indicates that the monitored target system has a fault. Therefore, when abnormal flow data occurs, the person in charge of the system is notified through some notification method.

[0062] In the related art, a quality monitoring threshold is usually set. The quality monitoring threshold is generally a specific value or a specific value range set based on experience. The flow data is compared with the quality monitoring threshold to monitor whether the flow data is abnormal.

[0063] However, the above-mentioned quality monitoring method, since it only sets fixed quality monitoring thresholds based on experience, has weak problem detection and quality verification capabilities, cannot meet the quality monitoring requirements of complex scenarios, and cannot achieve fine-grained quality verification, resulting in poor quality monitoring effects.

[0064] Taking the online car-hailing business as an example, the challenges of online quality assurance of the online car-hailing system mainly include the following three aspects: 1) The transaction scenarios of the online car-hailing business are extremely complex, with cross-correlations between different car models and different driver and passenger qualifications, forming complex transaction scenarios at the million level; 2) For a flow (data flow in the online car-hailing system, such as HTTP requests), the service call relationship is complex, with hundreds of downstream calls for a core main process interface; 3) The service availability requirements of the taxi-hailing scenario are very high, and failures in small scenarios will directly affect the driver and passenger experience and even the safety of the driver and passenger. In these complex scenarios with high quality assurance requirements, simply setting a fixed quality monitoring threshold to discover problems will not be able to expose problems in a timely manner, and fine-grained quality verification cannot be achieved, and the quality monitoring requirements of complex scenarios cannot be met.

[0065] In addition, it should be noted that the applicant has put in a lot of creative work in determining the reasons for the poor monitoring effect of quality monitoring and the technical solutions introduced in the following embodiments.

[0066] The technical solutions involved in the embodiments of the present disclosure are introduced below in combination with the scenarios to which the embodiments of the present disclosure are applied.

[0067] The quality monitoring method provided in the embodiment of the present disclosure can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. Taking the online car-hailing business as an example, the terminal 102 can be a terminal held by the driver (i.e., the driver's side) or a terminal held by the passenger (i.e., the passenger's side). The server 104 can obtain the traffic data corresponding to the target monitoring time period. The traffic data includes multiple traffic elements. The traffic data can refer to the full-link traffic data, for example, the data generated by the server 104 in response to the HTTP request sent by the terminal 102, or the data generated by the server 104 calling the downstream service, etc. The server 104 can determine the quality verification rules corresponding to the traffic data, and use the quality verification rules to perform quality verification on the traffic data to obtain the quality monitoring results corresponding to the target monitoring time period; wherein the quality verification rules are configured based on each traffic element.

[0068] The terminal 102 may be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented as an independent server or a server cluster consisting of multiple servers.

[0069] In one embodiment, Figure 2 As shown, a quality monitoring method is provided, which is applied to Figure 1 Taking the server in as an example, the following steps are included:

[0070] Step 201: The server obtains traffic data corresponding to a target monitoring time period.

[0071] There is a lot of traffic in the Internet system. Traffic refers to the data flow in the Internet system, such as HTTP requests. Taking the online car-hailing system as an example, the driver or passenger sends an HTTP request to the server to obtain the server's business response. For example, the passenger sends an HTTP request to the server to take a taxi. In response to the HTTP request, the server needs to generate a taxi order for the HTTP request and dispatch the taxi order until the taxi order is completed.

[0072] During the server response process, errors may occur in the response process or response results due to various reasons, which indicates that there is a fault in the online car-hailing system and an alarm message needs to be output in a timely manner. Therefore, it is necessary to monitor the quality of the server's response to the HTTP request after the server receives it to determine whether the server can successfully respond to the HTTP request.

[0073] Of course, during the business processing, the server will also call downstream services, and exceptions may occur in the process of calling the server's interface. Therefore, it is also necessary to monitor the quality of the server's calling process to determine whether the server's interface can be called sequentially, etc. In general, the quality monitoring of the embodiment of the present disclosure refers to quality monitoring of the entire traffic link.

[0074] In order to perform quality monitoring, in the embodiment of the present disclosure, the monitoring time period is first determined. The monitoring time period can be determined based on the actual quality monitoring needs. The monitoring time period can be any time period. For example, continuing to take the online car-hailing system as an example, the monitoring time period can be the morning peak time period, the evening peak time period, or the whole day time period, and so on.

[0075] The server obtains the traffic data corresponding to the target monitoring time period, which is the currently determined monitoring time period. The traffic data may refer to the full-link traffic data, for example, the data generated by the server responding to HTTP requests or the data generated by the server calling downstream services, etc.

[0076] In the disclosed embodiment, the traffic data may be obtained by recording the online traffic corresponding to the target monitoring time period, wherein traffic recording refers to the operation in which the server stores the input parameters, output parameters, downstream call input parameters and output parameters, dependency configuration, dependency storage and other information of the HTTP request of the response terminal.

[0077] During the target monitoring time period, the server performs traffic recording to obtain the above traffic data, which includes multiple traffic elements, namely the above-mentioned input parameters, output parameters, downstream call input parameters and output parameters, dependency configuration, dependency storage and other fields and their field values.

[0078] It can be understood that the traffic element can cover each key node of the entire traffic link, and the traffic data including multiple traffic elements can represent the complete process of the entire traffic link.

[0079] In step 202, the server determines a quality verification rule corresponding to the flow data, and performs a quality verification on the flow data using the quality verification rule to obtain a quality monitoring result corresponding to the target monitoring time period.

[0080] In the disclosed embodiment, the quality verification rule is configured based on each flow element. Exemplarily, the quality verification rule can be configured based on all flow elements included in the flow data, or the quality verification rule can be configured based on some flow elements included in the flow data.

[0081] In one possible implementation, the traffic elements on which the quality verification rules are based can be determined according to actual quality monitoring requirements. For example, if the input and output parameters of the HTTP request need to be verified, the quality verification rules can be configured based on the traffic element "input parameter" and the traffic element "output parameter".

[0082] In another possible implementation, the flow elements on which the quality verification rules are based can be determined according to the required quality verification granularity, and the size of the quality verification granularity is negatively correlated with the number of flow elements on which the quality verification rules are based, that is, the smaller the quality verification granularity, the greater the number of flow elements on which the quality verification rules are based, and so on.

[0083] In the embodiment of the present disclosure, the quality verification rules may include the fields corresponding to each traffic element and its field standard value. For example, the field standard value corresponding to the traffic element "input parameter" is "3", and the field standard value corresponding to the traffic element "output parameter" is "4".

[0084] In this way, after the server obtains the quality verification rules configured based on each traffic element, it uses the quality verification rules to perform quality verification on the traffic data. For example, the server can match the fields and their field standard values ​​corresponding to each traffic element included in the quality verification rules with the field values ​​of the corresponding fields in the traffic data for consistency, and the matching results of each field are the quality monitoring results.

[0085] If the field values ​​of each field in the traffic data are matched, the quality monitoring result corresponding to the target monitoring time period is determined to be quality verification passed.

[0086] The above-mentioned embodiment obtains the flow data corresponding to the target monitoring time period, and the flow data includes multiple flow elements. Then, the quality verification rules corresponding to the flow data are determined, and the quality verification rules are used to perform quality verification on the flow data to obtain the quality monitoring result corresponding to the target monitoring time period. The quality verification rules are configured based on each flow element. In this way, the embodiment of the present disclosure configures quality verification rules based on each flow element included in the flow data to perform quality verification on the flow data. The quality verification rules can cover any flow elements, so as to support the quality monitoring requirements of complex scenarios and realize fine-grained quality verification, avoiding the problem of poor monitoring effect caused by traditional technologies that only set fixed quality monitoring thresholds based on experience, have weak problem detection capabilities, that is, weak quality verification capabilities, and cannot meet the quality monitoring requirements of complex scenarios. The embodiment of the present disclosure improves the quality monitoring effect of flow data.

[0087] In one embodiment, based on Figure 2 The embodiment shown, see Figure 3 In this embodiment, the embodiment relates to how the server uses the quality verification rules to perform quality verification on the flow data and obtain the quality monitoring result corresponding to the target monitoring time period. Figure 3 As shown, the process includes step 301 and step 302:

[0088] Step 301: The server classifies each flow data according to a preset business scenario to obtain target flow data corresponding to each business scenario.

[0089] Step 302: The server performs quality verification on each target flow data using quality verification rules to obtain quality monitoring results.

[0090] In the embodiment of the present disclosure, there are multiple flow data corresponding to the target monitoring time period, and one flow data may refer to the full-link flow data for one flow.

[0091] After the server obtains multiple traffic data corresponding to the target monitoring time period, it can classify the multiple traffic data (or call it "traffic bucketing"). For example, the server can use a preset "bucketing algorithm" to classify the multiple traffic data and divide the multiple traffic data into multiple target traffic data. It can be understood that the target traffic data is one or more traffic data classified into the same category. Then, the server uses the quality verification rules to perform quality verification on each target traffic data to obtain the quality monitoring result.

[0092] The following describes the process of classifying each flow data by the server.

[0093] In the disclosed embodiment, the server may classify multiple flow data corresponding to a target monitoring time period according to a set business scenario, and obtain target flow data corresponding to each business scenario.

[0094] As an implementation method, for different business scenarios, in the entire traffic link, there must be differences in the processes such as the server responding to HTTP requests and the server calling downstream services. The traffic elements can cover all key nodes of the entire traffic link. Therefore, different business scenarios can be represented by their corresponding traffic element sets, that is, the business scenarios can be distinguished by the traffic element sets corresponding to each business scenario, and different business scenarios have different traffic element sets.

[0095] For example, the set of traffic elements corresponding to the business scenario "hailing a taxi at the airport" is different from the set of traffic elements corresponding to the business scenario "hailing a taxi in the city".

[0096] In this way, the server classifies each flow data according to the flow element set corresponding to each business scenario, and obtains the target flow data corresponding to each business scenario.

[0097] See also Figure 4 , the server can execute Figure 4 Steps 401, 402 and 403 shown in the figure implement the process of classifying each flow data according to the preset business scenario to obtain the target flow data corresponding to each business scenario:

[0098] Step 401: The server determines a set of traffic elements corresponding to each business scenario.

[0099] For each business scenario, optionally, the traffic element set corresponding to the business scenario may include all traffic elements included in the traffic data under the business scenario; optionally, the traffic element set corresponding to the business scenario may include some core traffic elements among all traffic elements included in the traffic data under the business scenario, and the core traffic elements may cover the key nodes that distinguish the current business scenario from other business scenarios.

[0100] For example, the calling interface corresponding to business scenario 1 is interface a, and the calling interface corresponding to business scenario 2 is interface b. Then the "calling interface" element in the traffic element set corresponding to business scenario 1 is interface a, and the "calling interface" element in the traffic element set corresponding to business scenario 2 is interface b, and so on.

[0101] Step 402: For each business scenario, the server matches the traffic elements in the traffic element set with the traffic elements included in each traffic data, and uses the successfully matched traffic data as the intermediate traffic data corresponding to the traffic element set.

[0102] For a business scenario, the server uses its corresponding traffic element set to match each traffic data. If the traffic elements in the traffic element set are all the same as the traffic elements included in a certain traffic data, it is determined that the traffic data is successfully matched with the traffic element set.

[0103] In this way, for each business scenario, multiple flow data belonging to the business scenario can be matched. For the convenience of description and to distinguish, the flow data belonging to the business scenario matched here is called intermediate flow data, that is, multiple intermediate flow data belonging to the business scenario are matched.

[0104] For example, for the carpooling scenario and special offer scenario under the online car-hailing express category, the corresponding traffic element sets are (input parameter business_id=3&downstream call input parameter combo_type=4), (input parameter business_id=3&downstream output parameter cap_price>0). In this way, by defining scenarios and classifying traffic data based on the traffic elements included in the traffic data, a more fine-grained division can be made for the massive online scenarios, thereby improving the sensitivity of quality verification for small scenarios.

[0105] Step 403: The server obtains target flow data corresponding to the business scenario based on each successfully matched intermediate flow data.

[0106] In a possible implementation, for a business scenario, the server may use the above-mentioned successfully matched intermediate flow data as the target flow data corresponding to the business scenario.

[0107] In another possible implementation, the server may divide each intermediate traffic data into equal parts to obtain target traffic data corresponding to the business scenario, where the number of target traffic data is multiple, thereby implementing the process of step 403.

[0108] Considering the large amount of intermediate traffic data, in order to improve the efficiency of quality verification, each intermediate traffic data can be divided equally (or called "evenly bucketed") to obtain multiple target traffic data corresponding to the business scenario.

[0109] In this way, for a business scenario, different target traffic data can be quality-checked in parallel, thereby improving the efficiency of quality verification.

[0110] Another implementation method for classifying each flow data by the server is briefly introduced below.

[0111] It can be understood that in the above-mentioned method of classifying each flow data, the calling interface is used as a flow element in the flow element set for flow element matching. In addition to matching each flow data with the calling interface in the flow element set, each flow data also needs to be matched with the remaining flow elements in the flow element set, and the classification speed is relatively low.

[0112] In view of this, in order to improve the speed of traffic data classification, each traffic data can also be directly classified according to the calling interface to obtain each target traffic data. As mentioned above, the target traffic data is one or more traffic data classified into the same category.

[0113] Then, the server uses the quality verification rules to perform quality verification on each target flow data to obtain the quality monitoring result.

[0114] In this way, by classifying the flow data corresponding to each target monitoring time period, and then performing quality verification on the collection of each classified flow data (ie, target flow data) in parallel, the efficiency of quality verification can be improved.

[0115] In one embodiment, based on Figure 3 The embodiment shown in the figure is related to how the server uses the quality verification rules to perform quality verification on each target flow data to obtain the quality monitoring result. Figure 5 As shown, step 302 includes Figure 5 Step 501 shown:

[0116] Step 501: For each business scenario, the server uses the target quality verification rules corresponding to the business scenario to perform quality verification on the target flow data corresponding to the business scenario to obtain a quality monitoring result.

[0117] The quality verification rules corresponding to different business scenarios are also different. The server can determine the target quality verification rules corresponding to each business scenario from the quality verification rules.

[0118] As described above, the quality verification rules are configured based on each traffic element. Therefore, for a business scenario, the target quality verification rules corresponding to the business scenario are configured based on each traffic element included in the target traffic data corresponding to the business scenario.

[0119] In this way, for each business scenario, the server can use the target quality verification rules belonging to the business scenario to perform quality verification on the target traffic data belonging to the business scenario, implement fine-grained quality verification, and obtain quality monitoring results.

[0120] In a possible implementation of step 501, step 501 may include the following steps A1, A2, and A3:

[0121] Step A1: The server divides the target quality verification rule into equal parts to obtain multiple sub-verification rules.

[0122] In the disclosed embodiment, in order to improve the efficiency of quality verification, for a business scenario, the server may equally divide the target quality verification rules belonging to the business scenario (or referred to as "rule bucketing") into multiple sub-verification rules.

[0123] As described above, for a business scenario, the target quality verification rule corresponding to the business scenario is configured based on each traffic element included in the target traffic data corresponding to the business scenario. Each traffic element can be all or part of the traffic elements included in the target traffic data corresponding to the business scenario. After the server obtains the filled-in value (the filled-in value refers to the type of traffic element involved in the configuration of the target quality verification rule), it first divides it into equal amounts, and then performs quality verification after division.

[0124] In step A2, the server performs quality verification on each sub-verification rule and the target flow data respectively to obtain the verification result of each sub-verification rule.

[0125] After the server divides the target quality verification rules corresponding to the business scenarios into equal parts, it then performs quality verification on each sub-verification rule and the target traffic data in parallel.

[0126] Exemplarily, as described in the above embodiments, for a business scenario, the target traffic data can be obtained by matching the intermediate traffic data corresponding to the target monitoring time period using the traffic element set corresponding to the business scenario, and then dividing the intermediate traffic data equally. The number of the target traffic data is multiple.

[0127] In this way, for this business scenario, multiple target traffic data and multiple sub-verification rules are finally divided. It can be understood that each sub-verification rule needs to perform quality verification on each target traffic data to obtain the verification results of each sub-verification rule. When each target traffic data is verified and passed for all sub-verification rules, that is, when all verification results are verified and passed, the quality verification of this business scenario is passed.

[0128] In step A3, the server uses each verification result as a quality monitoring result corresponding to the business scenario.

[0129] As an implementation method, for this business scenario, during the quality verification process, the server can run multiple rule verification tasks in parallel, each rule verification task picks up 1 target traffic data and 1 sub-verification rule, and each rule verification task starts parallel calculation.

[0130] Exemplarily, the rule verification task can call a library function to implement the matching process of quality verification: as mentioned above, matching refers to matching the fields and their field standard values ​​corresponding to each traffic element included in the sub-verification rule with the field values ​​of the corresponding fields in the target traffic data for consistency.

[0131] The matching results are as follows:

[0132] 1) If all fields and field values ​​match, it means that the online traffic matches the business scenario, and the execution continues until it ends.

[0133] 2) If the field matches but an error occurs in the field value matching, it indicates that the online traffic does not match the business scenario, and the rule verification task is exited.

[0134] 3) If the fields do not match, it indicates the current business scenario and there may be no traffic online during this target monitoring time period.

[0135] If all matches are passed, the quality monitoring result of the business scenario is that the quality verification passed; otherwise, the quality monitoring result of the business scenario is that the quality verification failed.

[0136] For a business scenario, after the quality verification of each target traffic data is completed, the quality monitoring results corresponding to the business scenario are stored in the database to achieve the reduction of the verification results.

[0137] In this way, the server buckets (i.e. divides) the recorded traffic data and the quality verification rules to which the traffic data belongs, so that the bucketed traffic data (i.e., target traffic data) and the bucketed quality verification rules (i.e., sub-verification rules) are evenly distributed in the quality monitoring task set. The rule verification task in the quality monitoring task set deduplicates the traffic and then picks up the target traffic data and sub-verification rules for quality verification. When the quality verification fails, the person in charge of the system is notified through an alarm, thereby achieving reliable monitoring of the traffic.

[0138] Another possible implementation of step A2 is introduced below.

[0139] As an implementation manner, step A2 may include the following steps B1, B2, B3, B4 and B5:

[0140] Step B1, the server performs a hash operation on the sub-verification rule and the target traffic data to obtain a target hash value.

[0141] In the disclosed embodiment, in order to avoid repeated calculations, each time the server verifies a pair of sub-verification rules and target traffic data, it performs a hash operation on the sub-verification rule and the target traffic data to obtain a target hash value, and then associates the target hash value with the verification result obtained from the quality verification and stores it in a cache.

[0142] In this way, during the quality verification, for each sub-verification rule and target traffic data to be verified, the server uses a hash algorithm to perform a hash operation on the sub-verification rule and the target traffic data to obtain a corresponding target hash value.

[0143] Step B2: The server searches the cache for a historical hash value that is the same as the target hash value.

[0144] Step B3: If there is no historical hash value, the server uses the sub-verification rule to perform quality verification on the target traffic data to obtain the verification result of the sub-verification rule.

[0145] If the historical hash value that is identical to the target hash value does not exist in the cache, it indicates that the server has not performed quality verification on the sub-verification rule to be verified and the target traffic data in the historical time. The server then performs the quality verification process, that is, uses the sub-verification rule to perform quality verification on the target traffic data to obtain the verification result of the sub-verification rule.

[0146] Step B4: If there is a historical hash value, the server uses the verification result associated with the historical hash value as the verification result of the sub-verification rule.

[0147] If there is a historical hash value that is the same as the target hash value in the cache, it means that the server has already performed quality verification on the sub-verification rule to be verified and the target traffic data at a historical time. In this way, the server does not have to repeat the quality verification, but directly uses the verification result associated with the historical hash value stored in the history as the verification result of the sub-verification rule.

[0148] Step B5: The server stores the verification result of the target hash value corresponding to the sub-verification rule in the cache.

[0149] Next, the server stores the verification result of the target hash value corresponding to the sub-verification rule in the cache, and deletes the historical hash value and the verification result associated with the historical hash value.

[0150] Alternatively, the server may also retain only historical hash values ​​and verification results associated with the historical hash values, thereby saving storage resources.

[0151] In another possible implementation of step 501, the server can also perform quality verification on the target traffic data corresponding to the business scenario according to the verification priority corresponding to the business scenario and use the target quality verification rules corresponding to the business scenario to obtain quality monitoring results, wherein the verification priorities of different business scenarios corresponding to the same calling interface are continuous in time sequence to implement the process of step 501.

[0152] Different calling interfaces correspond to different business scenarios, and the calling interfaces contained in different business scenarios may be the same or different.

[0153] In the disclosed embodiment, the server can continuously execute rule verification tasks for the same calling interface. For example, the business scenarios corresponding to calling interface a include business scenario 1 and business scenario 2. The verification priority corresponding to business scenario 1 is the first priority, and the verification priority corresponding to business scenario 2 is the second priority. The first priority and the second priority are continuous in time sequence. This ensures that the server continuously performs quality verification on business scenario 1 and business scenario 2, thereby continuously and quickly completing quality monitoring of the traffic data corresponding to calling interface a.

[0154] In addition, as mentioned above, in order to avoid repeated calculations, each time the server verifies a pair of sub-verification rules and target traffic data, it performs a hash operation on the sub-verification rule and the target traffic data to obtain a target hash value, and then associates the target hash value with the verification result obtained from this quality verification and stores it in the cache for subsequent rule verification task queries. In the embodiment of the present disclosure, for rule verification tasks of the same calling interface, the server can execute them continuously, and the data in the cache can be used continuously. After the verification of a calling interface is completed, the data in the cache is cleared and the calculation is restarted, which can save cache resources and avoid a reduction in the calculation speed due to excessive cache data.

[0155] In one embodiment, based on Figure 2 The embodiment shown, see Figure 6 This embodiment relates to the process of how the server obtains the flow data corresponding to the target monitoring time period. Figure 6 As shown, step 201 includes Figure 6 Step 601 and step 602 are shown:

[0156] Step 601: The server records initial traffic data within a target monitoring time period.

[0157] The initial traffic data can be obtained by recording the online traffic corresponding to the target monitoring time period by the server. Traffic recording refers to the operation in which the server stores the input parameters, output parameters, downstream call input parameters and output parameters, dependency configuration, dependency storage and other information of the HTTP request of the response terminal.

[0158] It should be noted that the types of traffic elements for traffic recording can be set according to the needs of quality monitoring. The richer the types of traffic elements, the more conducive it is to improving the effect of quality monitoring.

[0159] Step 602: The server converts the initial traffic data into a traffic format to obtain traffic data corresponding to a target monitoring time period.

[0160] The initial traffic data recorded by the server is a byte stream of the TCP (Transmission Control Protocol) layer. The server needs to convert the traffic format of the initial traffic data according to the protocol of the application layer to obtain traffic data that can be recognized by the application layer.

[0161] In a possible implementation, the server may also perform deduplication processing on the traffic data after the traffic format conversion to obtain the final traffic data corresponding to the target monitoring time period. The deduplication processing can avoid subsequent repeated calculations and improve computing efficiency.

[0162] Please continue to see Figure 6 The quality monitoring method of the disclosed embodiment also includes Figure 6 Step 603 shown:

[0163] Step 603: If the quality monitoring result is that the quality verification fails, the server outputs a quality monitoring alarm message.

[0164] In this way, timely output of quality monitoring alarm information can effectively remind relevant personnel to troubleshoot business failures and ensure the smooth progress of the business.

[0165] In one embodiment, a quality monitoring method is provided, the method comprising the following steps:

[0166] Step a: Record the initial traffic data within the target monitoring time period.

[0167] Step b: converting the initial flow data into a flow format to obtain flow data corresponding to the target monitoring time period.

[0168] There are multiple flow data, and each flow data includes multiple flow elements.

[0169] Step c: determine the set of traffic elements corresponding to each business scenario.

[0170] Step d: for each business scenario, the traffic elements in the traffic element set corresponding to the business scenario are matched with the traffic elements included in each traffic data, and the successfully matched traffic data is used as the intermediate traffic data corresponding to the traffic element set.

[0171] Step e: divide each intermediate flow data into equal parts to obtain target flow data corresponding to the business scenario, and the number of target flow data is multiple.

[0172] Step f: for each business scenario, the target quality verification rule corresponding to the business scenario is divided equally to obtain multiple sub-verification rules, and the target quality verification rule is configured based on each traffic element.

[0173] Step g, performing a hash operation on the sub-verification rule and the target traffic data to obtain a target hash value.

[0174] Step h, searching in the cache whether there is a historical hash value that is the same as the target hash value.

[0175] Step i: If there is no historical hash value, the target traffic data is quality checked using the sub-check rule to obtain the check result of the sub-check rule, and the check result of the target hash value corresponding to the sub-check rule is stored in the cache.

[0176] Step j: If there is a historical Hash value, the verification result associated with the historical Hash value is used as the verification result of the sub-verification rule.

[0177] Step k: use each verification result as the quality monitoring result corresponding to the business scenario.

[0178] Optionally, for each business scenario, the quality of the target traffic data corresponding to the business scenario can be verified according to the verification priority corresponding to the business scenario and using the target quality verification rules corresponding to the business scenario to obtain a quality monitoring result.

[0179] Among them, the verification priorities of different business scenarios corresponding to the same calling interface are continuous in time sequence.

[0180] Step 1: If the quality monitoring result is that the quality verification fails, a quality monitoring alarm message is output.

[0181] The following describes the implementation process of the quality monitoring method of the embodiment of the present disclosure in combination with the diagram. Figure 7 :

[0182] 1) The server first records the traffic flow and obtains the initial traffic data within the target monitoring time period.

[0183] 2) The server performs traffic analysis on the recorded initial traffic data and traffic preprocessing (i.e. traffic format conversion) on the initial traffic data to obtain the traffic data corresponding to the target monitoring time period. The number of traffic data is multiple, and each traffic data includes multiple traffic elements.

[0184] The traffic data is standardized traffic data.

[0185] 3) The server divides the standardized traffic data into traffic buckets.

[0186] Exemplarily, the server buckets traffic according to business scenarios. First, the server determines the traffic element set corresponding to each business scenario. For each business scenario, the server matches the traffic elements in the traffic element set corresponding to the business scenario with the traffic elements included in each traffic data, and then uses the successfully matched traffic data as the intermediate traffic data corresponding to the traffic element set; then, the server divides each intermediate traffic data equally to obtain target traffic data corresponding to the business scenario. There are multiple target traffic data, and each business scenario obtains a traffic set. The traffic combination includes multiple target traffic data.

[0187] 4) For each business scenario, the target quality verification rule corresponding to the business scenario is preprocessed (i.e., divided equally) to obtain multiple sub-verification rules. The target quality verification rule is configured based on each traffic element.

[0188] 5) The server performs rule matching to obtain quality monitoring results corresponding to the business scenario.

[0189] 6) If the quality monitoring result is that the quality verification fails, a quality monitoring alarm message is output.

[0190] In the disclosed embodiment, traffic bucketing is used to make traffic data enter traffic sets corresponding to different business scenarios. The target traffic data in the traffic set is matched one by one with multiple sub-check rules belonging to the business scenario. If an abnormality occurs, an alarm is triggered.

[0191] The bucketing rule can cover any traffic element, and the quality verification rule can also cover any traffic element. For example, for the carpooling scenario and the discount scenario under the online car-hailing express category, the corresponding traffic element sets are (input parameter business_id=3&downstream call input parameter combo_type=4), (input parameter business_id=3&downstream output parameter cap_price>0), and the quality verification rule can be assembled from the traffic elements of this business scenario. For example, the quality verification rule is output parameter total_fee=downstream service output parameter time_fee+distance_fee.

[0192] In this way, the traffic data is bucketed and quality checked based on the composition rules of the traffic elements itself, rather than a pre-set macro indicator. Fine-grained quality checks for fine scenes are completed through fine-grained traffic recording content, which makes it more capable of discovering problems. This avoids the drawback of the traditional technology of simply processing the indicator values ​​of all traffic and comparing them with the threshold, and failing to perform joint checks on other indicators of the traffic.

[0193] In addition, the disclosed embodiment can utilize distributed computing in the quality verification stage to divide the verification task data and reduce the results. During the parallel verification process, an operation unit is mainly responsible for matching the traffic data of the business scenario and the verification business expectations (i.e., quality verification rules) according to the instruction set. The specific calculation can be processed by calling the corresponding library function using the dynamic compilation method. Finally, the scheduling center issues an abnormal alarm for the reduction result according to the corresponding strategy, realizing reliable quality monitoring of online traffic.

[0194] It should be understood that although Figure 2-7 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2-7 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0195] In one embodiment, Figure 8 As shown, a quality monitoring device is provided, comprising:

[0196] An acquisition module 801 is used to acquire flow data corresponding to a target monitoring time period, wherein the flow data includes multiple flow elements;

[0197] A monitoring module 802 is used to determine a quality verification rule corresponding to the flow data, and perform quality verification on the flow data using the quality verification rule to obtain a quality monitoring result corresponding to the target monitoring time period;

[0198] Wherein, the quality verification rule is configured based on each of the traffic elements.

[0199] In one embodiment, the amount of the traffic data is multiple, and the monitoring module 802 includes:

[0200] A classification unit, used to classify each of the flow data according to a preset business scenario, and obtain target flow data corresponding to each of the business scenarios;

[0201] The verification unit is used to perform quality verification on each of the target flow data using the quality verification rule to obtain the quality monitoring result.

[0202] In one of the embodiments, the classification unit is specifically used to determine a set of traffic elements corresponding to each of the business scenarios; for each of the business scenarios, the traffic elements in the traffic element set are matched with the traffic elements included in each of the traffic data, and the successfully matched traffic data is used as the intermediate traffic data corresponding to the traffic element set; and the target traffic data corresponding to the business scenario is obtained based on each of the successfully matched intermediate traffic data.

[0203] In one of the embodiments, the classification unit is specifically used to divide each of the intermediate flow data into equal amounts to obtain the target flow data corresponding to the business scenario, and the number of the target flow data is multiple.

[0204] In one of the embodiments, the verification unit is specifically used to perform quality verification on the target flow data corresponding to the business scenario for each of the business scenarios using the target quality verification rules corresponding to the business scenario to obtain the quality monitoring result.

[0205] In one of the embodiments, the verification unit is specifically used to divide the target quality verification rule into equal parts to obtain multiple sub-verification rules; perform quality verification on each of the sub-verification rules and the target traffic data respectively to obtain verification results of each of the sub-verification rules; and use each of the verification results as the quality monitoring results corresponding to the business scenario.

[0206] In one of the embodiments, the verification unit is specifically used to perform a hash operation on the sub-verification rule and the target traffic data to obtain a target hash value; search the cache for a historical hash value that is the same as the target hash value; if the historical hash value does not exist, perform a quality verification on the target traffic data using the sub-verification rule to obtain a verification result of the sub-verification rule.

[0207] In one of the embodiments, the verification unit is further configured to use the verification result associated with the historical Hash value as the verification result of the sub-verification rule if the historical Hash value exists.

[0208] In one of the embodiments, the verification unit is further configured to store a verification result of the target Hash value corresponding to the sub-verification rule in a cache.

[0209] In one of the embodiments, the verification unit is specifically used to perform quality verification on the target traffic data corresponding to the business scenario according to the verification priority corresponding to the business scenario and using the target quality verification rule corresponding to the business scenario to obtain the quality monitoring result; wherein the verification priorities of different business scenarios corresponding to the same calling interface are continuous in time sequence.

[0210] In one of the embodiments, the acquisition module 801 is specifically used to record the initial flow data within the target monitoring time period; perform flow format conversion on the initial flow data to obtain the flow data corresponding to the target monitoring time period.

[0211] In one embodiment, the device further comprises:

[0212] The alarm module is used to output quality monitoring alarm information if the quality monitoring result is that the quality verification fails.

[0213] For the specific definition of the quality monitoring device, please refer to the definition of the quality monitoring method above, which will not be repeated here. Each module in the above-mentioned quality monitoring device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the electronic device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0214] Fig. 9 1 is a block diagram of a computer device 1400 according to an exemplary embodiment, and the computer device may be a server. Fig. 9 The computer device 1400 includes a processing component 1420, which further includes one or more processors, and a memory resource represented by a memory 1422 for storing instructions or computer programs, such as applications, that can be executed by the processing component 1420. The application stored in the memory 1422 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1420 is configured to execute the instructions to perform the above-mentioned quality monitoring method.

[0215] The computer device 1400 may also include a power supply component 1424 configured to perform power management of the device 1400, a wired or wireless network interface 1426 configured to connect the device 1400 to a network, and an input / output (I / O) interface 1428. The computer device 1400 may operate based on an operating system stored in the memory 1422, such as Windows 1414ServerTM, Mac O14XTM, UnixTM, LinuxTM, FreeB14DTM or the like.

[0216] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 1422 including instructions, which can be executed by a processor of the computer device 1400 to perform the above method. The storage medium can be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0217] In an exemplary embodiment, a computer program product is also provided, and when the computer program is executed by a processor, the above method can be implemented. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, part or all of the above method can be implemented in whole or in part according to the process or function described in the embodiment of the present disclosure.

[0218] It should be noted that the solutions described in this specification and the embodiments, if they involve the processing of personal information, will be processed on the premise of having a legal basis (such as obtaining the consent of the subject of personal information, or being necessary for the performance of a contract, etc.), and will only be processed within the scope of regulations or agreements. If a user refuses to process personal information other than the necessary information for basic functions, it will not affect the user's use of basic functions.

[0219] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in the embodiments of the present disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0220] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0221] The above-described embodiments only express several implementation methods of the embodiments of the present disclosure, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for those of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the embodiments of the present disclosure, and these all belong to the protection scope of the embodiments of the present disclosure. Therefore, the protection scope of the patent of the embodiments of the present disclosure shall be subject to the attached claims.

Claims

1. A quality monitoring method, characterized in that: The method comprises: Acquire flow data corresponding to a target monitoring time period, wherein the flow data includes a plurality of flow elements; Determine a quality verification rule corresponding to the flow data, and use the quality verification rule to perform quality verification on the flow data to obtain a quality monitoring result corresponding to the target monitoring time period; Wherein, the quality verification rule is configured based on each of the traffic elements.

2. The method according to claim 1, characterized in that The number of the flow data is multiple, and the quality verification of the flow data is performed using the quality verification rule to obtain the quality monitoring result corresponding to the target monitoring time period, including: Classify the traffic data according to the preset business scenarios to obtain target traffic data corresponding to the business scenarios; The quality verification rule is used to perform quality verification on each of the target flow data to obtain the quality monitoring result.

3. The method according to claim 2, characterized in that The flow data are classified according to the preset business scenarios to obtain the target flow data corresponding to the business scenarios, including: Determine a set of traffic elements corresponding to each of the business scenarios; For each of the business scenarios, the traffic elements in the traffic element set are matched with the traffic elements included in each of the traffic data, and the traffic data with successful matching is used as the intermediate traffic data corresponding to the traffic element set; The target flow data corresponding to the business scenario is obtained according to each successfully matched intermediate flow data.

4. The method according to claim 3, characterized in that The acquiring the target flow data corresponding to the business scenario according to each of the successfully matched intermediate flow data includes: Each of the intermediate flow data is divided equally to obtain the target flow data corresponding to the business scenario, and the number of the target flow data is multiple.

5. The method according to claim 2, characterized in that: The quality verification of each target flow data using the quality verification rule to obtain the quality monitoring result includes: For each of the business scenarios, the target quality verification rules corresponding to the business scenario are used to perform quality verification on the target traffic data corresponding to the business scenario to obtain the quality monitoring result.

6. The method according to claim 5, characterized in that The using the target quality verification rule corresponding to the business scenario to perform quality verification on the target flow data corresponding to the business scenario to obtain the quality monitoring result includes: Dividing the target quality verification rule into equal parts to obtain a plurality of sub-verification rules; Performing quality verification on each of the sub-verification rules and the target flow data respectively to obtain verification results of each of the sub-verification rules; Each of the verification results is used as the quality monitoring result corresponding to the business scenario.

7. The method according to claim 6, characterized in that The quality verification of each of the sub-verification rules is performed on the target flow data respectively to obtain the verification results of each of the sub-verification rules, including: Performing a hash operation on the sub-check rule and the target traffic data to obtain a target hash value; Searching in the cache whether there is a historical hash value that is the same as the target hash value; If the historical hash value does not exist, the sub-verification rule is used to perform quality verification on the target traffic data to obtain a verification result of the sub-verification rule.

8. The method according to claim 7, characterized in that The method further comprises: If the historical Hash value exists, the verification result associated with the historical Hash value is used as the verification result of the sub-verification rule.

9. The method according to claim 7, characterized in that: The method further comprises: The verification result of the target Hash value corresponding to the sub-verification rule is stored in a cache.

10. The method according to claim 5, characterized in that For each of the business scenarios, using the target quality verification rule corresponding to the business scenario, performing quality verification on the target flow data corresponding to the business scenario to obtain the quality monitoring result, including: According to the verification priority corresponding to the business scenario, using the target quality verification rule corresponding to the business scenario, performing quality verification on the target flow data corresponding to the business scenario to obtain the quality monitoring result; Among them, the verification priorities of different business scenarios corresponding to the same calling interface are continuous in time sequence.

11. The method according to any one of claims 1 to 10, characterized in that: The obtaining of the flow data corresponding to the target monitoring time period includes: Recording initial traffic data within the target monitoring time period; The initial flow data is converted into a flow format to obtain the flow data corresponding to the target monitoring time period.

12. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: If the quality monitoring result is that the quality verification fails, a quality monitoring alarm message is output.

13. A quality monitoring device, characterized in that: The device comprises: An acquisition module, used to acquire flow data corresponding to a target monitoring time period, wherein the flow data includes a plurality of flow elements; A monitoring module, used to determine a quality verification rule corresponding to the flow data, and perform quality verification on the flow data using the quality verification rule to obtain a quality monitoring result corresponding to the target monitoring time period; Wherein, the quality verification rule is configured based on each of the traffic elements.

14. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 12 are implemented.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

16. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.