CN112306797A - Embedded point information reporting method and device, storage medium and electronic equipment - Google Patents
Embedded point information reporting method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN112306797A CN112306797A CN202011141736.2A CN202011141736A CN112306797A CN 112306797 A CN112306797 A CN 112306797A CN 202011141736 A CN202011141736 A CN 202011141736A CN 112306797 A CN112306797 A CN 112306797A
- Authority
- CN
- China
- Prior art keywords
- reporting
- information
- control information
- avalanche
- service
- 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 66
- 238000012545 processing Methods 0.000 claims abstract description 16
- 238000004590 computer program Methods 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 238000002955 isolation Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000009877 rendering Methods 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/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
- G06F11/3433—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment for load management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the application discloses a method and a device for reporting embedded point information, a storage medium and electronic equipment, wherein the method comprises the following steps: receiving load information sent by a service server, generating avalanche control information based on the load information, adopting the avalanche control information to carry out reporting control processing on buried point information of a target service when the control validity period corresponding to the avalanche control information is within, and reporting the buried point information to the service server when the control validity period is over. By adopting the embodiment of the application, the service reporting buried point information is managed and controlled by acquiring the avalanche control information corresponding to the load condition of the service server, so that the overload of the service server caused by the centralized reporting of the buried point information by the service is prevented, and the avalanche of the server is avoided.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for reporting embedded point information, a storage medium, and an electronic device.
Background
The buried point is a process-specific collection of information in the application for tracking the usage status of the application, and then for further optimizing the product or providing data support for the operation. At present, a third-party Software Development Kit (SDK) is mostly used to help applications to perform data statistics, but the current SDK does not limit the reporting of embedded points, and it is easy to cause server avalanche and data loss because multiple services report a large amount of embedded points at the same time.
Disclosure of Invention
The embodiment of the application provides a method and a device for reporting embedded point information, a storage medium and an electronic device, which can manage and control the service reporting embedded point information by acquiring avalanche control information corresponding to the load condition of a service server, and prevent the overload of the service server caused by centralized reporting of the embedded point information by the service, thereby causing server avalanche. The technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a method for reporting embedded point information, where the method includes:
receiving load information sent by a service server, and generating avalanche control information based on the load information;
when the avalanche control information is within the control validity period corresponding to the avalanche control information, reporting, managing and controlling the buried point information of the target service by adopting the avalanche control information;
and when the control validity period is finished, reporting the embedded point information to the service server.
In a second aspect, an embodiment of the present application provides a device for reporting embedded point information, where the device includes:
the control information generation module is used for receiving load information sent by the service server and generating avalanche control information based on the load information;
the reporting management module is used for adopting the avalanche control information to carry out reporting management and control processing on the buried point information of the target service when the control validity period corresponding to the avalanche control information is within;
and the information reporting module is used for reporting the embedded point information to the service server when the control validity period is finished.
In a third aspect, embodiments of the present application provide a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the above-mentioned method steps.
In a fourth aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the above-mentioned method steps.
The beneficial effects brought by the technical scheme provided by some embodiments of the application at least comprise:
in one or more embodiments of the present application, load information sent by a service server is received, avalanche control information is generated based on the load information, when the control validity period corresponding to the avalanche control information is within, the avalanche control information is adopted to perform reporting control processing on embedded point information of a target service, and when the control validity period is over, the embedded point information can be directly reported to the service server. The service reporting embedded point information is managed and controlled by acquiring the avalanche control information corresponding to the load condition of the service server, so that the overload of the service server caused by the centralized reporting of the embedded point information by the service is prevented, and the avalanche of the server is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present application 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, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a method for reporting embedded point information according to an embodiment of the present disclosure;
fig. 2 is a schematic diagram illustrating an example of acquiring avalanche control information according to an embodiment of the present application;
fig. 3 is a schematic flow chart of another method for reporting embedded point information according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart of a process for determining whether avalanche control information is satisfied according to an embodiment of the present application;
fig. 5 is a schematic flowchart of another method for reporting embedded point information according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a device for reporting embedded point information according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a control information generation module according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a report management module according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of another device for reporting embedded point information according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
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 only a part of the embodiments of the present application, and not all of the 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.
In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the present application, it is noted that, unless explicitly stated or limited otherwise, "including" and "having" and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art. Further, in the description of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The method for reporting the embedded point information provided by the embodiment can be realized by depending on a computer program, and can be run on an embedded point information reporting device based on a von neumann system. The computer program may be integrated into the application or may run as a separate tool-like application. The device for reporting the embedded point information can be an embedded point SDK, and can also be an application client or an electronic device equipped with the embedded point SDK.
The method for reporting the embedded point information provided by the present application is described in detail below with reference to specific embodiments.
Fig. 1 is a schematic flow chart of a method for reporting embedded point information according to an embodiment of the present disclosure. As shown in fig. 1, the method of the embodiment of the present application may include the following steps S101-S104.
S101, receiving load information sent by a service server, and generating avalanche control information based on the load information.
The service server is a server for receiving the embedded point information sent by the service and performing big data analysis based on the embedded point information, and the load information sent by the service server refers to the load condition of a load port of the service server for receiving the embedded point information sent by the service. The avalanche control information comprises various conditions for controlling the service embedded point reporting by the embedded point SDK and the control validity period of the avalanche control information, and whether the embedded point information meets the conditions or not is judged to judge which embedded point information can be reported and which can not be reported in the control validity period, so that the purpose of preventing service server avalanche is achieved. The avalanche control information may include an expiration date of the avalanche control information, a retry time interval of the service server, a request threshold in a time slice, a reporting threshold in the time slice, and the like. The service may be a module installed in the same application or electronic device as the buried-point SDK, another SDK, or the like.
The generation of the avalanche control information based on the load information means that the avalanche control information with different contents is generated according to the load condition of the load port returned by the service server.
Further, as shown in fig. 2, after obtaining the load information, the embedded point SDK may send the load information to the cloud control center and request for avalanche control information corresponding to the load information, and the embedded point SDK manages and controls the embedded point report of the service based on the avalanche control information returned by the cloud control center.
Or after the embedded point SDK acquires the load information, the embedded point reporting of the service may be managed and controlled by invoking avalanche control information corresponding to the load information, which is pre-stored in the embedded point SDK, according to the load information. The avalanche control information stored in the embedded point SDK by the cloud line can be set by the cloud control center and sent to the embedded point SDK for storage, and can also be set on the embedded point SDK.
Further, if the utilization rate of the load port does not exceed the utilization rate threshold, the embedded point SDK may not obtain the avalanche control information, the embedded point information of the service may be normally reported, and the utilization rate threshold may be set on the service server, or may be set by the embedded point SDK and sent to the service server.
A feasible method for the service server to return the load information is that, according to the usage rate of the load port, the service server returns different character strings, for example:
if the utilization rate of the load port is more than or equal to 75%, the service server returns a character string 0 to the embedded point SDK;
if the utilization rate of the load port is greater than or equal to 85%, the service server returns a character string 1 to the embedded point SDK;
if the utilization rate of the load port is greater than or equal to 95%, the service server returns a character string 2 to the embedded point SDK;
and if the utilization rate of the load port is more than or equal to 100%, the service server returns the character string 3 to the embedded point SDK.
And after receiving the different character strings, the embedded point SDK requests or calls pre-stored avalanche control information from the cloud control center based on the character strings to control the embedded point report of the service. Similarly, the embedded point SDK may also generate an avalanche controller using the avalanche control information as configuration, and use the avalanche controller to manage and control the embedded point report of the service.
And S102, judging whether the avalanche control information is in the control validity period corresponding to the avalanche control information.
The control validity period refers to the validity time of the avalanche control information, the embedded point SDK can manage and control the embedded point report of the service according to the avalanche control information in the control validity period, when the avalanche control information is invalid, the embedded point report of the service cannot be controlled according to the avalanche control information, and the embedded point of the service can be normally reported to the service server.
If the avalanche control information is in the control validity period corresponding to the avalanche control information, executing S103; and if the avalanche control information is not in the control validity period corresponding to the avalanche control information, executing S104.
And S103, reporting, managing and controlling the buried point information of the target service by adopting the avalanche control information.
When the avalanche control information is within the valid period corresponding to the avalanche control information, the embedded point SDK judges whether the embedded point information of the target service meets the reporting condition or not according to the avalanche control information, wherein the embedded point information of the target service comprises embedded point data to be reported to the service server by the target service and an embedded point reporting request of the target service.
For example, whether the buried point reporting request of the target service is not in the retry time interval, whether the number of the buried point reporting requests of the target service in the current time slice of the target service does not exceed the request threshold, and/or whether the buried point data reporting amount of the target service in the current time slice of the target service does not exceed the reporting threshold is judged, if the above conditions are met, the buried point SDK normally reports the buried point information of the target service to the service server, and if the conditions are not met, the buried point SDK rejects the buried point reporting request of the target service.
Further, if the embedded point SDK rejects the embedded point reporting request of the target service, retry information is sent to the target service, and the target service is notified to resend the embedded point reporting request.
And S104, reporting the embedded point information to the service server.
And when the service is not in the valid period corresponding to the avalanche control information, the embedded point SDK cannot control the embedded point reporting of the service according to the avalanche control information, and directly reports the embedded point information of the target service to the service server.
In the embodiment of the application, load information sent by a service server is received, avalanche control information is generated based on the load information, when the load information is within a control validity period corresponding to the avalanche control information, the avalanche control information is adopted to carry out reporting control processing on buried point information of a target service, and when the control validity period is finished, the buried point information can be directly reported to the service server. The service reporting embedded point information is managed and controlled by acquiring the avalanche control information corresponding to the load condition of the service server, so that the overload of the service server caused by the centralized reporting of the embedded point information by the service is prevented, and the avalanche of the server is avoided.
Fig. 3 is a schematic flow chart of a method for reporting embedded point information according to an embodiment of the present disclosure. As shown in fig. 3, the method of the embodiment of the present application may include the following steps S201 to S209.
S201, when the access of the target service is detected, a target database corresponding to the target service is created.
When the embedded point SDK detects that a target service is accessed, a corresponding target database is established for the target service, and only data generated by the target service or data related to the target service is stored in the target database.
Further, when detecting that the target service is accessed, the embedded point SDK may also create an independent instance of the target service, a Uniform Resource Locator (URL), a network adapter, an exception catcher, or the like for the target service, so as to implement physical isolation and logical isolation between services.
S202, collecting the buried point information of the target service by adopting the buried point process corresponding to the target service, and storing the buried point information in the target database.
And the embedded point SDK adopts an embedded point process corresponding to the target service to acquire embedded point information of the target service, wherein the embedded point information comprises embedded point data and an embedded point reporting request of the service. The data of the buried point is data information collected by the process of the buried point, such as login and logout time of a user, browsing page of the user and other operation information of the user for the service. The embedded point reporting request is a request for applying reporting of the embedded point data to the service server, which is sent by the target service to the embedded point SDK, and the embedded point SDK reports the embedded point data of the target service to the service server according to the embedded point reporting request of the target service.
And the embedded point SDK stores the embedded point information of the acquired target data in a target database, and then reports the corresponding embedded point data in the target database according to the embedded point reporting request in the embedded point information. The embedded point reporting request can include application time for requesting the embedded point to report, and the embedded point SDK reports the embedded point data at the application time of the target service and judges whether the reporting condition is met.
Further, the embedded point SDK may also receive an embedded point reporting request of the target service, store the corresponding embedded point data in the target database, and report the embedded point data according to the embedded point reporting request.
And S203, when the target service is detected to be cold-started, sending a request for inquiring load to the service server.
The target service cold start means that when the target service is started, the background has no process of the target service, and at this time, the system will re-create a new process to be allocated to the target service, and this starting mode is cold start. Of course, when the application program where the target service is located is cold-started, the inquiry load request can also be sent to the service server, so that server avalanche caused by centralized reporting of the request by the buried point due to the fact that the multi-service of the cold-start application is pulled alive is prevented.
And when receiving the load inquiry request of the embedded point SDK, the service server sends the load information of the current load interface to the embedded point SDK.
And S204, receiving load information returned by the service server based on the query load request, and acquiring avalanche control information corresponding to the load information.
See S101 for details, which are not described herein.
S205, acquiring a buried point reporting request for the buried point information in the target database.
And acquiring a buried point reporting request in the buried point information in the target database, and reporting the corresponding buried point data by the buried point SDK according to the buried point reporting request.
And S206, judging whether the control validity period corresponding to the avalanche control information is within.
The control validity period refers to the validity time of the avalanche control information, the embedded point SDK can manage and control the embedded point report of the service according to the avalanche control information in the control validity period, when the avalanche control information is invalid, the embedded point report of the service cannot be controlled according to the avalanche control information, and the embedded point of the service can be normally reported to the service server.
If the avalanche control information is in the control validity period corresponding to the avalanche control information, executing S107; if the avalanche control information is not within the control validity period corresponding to the avalanche control information, S109 is executed.
And S207, judging whether the reporting condition of the buried point reporting request meets the avalanche control information.
Further, when the reporting time of the buried point reporting request is within the reporting retry time interval indicated by the avalanche control information, the reporting condition does not satisfy the avalanche control information.
The reporting retry time interval refers to a retry time interval contained in the avalanche control information, the embedded point SDK within the retry time interval rejects the embedded point reporting requests of all services, and the retry time interval is a time for buffering for the service server.
Further, a first reporting quantity of a point burying request and a second reporting quantity of the point burying data of the point burying information in the current time slice are obtained;
and when the first reporting quantity is greater than a request reporting threshold value and/or the second reporting quantity is greater than a data reporting threshold value, the reporting condition does not meet the avalanche control information.
The first reporting quantity refers to the number of reporting requests of the buried points of the target service in the current time slice, and the second reporting quantity refers to the size of the buried point data reported by the target service in the current time slice. And when the first reporting quantity is greater than the request reporting threshold and/or the second reporting quantity is greater than the data reporting threshold, the reporting condition does not meet the avalanche control information.
As shown in fig. 4, a schematic flow chart of determining whether the reporting condition of the buried point reporting request satisfies the avalanche control information, it should be noted that the execution sequence of the steps of determining whether the time interval is retry, determining whether the first reporting amount is greater than the request reporting threshold, and determining whether the second reporting amount is greater than the data reporting threshold is not sequential, and may be arbitrarily changed, and the steps are not limited herein.
And S208, rejecting the buried point reporting request.
And if the reporting condition of the buried point reporting request does not meet the avalanche control information, the buried point SDK rejects the buried point reporting request, and can send retry information to the target service while rejecting the buried point reporting request.
Further, after the target service receives the retry information, the embedded point reporting request may be sent to the embedded point SDK again to replace the embedded point reporting request originally stored in the target database, and if the reporting condition of the re-sent embedded point reporting request satisfies the avalanche control information, the embedded point SDK may directly report the embedded point data of the target service in the target database.
S209, reporting the buried point information in the target database to the service server.
And if the reporting condition of the embedded point reporting request of the embedded point meets the avalanche control information or is not in the valid period corresponding to the avalanche control information, the embedded point SDK directly reports the embedded point data corresponding to the embedded point reporting request in the target database to the service server.
Further, if the buried point data is reported successfully, the buried point SDK deletes the buried point data in the target database so as to save the storage space of the target database.
In the embodiment of the application, a corresponding target database is created for the target service, and the embedded point information of the target service is stored in the target database, so that the purpose of realizing physical isolation of each service is achieved, and the condition that one service data is mistaken to influence other services when multiple service data are stored together is avoided. When the target service is cold started, an inquiry load request is sent to the service server, avalanche control information is obtained according to the returned load information, excessive information of the reported embedded points is prevented when the target service is cold started, and overload or avalanche of a load port of the service server is avoided. When the control validity period corresponding to the avalanche control information is within, reporting control processing is carried out on the embedded point information of the target service by using the avalanche control information, and when the control validity period is over, the embedded point information can be directly reported to the service server. The service reporting embedded point information is managed and controlled by acquiring the avalanche control information corresponding to the load condition of the service server, so that the overload of the service server caused by the centralized reporting of the embedded point information by the service is prevented, and the avalanche of the server is avoided.
Fig. 5 is a schematic flow chart of a method for reporting embedded point information according to an embodiment of the present disclosure. As shown in fig. 5, the method of the embodiment of the present application may include the following steps S301 to S309.
S301, when detecting the access of the target service, creating a target database corresponding to the target service.
See S201 specifically, and the details are not repeated here.
S302, collecting the buried point information of the target service by adopting the buried point process corresponding to the target service, and storing the buried point information in the target database.
See S202 specifically, and will not be described herein.
And S303, receiving the load information sent by the service server, and generating the avalanche control information based on the load information.
See S101 for details, which are not described herein.
S304, acquiring a buried point reporting request for the buried point information in the target database.
And acquiring a buried point reporting request in the buried point information in the target database, and reporting the corresponding buried point data by the buried point SDK according to the buried point reporting request.
S305, judging whether the control validity period corresponding to the avalanche control information is within.
See S206 for details, which are not described herein.
If the avalanche control information is in the control validity period corresponding to the avalanche control information, executing S306; if the avalanche control information is not within the control validity period corresponding to the avalanche control information, S308 is executed.
And S306, judging whether the reporting condition of the buried point reporting request meets the avalanche control information.
See S207 specifically, and will not be described herein.
S307, rejecting the buried point reporting request.
See S208 for details, which are not described herein.
S308, reporting the buried point information in the target database to the service server.
See S209 specifically, and are not described herein again.
S309, when the buried point information of the target service is reported to the service server, receiving the load information sent by the server, and acquiring the avalanche control information corresponding to the load information.
After S309, S304 is continuously executed, in the process of reporting the target service buried point information, if the service server is avalanche or the usage rate of the load port exceeds the avalanche warning threshold, the service server sends the load information to the buried point SDK, and after the buried point SDK acquires the avalanche control information based on the load information, the avalanche control information may also be applied to control the reporting of the buried point information of the target service.
In the embodiment of the application, a corresponding target database is created for the target service, and the embedded point information of the target service is stored in the target database, so that the purpose of realizing physical isolation of each service is achieved, and the condition that one service data is mistaken to influence other services when multiple service data are stored together is avoided. When the control validity period corresponding to the avalanche control information is within, reporting control processing is carried out on the embedded point information of the target service by using the avalanche control information, and when the control validity period is over, the embedded point information can be directly reported to the service server. The service reporting embedded point information is managed and controlled by acquiring the avalanche control information corresponding to the load condition of the service server, so that the overload of the service server caused by the centralized reporting of the embedded point information by the service is prevented, and the avalanche of the server is avoided. In the process of reporting the embedded point information, the load information can be received and the avalanche control information can be obtained, the loss of mode data is prevented when the server is in avalanche, and the service server can be prevented from being in avalanche if the server is not in avalanche but is in overhigh load.
The following describes in detail the buried point information reporting device provided in the embodiment of the present application with reference to fig. 6 to 9. It should be noted that, the embedded point information reporting devices shown in fig. 6 to fig. 9 are used to execute the method of the embodiments shown in fig. 1 to fig. 5 of the present application, and for convenience of description, only the portions related to the embodiments of the present application are shown, and details of the specific technology are not disclosed, please refer to the embodiments shown in fig. 1 to fig. 5 of the present application.
Please refer to fig. 6, which shows a schematic structural diagram of a device for reporting embedded point information according to an exemplary embodiment of the present application. The buried point information reporting device can be realized by software, hardware or a combination of the software and the hardware to form all or part of the device. The device 1 comprises a control information generating module 11, a reporting management module 12 and an information reporting module 13.
A control information generation module 11, configured to receive load information sent by a service server, and generate avalanche control information based on the load information;
the reporting management module 12 is configured to, when the avalanche control information is within the control validity period corresponding to the avalanche control information, perform reporting management and control processing on the embedded point information of the target service by using the avalanche control information;
and an information reporting module 13, configured to report the embedded point information to the service server when the control validity period ends.
Optionally, the apparatus 1 further includes:
a buried point information storage module 14, configured to create a target database corresponding to a target service when detecting that the target service is accessed;
and acquiring the buried point information of the target service by adopting a buried point process corresponding to the target service, and storing the buried point information in the target database.
Optionally, the control information generating module 11 includes:
the pre-policy unit 111 is configured to send a request for querying a load to the service server when a cold start of the target service is detected;
and receiving load information returned by the service server based on the query load request, and acquiring avalanche control information corresponding to the load information.
Optionally, the controller generating module 11 includes:
and the post-policy unit 112 is configured to receive load information sent by a server and obtain avalanche control information corresponding to the load information when the embedded point information of the target service is reported to the service server.
Fig. 7 is a schematic structural diagram of a control information generation module.
Optionally, the reporting management module 12 is specifically configured to:
acquiring a buried point reporting request for the buried point information in the target database;
when the reporting condition of the buried point reporting request does not meet the avalanche control information, rejecting the buried point reporting request;
and when the reporting condition meets the avalanche control information, reporting the buried point information in the target database to the service server.
Optionally, the reporting management module 12 includes:
a retry interval determining unit 121, configured to reject the buried point reporting request when the reporting time of the buried point reporting request is within the reporting retry time interval indicated by the avalanche control information.
Optionally, the reporting management module 12 includes:
a reporting amount determining unit 122, configured to obtain a first reporting amount of a point burying request of the point burying information in a current time slice and a second reporting amount of the point burying data;
and when the first reporting quantity is larger than a request reporting threshold value and/or the second reporting quantity is larger than a data reporting threshold value, rejecting the buried point reporting request.
Fig. 8 is a schematic structural diagram of a reporting management module.
Fig. 9 shows a schematic structure of another device for reporting embedded point information.
In the embodiment of the application, load information sent by a service server is received, avalanche control information is generated based on the load information, when the load information is within a control validity period corresponding to the avalanche control information, the avalanche control information is adopted to carry out reporting control processing on buried point information of a target service, and when the control validity period is finished, the buried point information can be directly reported to the service server. The service reporting embedded point information is managed and controlled by acquiring the avalanche control information corresponding to the load condition of the service server, so that the overload of the service server caused by the centralized reporting of the embedded point information by the service is prevented, and the avalanche of the server is avoided.
It should be noted that, when the device for reporting embedded point information provided in the foregoing embodiment executes the method for reporting embedded point information, the division of each functional module is merely used as an example, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the embedded point information reporting device and the embedded point information reporting method provided by the above embodiments belong to the same concept, and details of implementation processes are found in the method embodiments, which are not described herein again.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
An embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method for reporting the embedded point information according to the embodiments shown in fig. 1 to 5, and a specific execution process may refer to specific descriptions of the embodiments shown in fig. 1 to 5, which is not described herein again.
The present application further provides a computer program product, where at least one instruction is stored in the computer program product, and the at least one instruction is loaded by the processor and executes the method for reporting the embedded point information according to the embodiments shown in fig. 1 to 5, where a specific execution process may refer to specific descriptions of the embodiments shown in fig. 1 to 5, and details are not described herein.
Please refer to fig. 10, which provides a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 10, the electronic device 1000 may include: at least one processor 1001, at least one network interface 1004, a user interface 1003, memory 1005, at least one communication bus 1002.
Wherein a communication bus 1002 is used to enable connective communication between these components.
The user interface 1003 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 1003 may also include a standard wired interface and a wireless interface.
The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.
The Memory 1005 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 1005 includes a non-transitory computer-readable medium. The memory 1005 may be used to store an instruction, a program, code, a set of codes, or a set of instructions. The memory 1005 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 1005 may optionally be at least one memory device located remotely from the processor 1001. As shown in fig. 10, the memory 1005, which is a computer storage medium, may include an operating system, a network communication module, a user interface module, and a buried point information reporting application.
In the electronic device 1000 shown in fig. 10, the user interface 1003 is mainly used as an interface for providing input for a user, and acquiring data input by the user; the processor 1001 may be configured to invoke the buried point information reporting application stored in the memory 1005, and specifically execute the following operations:
receiving load information sent by a service server, and generating avalanche control information based on the load information;
when the avalanche control information is within the control validity period corresponding to the avalanche control information, reporting, managing and controlling the buried point information of the target service by adopting the avalanche control information;
and when the control validity period is finished, reporting the embedded point information to the service server.
In one embodiment, before performing the receiving of the load information sent by the traffic server, the processor 1001 further performs the following operations:
when detecting that a target service is accessed, creating a target database corresponding to the target service;
and acquiring the buried point information of the target service by adopting a buried point process corresponding to the target service, and storing the buried point information in the target database.
In one embodiment, when the processor 1001 receives load information sent by a service server and generates avalanche control information based on the load information, it specifically performs the following operations:
when the target service is detected to be cold started, sending a request for inquiring load to a service server;
and receiving load information returned by the service server based on the query load request, and acquiring avalanche control information corresponding to the load information.
In one embodiment, when the processor 1001 receives load information sent by a service server and generates avalanche control information based on the load information, it specifically performs the following operations:
when the embedded point information of the target service is reported to the service server, the load information sent by the server is received, and the avalanche control information corresponding to the load information is obtained.
In an embodiment, when performing reporting management and control processing on the buried point information of the target service by using the avalanche control information, the processor 1001 specifically performs the following operations:
acquiring a buried point reporting request for the buried point information in the target database;
when the reporting condition of the buried point reporting request does not meet the avalanche control information, rejecting the buried point reporting request;
and when the reporting condition meets the avalanche control information, reporting the buried point information in the target database to the service server.
In an embodiment, when the processor 1001 rejects the buried point reporting request when the reporting condition does not satisfy the avalanche control information, specifically:
and when the reporting time of the buried point reporting request is within the reporting retry time interval indicated by the avalanche control information, rejecting the buried point reporting request.
In an embodiment, when the processor 1001 rejects the buried point reporting request when the reporting condition does not satisfy the avalanche control information, specifically:
acquiring a first reporting quantity of a point burying request of the point burying information in a current time slice and a second reporting quantity of the point burying information;
and when the first reporting quantity is larger than a request reporting threshold value and/or the second reporting quantity is larger than a data reporting threshold value, rejecting the buried point reporting request.
In the embodiment of the application, load information sent by a service server is received, avalanche control information is generated based on the load information, when the load information is within a control validity period corresponding to the avalanche control information, the avalanche control information is adopted to carry out reporting control processing on buried point information of a target service, and when the control validity period is finished, the buried point information can be directly reported to the service server. The service reporting embedded point information is managed and controlled by acquiring the avalanche control information corresponding to the load condition of the service server, so that the overload of the service server caused by the centralized reporting of the embedded point information by the service is prevented, and the avalanche of the server is avoided.
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 a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory or a random access memory.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.
Claims (10)
1. A method for reporting embedded point information is characterized by comprising the following steps:
receiving load information sent by a service server, and generating avalanche control information based on the load information;
when the avalanche control information is within the control validity period corresponding to the avalanche control information, reporting, managing and controlling the buried point information of the target service by adopting the avalanche control information;
and when the control validity period is finished, reporting the embedded point information to the service server.
2. The method of claim 1, wherein before receiving the load information sent by the traffic server, the method further comprises:
when detecting that a target service is accessed, creating a target database corresponding to the target service;
and acquiring the buried point information of the target service by adopting a buried point process corresponding to the target service, and storing the buried point information in the target database.
3. The method of claim 1, wherein the receiving load information sent by the traffic server and generating avalanche control information based on the load information comprises:
when the target service is detected to be cold started, sending a request for inquiring load to a service server;
and receiving load information returned by the service server based on the query load request, and acquiring avalanche control information corresponding to the load information.
4. The method of claim 1, wherein the receiving load information sent by the traffic server and generating avalanche control information based on the load information comprises:
when the embedded point information of the target service is reported to the service server, the load information sent by the server is received, and the avalanche control information corresponding to the load information is obtained.
5. The method according to claim 2, wherein the performing reporting management and control processing on the buried point information of the target service by using the avalanche control information includes:
acquiring a buried point reporting request for the buried point information in the target database;
when the reporting condition of the buried point reporting request does not meet the avalanche control information, rejecting the buried point reporting request;
and when the reporting condition meets the avalanche control information, reporting the buried point information in the target database to the service server.
6. The method of claim 5, wherein the rejecting the buried point reporting request when the reporting condition does not satisfy the avalanche control information comprises:
and when the reporting time of the buried point reporting request is within the reporting retry time interval indicated by the avalanche control information, rejecting the buried point reporting request.
7. The method of claim 5, wherein the rejecting the buried point reporting request when the reporting condition does not satisfy the avalanche control information comprises:
acquiring a first reporting quantity of a point burying request of the point burying information in a current time slice and a second reporting quantity of the point burying information;
and when the first reporting quantity is larger than a request reporting threshold value and/or the second reporting quantity is larger than a data reporting threshold value, rejecting the buried point reporting request.
8. A device for reporting embedded point information is characterized in that the device comprises:
the control information generation module is used for receiving load information sent by the service server and generating avalanche control information based on the load information;
the reporting management module is used for adopting the avalanche control information to carry out reporting management and control processing on the buried point information of the target service when the control validity period corresponding to the avalanche control information is within;
and the information reporting module is used for reporting the embedded point information to the service server when the control validity period is finished.
9. A computer storage medium, characterized in that it stores a plurality of instructions adapted to be loaded by a processor and to carry out the method steps according to any one of claims 1 to 7.
10. An electronic device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the method steps of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011141736.2A CN112306797A (en) | 2020-10-22 | 2020-10-22 | Embedded point information reporting method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011141736.2A CN112306797A (en) | 2020-10-22 | 2020-10-22 | Embedded point information reporting method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112306797A true CN112306797A (en) | 2021-02-02 |
Family
ID=74327200
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011141736.2A Pending CN112306797A (en) | 2020-10-22 | 2020-10-22 | Embedded point information reporting method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112306797A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113162982A (en) * | 2021-03-19 | 2021-07-23 | 维沃移动通信有限公司 | Buried point information reporting method and device and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101360093A (en) * | 2007-08-02 | 2009-02-04 | 华为技术有限公司 | Load control method and system thereof |
| CN103841129A (en) * | 2012-11-21 | 2014-06-04 | 华为技术有限公司 | Cloud computing resource information acquisition server, cloud computing resource information acquisition client and information processing method |
| CN106302421A (en) * | 2016-08-08 | 2017-01-04 | 腾讯科技（深圳）有限公司 | A kind of information intercepting processing method and device |
| WO2019205804A1 (en) * | 2018-04-23 | 2019-10-31 | 中兴通讯股份有限公司 | Web page pre-downloading method and device, storage medium and electronic device |
| CN110704097A (en) * | 2019-09-29 | 2020-01-17 | 腾讯科技（深圳）有限公司 | Data collection method and device, electronic equipment and storage medium |
| CN110716848A (en) * | 2019-10-18 | 2020-01-21 | 广州华多网络科技有限公司 | Data collection method and device, electronic equipment and storage medium |
-
2020
- 2020-10-22 CN CN202011141736.2A patent/CN112306797A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101360093A (en) * | 2007-08-02 | 2009-02-04 | 华为技术有限公司 | Load control method and system thereof |
| CN103841129A (en) * | 2012-11-21 | 2014-06-04 | 华为技术有限公司 | Cloud computing resource information acquisition server, cloud computing resource information acquisition client and information processing method |
| CN106302421A (en) * | 2016-08-08 | 2017-01-04 | 腾讯科技（深圳）有限公司 | A kind of information intercepting processing method and device |
| WO2019205804A1 (en) * | 2018-04-23 | 2019-10-31 | 中兴通讯股份有限公司 | Web page pre-downloading method and device, storage medium and electronic device |
| CN110704097A (en) * | 2019-09-29 | 2020-01-17 | 腾讯科技（深圳）有限公司 | Data collection method and device, electronic equipment and storage medium |
| CN110716848A (en) * | 2019-10-18 | 2020-01-21 | 广州华多网络科技有限公司 | Data collection method and device, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113162982A (en) * | 2021-03-19 | 2021-07-23 | 维沃移动通信有限公司 | Buried point information reporting method and device and electronic equipment |
| CN113162982B (en) * | 2021-03-19 | 2023-12-29 | 维沃移动通信有限公司 | Buried point information reporting method and device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10572285B2 (en) | Method and apparatus for elastically scaling virtual machine cluster | |
| CN107679718B (en) | List allocation method, apparatus and computer-readable storage medium | |
| CN110471749B (en) | Task processing method, device, computer readable storage medium and computer equipment | |
| CN109800204B (en) | Data distribution method and related product | |
| CN109510850B (en) | Method, device and system for processing browsing request | |
| CN110336888B (en) | Server distribution method, device, system and medium | |
| CN112306797A (en) | Embedded point information reporting method and device, storage medium and electronic equipment | |
| CN107332703B (en) | Method and device for checking multi-application logs | |
| CN106550021B (en) | Push method and device for push message | |
| CN110806930B (en) | Micro-service scheduling method, device, equipment and storage device | |
| CN107045452B (en) | Virtual machine scheduling method and device | |
| CN112084021A (en) | Interface configuration method, device and equipment of education system and readable storage medium | |
| CN112286930A (en) | Method, device, storage medium and electronic equipment for resource sharing of redis business side | |
| CN112104682A (en) | Intelligent distribution method and system for cloud desktop server, storage medium and central control server | |
| CN113721936A (en) | Application management method, intelligent terminal, device and storage medium | |
| CN113342776B (en) | Transaction information migration method, device, equipment and medium based on intelligent contract | |
| CN115309558A (en) | Resource scheduling management system, method, computer equipment and storage medium | |
| CN113938473A (en) | Automatic Mock method, device, equipment and storage medium based on flow | |
| CN112306791B (en) | Performance monitoring method and device | |
| CN105591980B (en) | A kind of bandwidth consumption management method and device | |
| CN113282455A (en) | Monitoring processing method and device | |
| CN108809763B (en) | Network performance parameter acquisition method, terminal device and storage medium | |
| CN113836405B (en) | Information query method, device and computer readable storage medium | |
| CN115840604B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN117176613B (en) | Data acquisition method and device |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210202 |