Buried point detection method and device and computing equipment
By receiving the service buried point parameters sent by the buried point component, requesting the status information of the target service from the service system, updating the status identification of the target service, and detecting whether the status identification is abnormal when the service exit notification is notified, the problem of lack of efficient buried point abnormal detection in the prior art is solved, and fast and accurate abnormal detection is achieved, ensuring data credibility and decision-making accuracy.
Patent Information
- Application Number
- CN202510073253.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-16
- Publication Date
- 2025-05-13
AI Technical Summary
The lack of efficient detection methods for buried point abnormalities in the prior art, which leads to untrustworthy data, which in turn affects decision-making accuracy.
By receiving the service buried point parameters sent by the buried point component, requesting the status information of the target service from the service system, updating the status identification of the target service, and detecting whether the status identification is abnormal when the service exit notification is notified to determine whether an abnormality occurred in the buried point.
It realizes the rapid and accurate judgment of whether abnormalities occur in the buried points of the target business, improves the efficiency of the buried points abnormal detection, and ensures the credibility of data and the accuracy of decision-making.
Smart Images
Figure CN119988197A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and specifically to a method, device, computing equipment, computer storage medium and computer program product for detecting buried points. Background Art
[0002] Tracking is a data collection technology that is mainly used to track user behavior on websites or applications. Generally, one behavior corresponds to one tracking point, which mainly counts the start, end, duration and other parameters of the behavior.
[0003] Tracking is often used for statistical analysis of mobile data. Tracking anomalies can lead to unreliable data and thus incorrect decisions. For example, to calculate the success rate of a behavior, it is necessary to use the number of successes, starts, and cancellations of the tracking of the behavior. If the tracking data is lost, the success rate indicator will be inaccurate. Based on this, it is necessary to detect whether the tracking is abnormal. There is no efficient method for detecting tracking anomalies in the prior art. Summary of the invention
[0004] In view of the above problems, the present application is proposed to provide a method, apparatus, computing device, computer storage medium and computer program product for detecting buried points that overcome the above problems or at least partially solve the above problems.
[0005] According to one aspect of the present application, a method for detecting buried points is provided, comprising:
[0006] Receiving business tracking point parameters sent by the tracking point component in response to the tracking point report of the business event;
[0007] According to the business tracking point parameters, request the business system for the status information of the target business corresponding to the business event;
[0008] Update the status identifier of the target business according to the status information of the target business;
[0009] Receive business exit notification sent by the business system;
[0010] According to the status identifier of the target business, detect whether there is any abnormality in the tracking point of the target business.
[0011] Optionally, updating the state identifier of the target service according to the state information of the target service further includes:
[0012] If the state information indicates that the target service is in the start state, performing a first update process on the state identifier of the target service;
[0013] If the status information indicates that the target service is in the end state, a second update process is performed on the status identifier of the target service.
[0014] Optionally, before the method is executed, the method further includes:
[0015] Receive registration request sent by business system;
[0016] Constructing a state data body; wherein the business identifier and state identifier of the target business are recorded in the state data body;
[0017] Updating the status identifier of the target service further includes:
[0018] The state identifier corresponding to the business identifier of the target business recorded in the state data body is updated.
[0019] Optionally, constructing the state data body further includes:
[0020] Requesting the business system for sub-step business information, and judging whether the business provided by the business system includes multiple sub-step businesses according to the request result;
[0021] If yes, construct a state data body for recording the business identifiers and state identifiers of the multiple sub-step businesses;
[0022] Updating the state identifier of the target service according to the state information of the target service further includes:
[0023] If the target service is any sub-step service in the services provided by the service system, the status identifier corresponding to the service identifier of the sub-step service recorded in the status data body is updated.
[0024] Optionally, the service identifier of the sub-step service is determined according to the global service identifier and the step identifier of the sub-step service.
[0025] Optionally, performing a first update process on the state identifier of the target service further includes:
[0026] Adding a preset value to the state identifier corresponding to the service identifier of the target service recorded in the state data body to obtain an updated state identifier of the target service;
[0027] The second updating process of the state identifier of the target service further includes:
[0028] Subtracting a preset value from the state identifier corresponding to the service identifier of the target service recorded in the state data body to obtain an updated state identifier of the target service;
[0029] According to the status identifier of the target business, detecting whether an abnormality occurs in the tracking point of the target business further includes:
[0030] Check whether the status identifier corresponding to the business identifier of the target business recorded in the status data body is the default value;
[0031] If so, it is determined that no abnormality occurs in the tracking point of the target business; if not, it is determined that an abnormality occurs in the tracking point of the target business.
[0032] According to another aspect of the present application, a buried point detection device is provided, comprising:
[0033] A receiving module, adapted to receive business tracking point parameters sent by the tracking point component in response to the tracking point report of the business event;
[0034] The request module is adapted to request the status information of the target business corresponding to the business event from the business system according to the business tracking point parameters;
[0035] An updating module, adapted to update a state identifier of a target service according to the state information of the target service;
[0036] The detection module is suitable for receiving the business exit notification sent by the business system; according to the state identifier of the target business, it detects whether the embedding point of the target business is abnormal.
[0037] Optionally, the update module is further adapted to:
[0038] If the state information indicates that the target service is in the start state, performing a first update process on the state identifier of the target service;
[0039] If the status information indicates that the target service is in the end state, a second update process is performed on the status identifier of the target service.
[0040] Optionally, the device further comprises:
[0041] A registration module, adapted to receive a registration request sent by a business system; construct a state data body; wherein the business identifier and state identifier of the target business are recorded in the state data body;
[0042] The update module is further adapted to:
[0043] The state identifier corresponding to the business identifier of the target business recorded in the state data body is updated.
[0044] Optionally, the registration module is further adapted to:
[0045] Requesting the business system for sub-step business information, and judging whether the business provided by the business system includes multiple sub-step businesses according to the request result;
[0046] If yes, construct a state data body for recording the business identifiers and state identifiers of the multiple sub-step businesses;
[0047] The updating module is further adapted to update the state identifier corresponding to the service identifier of the sub-step service recorded in the state data body if the target service is any sub-step service in the service provided by the service system.
[0048] Optionally, the service identifier of the sub-step service is determined according to the global service identifier and the step identifier of the sub-step service.
[0049] Optionally, the update module is further adapted to:
[0050] Adding a preset value to the state identifier corresponding to the service identifier of the target service recorded in the state data body to obtain an updated state identifier of the target service;
[0051] Subtracting a preset value from the state identifier corresponding to the service identifier of the target service recorded in the state data body to obtain an updated state identifier of the target service;
[0052] The detection module is further adapted to: detect whether the status identifier corresponding to the service identifier of the target service recorded in the status data body is a default value; if so, determine that no abnormality has occurred in the burying point of the target service; if not, determine that an abnormality has occurred in the burying point of the target service.
[0053] According to another aspect of the present application, there is provided a computing device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus;
[0054] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the above-mentioned buried point detection method.
[0055] According to another aspect of the present application, a computer storage medium is provided, wherein the storage medium stores at least one executable instruction, and the executable instruction enables a processor to perform operations corresponding to the above-mentioned buried point detection method.
[0056] According to another aspect of the present application, a computer program product is provided, comprising at least one executable instruction, wherein the executable instruction enables a processor to perform operations corresponding to the above-mentioned buried point detection method.
[0057] According to the buried point detection method, device, computing equipment, computer storage medium and computer program product provided in the embodiments of the present application, the business buried point parameters sent by the buried point component in response to the buried point reporting of the business event are received; based on the business buried point parameters, the status information of the target business corresponding to the business event is requested from the business system; based on the status information of the target business, the status identifier of the target business is updated; the business exit notification sent by the business system is received; based on the status identifier of the target business, whether the buried point of the target business is abnormal is detected. Through the above method, the status identifier of the target business is updated according to the status of the target business when the buried point is reported, the buried point reporting situation of the target business can be recorded through the status identifier, and whether the buried point of the target business is abnormal can be quickly and accurately determined based on the status identifier, so that efficient buried point abnormality detection can be achieved.
[0058] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0059] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:
[0060] Figure 1 A flow chart of a buried point detection method provided by an embodiment of the present application is shown;
[0061] Figure 2 A flowchart of a buried point detection method provided by another embodiment of the present application is shown;
[0062] Figure 3 A flowchart of a buried point detection method provided by another embodiment of the present application is shown;
[0063] Figure 4 A functional structure diagram of a buried point detection device provided in an embodiment of the present application is shown;
[0064] Figure 5 A schematic diagram of the structure of a computing device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION
[0065] The exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.
[0066] First, the terms involved in one or more embodiments of the present application are explained.
[0067] Map: A data structure used to store key-value pairs. Each key is unique and can be used to find the corresponding value. Map can be thought of as an associative array or mapping table that maintains the association of key-value pairs so that values can be quickly found by key.
[0068] Tracking: is a data collection technology that is mainly used to track user behavior on websites or applications. Each tracking point corresponds to a specific behavioral event. When the event occurs, the system automatically records the relevant information, which can then be used to analyze user usage patterns, evaluate functional effects, or optimize user experience.
[0069] Figure 1 The flowchart of the buried point detection method provided by an embodiment of the present application is shown. In order to facilitate the description of the interaction process of the method, the execution subject of the method of the embodiment of the present application is referred to as a detection system. Figure 1 As shown, the method comprises the following steps:
[0070] Step S110, receiving business tracking point parameters sent by the tracking point component in response to the tracking point reporting of the business event.
[0071] When the status of a service changes, a corresponding service event is triggered. For example, in a video service scenario, the service system will execute a video generation service to generate videos for users. When the video generation service starts executing, a video service start event is triggered, and when the video generation service ends executing, a video service end event is triggered.
[0072] The tracking component reports the tracking points in response to business events, that is, reports the business tracking point parameters to the server, and at the same time, sends the business tracking point parameters to the detection system.
[0073] Step S120: Request the business system for status information of the target business corresponding to the business event according to the business tracking point parameters.
[0074] Business tracking parameters include business system information and business information, and can also include other parameters, such as the type of business event, duration, user operation type, etc.
[0075] The detection system determines the business system according to the business system information, and determines the target business according to the business information, so as to request the state information of the target business from the business system. The state of the target business includes the start state and the end state. If the target business is successfully executed, the target business is cancelled, or the target business fails to execute, the state of the target business is the end state.
[0076] Step S130: updating the state identifier of the target service according to the state information of the target service.
[0077] The state identifier is used to indicate the state of the target service. The state identifier of the target service is updated according to the acquired state information of the target service. When the acquired state information of the target service is inconsistent, the update method of the state identifier of the target service is also inconsistent.
[0078] Step S140: receiving a service exit notification sent by the service system.
[0079] Specifically, when a user leaves a service provided by the service system, a service exit request is triggered. The service system sends a service exit notification to the detection system in response to the service exit request, and the detection system receives the service exit notification sent by the service system.
[0080] Step S150, based on the status identifier of the target business, detect whether an abnormality occurs in the embedding point of the target business.
[0081] The detection system performs point-of-sale abnormality detection in response to the received service exit notification. Since the status identifier of the target service is updated according to the status of the target service each time the point-of-sale is reported, it is possible to determine whether the point-of-sale of the target service is abnormal, that is, whether the point-of-sale data is lost, based on the final status identifier of the target service.
[0082] To summarize, according to the burying point detection method provided in this embodiment, the business burying point parameters sent by the burying point component in response to the burying point reporting of the business event are received; according to the business burying point parameters, the status information of the target business corresponding to the business event is requested from the business system; according to the status information of the target business, the status identifier of the target business is updated; the business exit notification sent by the business system is received; according to the status identifier of the target business, whether the burying point of the target business is abnormal is detected; through the above method, the status identifier of the target business is updated according to the status of the target business when the burying point is reported, the burying point reporting situation of the target business can be recorded through the status identifier, and whether the burying point of the target business is abnormal can be quickly and accurately determined according to the status identifier, thereby realizing efficient burying point anomaly detection.
[0083] Figure 2The flowchart of the buried point detection method provided by another embodiment of the present application is shown. In order to facilitate the description of the interaction process of the method, the execution subject of the method of the embodiment of the present application is referred to as a detection system. Figure 2 As shown, the method comprises the following steps:
[0084] Step S210: receiving a registration request sent by the business system.
[0085] Specifically, the business system sends a registration request in response to a specified business event, and the business system starts to execute the business after the user enters the business. When the business system detects the specified business event, it sends a registration request to the detection system.
[0086] It should be noted that when the service provided by the business system contains multiple sub-step services, executing the service means executing each sub-step service contained in the service, and each sub-step service needs to be reported.
[0087] A designated business event refers to the first business event triggered by the start of business execution. If the business system provides a business that includes multiple sub-step businesses, the designated business event is specifically the business event triggered when the first sub-step business starts executing; if the business system does not include any sub-step businesses, the designated business event is the business event triggered when the business starts executing.
[0088] Step S220, constructing a state data body.
[0089] In response to the received registration request, the detection system constructs a state data body for recording the service identifier and the state identifier, where the service identifier is a unique identifier of the service.
[0090] When constructing the state data body, the state identifier is set to the default value, and the state identifier is updated in the subsequent process according to the state changes of the business.
[0091] Furthermore, the specific implementation of step S220 is as follows: requesting the business system for sub-step business information, and judging whether the business provided by the business system includes multiple sub-step businesses according to the request result; if so, constructing a state data body for recording the business identifiers and state identifiers of multiple sub-step businesses; wherein, the business provided by the business system may be composed of multiple sub-step businesses. The detection system asks the business system whether it provides multiple sub-step businesses and the specific information of the sub-step businesses. If the business system provides a business including multiple sub-step businesses, the constructed state data body is used to record the business identifiers and state identifiers of each sub-step business, so as to record the buried point reporting situation of each sub-step business.
[0092] In an optional manner, the service identifier of the sub-step service is determined based on the global service identifier and the step identifier of the sub-step service. For example, the global service identifier and the step identifier of the sub-step service (such as the sequence number of the sub-step service) are combined as the service identifier of the sub-step service, and the global service identifier is generated during the process of constructing the state data body.
[0093] In an optional manner, a specific implementation of constructing a state data body includes the following steps:
[0094] Step S2201: receiving a registration request sent by a business system in response to a specified business event, generating a global business identifier, constructing a state data body, setting the state identifier to 0 (default value), and recording the global business identifier and the state identifier in the state data body;
[0095] Step S2202: Request sub-step business information from the business system;
[0096] Step S2203: judging whether the business system provides a business including multiple sub-steps according to the requested sub-step business information;
[0097] Step S2204: If yes, the data structure of the status data body is updated. Specifically, a business identifier is generated for each sub-step business, the status identifier of each sub-step business is set to 0, and recorded in the status data body. The updated status data body is a structure for recording the business identifiers and status identifiers of multiple sub-step businesses.
[0098] For example, after the user enters the business, the business system starts to execute the business, the business system sends a registration request to the detection system, and the detection system builds a state data body. At this time, the data recorded in the state data body is: {EventID1:0}, EventID1 is the global business identifier, and 0 is the state identifier.
[0099] Afterwards, the business system is asked for sub-step business information. If it is determined based on the sub-step business information that the business system provides a business that includes three sub-step businesses, the structure of the status data body is updated. The updated status data body records the following data: {EventID1:{StepID 1:0, StepID 2:0, StepID 3:0}}, where StepID 1, StepID2, and StepID 3 are the step identifiers of the three sub-step businesses respectively, and the combination of the global business identifier and the step identifier is the unique identifier of the sub-step business. 0 is the status identifier, and the status identifier will be updated according to the status of the sub-step business in the subsequent process.
[0100] In addition, if it is determined based on the sub-step business information that the business provided by the business system does not contain any sub-step business, there is no need to update the state data body constructed in the previous step. During the entire business execution period, only one global business identifier will be generated, and the state identifier corresponding to the global business identifier will be updated according to the state changes of the business.
[0101] In an optional manner, the data structure of the state data body is a Map structure, wherein the key is used to record the service identifier and the value is used to record the state identifier.
[0102] Step S230, receiving the business tracking point parameters sent by the tracking point component in response to the tracking point reporting of the business event.
[0103] The tracking component may be set in the business system. The corresponding business events are triggered when the target business starts and ends. The tracking component responds to the business events and reports the business tracking parameters to the server. At the same time, the business tracking parameters are also sent to the detection system.
[0104] Step S240: Request the business system for status information of the target business corresponding to the business event according to the business tracking point parameters.
[0105] Business tracking parameters include business system information and business information, and can also include other parameters, such as the type of business event, duration, user operation type, etc.
[0106] The detection system determines the business system according to the business system information, and determines the target business according to the business information, so as to request the state information of the target business from the business system. The state of the target business includes the start state and the end state. If the target business is successfully executed, the target business is cancelled, or the target business fails to execute, the state of the target business is the end state.
[0107] Step S250: updating the state identifier corresponding to the service identifier of the target service recorded in the state data body according to the state information of the target service.
[0108] The service identifier and status identifier of the target service are recorded in the status data body.
[0109] Specifically, if the state information indicates that the target service is in the start state, the state identifier of the target service is first updated; if the state information indicates that the target service is in the end state, the state identifier of the target service is second updated. The first update process and the second update process are different update methods.
[0110] The first update processing of the status identifier of the target business further includes: adding a preset value to the status identifier corresponding to the business identifier of the target business recorded in the status data body to obtain the updated status identifier of the target business; accordingly, the second update processing of the status identifier of the target business further includes: subtracting the preset value from the status identifier corresponding to the business identifier of the target business recorded in the status data body to obtain the updated status identifier of the target business.
[0111] Under normal circumstances, when the target business starts, a business event is triggered, and the tracking component reports the business tracking parameters and sends the business tracking parameters to the detection system. After receiving the business tracking parameters, the detection system requests the status information of the corresponding target business from the business system. The status information indicates that the target business starts. At this time, the state identifier of the target business is the default value 0. The state identifier at this time is added by 1 (preset value), and the updated state identifier is 1. When the target business ends, a business event is triggered, and the tracking component reports the business tracking parameters and sends the business tracking parameters to the detection system. After receiving the business tracking parameters, the detection system requests the status information of the target business from the business system. The status information indicates that the target business ends. At this time, the state identifier of the target business is 1. The state identifier at this time is subtracted by 1 (preset value), and the updated state identifier is 0. It can be seen that when a business starts and ends normally and a correct and complete tracking report is performed, its final state identifier is the default value. Therefore, when the user exits the business, it can be determined whether the tracking is abnormal based on the state identifier.
[0112] In addition, if the target service is any sub-step service in the service provided by the service system, the status identifier corresponding to the service identifier of the sub-step service recorded in the status data body is updated. In the case that the service provided by the service system does not include any sub-step service, the target service is also the service provided by the service system, and the service identifier of the target service is equal to the global service identifier, then the status identifier corresponding to the global service identifier is updated.
[0113] Step S260: receiving a service exit notification sent by the service system.
[0114] Specifically, the business system sends a business exit notification in response to a business exit request from a user. When receiving a business exit request from a user, the business system sends a business exit notification to the detection system.
[0115] Step S270, detect whether the status identifier corresponding to the business identifier of the target business recorded in the status data body is the default value, and obtain the buried point anomaly detection result.
[0116] Specifically, if the status identifier corresponding to the business identifier of the target business is the default value, it is determined that no abnormality has occurred in the burying point of the target business; if the status identifier corresponding to the business identifier of the target business is not the default value, it is determined that an abnormality has occurred in the burying point of the target business.
[0117] In response to the received service exit notification, a tracking point anomaly detection is performed. Specifically, it is detected whether the current status identifier of the target service recorded in the status data body is the default value; if so, it indicates that the tracking point was reported at the beginning of the target service and at the end of the target service, and it is determined that there is no abnormality in the tracking point of the target service; if they are inconsistent, it indicates that the tracking point was not reported at the beginning or end of the target service, and there is tracking point data loss in the target service, and it is determined that there is an abnormality in the tracking point of the target service.
[0118] In addition, when the service provided by the business system includes multiple sub-step services, the status identifiers of the multiple sub-step services of the service are recorded in the status data body. If the status identifier of each sub-step service is the default value, it is determined that there is no abnormality in the tracking point of the service provided by the business system; if there is at least one sub-step service whose status identifier is not the default value, it is determined that there is an abnormality in the tracking point of the service provided by the business system.
[0119] It should be noted that when the service provided by the business system does not contain any sub-step services, the target business refers to the service provided by the business system. For this service, a set of corresponding business identifiers and status identifiers are recorded in the status data body. The status identifier can be read to determine the tracking status of the service provided by the business system.
[0120] In an optional manner, after obtaining the buried point detection result, the detection system feeds back the buried point detection result to the business system.
[0121] To summarize, according to the tracking point detection method provided in the present embodiment, when a business event is triggered in the business system, the tracking point component reports the tracking point, and at the same time, requests the business system for the status of the target business and updates the status identifier. The tracking point reporting situation of the target business can be recorded through the status identifier. When exiting the business, it is possible to quickly and accurately determine whether the tracking point of the target business is abnormal based on the current status identifier of the target business, thereby achieving efficient tracking point anomaly detection. Furthermore, a status data body is constructed to record the correspondence between the business identifier and the status identifier, which can facilitate data management and query. Furthermore, when the target business starts, the status identifier at this time is first updated. When the target business ends, the status identifier at this time is updated for the second time, and finally whether the target business's tracking point is abnormal is determined according to the status identifier of the target business when the business is exited, which simplifies the logic of tracking point abnormality detection and can improve the efficiency of tracking point abnormality detection; further, for a business containing multiple sub-step businesses, the tracking point reporting status of the business can be determined according to the status identifiers of the multiple sub-step businesses, and a tracking point abnormality detection solution for special businesses containing multiple sub-step businesses is provided; further, the Map structure is used to store the corresponding business identifier and status identifier, so that the status identifier can be quickly found by key, thereby improving the efficiency of tracking point abnormality detection.
[0122] Figure 3 FIG. 4 shows an interactive flow chart of a buried point detection method provided by another embodiment of the present application. Figure 3 As shown, the interactive entities involved in the method include a user 30, a business system 31, a tracking component 32 (tracker), and a detection system 33 (checker).
[0123] Among them, the detection system 33 is responsible for detecting the embedded data of all events and needs to comply with the specified protocol. An abstract interface layer is set up, which is responsible for packaging all embedded events. By setting the abstract interface layer of the specified protocol, the detection system 33 and the business system 31 can communicate through the specified protocol, ensuring that the detection system can communicate with different business systems.
[0124] The specific process of the method of the embodiment of the present application is as follows:
[0125] Step S1: The user enters the service, and after entering the service, the service system starts behavior 1;
[0126] Step S2: triggering behavior 1 in the business system, the behavior corresponds to the execution logic in the business;
[0127] Step S3: The business system sends a registration request to the detection system, and the detection system generates a unique business identifier and constructs a state data body; the detection system generates the following data structure: {EventID1:0}, with key = EventID1, value = 0;
[0128] Step S4: The business system notifies the detection system to start detection;
[0129] Step S5: Detect the system reset state and reset the state identifier in the state data body to a default value;
[0130] Step S6: Behavior 1 starts tracking points;
[0131] Step S7: the tracking point component reports the tracking point;
[0132] Step S8: The tracking component notifies the detection system of the update status identifier;
[0133] The detection system queries the business system through the specified protocol interface, specifically asking the following three questions:
[0134] First, is it the start of the behavior? If so, the state flag is incremented by one, that is, value = value + 1; the business system returns the first field to indicate the start of the behavior;
[0135] Second, is the behavior finished? If so, the state flag is decremented by one, value = value - 1; the business system returns the second field to indicate the end of the behavior;
[0136] Third, whether the business has sub-step business; if so, the state data body is updated, and the updated state data body is: {EventID1:{StepID 1:0, StepID 2:0...StepIDn:0}}, where StepID 1 is the step ID of behavior 1, and n is the total number of sub-step business; the business system returns the third field to indicate whether there is a sub-step business;
[0137] Step S9: End tracking in Behavior 1;
[0138] Step S10: the tracking point component reports the tracking point;
[0139] Step S11: The tracking component notifies the detection system of the update status identifier;
[0140] Step S12: the user leaves the service;
[0141] Each triggered behavior in the business is processed according to the above process, which will not be repeated here.
[0142] Step S13: The business system notifies the detection system of the end of detection;
[0143] Step S14: the detection system performs buried point abnormality detection;
[0144] Step S15: The detection system notifies the business system of the detection result, which is normal or abnormal. The detection system traverses all values in the Map structure, and if at least one value is not 0, it means that the buried point is abnormal.
[0145] In simple terms, the general process of the method of the embodiment of the present application is: the business system triggers the tracking point component to report the tracking point, the tracking point component notifies the detection system to update the status data body, and the detection system performs tracking point anomaly detection and notifies the business system of the detection results.
[0146] Figure 4 The functional structure diagram of the buried point detection device provided in the embodiment of the present application is shown. Figure 4 As shown, the device comprises:
[0147] A receiving module 41, adapted to receive a service tracking point parameter sent by a tracking point component in response to a tracking point report of a service event;
[0148] A request module 42, adapted to request the status information of the target business corresponding to the business event from the business system according to the business tracking point parameters;
[0149] An updating module 43, adapted to update a state identifier of a target service according to the state information of the target service;
[0150] The detection module 44 is adapted to receive a service exit notification sent by the service system and detect whether an abnormality occurs in the embedding point of the target service according to the status identifier of the target service.
[0151] In an optional manner, the updating module 43 is further adapted to:
[0152] If the state information indicates that the target service is in the start state, performing a first update process on the state identifier of the target service;
[0153] If the status information indicates that the target service is in the end state, a second update process is performed on the status identifier of the target service.
[0154] In an optional manner, the device further comprises:
[0155] A registration module, adapted to receive a registration request sent by a business system; construct a state data body; wherein the business identifier and state identifier of the target business are recorded in the state data body;
[0156] The updating module 43 is further adapted to:
[0157] The state identifier corresponding to the business identifier of the target business recorded in the state data body is updated.
[0158] In an optional manner, the registration module is further adapted to:
[0159] Requesting the business system for sub-step business information, and judging whether the business provided by the business system includes multiple sub-step businesses according to the request result;
[0160] If yes, construct a state data body for recording the business identifiers and state identifiers of the multiple sub-step businesses;
[0161] The updating module 43 is further adapted to update the state identifier corresponding to the business identifier of the sub-step business recorded in the state data body if the target business is any sub-step business in the business provided by the business system.
[0162] In an optional manner, the service identifier of the sub-step service is determined according to the global service identifier and the step identifier of the sub-step service.
[0163] In an optional manner, the updating module 43 is further adapted to:
[0164] Adding a preset value to the state identifier corresponding to the service identifier of the target service recorded in the state data body to obtain an updated state identifier of the target service;
[0165] Subtracting a preset value from the state identifier corresponding to the service identifier of the target service recorded in the state data body to obtain an updated state identifier of the target service;
[0166] The detection module 44 is further adapted to: detect whether the status identifier corresponding to the service identifier of the target service recorded in the status data body is a default value; if so, determine that no abnormality has occurred in the burying point of the target service; if not, determine that an abnormality has occurred in the burying point of the target service.
[0167] To sum up, according to the buried point detection device provided in this embodiment, the status identifier of the target business is updated according to the status of the target business when the buried point is reported. The buried point reporting situation of the target business can be recorded through the status identifier, and whether the buried point of the target business is abnormal can be quickly and accurately determined according to the status identifier, thereby realizing efficient buried point anomaly detection.
[0168] An embodiment of the present application provides a non-volatile computer storage medium, which stores at least one executable instruction or computer program, and the executable instruction or computer program can enable a processor to perform operations corresponding to the buried point detection method in any of the above-mentioned method embodiments.
[0169] An embodiment of the present application provides a computer program product, which includes at least one executable instruction or computer program, and the executable instruction or computer program can enable a processor to perform operations corresponding to the buried point detection method in any of the above-mentioned method embodiments.
[0170] Figure 5 A schematic diagram of the structure of an embodiment of a computing device of the present application is shown. The specific embodiment of the present application does not limit the specific implementation of the computing device.
[0171] like Figure 5 As shown, the computing device may include: a processor (processor) 502 , a communications interface (Communications Interface) 504 , a memory (memory) 506 , and a communication bus 508 .
[0172] Wherein: the processor 502, the communication interface 504, and the memory 506 communicate with each other via the communication bus 508. The communication interface 504 is used to communicate with other devices such as a client or other server network elements. The processor 502 is used to execute the program 510, which can specifically execute the relevant steps in the above embodiment of the buried point detection method for computing devices.
[0173] Specifically, the program 510 may include program codes, which include computer operation instructions.
[0174] The processor 502 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the computing device may be processors of the same type, such as one or more CPUs; or may be processors of different types, such as one or more CPUs and one or more ASICs.
[0175] The memory 506 is used to store the program 510. The memory 506 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0176] Program 510 can be specifically used to enable processor 502 to execute the buried point detection method in any of the above-mentioned method embodiments. The specific implementation of each step in program 510 can refer to the corresponding description in the corresponding steps and units in the buried point detection embodiment, which will not be repeated here. Technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described equipment and modules can refer to the corresponding process description in the aforementioned method embodiment, which will not be repeated here.
[0177] The algorithm or display provided here are not inherently related to any specific computer, virtual system or other equipment. Various general systems can also be used together with the teaching based on this. According to the above description, it is obvious to construct the structure required for this type of system. In addition, the present application embodiment is not directed to any specific programming language yet. It should be understood that various programming languages can be utilized to realize the content of the present application described here, and the above description of specific languages is to disclose the best mode of implementation of the present application.
[0178] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.
[0179] Similarly, it should be understood that in order to streamline the present application and aid in understanding one or more of the various inventive aspects, in the above description of the exemplary embodiments of the present application, the various features of the embodiments of the present application are sometimes grouped together into a single embodiment, figure, or description thereof. However, the disclosed method should not be interpreted as reflecting the following intention: the claimed application requires more features than the features explicitly recited in each claim. More specifically, as reflected in the claims, the inventive aspects lie in less than all the features of the single embodiment disclosed above. Therefore, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, with each claim itself serving as a separate embodiment of the present application.
[0180] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.
[0181] In addition, those skilled in the art will appreciate that, although some embodiments herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present application and form different embodiments. For example, in the claims, any one of the claimed embodiments may be used in any combination.
[0182] The various component embodiments of the present application can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all functions of some or all components according to the embodiments of the present application. The application can also be implemented as a device or apparatus program (e.g., computer program and computer program product) for executing a part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.
[0183] It should be noted that the above embodiments illustrate the present application rather than limit the present application, and that those skilled in the art may design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be constructed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of multiple such elements. The present application may be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In a unit claim that lists several devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.
Claims
1. A buried point detection method, comprising: Receiving business tracking point parameters sent by the tracking point component in response to the tracking point report of the business event; According to the business tracking point parameters, request the business system for the status information of the target business corresponding to the business event; According to the status information of the target service, updating the status identifier of the target service; Receiving a service exit notification sent by the service system; According to the status identifier of the target business, detect whether an abnormality occurs in the embedding point of the target business.
2. The method according to claim 1, wherein: The updating of the state identifier of the target service according to the state information of the target service further comprises: If the status information indicates that the target service is in the start state, performing a first update process on the status identifier of the target service; If the status information indicates that the target service is in the end state, a second update process is performed on the status identifier of the target service.
3. The method according to claim 1 or 2, wherein: Before the method is performed, the method further comprises: Receive registration request sent by business system; Constructing a state data body; wherein the service identifier and the state identifier of the target service are recorded in the state data body; The updating of the status identifier of the target service further comprises: The state identifier corresponding to the service identifier of the target service recorded in the state data body is updated.
4. The method according to claim 3, wherein: The construction status data body further includes: Requesting the business system for sub-step business information, and determining whether the business provided by the business system includes multiple sub-step businesses according to the request result; If yes, construct a state data body for recording the business identifiers and state identifiers of the multiple sub-step businesses; The updating of the state identifier of the target service according to the state information of the target service further comprises: If the target service is any sub-step service in the services provided by the service system, the state identifier corresponding to the service identifier of the sub-step service recorded in the state data body is updated.
5. The method according to claim 4, wherein: The service identifier of the sub-step service is determined according to the global service identifier and the step identifier of the sub-step service.
6. The method according to claim 3, wherein: The first updating process of the status identifier of the target service further includes: Adding a preset value to the state identifier corresponding to the service identifier of the target service recorded in the state data body to obtain an updated state identifier of the target service; The second updating process of the status identifier of the target service further includes: Subtracting the preset value from the state identifier corresponding to the service identifier of the target service recorded in the state data body to obtain an updated state identifier of the target service; The detecting, according to the state identifier of the target service, whether an abnormality occurs in the embedding point of the target service further comprises: Detecting whether the status identifier corresponding to the service identifier of the target service recorded in the status data body is a default value; If so, it is determined that no abnormality occurs in the embedding point of the target business; if not, it is determined that an abnormality occurs in the embedding point of the target business.
7. A buried point detection device, comprising: A receiving module, adapted to receive business tracking point parameters sent by the tracking point component in response to the tracking point report of the business event; A request module, adapted to request the status information of the target business corresponding to the business event from the business system according to the business tracking point parameters; An updating module, adapted to update a status identifier of the target service according to the status information of the target service; A detection module, adapted to receive a service exit notification sent by the service system; According to the status identifier of the target business, detect whether an abnormality occurs in the embedding point of the target business.
8. A computing device comprising: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the buried point detection method as described in any one of claims 1-6.
9. A computer storage medium, wherein at least one executable instruction is stored in the storage medium, and the executable instruction enables a processor to perform operations corresponding to the buried point detection method as described in any one of claims 1-6.
10. A computer program product, comprising at least one executable instruction, wherein the executable instruction enables a processor to perform operations corresponding to the buried point detection method as described in any one of claims 1-6.