CN110647438A - Event monitoring method and device, computer equipment and storage medium - Google Patents
Event monitoring method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110647438A CN110647438A CN201910745281.6A CN201910745281A CN110647438A CN 110647438 A CN110647438 A CN 110647438A CN 201910745281 A CN201910745281 A CN 201910745281A CN 110647438 A CN110647438 A CN 110647438A
- Authority
- CN
- China
- Prior art keywords
- event
- buried point
- monitoring
- identifier
- code
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Mathematical Physics (AREA)
- Data Mining & Analysis (AREA)
- Debugging And Monitoring (AREA)
Abstract
The present application relates to buried point tracking in the field of data acquisition, and in particular, to an event monitoring method, apparatus, computer device, and storage medium. The method comprises the following steps: acquiring a monitoring file, and running a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is decoupled from an application program code, stored in the monitoring file, and used for monitoring whether a preset event is triggered in the application program code; monitoring a trigger event through an operating monitoring code, and acquiring an event identifier corresponding to the trigger event; acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and obtaining a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result. The method can improve the stability of the application program.
Description
Technical Field
The present application relates to the field of data acquisition, and in particular, to an event monitoring method and apparatus, a computer device, and a storage medium.
Background
With the development of computer technology, more and more computer-related applications are produced, and in order to reflect the functions of the applications or the use of users, the use and the functions of the applications are generally required to be analyzed.
Conventionally, when analyzing the use condition and the function of an application program, a listening code segment is added to a code segment corresponding to the application program, so that the coupling between the application program code segment and the listening code segment is strong, and therefore when the listening code segment is in an operation error in the process of implementing a buried point, the operation error of the application program code may be directly caused, and the stability is poor.
Disclosure of Invention
In view of the above, it is necessary to provide an event monitoring method, apparatus, computer device and storage medium capable of improving code stability.
A method of event monitoring, the method comprising:
acquiring a monitoring file, and running a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is decoupled from an application program code, stored in the monitoring file, and used for monitoring whether a preset event is triggered in the application program code;
monitoring a trigger event through the running monitoring code, and acquiring an event identifier corresponding to the trigger event;
acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and acquiring a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
In one embodiment, the obtaining of the buried point configuration file and selecting the buried point information corresponding to the event identifier from the buried point configuration file includes: inquiring the event type of the trigger event according to the event identifier;
when the event type is an operation event, inquiring a button identifier corresponding to the operation event;
and acquiring a buried point configuration file, and selecting button buried point information corresponding to the button identifier from the buried point configuration file.
In one embodiment, after querying the event type of the trigger event according to the event identifier, the method includes:
when the event type is an interface event, inquiring an interface identifier and a transmission state identifier;
and selecting interface buried point information from the buried point configuration file according to the interface identifier and the transmission state identifier.
In one embodiment, obtaining a buried point result according to the buried point information, where the buried point result is used for characterizing an event monitoring result, includes:
counting a first triggering frequency corresponding to the triggering event;
taking the trigger event with the first trigger times smaller than a first preset value as an event to be inquired;
inquiring an identifier to be inquired corresponding to the event to be inquired, and inquiring the monitoring code corresponding to the identifier to be inquired as a code to be filtered;
and adding a filtering identifier to the code to be filtered, or deleting the code to be filtered.
In one embodiment, the adding a filtering identifier to the code to be filtered or deleting the code to be filtered includes:
selecting information to be inquired from the buried point configuration file according to the identifier to be inquired;
and deleting the information to be inquired.
In one embodiment, the obtaining the buried point configuration file comprises:
when the buried point information is not inquired from the buried point configuration file according to the event identification, taking the event identification which is not inquired to the buried point information as an event identification to be added;
counting a second triggering frequency of the event to be added corresponding to the event to be added identifier;
and when the second triggering times exceed a second preset value, storing the event to be added and the buried point information to be added corresponding to the event to be added in the buried point configuration file in an associated manner.
An event monitoring device, the device comprising:
the acquisition module is used for acquiring a monitoring file and operating a monitoring code in the monitoring file;
the monitoring module is used for monitoring a trigger event through the running monitoring code and acquiring an event identifier corresponding to the trigger event, wherein the monitoring code is a code segment which is decoupled from an application program code, is stored in the monitoring file and is used for monitoring whether a preset event is triggered in the application program code;
and the selecting module is used for acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and obtaining a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
In one embodiment, the selecting module includes: the event type query unit is used for querying the event type of the trigger event according to the event identifier;
the button identifier query unit is used for querying a button identifier corresponding to the operation event when the event type is the operation event;
and the button embedded point information selecting unit is used for acquiring an embedded point configuration file and selecting the button embedded point information corresponding to the button identifier from the embedded point configuration file.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
acquiring a monitoring file, and running a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is decoupled from an application program code, stored in the monitoring file, and used for monitoring whether a preset event is triggered in the application program code;
monitoring a trigger event through the running monitoring code, and acquiring an event identifier corresponding to the trigger event;
acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and obtaining a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
acquiring a monitoring file, and running a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is decoupled from an application program code, stored in the monitoring file, and used for monitoring whether a preset event is triggered in the application program code;
monitoring a trigger event through the running monitoring code, and acquiring an event identifier corresponding to the trigger event;
acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and obtaining a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
The event monitoring method, the device, the computer equipment and the storage medium have the advantages that the monitoring code is not required to be added into the application program code to realize the point burying process, namely, the monitoring file is configured, the monitoring file comprises the monitoring code, namely, the monitoring code is decoupled from the application program code and is stored in the monitoring file, the monitoring file is used for monitoring whether the application program code triggers the code segment of the preset event or not, then the monitoring code is operated to monitor the triggering event and acquire the event identifier corresponding to the triggering event, the point burying information corresponding to the event identifier is selected from the point burying configuration file according to the point burying configuration file, the point burying information can be used for counting to obtain the point burying result for representing the event monitoring result, because the monitoring code segment is not strongly coupled with the application program code in the point burying process, the monitoring code has operation errors in the operation process, the application can continue to run, thereby improving stability.
Drawings
FIG. 1 is a diagram illustrating an exemplary scenario in which the event monitoring method is applied;
FIG. 2 is a flow diagram of a method for event monitoring in one embodiment;
FIG. 3 is a flow chart illustrating an embodiment of a step of selecting buried point information;
FIG. 4 is a block diagram of an event monitoring device according to an embodiment;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The event monitoring method provided by the application can be applied to the application environment shown in fig. 1. Wherein the buried point server 102 communicates with the terminal 104 through a network. The method comprises the steps that a buried point server 102 acquires a monitoring file and runs a monitoring code contained in the monitoring file, the monitoring code is separated from an application program code and is stored in the monitoring file, the monitoring code is used for monitoring whether the application program code triggers a preset event or not, the buried point server 102 monitors whether the preset event is triggered or not through the running monitoring code, when the trigger event exists, the buried point server 102 acquires an event identifier corresponding to the trigger event, the buried point server 102 acquires a buried point configuration file and selects buried point information corresponding to the event identifier from the buried point configuration file, then the buried point server 102 counts the buried point information to obtain a buried point result corresponding to the buried point information, namely the buried point result can represent an event monitoring result, and the buried point result is fed back to a terminal 104. The embedded point server 102 may be implemented by an independent server or a server cluster composed of a plurality of servers, and the terminal 104 may be, but is not limited to, various personal computers, notebook computers, smart phones, and tablet computers.
In one embodiment, as shown in fig. 2, an event monitoring method is provided, which is described by taking the method as an example applied to the sink server 102 in fig. 1, and includes the following steps:
s202: and acquiring a monitoring file, and operating a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is separated from the application program code, stored in the monitoring file and used for monitoring whether the application program code triggers a preset event or not.
Specifically, the listening file refers to a file containing a listening code. In a specific implementation, the listening file refers to a file containing a listening code for listening whether an event is triggered. The monitoring code refers to a code segment configured independently, which is separated from the application code segment, directly stored in a monitoring file, and used for monitoring whether a preset event is triggered in the running application code. In a specific implementation, an event identifier of an event to be monitored is set in the monitoring code, and an execution function corresponding to the event identifier of the event to be monitored is set, where the execution function may be a related function that calls the execution code.
Specifically, an application code corresponding to the application program is set in the embedded point server, the embedded point server obtains the monitoring file, and runs the monitoring code contained in the monitoring file, the monitoring code does not need to be directly configured in the application code, the application code and the monitoring code can be decoupled, and the monitoring code is stored in the monitoring file, so that whether a corresponding event is triggered or not in the process of running the application code can be monitored by running the monitoring code in the monitoring file. The embedded point server may be configured with an application code segment corresponding to the application, acquire a pre-stored monitoring file, query a monitoring code included in the monitoring file, select an initial code from the monitoring code, and when the embedded point server receives feedback information that the initial code is successfully run, the monitoring code may be started normally, so that the embedded point server may continue to run, and when the embedded point server does not receive feedback information that the initial code is successfully run, the embedded point server may output checking information to check the monitoring code.
S204; and monitoring the trigger event through the running monitoring code, and acquiring an event identifier corresponding to the trigger event.
Specifically, a trigger event refers to an event contained in the application code that requires statistics or analysis. It is understood that the trigger event may be a user operation event or an interface event. For example, the triggering event is that the user opens an application page, may be that the user clicks a button, may be that the interface receives a request, and the like. The event identification represents an event parameter that triggers the event. In a specific implementation, when the event is a user operation event, the event identifier may be a parameter of an operation corresponding to the operation, where if the user operation is to open a web page, the parameter of the operation is an address of the open web page, and when the event is an interface event, the event identifier may be a parameter corresponding to the interface.
Specifically, the embedded point server runs a monitoring code, when the application program is started, the embedded point server starts to run the application program code, the monitoring code queries running feedback of the application program code, an event identifier is arranged in the monitoring code of the embedded point server, the embedded point server can match the running identifier in the running feedback with the event identifier in the monitoring code according to the running feedback of the application program code, and when the matching is successful, the event corresponding to the event identifier is a trigger event, so that the embedded point server monitors the trigger event through the monitoring code, and the embedded point server obtains the event identifier corresponding to the trigger event.
For example, the embedded point server runs the monitoring code, when the application program is started, the embedded point server starts to run the application program code, the embedded point server queries the running feedback of the application program code through the monitoring code to render the data of the main page, so that the embedded point server identifies the running identifier in the rendered running feedback as a page address, matches the page address with the event identifier set in the application program code, and when the matching is successful, the event corresponding to the page address is a trigger event, that is, the trigger event is the opening of the application program, so that the embedded point server acquires the event identifier page address for opening the application program.
S206: acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and obtaining a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
Specifically, the buried point configuration file refers to a file that associates a trigger event with buried point information. In a specific implementation, the buried point configuration file may include event-related information and buried point information associated with the event-related information. For example, the embedded point configuration file includes an event identifier, an execution function corresponding to the event, and embedded point information associated with the event. The embedded point information is an embedded point identifier corresponding to the embedded point of the application program. In a specific implementation, the buried point information refers to a buried point identifier set so that the buried point server can distinguish data of different buried points. For example, the buried point information may be a buried point type, a buried point order, or the like corresponding to the buried point. The buried point result is a related result obtained by counting or analyzing the trigger event according to the buried point information, so that monitoring results corresponding to different event identifications can be obtained. In a specific implementation, the buried point result may be a result obtained by analyzing and counting the user operation behavior according to the buried point information, or may be a result obtained by analyzing and counting the interface, so that the result obtained by corresponding analysis and counting when the characterization event is the user operation event may be obtained, or the result obtained by corresponding analysis and counting when the characterization event is the interface event may be obtained.
Specifically, the buried point server acquires a buried point configuration file, acquires an event identifier corresponding to a trigger event when the buried point server monitors that the trigger event exists through a monitoring code, acquires a pre-stored buried point configuration file, matches the acquired event identifier with different event-related information contained in the buried point configuration file, and when the matching is successful, needs to perform subsequent analysis on the event, so that the buried point information associated with the event-related information that is successfully matched is queried. In addition, when the obtained event identifier is not successfully matched with different event related information contained in the buried point configuration file, the event does not need to be subjected to subsequent analysis, when the buried point server inquires the buried point information according to the event identifier, the buried point information is extracted, the number of times of extracting the buried point information can be counted, the buried point information is analyzed to obtain a buried point result, and the server takes the buried point result as an event monitoring result.
For example, if the event corresponding to the trigger event is an open application, the event identifier corresponding to the event is a page address, the buried point server acquires a buried point configuration file, matches the page address with the event-related information contained in the buried point configuration file, if the matching is successful, the event needs to perform subsequent statistical analysis, the buried point server queries the buried point information corresponding to the page address, which may be the order of buried points, such as the first buried point, the corresponding application, and the name of the buried point, such as an open program buried point, the buried point server extracts the buried point information, and counts the number of times of the buried point information within a preset time period, thereby obtaining the number of times of opening the application within the preset time period as a buried point result, and thus opening the buried point result corresponding to the event of the application, i.e. as an event monitoring result. Furthermore, the embedded point server can count the opening times of the application programs in different time periods in the whole day, analyze the use habits of the users on the application programs, obtain the use habit data and output the corresponding use habit data.
In the embodiment, a monitoring code does not need to be directly added into an application program code, so that the coupling between the monitoring code and the application program code is strong, and thus the monitoring code is wrong in the running process and the application program code is likely to be wrong in running, therefore, a buried point server only needs to acquire a monitoring file, the monitoring file contains the monitoring code, namely the monitoring code is decoupled from an application program code segment and is stored in the monitoring file, the buried point server can independently run the monitoring code to monitor a trigger event, the buried point server selects buried point information corresponding to an event identifier from an acquired buried point configuration file according to the event identifier of the trigger event, obtains a buried point result corresponding to the buried point information according to the buried point information, namely the monitoring code and the application program code can be decoupled, the stability of the code is enhanced, and when the code is modified, only the modification of the code needs to be carried out separately, thereby enhancing the applicability and improving the code development efficiency.
In one embodiment, please refer to fig. 3, which provides a flow chart of a buried point information selecting step, that is, obtaining a buried point configuration file, and selecting the buried point information corresponding to the event identifier from the buried point configuration file includes:
s302: and inquiring the event type of the trigger event according to the event identification.
Specifically, the event type refers to a flag that distinguishes the kinds of different events. In a specific implementation, the event type may be an operation event, and may also be an interface event, where the operation event may be an operation behavior, such as clicking a button, and the interface event may be an interface behavior, such as receiving data or sending data by an interface. Specifically, when the embedded point server receives the event identifier, the embedded point server may obtain a pre-stored type map, match the embedded point server with the to-be-matched parameter stored in the type map according to the event identifier, and when the matching is successful, use the parameter type associated with the successfully-matched to-be-matched parameter as the event type corresponding to the trigger event. It should be noted that the type mapping is to pre-store association relations between different event identifiers and event types, that is, the buried point server may directly query the corresponding event types through the event identifiers, and the event identifiers stored in the type mapping may be event parameters and the like.
For example, when the embedded point server receives an event identifier, if the event identifier is a click instruction of a button displayed on a corresponding click page, the embedded point server obtains a pre-stored type mapping, matches the click instruction with a parameter to be matched of the type mapping, and further, when matching is successful, queries a parameter type associated with the successfully matched parameter to be matched as the event type. The click command may be a command received by the buried point server to click a relevant button, and the like. In addition, for example, when the embedded point server receives an event identifier, if the event identifier is a page address, the embedded point server obtains a pre-stored type mapping and matches the pre-stored type mapping with a parameter to be matched stored in the type mapping, where when the event identifier is matched with the parameter to be matched, an address field in the page address may be matched with different fields stored in the type mapping, where the address field includes a communication protocol field, a domain name field, and the like, and when the matching is successful, a parameter type associated with the parameter to be matched that is successfully matched is queried as the event type.
S304: and when the event type is an operation event, inquiring a button identifier corresponding to the operation event.
Specifically, the operation event refers to an event triggered according to an operation by a user. In a specific implementation, the operation event may be an operation behavior of a user to which the fixed point server is to respond, such as clicking a button. The button identifier is a flag of a button to be operated corresponding to the operation event, and may be, for example, a button name triggered by the user performing the operation or a button coordinate triggered by the user performing the operation. Specifically, when the buried point server receives the event identifier, the event type corresponding to the trigger event is queried according to the event identifier, and when the buried point server queries that the event type is the operation event, the button identifier is queried according to the event parameter contained in the event identifier.
For example, when the buried point server inquires that the event type is an operation event for opening an application program, and the event is identified as a corresponding page address, the page address is used as a button identifier. In addition, when the embedded point server queries that the event type is an operation event of a click button, the embedded point server queries that the event identifier is a click instruction, and queries that a specific click button name carried by the click instruction is used as the button identifier.
S306: and acquiring a buried point configuration file, and selecting button buried point information corresponding to the button identifier from the buried point configuration file.
Specifically, the button buried point information refers to a buried point identifier corresponding to the button identifier, and for example, the button buried point information may be a buried point order, a buried point name, and the like corresponding to the button identifier. Specifically, when the buried point server obtains the button identifier, the buried point server obtains a buried point configuration file, the buried point server obtains the buried point configuration file, matches the button identifier with different event-related information contained in the buried point configuration file, and when the button identifier is successfully matched, queries the buried point information corresponding to the successfully matched event-related information. For example, when the button name corresponding to the operation event acquired by the buried point server and the buried point configuration file are acquired by the buried point server, the button name is matched with the relevant information of different times contained in the buried point configuration file, and when the button name is successfully matched with the relevant information of different times contained in the buried point configuration file, the button buried point information corresponding to the successfully matched event relevant information is inquired.
In this embodiment, when the embedded point server queries that the event type of the trigger event is the operation event according to the event identifier, the button embedded point information corresponding to the button identifier can be selected from the embedded point configuration file according to the button identifier corresponding to the operation event, and the button embedded point information is simply and easily selected, so that the selection efficiency is improved.
In an embodiment, please continue to refer to fig. 3, after step S302, that is, after querying the event type of the trigger event according to the event identifier, the method includes: s308: and when the event type is an interface event, inquiring the interface identifier and the transmission state identifier.
Specifically, an interface event refers to an event triggered by an interface when transmitting data. The interface identifier refers to interface marks corresponding to different interfaces, that is, the embedded point server can query the interface needing data transmission through the interface identifier. The transmission status flag refers to a status flag of a transmission status during transmission of different data, for example, the transmission status flag may be a success flag of successful data transmission or a failure flag of failed data transmission, and the failure flag may be a failure flag corresponding to different failure reasons.
Specifically, the embedded point server matches the acquired event identifier with the parameter to be matched in the type mapping, when the matching is successful, the event type corresponding to the parameter to be matched which is successfully matched is inquired to be the interface event, the corresponding interface identifier is extracted from the event identifier, and the corresponding transmission state identifier is extracted. For example, when the event type acquired by the buried point server is an interface event, the buried point server queries the interface name and extracts a transmission state identifier when the interface transmits data, for example, the transmission state identifier is transmission failure, and the failure reason of the transmission failure is interface response timeout.
S310: and selecting interface buried point information from the buried point configuration file according to the interface identifier and the transmission state identifier.
Specifically, the interface buried point information refers to a buried point identifier corresponding to the interface, for example, the interface buried point information may be a buried point sequence corresponding to the interface identifier and the transmission state identifier, or a corresponding buried point name. Specifically, when the embedded point server queries the interface identifier and the transmission state identifier, the embedded point configuration file is obtained, the interface identifier and the transmission state identifier are matched with different event related information in the embedded point configuration file, and when the matching is successful, the interface and the interface state need to be monitored, so that subsequent analysis is performed, and therefore the embedded point server selects interface embedded point information from the embedded point configuration file.
In this embodiment, when the embedded point server queries that the event type is an interface event, the interface embedded point information may be selected from the embedded point configuration file according to the interface identifier and the transmission state identifier, and the embedded point server may obtain the interface embedded point information, so that the applicability is enhanced, the interface embedded point information is easily obtained, and the embedded point efficiency is improved.
In one embodiment, obtaining a buried point result according to the buried point information, where the buried point result is used to characterize the event monitoring result, includes: counting a first triggering frequency corresponding to a triggering event; taking a trigger event with the first trigger times smaller than a first preset value as an event to be inquired; inquiring an identifier to be inquired corresponding to the event to be inquired, and inquiring a monitoring code corresponding to the identifier to be inquired as a code to be filtered; and adding a filtering identifier to the code to be filtered or deleting the code to be filtered.
Specifically, the event to be queried is an event that needs to be further checked when the first trigger time of the event is less than a first preset value. The identifier to be queried is a parameter of an event corresponding to the event to be queried, and may be, when the event to be queried is a user operation event, the identifier to be queried is a parameter of an operation corresponding to the operation, and if the user operation is clicking a corresponding button, the identifier to be queried is a button identifier. The code to be filtered refers to code that does not need to be executed in the monitoring code. The filtering mark refers to a symbol added to the code to be filtered, and when the buried point server runs the monitoring code in the monitoring file, and the symbol is detected to be added, the code added with the symbol is skipped to be executed.
Specifically, when the embedded point server inquires the operation feedback of the application program code by monitoring the code, matching is performed according to the operation identifier and the event identifier in the operation feedback, when the matching is successful, the event corresponding to the event identifier is a trigger event, the embedded point server records different trigger events, the number of times of occurrence of the trigger event is counted as a first trigger number within a preset time period, the embedded point server acquires a first preset value and compares the first trigger number with the first preset value, when the first trigger number is smaller than the first preset value, the embedded point server takes the trigger event of which the first trigger number is smaller than the first preset value as an event to be inquired as the event to be inquired because the data volume is smaller and does not have referential property in the counting process, and extracts the event identifier of the event to be inquired as the identifier to be inquired, and matching according to the identifier to be inquired and the event identifier contained in the monitoring code, when the matching is successful, inquiring a first code identifier corresponding to the code containing the event identifier, inquiring a second code identifier, extracting the code between the first code identifier and the second code identifier to be used as the code to be filtered, wherein the extracted code to be filtered contains the identifier to be inquired, and adding the filtering identifier to the filtering code by the embedded point server or directly deleting the code to be filtered. It should be noted that event files corresponding to different events may also be prestored in the embedded point server, the embedded point server may also perform matching according to different event identifiers corresponding to different trigger events and according to a preset matching time period and according to different identifiers included in the event identifiers and the event files, so as to select an event that is not matched, that is, the event is not triggered, and then the embedded point server takes the event that is not triggered as an event to be queried, selects a code to be filtered from the monitored codes according to the identifier to be queried corresponding to the event to be queried, and adds a filtering identifier to the code to be filtered or deletes the code to be filtered, thereby avoiding missing the event that is not triggered.
In addition, when the buried point server queries the event to be queried, the event to be queried and the associated identifier to be queried are output and displayed, the user selects the output identifier to be queried, so that a confirmation instruction is generated according to the selection of the user, the buried point server queries the identifier to be queried corresponding to the event to be queried according to the confirmation instruction, selects the corresponding monitoring code segment according to the identifier to be queried, and takes the monitoring code segment as the code to be filtered, namely the selected code to be filtered is ensured to be accurate.
In this embodiment, the embedded point server selects a code to be filtered from the monitored codes according to the counted first triggering times corresponding to the triggering event, and adds a filtering identifier to the code to be filtered, or deletes the code to be filtered, so as to cancel the embedded point of the event whose data amount does not meet the requirement, thereby saving space.
In one embodiment, adding a filtering identifier to the code to be filtered, or deleting the code to be filtered includes: selecting information to be inquired from the buried point configuration file according to the identifier to be inquired; and deleting the information to be inquired.
Specifically, the information to be queried refers to the buried point information contained in the buried point configuration file and associated with the identifier to be queried, for example, the information to be queried may be a buried point type or a buried point sequence corresponding to the buried point.
Specifically, when the embedded point server adds a filtering identifier to the filtering code, or deletes the code to be filtered, because the embedded point configuration file still contains corresponding embedded point information, the server may delete the embedded point information contained in the embedded point configuration file, that is, the embedded point server may match the identifier to be queried with different event-related information contained in the embedded point configuration file, and when the matching is successful, the embedded point information associated with the event-related information is used as the information to be queried and outputs the information to be queried, and a deletion instruction generated by a user according to the output information to be queried is received, the embedded point server deletes the information to be queried according to the deletion instruction, and the embedded point server may delete the event information associated with the information to be queried at the same time.
In this embodiment, the buried point server may further select information to be queried from the buried point configuration file according to the identifier to be queried, so that the information to be queried is deleted, and the storage space is saved.
In one embodiment, after obtaining the buried point configuration file, the method includes: when the buried point information is not inquired from the buried point configuration file according to the event identification, taking the event identification which is not inquired to the buried point information as the event identification to be added; counting a second triggering frequency of the event to be added corresponding to the event identifier to be added; and when the second triggering times exceed a second preset value, storing the event to be added and the buried point information to be added corresponding to the event to be added into the buried point configuration file in an associated manner.
Specifically, the to-be-added event identifier refers to an event identifier corresponding to an event which is not configured in the current buried point configuration file. The event to be added refers to an event that is not stored in the current buried point configuration file. The buried point information to be added refers to buried point information associated with an event to be added.
Specifically, when the buried point server monitors a trigger event according to the monitoring code, acquires an event identifier corresponding to the trigger event, the buried point server queries from the buried point configuration file according to the event identifier, when the buried point information is not queried from the buried point configuration file, the event identifier serves as an event identifier to be added, the buried point server can count the number of times that the monitoring code segment monitors to trigger the event to be added, namely the number of times serves as a second triggering number of times of the event to be added, the buried point server compares the second buried point number with a second preset value, when the second triggering number exceeds the second preset value, the event to be added needs to be associated with corresponding buried point information, the buried point server can output the corresponding event to be added and the event identifier to be added, and the buried point server receives the buried point information corresponding to the event to be added and the event identifier to be added, and the buried point server stores the event to be added and the buried point information to be added in a buried point configuration file in an associated manner, wherein the counted second triggering times can be counted within a preset counting time period.
In addition, when the second triggering times counted by the embedded point server in the preset counting time period do not exceed the second preset value, the monitoring codes in the monitoring file do not need to be operated again, so that the embedded point server finds the corresponding to-be-added event identifier according to the to-be-added event, queries the corresponding monitoring codes from the monitoring file according to the to-be-added event identifier, adds the filtering identifier to the monitoring codes corresponding to the to-be-added event identifier, or directly deletes the monitoring codes, that is, the monitoring codes can be directly maintained, the maintenance efficiency is improved, the monitoring codes only need to be modified in the monitoring file when modified, the application codes do not need to be modified correspondingly when modified, and the stability of the application codes is ensured.
In this embodiment, when the buried point server does not inquire the buried point information from the buried point configuration file according to the event identifier, the event identifier of the buried point information that is not inquired can be used as the identifier of the event to be added, and then the second trigger times of the event to be added corresponding to the time identifier to be added can be counted.
It should be understood that although the various steps in the flow charts of fig. 2-3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 4, there is provided an event monitoring apparatus including: an obtaining module 410, a monitoring module 420, a selecting module 430 and a counting module 440, wherein:
the obtaining module 410 is configured to obtain a monitoring file, and run a monitoring code in the monitoring file, where the monitoring code is a code segment that is decoupled from an application program code, stored in the monitoring file, and configured to monitor whether a preset event is triggered in the application program code.
The monitoring module 420 is configured to monitor the trigger event through the running monitoring code, and obtain an event identifier corresponding to the trigger event.
The selecting module 430 is configured to obtain a buried point configuration file, select buried point information corresponding to the event identifier from the buried point configuration file, and obtain a buried point result according to the buried point information, where the buried point result is used to represent an event monitoring result.
In one embodiment, the selecting module 430 includes: and the event type query unit is used for querying the event type of the trigger event according to the event identification.
And the button identifier query unit is used for querying the button identifier corresponding to the operation event when the event type is the operation event.
And the button embedded point information selecting unit is used for acquiring the embedded point configuration file and selecting the button embedded point information corresponding to the button identifier from the embedded point configuration file.
In one embodiment, the selecting module 430 may further include:
and the interface query unit is used for querying the interface identifier and the transmission state identifier when the event type is the interface event.
And the interface buried point information selecting unit is used for selecting the interface buried point information from the buried point configuration file according to the interface identifier and the transmission state identifier.
In one embodiment, the selecting module 430 includes:
and the frequency counting unit is used for counting a first triggering frequency corresponding to the triggering event and taking the triggering event with the first triggering frequency smaller than a first preset value as the event to be inquired.
And the code query unit is used for querying the to-be-queried identifier corresponding to the to-be-queried event and querying the monitoring code corresponding to the to-be-queried identifier as the to-be-filtered code.
And the code processing unit is used for adding a filtering identifier to the code to be filtered or deleting the code to be filtered.
In one embodiment, the selecting module 430 includes:
and the selecting unit is used for selecting the information to be inquired from the buried point configuration file according to the identifier to be inquired.
And the deleting unit is used for deleting the information to be inquired.
In one embodiment, the event monitoring apparatus 400 includes:
and the verification module is used for taking the event identifier which is not inquired to the buried point information as the event identifier to be added when the buried point information is not inquired from the buried point configuration file according to the event identifier.
And the event counting module is used for counting the second triggering times of the event to be added corresponding to the event identifier to be added.
And the storage module is used for storing the event to be added and the information of the buried point to be added corresponding to the event to be added into the buried point configuration file in a correlation manner when the second triggering frequency exceeds a second preset value.
For the specific definition of the event monitoring device, reference may be made to the above definition of the event monitoring method, which is not described herein again. The modules in the event monitoring device can be implemented in whole or in part by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used to store buried point data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of event monitoring.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a computer device comprising a memory storing a computer program and a processor implementing the following steps when the processor executes the computer program: acquiring a monitoring file, and running a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is decoupled from an application program code, stored in the monitoring file, and used for monitoring whether a preset event is triggered in the application program code. And monitoring the trigger event through the running monitoring code, and acquiring an event identifier corresponding to the trigger event. Acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and obtaining a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
In one embodiment, the processor, when executing the computer program, implements obtaining a buried point configuration file, and selecting buried point information corresponding to an event identifier from the buried point configuration file, including: and inquiring the event type of the trigger event according to the event identification. And when the event type is the operation event, inquiring the button identification corresponding to the operation event. And acquiring a buried point configuration file, and selecting button buried point information corresponding to the button identifier from the buried point configuration file.
In one embodiment, the processor, when executing the computer program, after querying the event type of the triggering event based on the event identification, comprises: and when the event type is an interface event, inquiring the interface identifier and the transmission state identifier. And selecting interface buried point information from the buried point configuration file according to the interface identifier and the transmission state identifier.
In one embodiment, the processor, when executing the computer program, implements obtaining a buried point result according to the buried point information, and after the buried point result is used for characterizing an event monitoring result, the method includes: and counting the first triggering times corresponding to the triggering events. And taking the trigger event with the first trigger times smaller than the first preset value as an event to be inquired. And inquiring the to-be-inquired identifier corresponding to the to-be-inquired event, and inquiring the monitoring code corresponding to the to-be-inquired identifier as the to-be-filtered code. And adding a filtering identifier to the code to be filtered or deleting the code to be filtered.
In one embodiment, the implementation of adding a filtering identifier to the code to be filtered or deleting the code to be filtered when the processor executes the computer program includes: and selecting the information to be inquired from the buried point configuration file according to the identifier to be inquired. And deleting the information to be inquired.
In one embodiment, the processor, when executing the computer program, after obtaining the buried point configuration file, comprises: and when the buried point information is not inquired from the buried point configuration file according to the event identifier, taking the event identifier of which the buried point information is not inquired as the event identifier to be added. And counting the second triggering times of the event to be added corresponding to the event identifier to be added. And when the second triggering times exceed a second preset value, storing the event to be added and the buried point information to be added corresponding to the event to be added into the buried point configuration file in an associated manner.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring a monitoring file, and running a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is decoupled from an application program code, stored in the monitoring file, and used for monitoring whether a preset event is triggered in the application program code. And monitoring the trigger event through the running monitoring code, and acquiring an event identifier corresponding to the trigger event. Acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and obtaining a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
In one embodiment, a computer program that when executed by a processor implements obtaining a buried point profile from which to select buried point information corresponding to an event identification, includes: and inquiring the event type of the trigger event according to the event identification. And when the event type is the operation event, inquiring the button identification corresponding to the operation event. And acquiring a buried point configuration file, and selecting button buried point information corresponding to the button identifier from the buried point configuration file.
In one embodiment, the computer program when executed by the processor, after identifying an event type for querying the trigger event based on the event, comprises: and when the event type is an interface event, inquiring the interface identifier and the transmission state identifier. And selecting interface buried point information from the buried point configuration file according to the interface identifier and the transmission state identifier.
In one embodiment, a computer program when executed by a processor for implementing a buried point result from buried point information, the buried point result being used to characterize an event monitoring result, includes: and counting the first triggering times corresponding to the triggering events. And taking the trigger event with the first trigger times smaller than the first preset value as an event to be inquired. And inquiring the to-be-inquired identifier corresponding to the to-be-inquired event, and inquiring the monitoring code corresponding to the to-be-inquired identifier as the to-be-filtered code. And adding a filtering identifier to the code to be filtered or deleting the code to be filtered.
In one embodiment, the computer program, when executed by a processor, implements adding a filtering identifier to the code to be filtered, or after deleting the code to be filtered, including: and selecting the information to be inquired from the buried point configuration file according to the identifier to be inquired. And deleting the information to be inquired.
In one embodiment, the computer program when executed by the processor, after obtaining the buried point profile, comprises: and when the buried point information is not inquired from the buried point configuration file according to the event identifier, taking the event identifier of which the buried point information is not inquired as the event identifier to be added. And counting the second triggering times of the event to be added corresponding to the event identifier to be added. And when the second triggering times exceed a second preset value, storing the event to be added and the buried point information to be added corresponding to the event to be added into the buried point configuration file in an associated manner.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method of event monitoring, the method comprising:
acquiring a monitoring file, and running a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is decoupled from an application program code, stored in the monitoring file, and used for monitoring whether a preset event is triggered in the application program code;
monitoring a trigger event through the running monitoring code, and acquiring an event identifier corresponding to the trigger event;
acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and acquiring a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
2. The method of claim 1, wherein the obtaining of the buried point profile and the selecting of the buried point information corresponding to the event identifier from the buried point profile comprises:
inquiring the event type of the trigger event according to the event identifier;
when the event type is an operation event, inquiring a button identifier corresponding to the operation event;
and acquiring a buried point configuration file, and selecting button buried point information corresponding to the button identifier from the buried point configuration file.
3. The method of claim 2, wherein after querying the event type of the triggering event according to the event identifier, the method further comprises:
when the event type is an interface event, inquiring an interface identifier and a transmission state identifier;
and selecting interface buried point information from the buried point configuration file according to the interface identifier and the transmission state identifier.
4. The method according to any one of claims 1 to 3, wherein the obtaining of the buried point result according to the buried point information, the buried point result being used for characterizing an event monitoring result, comprises:
counting a first triggering frequency corresponding to the triggering event;
taking the trigger event with the first trigger times smaller than a first preset value as an event to be inquired;
inquiring an identifier to be inquired corresponding to the event to be inquired, and inquiring the monitoring code corresponding to the identifier to be inquired as a code to be filtered;
and adding a filtering identifier to the code to be filtered, or deleting the code to be filtered.
5. The method according to claim 4, wherein the adding a filtering identifier to the code to be filtered or deleting the code to be filtered comprises:
selecting information to be inquired from the buried point configuration file according to the identifier to be inquired;
and deleting the information to be inquired.
6. The method of any one of claims 1 to 3, wherein after obtaining the site profile, comprising:
when the buried point information is not inquired from the buried point configuration file according to the event identification, taking the event identification which is not inquired to the buried point information as an event identification to be added;
counting a second triggering frequency of the event to be added corresponding to the event to be added identifier;
and when the second triggering times exceed a second preset value, storing the event to be added and the buried point information to be added corresponding to the event to be added in the buried point configuration file in an associated manner.
7. An event monitoring apparatus, characterized in that the apparatus comprises:
the acquisition module is used for acquiring a monitoring file and operating a monitoring code in the monitoring file, wherein the monitoring code is a code segment which is decoupled from an application program code, stored in the monitoring file and used for monitoring whether a preset event is triggered in the application program code;
the monitoring module is used for monitoring a trigger event through the running monitoring code and acquiring an event identifier corresponding to the trigger event;
and the selecting module is used for acquiring a buried point configuration file, selecting buried point information corresponding to the event identifier from the buried point configuration file, and obtaining a buried point result according to the buried point information, wherein the buried point result is used for representing an event monitoring result.
8. The apparatus of claim 7, wherein the selecting module comprises: the event type query unit is used for querying the event type of the trigger event according to the event identifier;
the button identifier query unit is used for querying a button identifier corresponding to the operation event when the event type is the operation event;
and the button embedded point information selecting unit is used for acquiring an embedded point configuration file and selecting the button embedded point information corresponding to the button identifier from the embedded point configuration file.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910745281.6A CN110647438B (en) | 2019-08-13 | 2019-08-13 | Event monitoring method and device, computer equipment and storage medium |
| PCT/CN2020/093574 WO2021027365A1 (en) | 2019-08-13 | 2020-05-30 | Event monitoring method, device, computer apparatus, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910745281.6A CN110647438B (en) | 2019-08-13 | 2019-08-13 | Event monitoring method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110647438A true CN110647438A (en) | 2020-01-03 |
| CN110647438B CN110647438B (en) | 2022-03-15 |
Family
ID=69009495
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910745281.6A Active CN110647438B (en) | 2019-08-13 | 2019-08-13 | Event monitoring method and device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110647438B (en) |
| WO (1) | WO2021027365A1 (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111338705A (en) * | 2020-02-13 | 2020-06-26 | 贝壳技术有限公司 | Data processing method, device and storage medium |
| CN111639007A (en) * | 2020-05-29 | 2020-09-08 | 北京金山云网络技术有限公司 | Data processing method, device, terminal and computer readable storage medium |
| CN111737100A (en) * | 2020-06-09 | 2020-10-02 | 北京三快在线科技有限公司 | Data acquisition method, device, equipment and storage medium |
| CN111857865A (en) * | 2020-06-28 | 2020-10-30 | 珠海豹趣科技有限公司 | Event type task processing method and device, electronic equipment and storage medium |
| CN112035321A (en) * | 2020-08-31 | 2020-12-04 | 辽宁振兴银行股份有限公司 | Vue-trace tracking embedded point SDK processing method |
| CN112181821A (en) * | 2020-09-24 | 2021-01-05 | 浙江大搜车软件技术有限公司 | Interface test coverage detection method and device, electronic device and storage medium |
| CN112363943A (en) * | 2020-11-20 | 2021-02-12 | 腾讯科技（深圳）有限公司 | Buried point setting method and device, computer equipment and storage medium |
| WO2021027365A1 (en) * | 2019-08-13 | 2021-02-18 | 平安科技（深圳）有限公司 | Event monitoring method, device, computer apparatus, and storage medium |
| CN112527414A (en) * | 2020-12-23 | 2021-03-19 | 平安普惠企业管理有限公司 | Front-end-based data processing method, device, equipment and storage medium |
| CN112559290A (en) * | 2020-12-14 | 2021-03-26 | 平安国际融资租赁有限公司 | Service call monitoring method and device, computer equipment and storage medium |
| CN112799925A (en) * | 2021-01-25 | 2021-05-14 | 北京嘀嘀无限科技发展有限公司 | Data acquisition method and device, electronic equipment and readable storage medium |
| CN113660533A (en) * | 2021-07-16 | 2021-11-16 | 广州虎牙科技有限公司 | Live broadcast data statistical method, electronic equipment and computer readable device |
| CN113778387A (en) * | 2020-06-09 | 2021-12-10 | 北京字节跳动网络技术有限公司 | Method and apparatus for generating code |
| CN114064144A (en) * | 2021-11-12 | 2022-02-18 | 南京论之语网络技术有限公司 | Communication plug-in unit for cross-application data acquisition and communication method |
| CN114661569A (en) * | 2022-03-25 | 2022-06-24 | 中企云链（北京）金融信息服务有限公司 | Dynamic embedded point acquisition method for user behavior data |
| CN117950719A (en) * | 2024-03-27 | 2024-04-30 | 睿云联(厦门)网络通讯技术有限公司 | Data embedding method, device and medium based on distributed application running |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113238948B (en) * | 2021-05-19 | 2024-03-12 | 北京达佳互联信息技术有限公司 | Buried point detection method, buried point detection device, electronic equipment and storage medium |
| CN113779337B (en) * | 2021-09-18 | 2023-10-20 | 康键信息技术（深圳）有限公司 | Supervision data uploading method, device, equipment and storage medium |
| CN114020566B (en) * | 2021-10-28 | 2024-08-27 | 建信金融科技有限责任公司 | Job monitoring method, device, medium and electronic equipment of job scheduling system |
| CN113918437A (en) * | 2021-11-23 | 2022-01-11 | 企查查科技有限公司 | User behavior data analysis method and device, computer equipment and storage medium |
| CN114860600B (en) * | 2022-05-12 | 2024-05-28 | 平安科技（深圳）有限公司 | Visual data embedded point method, device, equipment and storage medium |
| CN115470075B (en) * | 2022-09-15 | 2023-08-29 | 中电金信软件有限公司 | Application program fault detection method and device, electronic equipment and storage medium |
| CN117130944B (en) * | 2023-10-26 | 2024-02-09 | 数研院(福建)信息产业发展有限公司 | Real-time page debugging method and medium for terminal and terminal |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102831043A (en) * | 2011-06-17 | 2012-12-19 | 阿里巴巴集团控股有限公司 | Monitoring method and device for application program |
| US20160252576A1 (en) * | 2015-02-27 | 2016-09-01 | At&T Intellectual Property I, L.P. | Configurable probe blocks for system monitoring |
| CN106776247A (en) * | 2016-11-23 | 2017-05-31 | 腾云天宇科技（北京）有限公司 | Method, server and system for monitoring control in application |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9009680B2 (en) * | 2006-11-30 | 2015-04-14 | Ca, Inc. | Selecting instrumentation points for an application |
| CN110647438B (en) * | 2019-08-13 | 2022-03-15 | 平安科技（深圳）有限公司 | Event monitoring method and device, computer equipment and storage medium |
-
2019
- 2019-08-13 CN CN201910745281.6A patent/CN110647438B/en active Active
-
2020
- 2020-05-30 WO PCT/CN2020/093574 patent/WO2021027365A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102831043A (en) * | 2011-06-17 | 2012-12-19 | 阿里巴巴集团控股有限公司 | Monitoring method and device for application program |
| US20160252576A1 (en) * | 2015-02-27 | 2016-09-01 | At&T Intellectual Property I, L.P. | Configurable probe blocks for system monitoring |
| CN106776247A (en) * | 2016-11-23 | 2017-05-31 | 腾云天宇科技（北京）有限公司 | Method, server and system for monitoring control in application |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021027365A1 (en) * | 2019-08-13 | 2021-02-18 | 平安科技（深圳）有限公司 | Event monitoring method, device, computer apparatus, and storage medium |
| CN111338705B (en) * | 2020-02-13 | 2021-03-26 | 北京房江湖科技有限公司 | Data processing method, device and storage medium |
| CN111338705A (en) * | 2020-02-13 | 2020-06-26 | 贝壳技术有限公司 | Data processing method, device and storage medium |
| CN111639007A (en) * | 2020-05-29 | 2020-09-08 | 北京金山云网络技术有限公司 | Data processing method, device, terminal and computer readable storage medium |
| CN111639007B (en) * | 2020-05-29 | 2024-05-03 | 北京金山云网络技术有限公司 | Data processing method, device, terminal and computer readable storage medium |
| CN111737100A (en) * | 2020-06-09 | 2020-10-02 | 北京三快在线科技有限公司 | Data acquisition method, device, equipment and storage medium |
| CN113778387A (en) * | 2020-06-09 | 2021-12-10 | 北京字节跳动网络技术有限公司 | Method and apparatus for generating code |
| CN111857865A (en) * | 2020-06-28 | 2020-10-30 | 珠海豹趣科技有限公司 | Event type task processing method and device, electronic equipment and storage medium |
| CN112035321A (en) * | 2020-08-31 | 2020-12-04 | 辽宁振兴银行股份有限公司 | Vue-trace tracking embedded point SDK processing method |
| CN112035321B (en) * | 2020-08-31 | 2024-09-13 | 辽宁振兴银行股份有限公司 | Vue-trace tracking buried point SDK processing method |
| CN112181821A (en) * | 2020-09-24 | 2021-01-05 | 浙江大搜车软件技术有限公司 | Interface test coverage detection method and device, electronic device and storage medium |
| CN112363943B (en) * | 2020-11-20 | 2023-05-30 | 腾讯科技（深圳）有限公司 | Buried point setting method and device, computer equipment and storage medium |
| CN112363943A (en) * | 2020-11-20 | 2021-02-12 | 腾讯科技（深圳）有限公司 | Buried point setting method and device, computer equipment and storage medium |
| CN112559290A (en) * | 2020-12-14 | 2021-03-26 | 平安国际融资租赁有限公司 | Service call monitoring method and device, computer equipment and storage medium |
| CN112559290B (en) * | 2020-12-14 | 2024-04-05 | 平安国际融资租赁有限公司 | Service call monitoring method, device, computer equipment and storage medium |
| CN112527414B (en) * | 2020-12-23 | 2023-09-22 | 平安普惠企业管理有限公司 | Front-end-based data processing method, device, equipment and storage medium |
| CN112527414A (en) * | 2020-12-23 | 2021-03-19 | 平安普惠企业管理有限公司 | Front-end-based data processing method, device, equipment and storage medium |
| CN112799925A (en) * | 2021-01-25 | 2021-05-14 | 北京嘀嘀无限科技发展有限公司 | Data acquisition method and device, electronic equipment and readable storage medium |
| CN113660533A (en) * | 2021-07-16 | 2021-11-16 | 广州虎牙科技有限公司 | Live broadcast data statistical method, electronic equipment and computer readable device |
| CN114064144A (en) * | 2021-11-12 | 2022-02-18 | 南京论之语网络技术有限公司 | Communication plug-in unit for cross-application data acquisition and communication method |
| CN114661569A (en) * | 2022-03-25 | 2022-06-24 | 中企云链（北京）金融信息服务有限公司 | Dynamic embedded point acquisition method for user behavior data |
| CN114661569B (en) * | 2022-03-25 | 2024-04-26 | 中企云链股份有限公司 | Dynamic buried point acquisition method for user behavior data |
| CN117950719A (en) * | 2024-03-27 | 2024-04-30 | 睿云联(厦门)网络通讯技术有限公司 | Data embedding method, device and medium based on distributed application running |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110647438B (en) | 2022-03-15 |
| WO2021027365A1 (en) | 2021-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110647438B (en) | Event monitoring method and device, computer equipment and storage medium | |
| CN109743390B (en) | Task scheduling method and device, computer equipment and storage medium | |
| CN109672741B (en) | Micro-service monitoring method and device, computer equipment and storage medium | |
| CN109474578B (en) | Message checking method, device, computer equipment and storage medium | |
| CN109446068B (en) | Interface test method, device, computer equipment and storage medium | |
| CN108924258B (en) | Background information pushing method and device, computer equipment and storage medium | |
| CN107678869B (en) | Client abnormity positioning method and device, computer equipment and storage medium | |
| CN108304704B (en) | Authority control method and device, computer equipment and storage medium | |
| CN108427613B (en) | Abnormal interface positioning method and device, computer equipment and storage medium | |
| CN112631913B (en) | Method, device, equipment and storage medium for monitoring operation faults of application program | |
| CN110135129B (en) | Code segment protection method and device, computer equipment and storage medium | |
| CN108256322B (en) | Security testing method and device, computer equipment and storage medium | |
| CN110650186A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN108959384B (en) | Webpage data acquisition method and device, computer equipment and storage medium | |
| CN110727698A (en) | Database access method and device, computer equipment and storage medium | |
| CN111078559A (en) | Method, device, medium and computer equipment for extracting function call in java code | |
| CN112818343B (en) | Block chain big data analysis early warning method and system and cloud platform | |
| CN112698820B (en) | Unified monitoring management method and device for memory and switch and computer equipment | |
| CN111475324A (en) | Log information analysis method and device, computer equipment and storage medium | |
| CN114444072A (en) | Database cluster patrol method, database cluster patrol device, database cluster patrol equipment and database cluster patrol storage medium | |
| CN114579446A (en) | Data processing method and device, computer equipment and computer readable storage medium | |
| CN112070585A (en) | Order state unified management method and device, computer equipment and storage medium | |
| CN111416857A (en) | Client crash processing method, device, system, equipment and storage medium | |
| CN111767262A (en) | Log display method, device, equipment and storage medium | |
| CN112507010B (en) | Service data processing method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |