CN113778801A - Method and device for reporting start event, electronic equipment and storage medium - Google Patents
Method and device for reporting start event, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113778801A CN113778801A CN202111076581.3A CN202111076581A CN113778801A CN 113778801 A CN113778801 A CN 113778801A CN 202111076581 A CN202111076581 A CN 202111076581A CN 113778801 A CN113778801 A CN 113778801A
- Authority
- CN
- China
- Prior art keywords
- parameter
- field
- target
- request
- event
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000004891 communication Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000012360 testing method Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
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/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
Abstract
The application relates to a method and a device for reporting a start event, electronic equipment and a storage medium, which relate to the technical field of software development, and the method for reporting the start event comprises the following steps: under the condition of receiving a first request sent by a target application, acquiring a target template from a preset template library, wherein the first request is obtained based on a starting event of the target application, and the first request carries a request parameter of the starting event; and reporting the starting event under the condition that the current condition meets the preset reporting condition according to the request parameter and the target template. Therefore, each starting of the target application can be tracked or recorded, and the use frequency of different users for the target application can be conveniently analyzed subsequently.
Description
Technical Field
The present application relates to the field of software development technologies, and in particular, to a method and an apparatus for reporting a start event, an electronic device, and a storage medium.
Background
The point burying event can be used for tracking or recording the operation behavior or business process of the user, such as registering an account, logging in an account, agreeing on, commenting and the like, and is widely applied to various application software. However, the types of the existing point-burying events are generally classified into a click event, a load event, a jump event, an exposure event, a page-staying time event, and the like, and these types of events cannot track or record each time of the application program, so that when analyzing the frequency of use of an application program by different users, effective and direct data is lacking, and therefore, how to track or record each time of the application program is called as a technical problem to be solved urgently.
Disclosure of Invention
The application provides a method and a device for reporting a start event, electronic equipment and a storage medium, which are used for solving the problem that the conventional embedded event cannot track or record each start of an application program.
In a first aspect, the present application provides a method for starting event reporting, where the method includes:
under the condition of receiving a first request sent by a target application, acquiring a target template from a preset template library, wherein the first request is obtained based on a starting event of the target application, and the first request carries a request parameter of the starting event;
and reporting the starting event under the condition that the current condition meets the preset reporting condition according to the request parameter and the target template.
Optionally, before reporting the start event when it is determined that the current condition satisfies a preset reporting condition according to the request parameter and the target template, the method further includes:
judging whether fields in the request parameters comprise fields matched with target parameter fields of the target template or not;
under the condition that the fields in the request parameters comprise the fields matched with the target parameter fields, judging whether the parameter values of the fields matched with the target parameter fields in the request parameters are matched with the parameter values of the target parameter fields;
and under the condition that the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field, determining that the current condition meets the preset reporting condition.
Optionally, before reporting the start event when it is determined that the current condition satisfies a preset reporting condition according to the request parameter and the target template, the method further includes:
and determining that the current condition does not satisfy the preset reporting condition under the condition that the field in the request parameter does not include the field matched with the target parameter field, or under the condition that the field in the request parameter includes the field matched with the target parameter field and the parameter value of the field matched with the target parameter field in the request parameter does not match with the parameter value of the target parameter field.
Optionally, before the step of determining whether the parameter value of the field matching the target parameter field in the request parameter matches the parameter value of the target parameter field, the method further includes:
judging whether an unreported event exists in a preset database, wherein the unreported event is an unreported event in events generated before the target application is executed with a starting operation;
reporting the unreported event under the condition that the unreported event exists in the preset database, and executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
Optionally, the target parameter field includes an event name field, an equipment identification field, and a parameter customization field, where the event name field is used to represent identification information corresponding to different event types, the equipment identification field is used to represent equipment information to which the target application belongs, and the parameter customization field is used to represent a customization parameter corresponding to a service requirement of the target application.
Optionally, after determining whether an unreported event exists in the preset database, the method further includes:
judging whether the running environment of the target application is a formal environment or not;
under the condition that the running environment of the target application is an informal environment, acquiring the parameter value of the parameter matched with the parameter custom field from the preset database, and executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field;
and under the condition that the running environment of the target application is a formal environment, executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
In a second aspect, the present application provides a device for reporting a start event, where the device includes:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a target template from a preset template library under the condition of receiving a first request sent by a target application, the first request is obtained based on a starting event of the target application, and the first request carries a request parameter of the starting event;
and the first reporting module is used for reporting the starting event under the condition that the current condition is determined to meet the preset reporting condition according to the request parameter and the target template.
In a third aspect, an air conditioner control device is provided, which comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
the processor is configured to implement the steps of the method for starting event reporting according to any embodiment of the first aspect when executing the program stored in the memory.
In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the method for initiating reporting of an event according to any embodiment of the first aspect.
In the embodiment of the application, a target template is obtained from a preset template library under the condition that a first request sent by a target application is received, wherein the first request is obtained based on a starting event of the target application, and the first request carries a request parameter of the starting event; and reporting the starting event under the condition that the current condition meets the preset reporting condition according to the request parameter and the target template. By the method, when a user starts the target application each time, the first request is generated by triggering the target application and is sent to the back-end server, the back-end server matches the request data of the first request with the target template after receiving the first request, so that whether the current condition meets the preset reporting condition is determined, and the starting event is reported under the condition that the current condition meets the preset reporting condition is determined. Therefore, each starting of the target application can be tracked or recorded, and the use frequency of different users to the target application can be conveniently analyzed subsequently.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic flow chart of a method for reporting a start event according to an embodiment of the present application;
fig. 2 is a second schematic flowchart of a method for reporting a start event according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a device for reporting a start event according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a schematic flow chart of a method for reporting a start event according to an embodiment of the present application. As shown in fig. 1, the method for reporting a start event may include the following steps:
102, under the condition that a first request sent by a target application is received, acquiring a target template from a preset template library, wherein the first request is obtained based on a starting event of the target application, and the first request carries a request parameter of the starting event.
Specifically, the target application may be any application Program (app for short) installed on the user terminal, such as a video playing application, a social application, a browser application, and the like, and the application is not limited in detail. The preset template library is an event template preset on a back-end server by a developer of target application, and a plurality of different event templates can be set according to the reporting requirements of event types, wherein each event template corresponds to one event type. The target template is an event template corresponding to the type of the starting event.
It should be noted that each event template may include one or more parameter fields, and a parameter value of each parameter field may be set according to a service requirement. The parameter fields contained in different event templates may be the same or different.
When a user executes a starting operation on a target application on a display interface of a user terminal, the target application detects a starting event, so that a first request is triggered and generated, and the first request is sent to a back-end server. After receiving the first request, the back-end server may determine a target template from a preset template library based on a data type of a request parameter carried by the first request, and analyze the request parameter in the first request according to the target template.
And step 104, reporting the starting event under the condition that the current condition meets the preset reporting condition according to the request parameter and the target template.
Specifically, the preset reporting condition may be set according to an actual situation, and the application is not particularly limited. For example, the preset reporting condition may be that a field in the request parameter in the first request includes part or all of fields in the target template, or that a parameter value in a field matched with the target template in the first request satisfies a parameter value of a corresponding field in the target template, or a combination of the two cases.
After acquiring the target template and the first request, the back-end server can determine whether the current condition meets a preset reporting condition according to request parameters in the target template and the first request, and report the starting event under the condition that the current condition meets the preset reporting condition; and under the condition that the current condition meets the preset reporting condition, the starting event is not reported.
In this embodiment, each time a user performs a starting operation on a target application, a first request may be generated by triggering, and after receiving the first request, a back-end server matches request data of the first request with a target template, so as to determine whether a current condition satisfies a preset reporting condition, and report a starting event when it is determined that the current condition satisfies the preset reporting condition. Therefore, each starting of the target application can be tracked or recorded, and the use frequency of different users to the target application can be conveniently analyzed subsequently.
Further, based on the embodiment shown in fig. 1, before reporting the start event in the step 104 under the condition that it is determined that the current condition meets the preset reporting condition according to the request parameter and the target template, the start event reporting method further includes the following steps:
judging whether the fields in the request parameters comprise fields matched with the target parameter fields of the target template or not;
under the condition that the fields in the request parameters comprise the fields matched with the target parameter fields, judging whether the parameter values of the fields matched with the target parameter fields in the request parameters are matched with the parameter values of the target parameter fields or not;
and under the condition that the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field, determining that the current condition meets the preset reporting condition.
Specifically, one or more target parameter fields in the target template may be provided, and the present application is not limited specifically. In an embodiment, the target parameter fields may include, but are not limited to: an event name field, a device identification field, a parameter customization field, etc. The event name field is used for representing identification information corresponding to different event types, the corresponding parameter value can be a unique identification of the event type, and the parameter values of the parameter fields of events of the same type are the same. The device identification field is used for representing the device information to which the target application belongs, the corresponding parameter value can be the unique identification of the user terminal, and the device identifications of the parameter field are different if a plurality of users start the target application by using different user terminals. The parameter custom field is used for representing custom parameters corresponding to the service requirements of the target application, the custom parameters of the parameter custom field are different in different event types, and if a certain event type is a starting event, the custom parameters of the parameter custom field can be null; if a certain event type is a time period event (such as a video playing event), the custom parameter of the parameter custom field can set parameters such as a video name and a video type.
In this embodiment, the back-end server may determine the fields in the request parameters and the parameter values in the fields, and only when the fields in the request parameters include the fields matched with the target parameter fields of the target template and whether the parameter values of the fields matched with the target parameter fields in the request parameters are matched with the parameter values of the target parameter fields, the back-end server considers that the current conditions satisfy the preset reporting conditions, and reports the start event. If the field in the request parameter does not include the field matched with the target parameter field of the target template, or if the field in the request parameter includes the field matched with the target parameter field of the target template, the parameter value of the field matched with the target parameter field in the request parameter is not matched with the parameter value of the target parameter field, the back-end server considers that the current condition does not meet the preset reporting condition, does not report the starting event, and throws out an abnormal prompt. Therefore, the target parameter field necessary for starting the event is set in the target template, and the request data is analyzed according to the target parameter field, so that the event type to be reported is ensured to be the starting event.
Further, in step 104, before reporting the start event under the condition that it is determined that the current condition meets the preset reporting condition according to the request parameter and the target template, the start event reporting method further includes the following steps:
and under the condition that the field in the request parameter does not comprise the field matched with the target parameter field, or under the condition that the field in the request parameter comprises the field matched with the target parameter field and the parameter value of the field matched with the target parameter field in the request parameter is not matched with the parameter value of the target parameter field, determining that the current condition does not meet the preset reporting condition.
In this embodiment, the backend server may determine fields in the request parameters and parameter values in the fields, and may determine that the current condition does not satisfy the preset reporting condition when the fields in the request parameters do not include a field matched with the target parameter field, or when the fields in the request parameters include a field matched with the target parameter field and the parameter values of the fields in the request parameters matched with the target parameter field do not match the parameter values of the target parameter field. At this time, the back-end server throws an exception prompt for the developer to perform subsequent analysis.
Further, before the step of determining whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field, the method further includes:
judging whether an unreported event exists in a preset database, wherein the unreported event is an unreported event in events generated before a target application is executed to start operation;
and reporting the unreported event under the condition that the unreported event exists in the preset database, and executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
In an embodiment, after receiving various events, the background server does not report the events in real time, but reports the events until the number of the events reaches a preset number, so that there are often situations that the target application is not reported before the current start and the events are not reported after the last start in a preset database of the background server. Therefore, before judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field, the background server needs to monitor an unreported event in a preset database, and when the unreported event exists in the preset database, a pre-event submission method needs to be called to report the unreported event, so that when the parameter value of the request parameter of the current start event is matched, the interference of the parameter value of the unreported event is avoided, and the accuracy of parameter value matching is ensured.
Further, the target parameter field includes an event name field, a device identification field and a parameter customization field, where the event name field is used to represent identification information corresponding to different event types, the device identification field is used to represent device information to which the target application belongs, and the parameter customization field is used to represent a customization parameter corresponding to a service requirement of the target application.
In one embodiment, the target parameters field may include 3 fields, an event name field, a device identification field, and a parameter customization field. The event name field is used for representing identification information corresponding to different event types, the corresponding parameter value can be a unique identification of the event type, and the parameter values of the parameter fields of events of the same type are the same. The device identification field is used for representing the device information to which the target application belongs, the corresponding parameter value can be the unique identification of the user terminal, and the device identifications of the parameter field are different if a plurality of users start the target application by using different user terminals. The parameter custom field is used for representing custom parameters corresponding to the service requirements of the target application, the custom parameters of the parameter custom field are different in different event types, and if a certain event type is a starting event, the custom parameters of the parameter custom field can be null; if a certain event type is a time period event (such as a video playing event), the custom parameter of the parameter custom field can set parameters such as a video name and a video type. Therefore, the target parameter field necessary for starting the event is set in the target template, and the request data is analyzed according to the target parameter field, so that the event type to be reported is ensured to be the starting event.
Further, after determining whether an unreported event exists in the preset database, the method for starting event reporting further includes:
judging whether the running environment of the target application is a formal environment;
under the condition that the running environment of the target application is an informal environment, acquiring the parameter value of the parameter matched with the parameter custom field from a preset database, and executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field;
and under the condition of an informal environment of the running environment of the target application, executing a step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
In an embodiment, since the target application needs to test the reporting function of the start event before formal use, that is, the background server needs to analyze and verify the request parameter corresponding to the start event when the target application is in a test environment, and after the target application is put into use formally, the background server also needs to analyze and verify the request parameter corresponding to the start event when the target application is in a formal environment, in order to be compatible with the test environment and the formal environment of the target application, ensure that the background server can be used normally no matter in the test environment or in the formal environment of the target application, the background server can judge the running environment of the target application according to the Env field, and when the running environment of the target application is an informal environment, the back-end server can obtain the parameter value of the parameter matched with the parameter custom field from the preset database according to the event name field, and executing the steps as follows: judging whether the parameter value of a field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field; when the running environment of the target application is a formal environment, the steps are directly executed: and judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
Referring to fig. 2, fig. 2 is a second flowchart of a method for reporting a start event according to an embodiment of the present application. As shown in fig. 2, the method for reporting a start event may include the following steps:
The first request is obtained based on a starting event triggered and generated by a user executing a starting operation on a target application, the first request carries a request parameter of the starting event, and the target template is a template matched with the request parameter.
The target parameter field comprises an event name field, an equipment identification field and a parameter custom field, wherein the event name field is used for representing identification information corresponding to different event types, the equipment identification field is used for representing equipment information to which the target application belongs, and the parameter custom field is used for representing custom parameters corresponding to service requirements of the target application. When the fields in the request parameters include fields matching the target parameter fields, step 203 is executed; when the fields in the request parameters do not include fields that match the target parameters fields, step 209 is performed.
When the unreported event exists in the preset database, executing step 204 first, and then executing step 205; when there is no unreported event in the preset database, step 205 is executed.
And step 204, calling an event submitting method to report the unreported event.
And step 205, judging whether the running environment of the target application is a formal environment.
When the running environment of the target application is an informal environment, executing step 206 first and then executing step 207; when the running environment of the target application is the formal environment, step 207 is directly performed.
And step 206, acquiring parameter values of the parameters matched with the parameter custom fields from a preset database.
And step 207, judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
When the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field, executing step 208; when the parameter value of the field of the request parameter matching the target parameter field does not match the parameter value of the target parameter field, step 209 is performed.
And step 208, calculating the occurrence time of the starting events according to the time difference, storing the occurrence time into a preset database, and reporting when the number of the events reaches a preset number.
And step 209, throwing an exception prompt.
It should be noted that the detailed processes of step 201 to step 209 are already described in the above embodiments, and are not described herein again.
In this way, when the user executes the starting operation on the target application each time, the first request is triggered and generated, after the back-end server receives the first request, the request data of the first request is matched with the target template, so as to determine whether the current condition meets the preset reporting condition, and the starting event is reported under the condition that the current condition meets the preset reporting condition. Therefore, each starting of the target application can be tracked or recorded, and the use frequency of different users to the target application can be conveniently analyzed subsequently.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a device for reporting a start event according to an embodiment of the present application. The start event reporting apparatus 300 may include:
an obtaining module 302, configured to obtain a target template from a preset template library when a first request sent by a target application is received, where the first request is obtained based on a start event of the target application, and the first request carries a request parameter of the start event;
a first reporting module 304, configured to report the start event when it is determined that the current condition meets a preset reporting condition according to the request parameter and the target template.
Optionally, the apparatus for reporting a start event 300 may further include:
the first judgment module is used for judging whether the fields in the request parameters comprise fields matched with the target parameter fields of the target template;
the second judgment module is used for judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field or not under the condition that the field in the request parameter comprises the field matched with the target parameter field;
and the first determining module is used for determining that the current condition meets the preset reporting condition under the condition that the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
Optionally, the apparatus for reporting a start event 300 may further include:
and the second determining module is used for determining that the current condition does not meet the preset reporting condition under the condition that the field in the request parameter does not comprise the field matched with the target parameter field, or the field in the request parameter comprises the field matched with the target parameter field, and the parameter value of the field matched with the target parameter field in the request parameter is not matched with the parameter value of the target parameter field.
Optionally, the apparatus for reporting a start event 300 may further include:
the second judgment module is used for judging whether an unreported event exists in the preset database, wherein the unreported event is an unreported event in events generated before the target application is executed and started;
and the second reporting module is used for reporting the unreported event under the condition that the unreported event exists in the preset database, and executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
Optionally, the target parameter field includes an event name field, a device identification field, and a parameter customization field, where the event name field is used to represent identification information corresponding to different event types, the device identification field is used to represent device information to which the target application belongs, and the parameter customization field is used to represent a customization parameter corresponding to a service requirement of the target application.
Optionally, the apparatus for reporting a start event 300 may further include:
the third judgment module is used for judging whether the running environment of the target application is a formal environment;
the first execution module is used for acquiring the parameter value of the parameter matched with the parameter custom field from the preset database under the condition that the running environment of the target application is an informal environment, and executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field;
and the second execution module is used for executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field under the condition that the running environment of the target application is a formal environment.
It should be noted that the start event reporting apparatus 300 can implement the steps in the embodiments of the start event reporting method, and can achieve the same technical effect.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an electronic device provided in the embodiment of the present application, the electronic device includes a processor 411, a communication interface 412, a memory 413, and a communication bus 414, where the processor 411, the communication interface 412, and the memory 413 complete mutual communication through the communication bus 414,
a memory 413 for storing a computer program;
in an embodiment of the present application, when the processor 411 is configured to execute a program stored in the memory 413, the method for reporting a start event according to any one of the foregoing method embodiments is implemented, including:
under the condition of receiving a first request sent by a target application, acquiring a target template from a preset template library, wherein the first request is obtained based on a starting event of the target application, and the first request carries a request parameter of the starting event;
and reporting the starting event under the condition that the current condition meets the preset reporting condition according to the request parameter and the target template.
An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the method for starting event reporting provided in any of the foregoing method embodiments.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for reporting a start event, the method comprising:
under the condition of receiving a first request sent by a target application, acquiring a target template from a preset template library, wherein the first request is obtained based on a starting event of the target application, and the first request carries a request parameter of the starting event;
and reporting the starting event under the condition that the current condition meets the preset reporting condition according to the request parameter and the target template.
2. The method according to claim 1, wherein before reporting the start event when it is determined that the current condition satisfies a preset reporting condition according to the request parameter and the target template, the method further comprises:
judging whether fields in the request parameters comprise fields matched with target parameter fields of the target template or not;
under the condition that the fields in the request parameters comprise the fields matched with the target parameter fields, judging whether the parameter values of the fields matched with the target parameter fields in the request parameters are matched with the parameter values of the target parameter fields;
and under the condition that the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field, determining that the current condition meets the preset reporting condition.
3. The method according to claim 2, wherein before reporting the start event when it is determined that the current condition satisfies a preset reporting condition according to the request parameter and the target template, the method further comprises:
and determining that the current condition does not satisfy the preset reporting condition under the condition that the field in the request parameter does not include the field matched with the target parameter field, or under the condition that the field in the request parameter includes the field matched with the target parameter field and the parameter value of the field matched with the target parameter field in the request parameter does not match with the parameter value of the target parameter field.
4. The method of claim 2, wherein prior to the step of determining whether the parameter value of the field of the request parameter that matches the target parameter field matches the parameter value of the target parameter field, the method further comprises:
judging whether an unreported event exists in a preset database, wherein the unreported event is an unreported event in events generated before the target application is executed with a starting operation;
reporting the unreported event under the condition that the unreported event exists in the preset database, and executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
5. The method according to any one of claims 1-4, wherein the target parameter fields include an event name field, a device identification field and a parameter customization field, wherein the event name field is used for characterizing identification information corresponding to different event types, the device identification field is used for characterizing device information to which the target application belongs, and the parameter customization field is used for characterizing customization parameters corresponding to business requirements of the target application.
6. The method of claim 5, wherein after determining whether there are any unreported events in the predefined database, the method further comprises:
judging whether the running environment of the target application is a formal environment or not;
under the condition that the running environment of the target application is an informal environment, acquiring the parameter value of the parameter matched with the parameter custom field from the preset database, and executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field;
and under the condition that the running environment of the target application is a formal environment, executing the step of judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
7. An apparatus for reporting a start event, the apparatus comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a target template from a preset template library under the condition of receiving a first request sent by a target application, the first request is obtained based on a starting event of the target application, and the first request carries a request parameter of the starting event;
and the first reporting module is used for reporting the starting event under the condition that the current condition is determined to meet the preset reporting condition according to the request parameter and the target template.
8. The apparatus of claim 7, further comprising:
the first judging module is used for judging whether fields in the request parameters comprise fields matched with target parameter fields of the target template or not;
the second judging module is used for judging whether the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field or not under the condition that the field in the request parameter comprises the field matched with the target parameter field;
and the determining module is used for determining that the current condition meets the preset reporting condition under the condition that the parameter value of the field matched with the target parameter field in the request parameter is matched with the parameter value of the target parameter field.
9. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor, configured to implement the steps of the method for reporting a start event according to any one of claims 1 to 6 when executing a program stored in a memory.
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 for initiating event reporting according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111076581.3A CN113778801A (en) | 2021-09-14 | 2021-09-14 | Method and device for reporting start event, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111076581.3A CN113778801A (en) | 2021-09-14 | 2021-09-14 | Method and device for reporting start event, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113778801A true CN113778801A (en) | 2021-12-10 |
Family
ID=78843860
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111076581.3A Pending CN113778801A (en) | 2021-09-14 | 2021-09-14 | Method and device for reporting start event, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113778801A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060136784A1 (en) * | 2004-12-06 | 2006-06-22 | Microsoft Corporation | Controlling software failure data reporting and responses |
| CN106789195A (en) * | 2016-12-02 | 2017-05-31 | 华为技术有限公司 | A kind of event-handling method and Network Management Equipment, server |
| CN106940679A (en) * | 2017-02-23 | 2017-07-11 | 中科创达软件股份有限公司 | Data processing method and device |
| CN107343091A (en) * | 2017-06-27 | 2017-11-10 | 努比亚技术有限公司 | Data reporting method and system |
| CN108134838A (en) * | 2017-12-27 | 2018-06-08 | 广东欧珀移动通信有限公司 | data reporting method, device, mobile terminal and computer-readable medium |
| CN112069034A (en) * | 2020-09-22 | 2020-12-11 | 深圳市欢太科技有限公司 | Fast application exception handling method and device, electronic equipment and storage medium |
| CN112559283A (en) * | 2020-12-08 | 2021-03-26 | 中国联合网络通信集团有限公司 | Signaling record processing method, device and equipment |
| CN113157525A (en) * | 2021-04-23 | 2021-07-23 | 北京高途云集教育科技有限公司 | Data collection method and device, computer equipment and storage medium |
-
2021
- 2021-09-14 CN CN202111076581.3A patent/CN113778801A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060136784A1 (en) * | 2004-12-06 | 2006-06-22 | Microsoft Corporation | Controlling software failure data reporting and responses |
| CN106789195A (en) * | 2016-12-02 | 2017-05-31 | 华为技术有限公司 | A kind of event-handling method and Network Management Equipment, server |
| CN106940679A (en) * | 2017-02-23 | 2017-07-11 | 中科创达软件股份有限公司 | Data processing method and device |
| CN107343091A (en) * | 2017-06-27 | 2017-11-10 | 努比亚技术有限公司 | Data reporting method and system |
| CN108134838A (en) * | 2017-12-27 | 2018-06-08 | 广东欧珀移动通信有限公司 | data reporting method, device, mobile terminal and computer-readable medium |
| CN112069034A (en) * | 2020-09-22 | 2020-12-11 | 深圳市欢太科技有限公司 | Fast application exception handling method and device, electronic equipment and storage medium |
| CN112559283A (en) * | 2020-12-08 | 2021-03-26 | 中国联合网络通信集团有限公司 | Signaling record processing method, device and equipment |
| CN113157525A (en) * | 2021-04-23 | 2021-07-23 | 北京高途云集教育科技有限公司 | Data collection method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109189665B (en) | Method and device for recording, replaying and automatically testing data | |
| CN108491321B (en) | Method and device for determining test case range and storage medium | |
| CN110502442B (en) | Dynamic parameter checking method, device, equipment and storage medium | |
| US20150186195A1 (en) | Method of analysis application object which computer-executable, server performing the same and storage media storing the same | |
| CN111522711A (en) | Data monitoring processing system, method, execution end, monitoring end and electronic equipment | |
| CN115292163A (en) | Application program detection method and device and computer readable storage medium | |
| CN112529575A (en) | Risk early warning method, equipment, storage medium and device | |
| CN110020550B (en) | Assessment method, device and equipment for verification platform | |
| CN112948224A (en) | Data processing method, device, terminal and storage medium | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN117495544A (en) | Sandbox-based wind control evaluation method, sandbox-based wind control evaluation system, sandbox-based wind control evaluation terminal and storage medium | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN112882933A (en) | Script recording method, device, equipment and storage medium | |
| CN113778801A (en) | Method and device for reporting start event, electronic equipment and storage medium | |
| CN111651500A (en) | User identity recognition method, electronic device and storage medium | |
| CN111340635A (en) | Data checking method, equipment, server and readable storage medium | |
| CN111078382A (en) | Command timeout processing method and device | |
| CN115757107A (en) | Embedded point detection method, device, server and storage medium | |
| CN110688173A (en) | Positioning method and device of components in cross-platform interface framework and electronic equipment | |
| CN115756934A (en) | Application crash analysis method and device | |
| CN115391224A (en) | Flow playback method and device, computer equipment and readable storage medium | |
| CN109165127B (en) | Problem interface positioning method and device and electronic equipment | |
| CN114115933A (en) | Method, system, device, electronic equipment and medium for software upgrading | |
| CN112433946A (en) | Interface test management method, device, equipment and storage medium | |
| CN113923190A (en) | Method and device for identifying equipment identification jump, server 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 |