CN110377331B - Monitoring method, device, equipment and storage medium for issuing application program - Google Patents
Monitoring method, device, equipment and storage medium for issuing application program Download PDFInfo
- Publication number
- CN110377331B CN110377331B CN201910662012.3A CN201910662012A CN110377331B CN 110377331 B CN110377331 B CN 110377331B CN 201910662012 A CN201910662012 A CN 201910662012A CN 110377331 B CN110377331 B CN 110377331B
- Authority
- CN
- China
- Prior art keywords
- release
- application program
- channel
- application
- distribution
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The application discloses a monitoring method, a device, equipment and a storage medium for issuing application programs, wherein in the scheme, the application programs are distributed to each issuing channel, each issuing channel is scanned according to a period, and thus the update information of the application programs can be obtained from each issuing channel; if the update information is acquired, respectively determining the release time of the application program in each release channel according to the update information; according to the release time length and the user proportion of the application program in each release channel, the release live of the application program in each release channel is determined, so that whether the application program is released in each release channel or not can be monitored in real time, the release live is monitored in real time, the follow-up timeliness of the release process is improved, and the workload is reduced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for monitoring a published application program.
Background
Currently, in order to widely popularize an Application, a developer of the Application (APP) will issue the Application to a plurality of issue channels. The release channel is an application store (such as an application treasures).
In the prior art, when a new application program or an updated version of an old application program is transmitted to each distribution channel, the distribution situation needs to be manually followed until the application program is successfully distributed. However, the efficiency of manual follow-up and inquiry is lower due to more release channels; and when the current release version of the application program is not queried, the operation needs to be repeated for a plurality of times by the staff, so that the workload is increased.
Disclosure of Invention
In view of the above, the present application aims to provide a method, an apparatus, a device and a storage medium for monitoring a published application program, so as to realize real-time monitoring of a published live of the application program. The specific scheme is as follows:
in order to achieve the above object, in one aspect, the present application provides a method for monitoring a published application, including:
distributing the application program to each distribution channel;
scanning each release channel according to a period, and acquiring update information of the application program from each release channel; the update information at least comprises: the name, version number and update time of the application program;
if the update information is acquired, respectively determining the release time of the application program in each release channel according to the update information;
And respectively determining the release live of the application program in each release channel according to the release time and the user duty ratio of the application program in each release channel.
In still another aspect, the present application further provides a monitoring device for publishing an application, including:
the distribution module is used for distributing the application programs to each distribution channel;
the acquisition module is used for scanning each release channel according to a period and acquiring the update information of the application program from each release channel; the update information at least comprises: the name, version number and update time of the application program;
the first determining module is used for determining the release time of the application program in each release channel according to the update information if the update information is acquired;
and the second determining module is used for respectively determining the release live of the application program in each release channel according to the release time and the user proportion of the application program in each release channel. In yet another aspect, the present application also provides an electronic device including a processor and a memory; the memory is used for storing a computer program, and the computer program is loaded and executed by the processor to realize the monitoring method of the release application program.
In yet another aspect, the present application further provides a storage medium having stored therein computer-executable instructions that, when loaded and executed by a processor, implement the foregoing method for monitoring an issuing application.
After the application program is distributed to each distribution channel, each distribution channel is scanned according to the period, so that the update information of the application program can be obtained from each distribution channel; if the update information is acquired, further determining the release time of the application program in each release channel according to the update information; according to the release time length and the user duty ratio of the application program in each release channel, the release live of the application program in each release channel can be determined. Wherein, the release duration is: the time interval between the point in time of distributing the application to the distribution channel and the point in time of the application being up-listed on the distribution channel. Therefore, the update information of the application program is periodically obtained from each release channel, and whether the application program is released or not can be known in time; furthermore, the release time of the application program in the current release channel can be determined based on the update time in the update information, namely whether the application program is released in time, delayed, advanced or not released. And based on the release time length and the user duty ratio of the application program in each release channel, the release live of the application program in each release channel can be determined, namely the release effect of the application program in each release channel is determined, so that the release process of the application program can be followed in time.
Wherein, the update information at least comprises: the name of the application, version number, and update time, which may indicate the current release live of the application. Specifically, if the update information is acquired from the release channel and the update information is consistent with the current release version of the application program, the application program is indicated to be successfully released in the current release channel; if the acquired update information is inconsistent with the current release version of the application program, the acquired update information is the historical version information of the application program, namely the application program is not released in the current release channel; if the update information of the application program acquired from the distribution channel is empty, the application program is indicated to be not put on shelf in the current distribution channel, and the first put on shelf is the first time. The application automatically acquires the update information of the application program from each release channel according to the period, can monitor whether the application program is released in each release channel in real time and monitor release live in real time, thereby improving the query efficiency and the follow-up timeliness of the release process and reducing the workload.
Correspondingly, the monitoring device, the equipment and the storage medium for the release application program have the same technical effects.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a prior art application publishing process provided by the present application;
FIG. 2 is a schematic diagram of a physical architecture to which the present application is applied;
FIG. 3 is a schematic diagram of a logic framework applicable to the present application;
FIG. 4 is a flowchart of a method for monitoring a publishing application;
FIG. 5 is a flowchart of a method for monitoring a publishing application;
FIG. 6 is a schematic diagram of a report of the present application;
FIG. 7 is a flowchart of a method for monitoring a publishing application;
FIG. 8 is a schematic diagram of a monitoring flow of a publishing application provided by the present application;
FIG. 9 is a schematic diagram of a man-machine interface for inputting detection instructions according to the present application;
FIG. 10 is a schematic diagram of a monitoring trigger interface of an application program according to the present application;
FIG. 11 is a schematic diagram of a release record of an application according to the present application;
FIG. 12 is a schematic diagram of a monitoring flow of a publishing application provided by the present application;
FIG. 13 is a schematic diagram of a monitoring device for publishing an application program according to the present application;
FIG. 14 is a diagram illustrating a server configuration according to the present application;
fig. 15 is a diagram of a terminal structure according to the present application.
Detailed Description
The publishing process of the existing application may be referred to in fig. 1, and fig. 1 is a schematic diagram of the publishing process of the existing application. The follow-up process of the existing release process lacks timeliness, the query efficiency is low, and the workload is increased. In view of the problems existing at present, the application provides a monitoring scheme for the release application program, by which the release live of the application program in each release channel can be monitored in real time, the query efficiency and the follow-up timeliness of the release process are improved, and the workload is reduced.
For ease of understanding, a description of the physical framework to which the present application applies will be presented. See fig. 2 for a physical framework. In fig. 2, the physical framework to which the present application is applied includes: the system comprises a background server, a web server, a database and a user monitoring end; the background server is used for realizing the method provided by the application; the database is used for storing the updated information obtained by the method provided by the application; the web server is used for connecting the database and the background server; the user monitoring end is used for displaying and acquiring update information and release live of the application program in each release channel. The background server communicates with the web servers of all channels through the firewall, so that the update information of the application program can be obtained.
Corresponding to the physical framework diagram shown in fig. 2, the logical framework to which the present application is applied is shown in fig. 3. In fig. 3, a user management module, a channel access management module, a DB database, an application access management module, a version management module, and a data statistics module are implemented in the web server; the background server is provided with a general network communication module, a task scheduling module, a data pulling module of each release channel and a DB database.
Specifically, a user management module in the web server is used for managing users using the user monitoring end; the channel access management module is used for managing the monitored release channels; the DB database is used for storing corresponding data in the web server; the application access management module user manages the application program to be monitored; the version management module is used for managing each version of the monitored application program; the data statistics module is used for counting corresponding data according to the crawled updated information.
The universal network communication module in the background server is used for communicating with the web servers of all the release channels; the task scheduling module is used for controlling the execution and the end of the monitoring task, and each time of obtaining the update data can be regarded as a task; the data pulling module of each release channel is used for acquiring update information in each release channel under the control of the task scheduling module; the DB database is used to store corresponding data in the background server.
The background server, the web server and the database can comprise x86 architecture processors, and are applicable to Windows xp and above and Linux operating systems. The background server may perform the methods disclosed herein.
With reference to fig. 4 in combination with the above commonalities, fig. 4 is a flowchart of a monitoring method of a publishing application according to an embodiment of the present application. Referring to fig. 4, the monitoring method of the publishing application may include the steps of:
s401, distributing application programs to each distribution channel.
S402, scanning each distribution channel according to the period, and acquiring update information of the application program from each distribution channel.
The publishing channel is a preset publishing platform needing to be monitored. The update information is an up-shelf version of the application program in a certain distribution channel, and at least comprises: the name of the application, version number, and update time. The update information may further include: download amount, application developer name and score, etc. The period can be preset to be 1 minute, 10 minutes, 1 hour and the like, and the time duration can be flexibly adjusted according to the actual application condition.
For example: application 1 is the currently published application, its 1.0 version is up-listed in the publication channel X, Y, Z, and the current publication version of application 1 is 1.1, whereas version 1.1 wants to be up-listed in the publication channels X, Y, Z and W, then X, Y, Z and W are the publication platforms that need to be monitored. Before release of version 1.1, the update information of the application program in the release channel X includes: the application name, version 1.0, and the time of the release of version 1.0 of the application from the shelf in the release channel X, the update information of the application in the release channels Y and Z are similar to this. The application has no updated information in the distribution channel W unless version 1.1 is top-up distributed in the distribution channel W.
S403, if the update information is acquired, the release time of the application program in each release channel is respectively determined according to the update information.
It will be appreciated that it may be determined from the update information whether the application is published in each of the publication channels, including the following:
first kind: update information is acquired from the release channel, and the update information is consistent with the current release version of the application program, so that the application program is successfully released in the current release channel.
Second kind: the update information is acquired from the release channel, but the acquired update information is inconsistent with the current release version of the application program, which indicates that the acquired update information is the historical version information of the application program, that is, the application program is not released in the current release channel.
Third kind: the update information of the application acquired from the distribution channel is empty, indicating that the application has not been put on shelf in the current distribution channel for the first time.
The first category is classified as update information is acquired, and the second and third categories are classified as update information is not acquired. Based on the above, it can be determined whether the application has been published in each of the distribution channels.
Wherein, the release duration is: the time interval between the point in time of distributing the application to the distribution channel and the point in time of the application being up-listed on the distribution channel. It should be noted that, the point in time when the application program is released from the release channel is generally the update time included in the update information, so that the point in time when the application program is released from the release channel can be determined according to the update information, and the difference between the point in time and the point in time when the application program is released from the release channel is further determined as the release time.
S404, according to the release time length and the user proportion of the application program in each release channel, the release live of the application program in each release channel is respectively determined.
In one embodiment, the distribution of the application program in each distribution channel is live, that is, the distribution effect of the application program in each distribution channel.
The release effect can be obtained according to the release time of the application program in the release channel and the user duty ratio. The user duty ratio of the application program in the release channel is as follows: the ratio of the user of the application to all users of the application is downloaded and used in a certain distribution channel. Wherein the user duty cycle is generally determined based on historical usage information. For example: the version of the currently published application is 1.1, then the user's duty cycle can be determined based on the use of the last version 1.0 of the application. If an application is first put on a shelf in a certain distribution channel, its user ratio can be replaced with the user ratio of a certain bid in the current distribution channel.
In a specific embodiment, determining the distribution live of the application program in each distribution channel according to the distribution time length and the user ratio of the application program in each distribution channel respectively includes: determining the difference degree of the reference release time length and the release time length of the application program in any release channel; determining the ratio of the difference degree to the reference release time length as a release coefficient; and determining the product of the user duty ratio of the application program in the current distribution channel and the distribution coefficient as the distribution live of the application program in the current distribution channel.
Specifically, the above calculation process can be expressed by the following formula:
wherein W is n Representing a release live of the application at release channel n; y is n Representing the user duty ratio of the application program in the distribution channel n, wherein the sum of the user duty ratios of the application program in all the distribution channels is 1; t (T) n Representing that an application is inThe release time of the release channel n; 24-T n The difference degree of the reference release time length and the release time length of the application program in any release channel is used as the reference release time length; 24 is a reference release duration in units of: the time is small, and the time can be flexibly adjusted according to actual application conditions. If the release demand time is urgent, the reference release time can be correspondingly shortened. The ratio of the difference degree to the reference release time length is the release coefficient, and then the release coefficient is:
according to the formula, the release live of the application program in a certain release channel can be determined, and the release live is calculated to obtain W n Representing, i.e. representing the distribution of an application in a distribution channel with a certain value.
It should be noted that, the method provided in this embodiment may be integrated in the distribution tool, so that after the distribution tool distributes the application program to each distribution channel, the method provided in this embodiment may be automatically executed, so that the execution efficiency of this embodiment may be improved. The distribution tool is a tool that distributes an application program to each distribution channel.
Therefore, the embodiment of the application automatically acquires the update information of the application program from each release channel according to the period, can monitor whether the application program is released in each release channel in real time and monitor the release live in real time, thereby improving the query efficiency and the follow-up timeliness of the release process and reducing the workload.
Referring to fig. 5, fig. 5 is a flowchart of a method for monitoring a publishing application according to an embodiment of the application. Referring to fig. 5, the monitoring method of the publishing application may include the steps of:
s501, distributing application programs to each distribution channel.
S502, scanning each release channel according to the period, and acquiring update information of the application program from each release channel.
Wherein, the update information at least comprises: the name of the application, version number, and update time.
And S503, if the update information is acquired, respectively determining the release time of the application program in each release channel according to the update information.
S504, according to the release time length and the user proportion of the application program in each release channel, the release live of the application program in each release channel is respectively determined.
S505, overlapping the release live of the application program in each release channel to obtain an overlapping result.
S506, determining the superposition result as a comprehensive release result of the application program.
In one embodiment, since the distribution of the application program in a certain distribution channel can be represented by a certain value, the value can be added when the application program is superimposed on the distribution of the application program in each distribution channel, so that the comprehensive distribution result of the application program can be obtained.
Specifically, the comprehensive release result of the application program can be calculated according to the following formula:
wherein W is Total (S) Representing the comprehensive release result of a certain application program in each release channel, wherein:
in a specific embodiment, in order to effectively embody the comprehensive release result of the current application program, the comprehensive release result of a certain application program in each release channel may also be calculated according to the following formula:
wherein W is Total (S) Representing a certain application program in each distribution channel100 is a preset evaluation value, namely, the preset comprehensive release result is 100; y is n Representing the user duty ratio of the application program in the distribution channel n; t (T) n The release time of the application program in the release channel n is represented; 24 is a reference release duration in units of: hours. In the calculation formula, when the calculation application program calculates the release live condition of a certain release channel, the 1 is used for negating, so that when the calculation application program calculates the comprehensive release result of each release channel, the preset evaluation value is also used for negating, and the comprehensive release result of the application program in each release channel can be obtained.
S507, determining the update rate and the loading rate of the application program according to the update information and the release live.
And S508, adding the update rate, the loading rate and the comprehensive release result to a release report of the application program and displaying.
In this embodiment, in order to clearly display the comprehensive release result of the application program, the update rate, the shelf rate and the comprehensive release result of the application program may be used to generate and display the present release report of the application program.
Wherein the update rate and the put-on rate can be explained with reference to the following:
application 1 is the currently published application whose 1.0 version is up-listed in the publication channel X, Y, Z, and the current publication version of application 1 is 1.1, while version 1.1 wants to be up-listed in the publication channels X, Y, Z, W and N, and at some point, version 1.1 appears only in X, Y and W, then the update rate is: 2/3×100% ≡67%; the loading rate is as follows: 4/5×100% =80%.
According to the calculation scheme, the following steps are: if an application needs to be published in 20 publishing channels, at a certain moment, the current publishing version of the application can be queried in 15 publishing channels, and the application can be queried in 17 publishing channels (the version is not concerned at this time), then: update rate=15/17×100%, loading rate=17/20×100%.
In particular, the application release report can be seen in fig. 6. In fig. 6, the publication score is the above-mentioned integrated publication result. The predicted impact users are presented in percentages, which may be determined based on the user's duty cycle; if an application program is first put on shelf for release in a certain release channel, the user duty ratio of a certain bid in the current release channel can be used for determining. The new version update time may be the time when the application completes the release in all release channels. The latest version number is the currently released version number of the application program. The content displayed by the channel data can be regarded as the release live of the application program in each release channel, wherein the evaluation star is the evaluation of the application program in the current release channel; the total download amount is the number of times the user downloads the application from the current distribution channel.
It should be noted that, the release condition of the application program can be evaluated according to the release report of the application program in a preset time period (such as a year), so that reliable reference data can be provided for reissuing the application program.
It should be noted that other implementation steps in the present embodiment are the same as or similar to those in the above embodiment, so that the description of the present embodiment is omitted here.
Therefore, after the application program is distributed to each distribution channel, each distribution channel is scanned according to the period, and the update information of the application program can be obtained from each distribution channel in real time; and then the release live of the application program in each release channel can be determined according to the acquired update information, and the comprehensive release result of the current application program can be determined and displayed according to the release live, so that the release condition of the current application program can be evaluated, and a reliable basis is provided for release of other application programs or reissue of the current application program.
Referring to fig. 7, fig. 7 is a flowchart of a method for monitoring a publishing application according to an embodiment of the application. Referring to fig. 7, the monitoring method of the publishing application may include the steps of:
s701, distributing an application program to each distribution channel.
S702, querying crawler addresses of all the distribution channels in the configuration file.
S703, generating a crawler instruction containing the crawler address.
Specifically, the crawler addresses of the release channels may be stored in the configuration file in advance, and when the crawler operation needs to be executed, the configuration file is queried, so as to generate a corresponding crawler instruction. The format and storage manner of the configuration file are not particularly limited herein. Of course, a crawler script may be preset, and when the crawler operation needs to be executed, the corresponding crawler script may be executed.
And S704, crawling the update information of the application program from each release channel according to the period and the crawler instruction.
Wherein, the update information at least comprises: the name of the application, version number, and update time.
S705, if the updated information is obtained, judging whether the updated information is consistent with the current release information of the application program; if yes, then execution S707; if not, S706 is performed.
S706, sending a prompt message to the target distribution channel.
The target release channel is a release channel of which the update information is inconsistent with the current release information of the application program.
And S707, respectively determining the release time of the application program in each release channel according to the update information.
S708, according to the release time and the user proportion of the application program in each release channel, the release live of the application program in each release channel is respectively determined.
In this embodiment, the crawler technology may be used to obtain update information of the application program from each distribution channel, and after the update information is obtained, it may be determined whether the obtained update information is consistent with the current distribution information of the application program; if the distribution results are consistent, indicating that the application program is successfully distributed in the current distribution channel, and recording the distribution live of the application program in the current distribution channel; if the information is inconsistent, the application program is indicated not to be published in the current publishing channel, and a prompt message is sent to the target publishing channel so as to prompt the target publishing channel to put the application program on shelf for publishing as soon as possible. If the acquired update information is empty, the acquired update information is classified as a case that the acquired update information is inconsistent with the current release information of the application program.
The execution time of sending the prompt message to the target distribution channel may be preset, for example, when the waiting time period exceeds the reference distribution time period, the step of sending the prompt message to the target distribution channel is executed.
In a specific embodiment, the developer of the application program may also negotiate with each distribution channel to open the back end interface of the distribution channel, so that update information may be directly obtained from the back end interface of each distribution channel. That is, update information is acquired through the interfaces of the respective distribution channels according to the period.
Therefore, after the application program is distributed to each distribution channel, each distribution channel is scanned according to the period, and the update information of the application program can be obtained from each distribution channel in real time; and then, the release live of the application program in each release channel can be determined according to the acquired update information, so that the release condition of the current application program can be evaluated, and a reliable basis is provided for release of other application programs or reissue of the current application program.
The following describes a specific application scenario example to introduce the monitoring scheme of the publishing application program provided by the application.
If the scheme provided by the application is independent of the distribution tool, the user can trigger the execution of the scheme based on the user monitoring terminal, and the specific process comprises the following steps: after the application program is distributed to each distribution channel by using the distribution tool, the user inputs information such as the name of the application program based on the man-machine interaction interface of the user monitoring terminal, so that the background server can determine the current distribution information of the application program and contents such as the distribution channel to be monitored based on the name. Further, the method provided by the application can be executed to scan each release channel according to the period and acquire the update information of the application program from each release channel; and respectively determining the release live of the application program in each release channel according to the update information.
Referring to fig. 8, fig. 8 is a schematic diagram of a monitoring flow of a publishing application according to the present application. The solution shown in fig. 8 is independent of the distribution tool, that is, the user needs to search for information such as the name of the application program based on the man-machine interaction interface, so as to trigger the monitoring process. The user monitoring terminal, the background server, the database and the web server shown in fig. 8 can be seen in fig. 2.
Specifically, the monitoring flow of the scheme shown in fig. 8 specifically includes:
s801, after receiving an instruction of completing the execution of the distribution operation, the user monitoring terminal displays a man-machine interaction interface for inputting a detection instruction.
Specifically, please refer to fig. 9 for a man-machine interface for inputting a detection command. Fig. 9 is a schematic diagram of a man-machine interaction interface for inputting a detection command according to the present application. In the man-machine interaction interface shown in fig. 9, a button for immediate detection is provided, and a user can input a detection instruction by clicking the button. The android channel quality monitoring platform shown in fig. 9 is a platform realized by the method provided by the application, and the android channel quality monitoring platform further comprises a statistical analysis platform and a channel piracy package monitoring platform. The android channel quality monitoring platform monitors the publishing process of the android application program. Of course, the monitoring of the release process of the iOS application program can also be realized according to the method provided by the application.
S802, the user monitoring terminal obtains a detection instruction input by a user based on the human-computer interaction interface, and switches the human-computer interaction interface to a monitoring trigger interface of the application program according to the detection instruction.
S803, the user monitoring terminal acquires the name of the application program input by the user based on the monitoring trigger interface.
Fig. 10 is a schematic diagram of a monitoring trigger interface of an application program according to the present application. In the monitoring trigger interface shown in fig. 10, an input box is provided, based on which a user can input the name of an application.
S804, the user monitoring terminal transmits the name of the application program to the web server, and the name is forwarded to the background server by the web server.
S805, the background server determines the current release information of the application program according to the name, and each release channel; and according to each release channel needing to be monitored, periodically scanning, and acquiring the update information of the application program from each release channel.
And S806, if the update information is acquired, the background server respectively determines the release live of the application program in each release channel according to the update information.
The method for determining the release live of the application program in each release channel according to the update information comprises the following steps: respectively determining the release time of the application program in each release channel according to the update information; and respectively determining the release live of the application program in each release channel according to the release time and the user duty ratio of the application program in each release channel.
S807, the background server superimposes the release live of the application program in each release channel, and the superimposed result is used as the comprehensive release result of the application program.
S808, the background server determines the update rate and the loading rate of the application program according to the update information and the release live, and adds the update rate, the loading rate and the comprehensive release result to the release report of the application program.
S809, the background server transmits the release live and release reports of the application program in each release channel to the database and the web server.
S810, a database stores distribution live and distribution reports of the application program in each distribution channel.
S811, the web server performs format conversion and web processing on the release live and release reports of the application program in each release channel.
The process of processing the distribution live and the distribution report of the application program in each distribution channel by the web server may refer to the prior art, and will not be described in detail herein for avoiding redundancy.
And S812, receiving a search request sent by the user monitoring terminal.
Specifically, a search interface for a user to search for a name of an application based on a user monitoring terminal may be referred to in fig. 10. The user inputs the name of the application based on the input box shown in fig. 10, or directly clicks the application name indicated by the popular search field, i.e., can input the search request. The user monitoring terminal transmits the search request to the web server so that the web server returns a release report of the application program.
And S813, the web server transmits the release report to the user monitoring terminal.
And S812, the user monitoring terminal displays the release report.
To facilitate the user's querying of the monitored history, the background server will collect the published records of all the monitored applications as an updated list, while recording the updated records of each application in a timeline in the list. In which icons and release time of each application program are recorded, refer to fig. 11 specifically, and fig. 11 is a schematic diagram of release record of an application program provided by the present application. The time shown in fig. 11 is the time when the application update or release is completed.
If the scheme provided by the application is integrated in the distribution tool, after the execution of the distribution operation is completed, the execution of the scheme can be triggered, and the specific process comprises the following steps: distributing application programs to each distribution channel by using a distribution tool, and when the completion of the execution of the distribution operation is detected, scanning each distribution channel according to a period in the application, and acquiring the update information of the application programs from each distribution channel; and respectively determining the scheme of step disclosure of the application program for publishing the live in each publishing channel according to the updated information.
Referring to fig. 12, fig. 12 is a schematic diagram of a monitoring flow of a publishing application according to the present application. The solution shown in fig. 12 is integrated in the dispensing tool, i.e. the dispensing tool performs the dispensing operation automatically triggering the monitoring procedure. The user monitoring terminal, the background server and the database shown in fig. 12 can be seen in fig. 2.
Specifically, the scheme shown in fig. 12 is executed by a background server, and specifically includes:
s1201, the application is distributed to each distribution channel by using the distribution tool.
And S1202, determining the current release information of the application program and the release channel to be monitored when the completion of the execution of the distribution operation is detected.
S1203 scans each distribution channel to be monitored according to the period, and obtains update information of the application program from each distribution channel.
And S1204, if the update information is acquired, respectively determining the release time of the application program in each release channel according to the update information.
S1205, according to the release time length and the user proportion of the application program in each release channel, respectively determining the release live of the application program in each release channel.
After determining that the application program is published in the publishing channel, the application program may continue to execute according to the flowchart shown in fig. 8, which is not repeated here for avoiding redundancy.
Assuming that the application program has been successfully published in the target publication channel, with the update information of the application program in the target publication channel as a reference version, a specific process of the present application may include: the user inputs the name of the application program based on a man-machine interaction interface of the user monitoring terminal, and the background server inquires the application program in the target release channel based on the name; if the application program is inquired, acquiring update information of the application program in each release channel; judging whether the acquired update information is consistent with the reference version, if so, indicating that the application program is successfully published in the current publishing channel; if not, the current release information of the application program is indicated to be not released in the current release channel. If the update information of the application program acquired in the release channel is empty, the current channel is indicated to have no application program.
The comprehensive release result of the current application program can be determined according to the acquired update information, and the corresponding release report is displayed, so that the real-time monitoring of the release application program is realized, the monitoring efficiency is improved, and available data for reference can be provided for subsequent release operation.
Referring to fig. 13, fig. 13 is a monitoring device for publishing an application program according to an embodiment of the present application, including:
a distribution module 1301 for distributing the application program to each distribution channel;
an acquiring module 1302, configured to periodically scan each distribution channel, and acquire update information of an application program from each distribution channel; the update information at least comprises: the name, version number, and update time of the application;
the first determining module 1303 is configured to determine, if update information is obtained, a release duration of the application program in each release channel according to the update information;
a second determining module 1304, configured to determine, according to the distribution duration and the user duty ratio of the application program in each distribution channel, a distribution live of the application program in each distribution channel.
In one embodiment, the second determining module includes:
a first determining unit for determining a reference distribution time length and a degree of difference of the distribution time length of the application program in any distribution channel;
The second determining unit is used for determining the ratio of the difference degree to the reference release time length as a release coefficient;
and the third determining unit is used for determining the product of the user duty ratio of the application program in the current distribution channel and the distribution coefficient as the distribution live of the application program in the current distribution channel.
In one specific embodiment, the method further comprises:
the superposition module is used for superposing the release live of the application program in each release channel to obtain a superposition result;
and the third determining module is used for determining the superposition result as the comprehensive release result of the application program.
In one specific embodiment, the method further comprises:
the fourth determining module is used for determining the update rate and the loading rate of the application program according to the update information and the release live condition;
and the adding module is used for adding the update rate, the shelf rate and the comprehensive release result to the release report of the application program and displaying the release report.
In one embodiment, the obtaining module includes:
the inquiry unit is used for inquiring the crawler addresses of all the release channels in the configuration file;
the generation unit is used for generating a crawler instruction containing a crawler address;
and the crawling unit is used for crawling updated information from each issuing channel according to the period and the crawler instruction.
In one embodiment, the obtaining module is specifically configured to:
and acquiring updated information through interfaces of all the release channels according to the period.
In one specific embodiment, the method further comprises:
the judging module is used for judging whether the acquired updated information is consistent with the current release information of the application program;
the sending module is used for sending a prompt message to the target release channel if the acquired update information is inconsistent with the current release information of the application program; the target distribution channel is a distribution channel in which the update information is inconsistent with the current distribution information of the application program.
The more specific working process of each module and unit in this embodiment may refer to the corresponding content disclosed in the foregoing embodiment, and will not be described herein.
It can be seen that this embodiment provides a monitoring device for publishing an application program, including: the device comprises a distribution module, an acquisition module, a first determination module and a second determination module. Firstly, distributing application programs to each distribution channel by a distribution module; the acquisition module scans each release channel according to the period and acquires the update information of the application program from each release channel; the update information at least comprises: the name, version number, and update time of the application; if the update information is acquired, the first determining module respectively determines the release time of the application program in each release channel according to the update information; and finally, the second determining module respectively determines the release live of the application program in each release channel according to the release time and the user duty ratio of the application program in each release channel. Therefore, the modules work separately and cooperate, and each module performs its own job, so that the real-time monitoring of the release live of the application program in each release channel is realized, the query efficiency and the timeliness of the follow-up release process are improved, and the workload is reduced.
Further, the embodiment of the application also provides electronic equipment. The electronic device may be the server 50 shown in fig. 14 or the terminal 60 shown in fig. 15. Fig. 14 and 15 are each a structural diagram of an electronic device according to an exemplary embodiment, and the contents of the drawings should not be construed as any limitation on the scope of use of the present application.
Fig. 14 is a schematic structural diagram of a server according to an embodiment of the present application. The server 50 may specifically include: at least one processor 51, at least one memory 52, a power supply 53, a communication interface 54, an input output interface 55, and a communication bus 56. Wherein the memory 52 is configured to store a computer program that is loaded and executed by the processor 51 to implement the relevant steps in the monitoring of a publishing application as disclosed in any of the foregoing embodiments.
In this embodiment, the power supply 53 is configured to provide an operating voltage for each hardware device on the server 50; the communication interface 54 can create a data transmission channel between the server 50 and an external device, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein; the input/output interface 55 is used for acquiring external input data or outputting external output data, and the specific interface type thereof may be selected according to the specific application needs, which is not limited herein.
The memory 52 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk, or an optical disk, and the resources stored thereon include an operating system 521, a computer program 522, and data 523, and the storage may be temporary storage or permanent storage.
The operating system 521 is used for managing and controlling various hardware devices on the Server 50 and the computer program 522 to implement the operation and processing of the data 523 in the memory 52 by the processor 51, which may be Windows Server, netware, unix, linux, etc. The computer program 522 may further include a computer program that can be used to perform other specific tasks in addition to the computer program that can be used to perform the monitoring method of the publishing application disclosed in any of the foregoing embodiments. The data 523 may include data such as application program developer information in addition to data such as application program update information.
Fig. 15 is a schematic structural diagram of a terminal according to an embodiment of the present application, and the terminal 60 may specifically include, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, or the like.
Generally, the terminal 60 in this embodiment includes: a processor 61 and a memory 62.
Processor 61 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 61 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 61 may also include a main processor, which is a processor for processing data in an awake state, also called a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 61 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and drawing of content required to be displayed by the display screen. In some embodiments, the processor 61 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.
Memory 62 may include one or more computer-readable storage media, which may be non-transitory. Memory 62 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 62 is at least used for storing a computer program 621, where the computer program is loaded and executed by the processor 61, and then can implement relevant steps in the method for monitoring a distribution application executed by the terminal side as disclosed in any of the foregoing embodiments. In addition, the resources stored by the memory 62 may also include an operating system 622, data 623, and the like, and the storage manner may be transient storage or permanent storage. The operating system 622 may include Windows, unix, linux, among others. The data 623 may include, but is not limited to, update information of the application.
In some embodiments, the terminal 60 may further include a display 63, an input-output interface 64, a communication interface 65, a sensor 66, a power supply 67, and a communication bus 68.
Those skilled in the art will appreciate that the configuration shown in fig. 15 is not limiting of the terminal 60 and may include more or fewer components than shown.
Further, the embodiment of the application also discloses a storage medium, wherein the storage medium stores computer executable instructions, and when the computer executable instructions are loaded and executed by a processor, the method for monitoring the issuing application program disclosed in any embodiment is realized. For specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no further description is given here.
It should be noted that the foregoing is only a preferred embodiment of the present application, and is not intended to limit the present application, but any modification, equivalent replacement, improvement, etc. which fall within the spirit and principles of the present application should be included in the scope of the present application.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
The principles and embodiments of the present application have been described herein with reference to specific examples, the description of which is intended only to assist in understanding the methods of the present application and the core ideas thereof; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (14)
1. A method for monitoring a published application, comprising:
distributing the application program to each distribution channel;
scanning each release channel according to a period, and acquiring update information of the application program from each release channel; the update information at least comprises: the name, version number and update time of the application program;
if the update information is acquired, respectively determining the release time of the application program in each release channel according to the update information;
determining the difference degree of the reference release time length and the release time length of the application program in any release channel;
determining the ratio of the difference degree to the reference release time length as a release coefficient;
And determining the product of the user duty ratio of the application program in the current distribution channel and the distribution coefficient as the distribution live of the application program in the current distribution channel.
2. The method for monitoring a distribution application according to claim 1, further comprising, after determining the distribution of the live program:
superposing the release live of the application program in each release channel to obtain a superposition result;
and determining the superposition result as a comprehensive release result of the application program.
3. The method for monitoring the published application according to claim 2, wherein after determining the superposition result as the integrated published result of the application, further comprises:
determining the update rate and the shelf rate of the application program according to the update information and the release live;
and adding the update rate, the loading rate and the comprehensive release result to a release report of the application program and displaying the release report.
4. The method for monitoring a distribution application according to claim 1, wherein the scanning each of the distribution channels in a cycle and acquiring update information of the application from each of the distribution channels comprises:
Inquiring crawler addresses of the release channels in the configuration file;
generating a crawler instruction containing the crawler address;
and crawling the updated information from each distribution channel according to the period and the crawler instruction.
5. The method for monitoring a distribution application according to claim 1, wherein the scanning each of the distribution channels in a cycle and acquiring update information of the application from each of the distribution channels comprises:
and acquiring the updated information through interfaces of the distribution channels according to the period.
6. The method for monitoring a distribution application according to any one of claims 1 to 5, wherein determining, according to the update information, a distribution duration of the application before each of the distribution channels, respectively, further comprises:
judging whether the acquired updated information is consistent with the current release information of the application program;
if not, sending a prompt message to a target release channel; the target distribution channel is a distribution channel in which the updated information is inconsistent with the current distribution information of the application program.
7. A monitoring apparatus for publishing an application, comprising:
The distribution module is used for distributing the application programs to each distribution channel;
the acquisition module is used for scanning each release channel according to a period and acquiring the update information of the application program from each release channel; the update information at least comprises: the name, version number and update time of the application program;
the first determining module is used for determining the release time of the application program in each release channel according to the update information if the update information is acquired;
the second determining module is used for determining the difference degree between the reference release time length and the release time length of the application program in any release channel; determining the ratio of the difference degree to the reference release time length as a release coefficient; and determining the product of the user duty ratio of the application program in the current distribution channel and the distribution coefficient as the distribution live of the application program in the current distribution channel.
8. The apparatus of claim 7, wherein the apparatus further comprises:
the superposition module is used for superposing the release live of the application program in each release channel to obtain superposition results;
And the third determining module is used for determining the superposition result as the comprehensive release result of the application program.
9. The apparatus of claim 8, wherein the apparatus further comprises:
a fourth determining module, configured to determine an update rate and an on-shelf rate of the application according to the update information and the published live condition;
and the adding module is used for adding the update rate, the shelf rate and the comprehensive release result to a release report of the application program and displaying the release report.
10. The apparatus of claim 7, wherein the acquisition module comprises:
the inquiring unit is used for inquiring the crawler addresses of the release channels in the configuration file;
the generation unit is used for generating a crawler instruction containing the crawler address;
and the crawling unit is used for crawling the updated information from each distribution channel according to the period and the crawler instruction.
11. The apparatus according to claim 7, wherein the obtaining module is specifically configured to obtain the update information through an interface of each of the distribution channels according to the period.
12. The apparatus according to any one of claims 7-11, wherein the apparatus further comprises:
The judging module is used for judging whether the acquired updated information is consistent with the current release information of the application program;
the sending module is used for sending a prompt message to the target release channel if the acquired update information is inconsistent with the current release information of the application program; the target distribution channel is a distribution channel in which the updated information is inconsistent with the current distribution information of the application program.
13. An electronic device comprising a processor and a memory; wherein the memory is for storing a computer program that is loaded and executed by the processor to implement the method of monitoring a published application as claimed in any of claims 1 to 6.
14. A storage medium having stored therein computer executable instructions which, when loaded and executed by a processor, implement the method of monitoring a publishing application as claimed in any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910662012.3A CN110377331B (en) | 2019-07-22 | 2019-07-22 | Monitoring method, device, equipment and storage medium for issuing application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910662012.3A CN110377331B (en) | 2019-07-22 | 2019-07-22 | Monitoring method, device, equipment and storage medium for issuing application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110377331A CN110377331A (en) | 2019-10-25 |
| CN110377331B true CN110377331B (en) | 2023-10-13 |
Family
ID=68254707
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910662012.3A Active CN110377331B (en) | 2019-07-22 | 2019-07-22 | Monitoring method, device, equipment and storage medium for issuing application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110377331B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111046316B (en) * | 2019-12-16 | 2023-03-21 | 北京智游网安科技有限公司 | Application on-shelf state monitoring method, intelligent terminal and storage medium |
| CN112732518A (en) * | 2020-12-30 | 2021-04-30 | 北京神州泰岳智能数据技术有限公司 | Application program version monitoring method and device, electronic equipment and storage medium |
| CN113176976A (en) * | 2021-04-12 | 2021-07-27 | 网易（杭州）网络有限公司 | Method and device for monitoring on-shelf inclusion of application program |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104346167A (en) * | 2014-08-25 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Method and device for generating application channel package |
| CN104615719A (en) * | 2015-02-05 | 2015-05-13 | 百度在线网络技术（北京）有限公司 | Intelligent application distributing method and device |
| CN106487602A (en) * | 2015-08-24 | 2017-03-08 | 腾讯科技（深圳）有限公司 | Application issued version monitoring method and supervising device |
| WO2017084266A1 (en) * | 2015-11-16 | 2017-05-26 | 乐视控股（北京）有限公司 | Method and device for customizing multi-channel installation package |
| CN106909357A (en) * | 2015-12-22 | 2017-06-30 | 中国移动通信集团公司 | A kind of application program channel information acquisition methods and device |
| CN108628612A (en) * | 2017-03-24 | 2018-10-09 | 埃森哲环球解决方案有限公司 | Application management platform |
| WO2019029457A1 (en) * | 2017-08-07 | 2019-02-14 | 阿里巴巴集团控股有限公司 | Method and apparatus for updating application program on client, and electronic device |
| CN109542461A (en) * | 2018-10-16 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Dissemination method, terminal device and the medium of application installation package |
-
2019
- 2019-07-22 CN CN201910662012.3A patent/CN110377331B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104346167A (en) * | 2014-08-25 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Method and device for generating application channel package |
| CN104615719A (en) * | 2015-02-05 | 2015-05-13 | 百度在线网络技术（北京）有限公司 | Intelligent application distributing method and device |
| CN106487602A (en) * | 2015-08-24 | 2017-03-08 | 腾讯科技（深圳）有限公司 | Application issued version monitoring method and supervising device |
| WO2017084266A1 (en) * | 2015-11-16 | 2017-05-26 | 乐视控股（北京）有限公司 | Method and device for customizing multi-channel installation package |
| CN106909357A (en) * | 2015-12-22 | 2017-06-30 | 中国移动通信集团公司 | A kind of application program channel information acquisition methods and device |
| CN108628612A (en) * | 2017-03-24 | 2018-10-09 | 埃森哲环球解决方案有限公司 | Application management platform |
| WO2019029457A1 (en) * | 2017-08-07 | 2019-02-14 | 阿里巴巴集团控股有限公司 | Method and apparatus for updating application program on client, and electronic device |
| CN109542461A (en) * | 2018-10-16 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Dissemination method, terminal device and the medium of application installation package |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110377331A (en) | 2019-10-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111831420B (en) | Method for task scheduling, related device and computer program product | |
| CN110377331B (en) | Monitoring method, device, equipment and storage medium for issuing application program | |
| CN107295064B (en) | Web-based configuration type remote monitoring method, electronic equipment and storage medium | |
| CN104520815B (en) | A kind of method and device of task schedule | |
| CN112786188A (en) | Offline working method and device of auxiliary diagnosis system, terminal equipment and medium | |
| CN112199007A (en) | Menu display method and device, electronic equipment and storage medium | |
| CN111459629A (en) | Azkaban-based project operation method and device and terminal equipment | |
| CN113608751B (en) | Operation method, device and equipment of reasoning service platform and storage medium | |
| CN111176577B (en) | Distributed block storage service command processing method, device, equipment and medium | |
| CN103164409A (en) | Network advertisement show type post test method and network advertisement show type post test system | |
| CN110290216B (en) | Monitoring execution method, instruction issuing method, device, equipment and storage medium | |
| CN115860877A (en) | Product marketing method, device, equipment and medium | |
| CN115543423A (en) | Method, device and equipment for generating benchmarks and storage medium | |
| CN113268183B (en) | List page countdown display method and device | |
| CN112817992A (en) | Method, device, electronic equipment and readable storage medium for executing change task | |
| CN112182078A (en) | Method, device, equipment and storage medium for issuing and using electronic product | |
| CN110022296A (en) | Real-time data processing method, device, storage medium and computer equipment | |
| CN116684306B (en) | Fault prediction method, device, equipment and readable storage medium | |
| CN115312208B (en) | Method, device, equipment and medium for displaying treatment data | |
| CN108509287A (en) | Solicited status management method, device, electronic equipment and readable storage medium storing program for executing | |
| CN117130873B (en) | Task monitoring method and device | |
| CN112994968B (en) | Network information acquisition method, server, terminal and system | |
| CN114996605A (en) | Page loading method and device, electronic equipment and storage medium | |
| CN115563182A (en) | Data processing method, device, electronic equipment and medium | |
| CN116233051A (en) | Page sharing method, device and equipment for applet and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |