CN118035041A

CN118035041A - Operation monitoring method and system

Info

Publication number: CN118035041A
Application number: CN202410278882.1A
Authority: CN
Inventors: 任浩郁; 万东昱
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2024-03-11
Filing date: 2024-03-11
Publication date: 2024-05-14

Abstract

The embodiment of the specification discloses an operation monitoring method and system, when a target applet is monitored, user access data of a native application running the target applet can be obtained, and then full-link topology data of the target applet is generated according to the user access data. The full-link topology data comprises page links, access quantity of each page, interfaces corresponding to each page and call quantity of each interface. Therefore, the operation monitoring system can monitor the service operation condition of the target applet according to the full-link topology data. The embodiment of the specification can monitor the service operation of the applet.

Description

Operation monitoring method and system

Technical Field

The embodiment of the specification relates to the technical field of operation monitoring, in particular to an operation monitoring method and system.

Background

With the development of network technology, various native applications have been able to support user loading and use of applets. Many applets are usually opened by third parties, and the interface design and implementation method of the applets are black boxes for developers of native applications. Therefore, developers of the native application cannot monitor service operation conditions of the applet operated by the native application, so that it is difficult to know service quality of the applet according to operation data.

It is therefore desirable to provide a solution that enables operational monitoring of applets run by native applications.

The statements in this background section merely provide information to the inventors and may not represent prior art to the present disclosure nor may they represent prior art to the filing date of the present disclosure.

Disclosure of Invention

The embodiment of the specification provides an operation monitoring method and system, which can monitor the service operation of an applet.

In order to achieve the above purpose, the embodiment of the present specification adopts the following technical scheme:

In a first aspect, embodiments of the present disclosure provide an operation monitoring method, which may be used to monitor a service operation condition of a target applet, where the target applet is an application program running in a native application through an external code, the method including: acquiring user access data, wherein the user access data comprises user access data of the native application running the target applet; generating full-link topology data of the target applet according to the user access data, wherein the full-link topology data comprises page links, access quantity of each page, interfaces corresponding to each page and call quantity of each interface, and the page links comprise links formed by pages respectively accessed by the user in the process of accessing the target applet; and monitoring the service operation condition of the target applet according to the full-link topology data.

By adopting the technical scheme, the full-link topology data of the target applet can be obtained through the user access data of the native application. The full-link topology data may include data such as page links, access amounts of each page, interfaces corresponding to each page, and call amounts of each interface. Therefore, the service operation condition of the target applet can be monitored according to the full-link topology data. Such as interface call condition, page access condition, etc. of the monitoring target applet. And a developer of the native application is convenient to monitor the service operation condition of the third party applet.

In one possible implementation manner, the generating the full-link topology data of the target applet according to the user access data includes: performing data cleaning on the user access data to obtain target user access data corresponding to the target applet; and generating the full-link topology data of the target applet according to the target user access data corresponding to the target applet.

In one possible implementation, the user access data includes page access data of the user and interfaces corresponding to the pages; the generating full-link topology data of the target applet according to the target user access data corresponding to the target applet includes: obtaining each page link and the access quantity of each page corresponding to the target applet according to the page access data; obtaining the call quantity of each interface corresponding to the target applet according to the access quantity of each page and the interfaces corresponding to each page; and aggregating according to the page links of the users, the access amount of the pages, the call amount of the interfaces and the interfaces corresponding to the pages to obtain the full-link topology data.

In one possible implementation manner, before the aggregating according to the links of each page, the access amount of each page, the call amount of each interface, and the interfaces corresponding to each page to obtain the full-link topology data, the method further includes: pruning is carried out on each page link according to a preset rule, each page link after pruning is obtained, and the preset rule is used for pruning page links which do not need to be concerned; the step of obtaining the full-link topology data according to the links of the pages, the access amount of the pages, the call amount of the interfaces and the interfaces corresponding to the pages in an aggregation way, comprises the following steps: and aggregating according to the pruned links of each page, the access quantity of each page, the call quantity of each interface and the interfaces corresponding to each page to obtain the full-link topology data.

In one possible implementation manner, the pruning processing is performed on each page link according to a preset rule to obtain each page link after pruning, including: acquiring a cyclic call link and an out-of-range link in each page link, wherein the out-of-range link is a page link outside a preset monitoring range; and removing the loop call link and the out-of-range link in the page links.

In one possible implementation, the method further includes: and obtaining a loop page according to the loop call link to determine the loop call risk.

In one possible implementation manner, the monitoring the service operation condition of the target applet according to the full link topology data includes: and determining a flow funnel corresponding to each page link according to the access quantity of each page and the page link.

In one possible implementation manner, the monitoring the service operation condition of the target applet according to the full link topology data includes: and monitoring the interface calling condition of the target applet according to the calling quantity of each interface.

In one possible implementation manner, the monitoring the service operation condition of the target applet according to the full link topology data includes: monitoring the states of all interfaces of the target applet; and when the abnormal interfaces are detected, determining the pages corresponding to the abnormal interfaces according to the interfaces corresponding to the pages.

In one possible implementation manner, the monitoring the service operation condition of the target applet according to the full link topology data includes: when the returned data corresponding to the target applet is abnormal, determining an interface corresponding to the abnormal page based on the abnormal page corresponding to the abnormal returned data according to the interfaces corresponding to the pages.

In one possible implementation manner, when the returned data corresponding to the target applet is abnormal, determining, based on an abnormal page corresponding to the abnormal returned data, an interface corresponding to the abnormal page according to the interfaces corresponding to the pages, includes: detecting an abnormality of the returned data, and displaying the abnormal returned data; receiving the input abnormal page, wherein the abnormal page is obtained based on the return data playback; and responding to the received input abnormal pages, and determining the interfaces corresponding to the abnormal pages according to the interfaces corresponding to the pages.

In one possible implementation manner, the monitoring the service operation condition of the target applet according to the full link topology data includes: determining a source channel page of the target page according to the page link; and determining the access amount of each source channel page according to the access amount of each page.

In one possible implementation, the interface includes at least one of a gateway interface, an application programming interface API, or a hypertext transfer protocol HTTP interface.

In a second aspect, embodiments of the present disclosure provide an operation monitoring apparatus, which may be applied to an electronic device, for implementing the method in the first aspect. The functions of the device can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions, for example, a processing module, an acquisition module, and the like.

The acquisition module can be used for acquiring user access data, wherein the user access data is user access data of a native application running the target applet; the processing module can be used for generating full-link topology data of the target applet according to the user access data, wherein the full-link topology data comprises page links, access quantity of each page, interfaces corresponding to each page and call quantity of each interface, and the page links are page links formed by pages respectively accessed by the user in the process of accessing the target applet; and monitoring the service operation condition of the target applet according to the full-link topology data.

In a possible implementation manner, the processing module is specifically configured to perform data cleaning on the user access data of the native application, so as to obtain the user access data corresponding to the target applet; and generating full-link topology data of the target applet according to the user access data corresponding to the target applet.

In one possible implementation, the user access data includes page access data of the user and interfaces corresponding to the pages; the processing module is specifically used for obtaining each page link corresponding to the target applet and the access quantity of each page according to the page access data; obtaining the call quantity of each interface corresponding to the target applet according to the access quantity of each page and the interfaces corresponding to each page; and aggregating according to the links of the pages, the access amount of the pages, the call amount of the interfaces and the interfaces corresponding to the pages to obtain the full-link topology data.

In a possible implementation manner, the processing module is further configured to prune each page link according to a preset rule, so as to obtain each page link after pruning, where the preset rule is used to prune the page links that do not need attention; the processing module is specifically configured to aggregate the full-link topology data according to the pruned links of each page, the access amount of each page, the call amount of each interface, and the interfaces corresponding to each page.

In one possible implementation manner, the processing module is specifically configured to obtain a loop call link and an out-of-range link in the page links, where the out-of-range link is a page link outside a monitoring range preset by a user; and removing the loop call link and the out-of-range link in the page links.

In a possible implementation manner, the processing module is further configured to obtain a loop page according to the loop call link to determine a loop call risk.

In one possible implementation manner, the processing module is specifically configured to determine, according to the access amount of each page and the page link, a traffic funnel corresponding to each page link.

In one possible implementation manner, the processing module is specifically configured to monitor an interface call condition of the target applet according to the call quantity of each interface.

In one possible implementation manner, the processing module is specifically configured to monitor a state of each interface of the target applet; when an abnormal interface is detected, determining a page corresponding to the abnormal interface according to the interface corresponding to each page.

In one possible implementation manner, the processing module is specifically configured to determine, when the returned data corresponding to the target applet is abnormal, an interface corresponding to the abnormal page based on the abnormal page corresponding to the abnormal returned data according to the interfaces corresponding to the pages.

In one possible implementation manner, the processing module is specifically configured to detect an exception of returned data, and display the abnormal returned data; receiving the input abnormal page, wherein the abnormal page is obtained based on the return data playback; and responding to the received input abnormal pages, and determining the interfaces corresponding to the abnormal pages according to the interfaces corresponding to the pages.

In one possible implementation manner, the processing module is specifically configured to determine, according to the page link, a source channel page of the target page; and determining the access amount of each source channel page according to the access amount of each page.

In a third aspect, embodiments of the present disclosure provide an operation monitoring system, including: at least one storage medium storing at least one set of instructions for implementing operation monitoring; and at least one processor communicatively coupled to the at least one storage medium, wherein the at least one processor reads the at least one instruction set and implements the method as in the first aspect or any of the possible implementations of the first aspect when the operation monitoring system is running.

In a fourth aspect, embodiments of the present description provide a computer-readable storage medium having computer program instructions stored thereon. The computer program instructions, when executed by an electronic device, cause the electronic device to implement the method as claimed in the first aspect or any one of the possible implementations of the first aspect.

In a fifth aspect, embodiments of the present description provide a computer program product comprising computer readable code which, when run in an electronic device, causes the electronic device to implement the method as claimed in the first aspect or any one of the possible implementations of the first aspect.

It should be appreciated that the advantages of the second to fifth aspects may be referred to in the description of the first aspect, and are not described herein.

Drawings

Fig. 1 is an application scenario schematic diagram of an operation monitoring method provided in an embodiment of the present disclosure;

Fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure;

Fig. 3 is a flow chart of an operation monitoring method according to an embodiment of the present disclosure;

fig. 4 is a link schematic diagram of a page link according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a page access amount trend according to an embodiment of the present disclosure; and

Fig. 6 is a schematic structural diagram of an operation monitoring device according to an embodiment of the present disclosure.

Detailed Description

The following description is presented to enable one of ordinary skill in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the disclosure. Thus, the present description is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. For example, as used herein, the singular forms "a", "an" and "the" include plural referents unless the context clearly dictates otherwise. The terms "comprises," "comprising," "includes," and/or "including," when used in this specification, are taken to specify the presence of stated integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

These and other features of the present specification, as well as the operation and function of the related elements of structure, as well as the combination of parts and economies of manufacture, may be significantly improved upon in view of the following description. All of which form a part of this specification, reference is made to the accompanying drawings. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the description. It should also be understood that the drawings are not drawn to scale.

The flowcharts used in this specification illustrate operations implemented by systems according to some embodiments in this specification. It should be clearly understood that the operations of the flow diagrams may be implemented out of order. Rather, operations may be performed in reverse order or concurrently. Further, one or more other operations may be added to the flowchart. One or more operations may be removed from the flowchart.

In the present specification, the expression "X includes at least one of A, B or C" means that X includes at least a, or X includes at least B, or X includes at least C. That is, X may include only any one of A, B, C, or any combination of A, B, C, as well as other possible content/elements. Any combination of the A, B, C may be A, B, C, AB, AC, BC, or ABC.

In the present specification, unless explicitly stated otherwise, the association relationship generated between structures may be a direct association relationship or an indirect association relationship. For example, when "a is connected to B" is described, unless it is specifically stated that a is directly connected to B, it is understood that a may be directly connected to B or indirectly connected to B; for another example, when "a is above B" is described, unless it is explicitly stated that a is directly above B (AB is adjacent to and a is above B), it should be understood that a may be directly above B, or a may be indirectly above B (AB is sandwiching other elements, and a is above B). And so on.

The embodiment of the specification provides an operation monitoring method. The operation monitoring method can be used for monitoring the service operation condition of the target applet. The service operation condition may be a user access condition reflecting the operation condition of the target applet or a parameter of the operation condition of the target applet. For example, the service operation condition may be an access amount of each page of the applet, a call amount of each interface, a page conversion rate, a loop call risk condition, an interface abnormality condition, a page abnormality condition, and the like in the process of providing the service by the applet.

The operation monitoring method can be applied to a scene that a developer of the native application monitors the service operation condition of an applet operated by the native application. Wherein the applet is an application running in a native application through external code. The applet may be a third party application that is distinct from the native application to provide a third party service to the user that is distinct from the native application. For example, taking the operation of a certain applet by a native application as an example, and providing an applet service to a user, the service operation condition of the applet can be monitored by the method, so that a developer of the native application can conveniently analyze and know the operation quality of the applet according to the service operation condition of the applet. The applet that the native application runs on is monitored may be any applet. For example, an applet that provides game services, an applet that provides payment services, an applet that provides ticketing services, an applet that provides shopping services, an applet that provides social services, an applet that provides navigation services, an applet that provides video services, and the like.

The operation monitoring method can be applied to an operation monitoring system. As shown in fig. 1, the application scenario of the operation monitoring method may include a server 101 that provides a service of a native application, where the server 101 may be communicatively connected to one or more (3 are shown as examples in the figure) terminal devices 102 running the native application. The terminal device 102 may have a native application running thereon, which may then have a target applet running thereon. An operation monitoring system, such as an electronic device 103, may be communicatively connected to the server 101, so that a user (such as a developer of a native application) 100 may monitor the service operation of the target applet through the electronic device 103.

By way of example, the communication connection between the above-mentioned server 101 and the terminal device 102, and the communication connection between the electronic device 103 and the server 101 may be a cable network, a wired network, a fiber optic network, a telecommunication network, an intranet, the internet, a local area network (local area networks, LAN), a wide area network (wide area network, WAN), a wireless local area network (wireless local area network, WLAN), a metropolitan area network (metropolitan area network, MAN), a public switched telephone network (public switched telephone network, PSTN), a bluetooth ^TM network, a ZigBee ^TM network, a near field communication (NEAR FIELD communication, NFC) network, or the like. The user 100 may monitor the service operation condition of the target applet through the electronic device 103, so as to know the service quality of the service provided by the target applet.

The operation monitoring method provided in the embodiment of the present disclosure may be executed in the electronic device 103. At this time, the electronic device 103 may store data or instructions for performing the operation monitoring method provided in the embodiment of the present specification, and may perform or be used to perform the data or instructions. In some possible implementations, the electronic device 103 may include a hardware device having a data information processing function and necessary programs required to drive the hardware device to operate. By way of example, the electronic device 103 may be a server, a PC, a tablet, a Personal Digital Assistant (PDA), or the like. The embodiment of the present specification is not particularly limited to the specific device configuration of the electronic device 103. In some possible implementations, the electronic device 103 may be further communicatively connected to other user devices, so that a developer of the native application may access the electronic device 103 through the user device to control the electronic device 103 to perform the operation monitoring method.

In an embodiment of the present specification, an electronic device capable of executing the operation monitoring method is provided. The electronic device may be the electronic device 103 shown in fig. 1.

By way of example, fig. 2 shows a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

As shown in fig. 2, the electronic device may include: radio Frequency (RF) circuitry 210, memory 220, input unit 230, display unit 240, sensor 250, audio circuitry 260, wireless fidelity (WIRELESS FIDELITY, wiFi) module 270, processor 280, power supply 290, and bluetooth module 2100. It will be appreciated by those skilled in the art that the electronic device structure shown in fig. 2 is not limiting of the electronic device and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

The following describes some of the constituent components of the electronic device in detail with reference to fig. 2:

The memory 220 may be used to store software programs and modules that the processor 280 performs various functional applications and data processing of the electronic device by executing the software programs and modules stored in the memory 220. The memory 220 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program (such as an operation monitoring function, etc.) required for at least one function, a boot loader (boot loader), etc.; the storage data area may store data created from the use of the electronic device (such as operational data required to operate the monitoring function, etc.). In addition, memory 220 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The input unit 230 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function controls of the electronic device. In particular, the input unit 230 may include a touch panel 231 and other input devices 232. The touch panel 231, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 231 or thereabout by using any suitable object or accessory such as a finger, a stylus, etc.), and drive the corresponding connection device according to a predetermined program. Alternatively, the touch panel 231 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 280, and can receive commands from the processor 280 and execute them. In particular, other input devices 232 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc. In the present embodiment, the user may input an operation of opening a file in the simulator through the system of the computer through the touch panel 231, the mouse, or the keyboard.

The display unit 240 may be used to display information input by a user or information provided to the user and various menus of the electronic device. The display unit 240 may include a display panel 241, and alternatively, the display panel 241 may be configured in the form of a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), or the like. Further, the touch panel 231 may cover the display panel 241, and when the touch panel 231 detects a touch operation thereon or thereabout, the touch operation is transferred to the processor 280 to determine the type of the touch event, and then the processor 280 provides a corresponding visual output on the display panel 241 according to the type of the touch event. Although in fig. 2, the touch panel 231 and the display panel 241 implement the input and input functions of the electronic device as two separate components, in some embodiments, the touch panel 231 and the display panel 241 may be integrated to implement the input and output functions of the electronic device.

Processor 280 is a control center of the electronic device that utilizes various interfaces and lines to connect various portions of the overall electronic device, perform various functions of the electronic device and process data by running or executing software programs or modules stored in memory 220, and invoking data stored in memory 220. Optionally, the processor 280 may include one or more processing units; preferably, the processor 280 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 280.

Of course, it will be appreciated that the above illustration of FIG. 2 is merely exemplary of an electronic device. In the case of the electronic device being in the form of a tablet computer, a handheld computer, a PC, a PDA, a server, or the like, the electronic device may include fewer structures than those shown in fig. 2, or may include more structures than those shown in fig. 2, which is not limited thereto.

The methods in the embodiments of the present specification may be implemented in an electronic device having the above-described hardware structure. Embodiments of the present specification will be exemplified below with reference to the accompanying drawings.

Fig. 3 shows a flow chart of an operation monitoring method according to an embodiment of the present disclosure. As shown in fig. 3, the operation monitoring method may include the following steps.

S301, acquiring user access data.

Wherein the user access data may be user access data of a native application running the target applet.

By way of example, the user access data may include page access data for the user, interfaces associated with pages accessed by the user, and the like. The page access data includes pages accessed by the user in the native application (which may include pages of the native application itself or pages in an applet run by the native application).

As an example, the manner in which the electronic device obtains the user access data may be that the electronic device obtains through a buried point provided on a server of the native application. For example, by embedding points, the server may record clicking, browsing, jumping and other actions performed by the user on the native application, and events and attribute information corresponding to the relevant actions, so as to generate embedded point data. The electronic device may acquire the embedded data, and clean and aggregate the embedded data, so as to obtain user access data including page access data and data such as interfaces associated with each page accessed by the user.

For example, when a user's operation in a native application includes clicking on a target applet control in the home page of the native application, the native application is caused to jump to the first page of the target applet. The user then clicks on the first video control again in the first page of the target applet, causing the target applet to jump to a second page for playing the first video. At this time, through the buried point set in the server that provides the service for the native application, the server may obtain the click behavior of the user clicking on the target applet control, clicking on the first video control, and the first page of the target applet is jumped by the native application, the jump behavior of the target applet to the second page, and buried point data is generated. After the embedded point data is acquired, the electronic equipment can clean and aggregate the embedded point data to obtain the page access data comprising the original application first page, the target applet first page and the second page and the user access data formed by the interfaces respectively associated with the pages.

Alternatively, the interfaces involved in the user accessing the data may be interfaces that the applet needs to invoke based on the pages accessed by the user. For example, it may be at least one of a gateway interface, an application programming interface (Application Programming Interface, API), or a hypertext transfer protocol (Hypertext Transfer Protocol, HTTP) interface.

S303, generating full-link topology data of the target applet according to the user access data.

The full-link topology data may include page links, access amounts of each page, interfaces corresponding to each page, and call amounts of each interface.

It should be noted that, the page links are page links formed by pages respectively accessed in the process of accessing the target applet by the user. For example, operations performed by the user in the native application include accessing a first page of the native application, clicking on a target applet control in the first page, causing the native application to jump to the first page of the target applet. Clicking a picture upload control on the first page causes the target applet to jump to a second page for uploading the picture, for example. Then, the page link corresponding to the current process of accessing the target applet by the user may be: native application first page-target applet second page.

For the target applet, since the number of users accessing is large, and the number of times each user accesses is typically more than one, the page links in the full link topology data may include one or more. And the page links may be stored in a diagrammatic form and/or presented to the user.

Illustratively, taking the example that the page link includes a plurality of, the page link may be presented in the manner shown in FIG. 4. For example, as shown in FIG. 4, the page link may include page A-page B-page C-page D; page a-page B-page-E; page F-page G; page H-Page I-Page J-Page K.

The access amounts of the pages may also be stored in a chart form and/or presented to the user, for example.

For example, taking the example that the pages include page a, page B, page C, and page D, the access amount of each page may be presented in the manner as in table 1 below.

TABLE 1

Page identification	Applet identification	Page name	Access volume	Access duty cycle
					xxx.xx.1	xxx.1	Page A	50	50％
xxx.xx.2	xxx.1	Page B	20	20％
					xxx.xx.3	xxx.1	Page C	20	20％
xxx.xx.4	xxx.1	Page D	10	10％

The page identifier is an identifier corresponding to the corresponding page, the applet identifier is an identifier of the applet corresponding to the corresponding page, the page name is a name of the corresponding page, and the difference between the applet identifier and the page identifier is that the page identifier is a unique identifier, a unified format is generally adopted, and different pages can have the same name.

As a possible implementation manner, the access ratio of each page may be calculated according to the access amount of each page, and stored in a manner shown in table 1, and/or displayed to the user.

The call volume of each interface may also be stored in a graphical form and/or presented to the user, for example.

For example, taking the interface as a gateway interface, and the gateway interface includes gateway a, gateway B, gateway C, and gateway D as examples, the call volume of each interface may be presented in the manner as table 2 below.

TABLE 2

The gateway identifier is an identifier corresponding to the corresponding gateway, the gateway name is the name of the corresponding gateway, and the difference between the gateway identifier and the gateway identifier is that the gateway identifier is a unique identifier, a unified format is generally adopted, and the gateway name is a custom name in the development process.

As a possible implementation manner, the calling duty ratio of each gateway can be calculated according to the calling amount of each gateway, and stored in a manner shown in table 2, and/or displayed to the user.

For another example, taking an interface as an API, and an API including API-A, API-B, API-C and API-D as an example, the call volume of each interface may be presented as shown in the following table 3.

TABLE 3 Table 3

API identification	API name	Quantity of adjustment	Calling duty cycle
				xxx.xx.1	API-A	50	50％
xxx.xx.2	API-B	20	20％
				xxx.xx.3	API-C	20	20％
xxx.xx.4	API-D	10	10％

The API identifier is an identifier corresponding to the corresponding API, the API name is a name of the corresponding API, and the API identifier is different from the API identifier in that the API identifier is a unique identifier, a unified format is generally adopted, and the API name is a custom name in the development process.

As a possible implementation manner, the calling duty ratio of each API may be calculated according to the calling amount of each API, and stored in a manner shown in table 3, and/or displayed to the user.

For another example, taking an interface as an HTTP interface, and the HTTP interface includes xxx.xx.1, xxx.xx.2, xxx.xx.3, and xxx.xx.4 as examples, the call volume of each interface may be presented as shown in table 4 below.

TABLE 4 Table 4

HTTP identification	Quantity of adjustment	Calling duty cycle
			xxx.xx.1	50	50％
xxx.xx.2	20	20％
			xxx.xx.3	20	20％
xxx.xx.4	10	10％

The HTTP identifier is an identifier corresponding to the corresponding HTTP interface.

As a possible implementation manner, the call duty ratio of each HTTP interface may be calculated according to the call amount of each HTTP interface, and stored in a manner shown in table 4, and/or displayed to the user.

It should be noted that, when the interface includes at least two of the gateway interface, the API, and the HTTP interface, the interfaces may be stored and/or displayed to the user in the manner illustrated by the corresponding table.

As an example, in the embodiment of the present specification, the acquired user access data is user access data of a native application running the target applet. Therefore, when the full-link topology data of the target applet is generated according to the user access data, the acquired user access data is subjected to data cleaning, so that when the user accesses other pages or other applets except the target applet, the corresponding user access data which is not related to the target applet is removed, and the target user access data corresponding to the target applet is obtained. And generating full-link topology data of the target applet according to the target user access data corresponding to the target applet.

For example, when generating the full-link topology data of the target applet according to the target user access data corresponding to the target applet, the target access data may be processed and aggregated according to the target user access data corresponding to different users and different times of access to the native application to obtain corresponding data in the full-link topology data.

For example, the link of each page and the access amount of each page corresponding to the target applet may be obtained according to the page access data included in the target user access data.

As a possible implementation manner, the page link corresponding to each time the user accesses the target applet of the native application can be obtained according to the obtained page access data of the target applet corresponding to the different users and the times when the users access the native application. Thus, the page links may be aggregated, and overlapping page links may be combined, thereby obtaining different page links, and the access amount (or referred to as the number of accesses) of each page.

For another example, the call volume of each interface corresponding to the target applet may be obtained from the access volume of each page obtained as described above and the interface corresponding to each page included in the target user access data.

As a possible implementation manner, interfaces corresponding to different pages may be determined according to the interfaces corresponding to the pages, and then the call volume corresponding to each interface associated with each page may be determined according to the access volume of each page. Because the same interfaces may be associated with different pages, call volumes corresponding to the interfaces respectively associated with the different pages can be aggregated, so that call volumes of the same interfaces corresponding to the different pages are aggregated together, and call volumes corresponding to the different interfaces are finally obtained.

Based on the foregoing example, after obtaining the above link of each page, the access amount of each page, and the call amount of each interface, the interfaces corresponding to each page may be aggregated to obtain the full-link topology data. Or integrating the links of each page, the access quantity of each page, the call quantity of each interface and the interfaces corresponding to each page in the user access data, which are respectively obtained, as full-link topology data.

In the embodiment of the present disclosure, based on the foregoing example, before the full-link topology data is obtained according to the obtained links of each page, the access amount of each page, the call amount of each interface, and the aggregation of the interfaces corresponding to each page, pruning may be performed on the links of the page, so that the links of the page that do not need to be concerned are removed. Therefore, the obtained page links are prevented from interfering with the subsequent monitoring of the operation condition of the target applet service due to the fact that the page links which do not need to be concerned are included, or the calculated amount is increased due to the fact that the page links which do not need to be concerned are more. Correspondingly, the link of each page after pruning, the access quantity of each page, the call quantity of each interface and the interface corresponding to each page can be aggregated to obtain the full-link topology data.

For example, the corresponding preset rule may be set based on the features of the page link that do not need to be concerned, so that the electronic device performs pruning processing of the page link according to the preset rule.

For example, the preset rules may include removing loop call links as well as out-of-range links. Accordingly, the manner in which the electronic device performs pruning processing on each page link may be to first obtain the loop call link and the out-of-range link in each page link, and then remove the loop call link and the out-of-range link in each page link.

The out-of-range link is typically a page link outside a preset monitoring range. For example, the monitoring scope may be a page of the target applet. The out-of-range link may be a portion of the page links that contain pages that do not belong to the targeted applet. For another example, the monitoring scope may be a page of the target applet as well as a native application page that may jump to the page of the target applet. The out-of-range link may be a partial link of the page link that contains pages that do not belong to the target applet and/or native application pages that do not belong to pages that can jump to the target applet.

The removal of the over-range link can avoid the access information of the pages except the target applet from being included in the finally obtained full-link topology data, so that the calculated amount when the service operation condition of the target applet is monitored according to the full-link topology data is reduced.

The loop call link is a link that is constantly reciprocated between two pages. In general, when an abnormality occurs in the page return, after the operation that the user clicks to jump to the next page occurs, the page cannot jump normally, but when the previous page is returned, a loop call link is obtained. Thus, when a loop call link is obtained, it is typically accompanied by a corresponding page exception. In the process of pruning the page link, after the loop call link is acquired, the electronic device can also determine a corresponding loop page according to the loop call link, so as to determine a loop call risk. So that developers of the native application can timely find the loop call risk of the target applet and take corresponding processing measures.

For example, when the electronic device determines a corresponding loop page according to the acquired loop call link, the electronic device may display the corresponding loop page to a developer (or an operation and maintenance person). Therefore, a developer can timely determine the abnormal page and take corresponding processing measures to timely eliminate the circulating call risk.

And S305, monitoring the service operation condition of the target applet according to the full-link topology data.

In general, in practical applications, the monitoring data obtained by monitoring the service operation condition may include the access amount of each page of the target applet, the call amount of each interface, the conversion rate of each page, the loop call risk condition, the interface abnormality condition, the page abnormality condition, and the like. The loop call risk condition may be monitored and determined according to the loop call link obtained when pruning the page link in the foregoing example, and the specific embodiment may refer to the related description in the foregoing example, which is not repeated herein.

The data related to the access amount of each page of the target applet and the call amount of each interface is included in the full link topology data obtained in the foregoing example. Thus, the electronic device may be directly available through the full link topology data.

For the conversion rate, interface abnormal condition, page abnormal condition, and the like of each page, the electronic equipment can be obtained by processing according to the full-link topology data.

For example, the electronic device may determine, according to the access amount of each page in the full-link topology data and the page links, the conversion rate between pages in each page link, so as to obtain the traffic funnel of each page link.

For example, for each page link, the electronic device may first determine, according to the access amount of each page, the time-level access amount of each page on the page link within a preset duration. And then the electronic equipment can calculate and obtain the duty ratio of the time-level access amount of the next page to the time-level access amount of the previous page according to the time-level access amount of each page on the page link, wherein the duty ratio is the conversion rate of the next page. The electronic device can calculate the conversion rate between pages on each page link, so that the flow funnel of each page link is obtained.

For example, taking a page link as page a-page B-page C, the minute access amount of page a is 100, the minute access amount of page B is 50, and the minute access amount of page C is 20. The conversion rate from page a to page B can be determined to be 50% based on the ratio between the minute-level access amount of page B and the minute-level access amount of page a. The conversion rate from page B to page C can also be determined to be 40% based on the ratio between the minute access amount of page C and the minute access amount of page B. Thereby obtaining the traffic funnel for the page link.

When determining the flow funnel corresponding to each page link according to the full link topology data, a developer can search the page with lower conversion rate according to the conversion rate among the pages, so that corresponding measures can be timely taken to improve the conversion rate of the corresponding page, and the target applet can be improved to provide better service.

For another example, the electronic device may monitor the interface call condition of the target applet according to the call quantity of each interface in the full link topology data. Therefore, a user can find the interface with overlarge call quantity in time according to the interface call condition, measures such as current limiting and the like can be taken in time, and the service stability of the target applet is improved.

As an example, a developer may set a call volume threshold for each interface in advance according to experience and actual requirements, so that the electronic device may monitor the call volume of each interface according to the call volume threshold of each interface, and when the call volume of a certain interface exceeds the corresponding call volume threshold, the electronic device may send a prompt message to the developer to prompt the developer that the call volume of the corresponding interface exceeds the threshold. Thereby facilitating the developer to take measures such as current limiting on the corresponding interface in time. Of course, in some other possible implementations, the developer may not set the call volume threshold of the interface, and the electronic device may monitor the call condition of each interface according to the call volume of each interface in the full-link topology data, and display the call volume of each interface to the user. Therefore, a developer can check the call volume of each interface conveniently, judge the interface with overlarge call volume according to actual conditions, and adopt measures such as corresponding current limiting.

For another example, the electronic device may monitor the status of the interfaces of the target applet. When an abnormal interface (namely, the interface state is abnormal) is detected, the page corresponding to the abnormal interface is determined according to the interface corresponding to each page in the full-link topology data. Therefore, a developer can conveniently and timely check the abnormal page condition and the abnormal interface condition according to the monitoring result.

As an example, when the electronic device discovers an abnormal interface (such as an interface with a reduced success rate, an interface with increased time consumption, etc.) in the process of monitoring the state of each interface of the target applet, the electronic device determines a page corresponding to the abnormal interface according to the interface corresponding to each page in the full-link topology data, so as to determine an abnormal page corresponding to the abnormal interface. For example, taking the state of the interface a of the monitored target applet as an exception, the interface corresponding to each page includes the interface corresponding to (or called association with) the interface a of the page B. When the electronic equipment monitors that the state of the interface A is abnormal, the page corresponding to the interface A can be searched according to the interface corresponding to each page, so that the page B is determined to be an abnormal page.

Of course, in some other possible embodiments, there may be a case where one interface is associated with two or more pages for each page's corresponding interface. At this time, if the electronic device determines two or more pages according to the interfaces corresponding to the pages when monitoring the abnormal interfaces, the pages can be displayed to the developer, so that the developer can check the pages respectively to determine the abnormal pages. The manner of displaying the page to the developer may be displaying an image of the corresponding page, displaying a name of the corresponding page, displaying an identifier of the corresponding page, and the like, which is not limited herein. For example, taking the state of the interface a monitored to the target applet as an exception, the interface corresponding to each page includes the page B and the page C, which are both corresponding (or referred to as association) to the interface a. When the electronic equipment monitors that the state of the interface A is abnormal, the page corresponding to the interface A can be searched according to the interface corresponding to each page, so that the page B and the page C are determined, and the page B and the page C are displayed to a developer, so that the developer can conveniently and respectively check the page B and the page C to determine the abnormal page.

For another example, when the returned data corresponding to the target applet is abnormal, the electronic device may determine, based on the abnormal page corresponding to the abnormal returned data, an interface corresponding to the abnormal page according to the interfaces corresponding to the pages in the full-link topology data. Therefore, a developer can conveniently and timely check the abnormal page condition and the abnormal interface condition according to the monitoring result.

As one example, the electronic device may monitor the return data of the target applet to obtain abnormal return data and present the abnormal return data to the developer. Therefore, the developer can conveniently play back the abnormal returned data to obtain the abnormal page. When the developer obtains the abnormal page, the abnormal page can be input to the electronic device. When the electronic equipment receives the input abnormal page, the interface corresponding to the abnormal page can be determined according to the interface corresponding to each page in the full-link topology data in response to receiving the abnormal page. The electronic device may determine whether the returned data is abnormal according to a field in the returned data indicating whether the return is successful. Of course, whether the returned data is abnormal can be judged according to whether the response is successfully made after the returned data is received by the target applet. The target applet can successfully respond after receiving the returned data, and the returned data is normal, otherwise, the returned data is abnormal.

For example, taking the returned data a monitored to the target applet as an exception, the page corresponding to the returned data a is the page B, and the interface corresponding to each page includes the page B corresponding to (or called association with) the interface C as an example. The electronic device may display the returned data a to the developer when it monitors that the returned data a is abnormal. When an abnormal page (namely, page B) obtained by the developer according to the playback of the returned data A is received, the electronic equipment can search the interface corresponding to the page B according to the interface corresponding to each page, so that the interface C is determined to be the abnormal interface.

Of course, in some other possible embodiments, there may be a case where two or more interfaces are associated with one page for each interface corresponding to each page. At this time, if the electronic device determines two or more interfaces according to the page corresponding to the returned data and the interfaces corresponding to the pages when the electronic device monitors the abnormal returned data, the electronic device may display the interfaces to a developer, so that the developer may check the interfaces respectively to determine the abnormal interfaces. The manner of displaying the interface to the developer may be to display the name of the corresponding interface, or may display the identifier of the corresponding interface, etc., which is not limited herein. For example, taking the returned data a monitored to the target applet as an exception, the page corresponding to the returned data a is the page B, and the interface corresponding to each page includes the page B corresponding to (or called association with) the interface C and the interface D as an example. The electronic device may display the returned data a to the developer when it monitors that the returned data a is abnormal. When the electronic equipment receives an abnormal page (namely page B) obtained by the developer according to the playback of the returned data A, the electronic equipment can search the interface corresponding to the page B according to the interfaces corresponding to the pages, so that an interface C and an interface D are determined, and the interface C and the interface D are displayed to the developer, so that the developer can conveniently and respectively check the interface C and the interface D to determine the abnormal interface.

In this embodiment of the present disclosure, as another example, based on the foregoing example, when the electronic device monitors the returned data of the target applet, so as to obtain the abnormal returned data, the electronic device may also directly play back, according to the abnormal returned data, an abnormal page corresponding to the returned data through a playback tool, and then determine, according to the interface corresponding to each page, the interface corresponding to the abnormal page, and display the abnormal page and the corresponding interface to the developer. By the method, the process of manually replaying the returned data to determine the abnormal page by the developer can be omitted, the degree of automation for monitoring the service operation condition of the target applet is improved, and the efficiency is improved.

For another example, the electronic device may determine a source channel page of the target page according to the page links in the full link topology data. And determining the access amount of each source channel page according to the access amount of each page.

Where the target page is typically the first page of the target applet or the page of the target applet that can be jumped to by the page of the native application itself. The source channel page is the last level page of the target page in the page link, namely the page capable of jumping to the target page. By determining the access quantity of the source channel page of the target page, a developer can conveniently know the access condition of each popularization channel of the target applet, and therefore channels with poor popularization effects are arranged for improvement. The access amount of the source channel page may be a time-length level access amount within a preset time length, such as a minute-length level access amount, or an accumulated access amount, etc., which is not limited herein. Optionally, the electronic device may also show the user the access amount of each source channel page in the form of a chart.

For example, the source channel page of the home page taking the target page as the target applet includes the home page, the atmosphere map page, the advertisement page and the popup window page which are arranged in the native application. The electronic device may determine the access amount of each source channel page according to the access amount of each page in the full-link topology data after determining the source channel page corresponding to the first page of the target applet according to the page link. For example, the electronic device may determine that the access amount corresponding to the home page in the native application is 100, the access amount corresponding to the atmosphere map page is 80, the access amount corresponding to the advertisement page is 90, the access amount corresponding to the popup page is 20, and the like.

For example, after determining the source channel page of the target page and the access amount of each source channel page, the electronic device may further generate a corresponding chart to store the source channel page of the target page and the access amount related data of each source channel page, and/or display the data to a user (such as a developer of the native application). For example, based on the foregoing example, when the electronic device determines the source channel page of the target page, the access amounts of the different source channel pages in each section of the preset duration may be determined respectively with the preset time length as an interval, so as to generate a graph related to the access amounts corresponding to the different source channel pages in each section of the preset duration. For example, taking a preset time length as one hour, the access amount of different source channel pages in each section of preset time length in 6 hours is shown, and the source channel pages comprise a home page, an atmosphere chart page, an advertisement page and a popup window page of the original application. The electronic device may generate a source channel page access trend in the page access trend graph as shown in fig. 5, where the access amounts corresponding to the first page in the native application are respectively 100, 85, 88, 70, 80, 99 in each preset period of 0-5, the access amounts corresponding to the atmosphere map page are respectively 80, 90, 95, 70, 75, 70 in each preset period of 0-5, the access amounts corresponding to the advertisement page are respectively 90, 80, 85, 70, 75 in each preset period of 0-5, and the access amounts corresponding to the popup page are respectively 20, 40, 45, 30, 35, 40 in each preset period of 0-5.

In some possible implementations, the electronic device may also store the access amount of the target page in the form of a chart and/or present to a user (e.g., a developer of the native application). For example, the electronic device may further determine, according to the preset time length, the access amount of the target page in each preset time length, so as to generate a chart related to the access amount corresponding to the target page in each preset time length. For example, taking the preset time length as one hour, the access amount of the target page in each section of preset time length in 6 hours is shown, and the target page is the first page of the target applet. The electronic device may generate a target page (e.g., a home page of a target applet) access trend in the page access amount trend chart shown in fig. 5, where the access amount corresponding to the home page of the target applet is 1000, 850, 880, 700, 800, 990, respectively, within each preset time period of 0-5.

In some other embodiments, the two charts of the source channel page access trend and the target page access trend generated by the electronic device may also be presented to the user through different pages, instead of being integrated into one page as shown in fig. 5, which is not limited herein. Of course, in practical application, the electronic device may also generate a chart related to the access trend of other pages according to the user configuration, and the specific embodiment may refer to the foregoing source channel page access trend and the target page access trend, which are not described herein again.

Optionally, after obtaining the access amount of the source channel page, the electronic device may further determine the access amount of the target page according to the access amount of each page, so as to calculate, according to the access amount of the target page and the access amount of each source channel page, the conversion rate from each source channel page to the target page. So that a developer can check the source channel page with poor conversion rate according to the conversion rate, thereby improving the corresponding popularization channel in time.

By adopting the method in the embodiment, the full-link topology data of the target applet can be obtained by accessing the data by the user of the native application. The full-link topology data may include data such as page links, access amounts of each page, interfaces corresponding to each page, and call amounts of each interface. Therefore, the service operation condition of the target applet can be monitored according to the full-link topology data. Such as interface call condition, page access condition, etc. of the monitoring target applet. And a developer of the native application is convenient to monitor the service operation condition of the third party applet.

For example, the native application may be a shopping application, a payment application, a lifestyle application, etc., and the targeting applet may be a ticketing applet, an event applet, a lifestyle servlet, etc., accordingly. Based on the foregoing embodiment, taking the native application as the payment application and the objective applet as the event applet as an example, the user access data of the event applet may be obtained by obtaining the user access data of the payment application and performing data cleaning on the user access data of the payment application, thereby obtaining the full link topology data of the event applet. The full-link topology data may include data such as page links of the event applet, access amounts of each page, interfaces corresponding to each page, and call amounts of each interface. The service operation condition of the event applet can be monitored according to the full link topology data. For example, interface call conditions, page access conditions, etc. of the event applet may be monitored.

By way of example, the call quantity of each interface can be aggregated according to the interfaces corresponding to each page in the full-link topology data and the call quantity of each interface, so as to obtain the call condition of each interface of the event applet, so that a developer can find out the interface calling abnormally in time according to the call condition of each interface, and can conveniently realize the interface coverage of the event applet according to the information of each interface, and thus measures such as current limiting can be adopted for the corresponding interface in time when a certain interface of the event applet calls abnormally. The conversion rate among the pages of the event applet can be obtained by combing according to the page links in the full-link topology data and the access quantity of each page, so that operators can know the operation condition of the event applet according to the conversion rate among the pages of the event applet. When an abnormality occurs to a certain page of the event applet, the interface corresponding to the abnormal page can be arranged according to the full-link topology data so as to find out the abnormal interface in time and take corresponding processing measures. Or when an interface of the event applet is abnormal (such as a decrease in success rate of the interface or an increase in time consumption of the interface), determining a page corresponding to the abnormal interface according to the full-link topology data, thereby determining an abnormal page so as to enable a developer to optimize the abnormal page.

By way of example, channel tracing of the event operation activity of the event applet can be performed according to page links in the full-link topology data, the access quantity of each page and the like, so that operators can know conversion conditions of each delivery channel conveniently according to channel tracing. For example, each source channel page of the front page of the event operation activity of the event applet (i.e. each previous page of the front page of the event operation activity in the page link, such as a search result page, a payment application front page, an event atmosphere map page, etc.), the access amount of the front page of the event operation activity and the access amount of each source channel page can be determined according to the full link topology data, so that an operator can determine a channel with better release effect (such as a release channel corresponding to a source channel page with higher access amount), and the quality of the operation activity is ensured.

Corresponding to the method in the foregoing embodiment, the embodiment of the present specification further provides an operation monitoring device. The apparatus may be applied to the electronic device described above for implementing the method in the foregoing embodiment. The functions of the device can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above. For example, fig. 6 shows a schematic structural diagram of an operation monitoring apparatus, as shown in fig. 6, which includes: an acquisition module 601, a processing module 602, and the like. The acquisition module 601 and the processing module 602 may be used in combination to implement the operation monitoring method related to the above embodiment.

It should be understood that the division of units or modules (hereinafter referred to as units) in the above apparatus is merely a division of logic functions, and may be fully or partially integrated into one physical entity or may be physically separated. And the units in the device can be all realized in the form of software calls through the processing element; or can be realized in hardware; it is also possible that part of the units are implemented in the form of software, which is called by the processing element, and part of the units are implemented in the form of hardware.

For example, each unit may be a processing element that is set up separately, may be implemented as integrated in a certain chip of the apparatus, or may be stored in a memory in the form of a program, and the functions of the unit may be called and executed by a certain processing element of the apparatus. Furthermore, all or part of these units may be integrated together or may be implemented independently. The processing element described herein, which may also be referred to as a processor, may be an integrated circuit with signal processing capabilities. In implementation, each step of the above method or each unit above may be implemented by an integrated logic circuit of hardware in a processor element or in the form of software called by a processing element.

In one example, the units in the above apparatus may be one or more integrated circuits configured to implement the above method, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of at least two of these integrated circuit forms.

For another example, when the units in the apparatus may be implemented in the form of a scheduler of processing elements, the processing elements may be general-purpose processors, such as CPUs or other processors that may invoke programs. For another example, the units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

In one implementation, the above means for implementing each corresponding step in the above method may be implemented in the form of a processing element scheduler. For example, the apparatus may comprise a processing element and a storage element, the processing element invoking a program stored in the storage element to perform the method described in the above method embodiments. The memory element may be a memory element on the same chip as the processing element, i.e. an on-chip memory element.

In another implementation, the program for performing the above method may be on a memory element on a different chip than the processing element, i.e. an off-chip memory element. At this point, the processing element invokes or loads a program from the off-chip storage element onto the on-chip storage element to invoke and execute the method described in the method embodiments above.

For example, embodiments of the present description may also provide an operation monitoring system, which may include an electronic device, which may include: a processor, a memory for storing instructions executable by the processor. The processor is configured to execute the above-described instructions, causing the electronic device to implement an operation monitoring method as may be implemented in an electronic device in the foregoing embodiments. The memory may be located within the electronic device or may be located external to the electronic device. And the processor includes one or more.

In yet another implementation, the unit implementing each step in the above method may be configured as one or more processing elements, where the processing elements may be disposed on the electronic device corresponding to the above, and the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

For example, the embodiments of the present specification also provide a chip system that can be applied to the above-described electronic device. The system on a chip includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected through a circuit; the processor receives and executes computer instructions from the memory of the electronic device via the interface circuit to implement the methods associated with the electronic device in the above method embodiments.

Embodiments of the present specification also provide a computer program product comprising computer instructions for an electronic device, such as the electronic device described above, to operate.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above.

In the several embodiments provided in this specification, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present specification may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present description may be embodied in the form of a software product, such as: and (5) program. The software product is stored in a program product, such as a computer readable storage medium, comprising instructions for causing a device (which may be a single-chip microcomputer, chip or the like) or processor (processor) to perform all or part of the steps of the methods described in the various embodiments of this specification. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.

For example, embodiments of the present description may also provide a computer readable storage medium having computer program instructions stored thereon. The computer program instructions, when executed by an electronic device, cause the electronic device to carry out the method as described in the foregoing method embodiments.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

In view of the foregoing, it will be evident to a person skilled in the art that the foregoing detailed disclosure may be presented by way of example only and may not be limiting. Although not explicitly described herein, those skilled in the art will appreciate that the present description is intended to encompass various adaptations, improvements, and modifications of the embodiments. Such alterations, improvements, and modifications are intended to be proposed by this specification, and are intended to be within the spirit and scope of the exemplary embodiments of this specification.

Furthermore, certain terms in the present description have been used to describe embodiments of the present description. For example, "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present description. Thus, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined as suitable in one or more embodiments of the invention.

It should be appreciated that in the foregoing description of embodiments of the present specification, various features have been combined in a single embodiment, the accompanying drawings, or description thereof for the purpose of simplifying the specification in order to assist in understanding one feature. However, this is not to say that a combination of these features is necessary, and it is entirely possible for a person skilled in the art to label some of the devices as separate embodiments to understand them upon reading this description. That is, embodiments in this specification may also be understood as an integration of multiple secondary embodiments. While each secondary embodiment is satisfied by less than all of the features of a single foregoing disclosed embodiment.

Each patent, patent application, publication of patent application, and other materials, such as articles, books, specifications, publications, documents, articles, etc., cited herein are hereby incorporated by reference. All matters are to be interpreted in a generic and descriptive sense only and not for purposes of limitation, except for any prosecution file history associated therewith, any and all matters not inconsistent or conflicting with this document or any and all matters not complaint file histories which might have a limiting effect on the broadest scope of the claims. Now or later in association with this document. For example, if there is any inconsistency or conflict between the description, definition, and/or use of terms associated with any of the incorporated materials, the terms in the present document shall prevail.

Finally, it is to be understood that the embodiments of the application disclosed herein are illustrative of the principles of the embodiments of the present specification. Other modified embodiments are also within the scope of this specification. Accordingly, the embodiments disclosed herein are by way of example only and not limitation. Those skilled in the art can adopt alternative arrangements to implement the application in the specification based on the embodiments in the specification. Therefore, the embodiments of the present specification are not limited to the embodiments precisely described in the application.

Claims

1. An operation monitoring method for monitoring service operation conditions of a target applet, the target applet being an application program that is run in a native application through an external code, the method comprising:

acquiring user access data, wherein the user access data comprises user access data of the native application running the target applet;

generating full-link topology data of the target applet according to the user access data, wherein the full-link topology data comprises page links, access quantity of each page, interfaces corresponding to each page and call quantity of each interface, and the page links comprise links formed by pages respectively accessed by the user in the process of accessing the target applet; and

And monitoring the service operation condition of the target applet according to the full-link topology data.

2. The method of claim 1, wherein the generating full link topology data of the targeted applet from the user access data comprises:

Performing data cleaning on the user access data to obtain target user access data corresponding to the target applet; and

And generating the full-link topology data of the target applet according to the target user access data corresponding to the target applet.

3. The method of claim 2, wherein the user access data includes page access data of a user and interfaces corresponding to respective pages; the generating the full-link topology data of the target applet according to the target user access data corresponding to the target applet includes:

Obtaining the links of each page and the access quantity of each page corresponding to the target applet according to the page access data;

Obtaining the call quantity of each interface corresponding to the target applet according to the access quantity of each page and the interfaces corresponding to each page; and

And aggregating according to the page links, the access amount of the pages, the call amount of the interfaces and the interfaces corresponding to the pages to obtain the full-link topology data.

4. The method according to claim 3, wherein before the aggregating the full-link topology data according to the links of the pages, the access amounts of the pages, the call amounts of the interfaces, and the interfaces corresponding to the pages, the method further comprises:

Pruning is carried out on each page link according to a preset rule, each page link after pruning is obtained, and the preset rule is used for pruning page links which do not need to be concerned;

The step of obtaining the full-link topology data according to the links of the pages, the access amount of the pages, the call amount of the interfaces and the interfaces corresponding to the pages in an aggregation way, comprises the following steps:

And aggregating according to the pruned links of each page, the access quantity of each page, the call quantity of each interface and the interfaces corresponding to each page to obtain the full-link topology data.

5. The method of claim 4, wherein pruning the page links of the users according to a preset rule to obtain pruned page links, comprises:

Acquiring a cyclic call link and an out-of-range link in each page link, wherein the out-of-range link is a page link outside a preset monitoring range; and

And removing the loop call link and the out-of-range link in the page links.

6. The method of claim 5, wherein the method further comprises:

And obtaining a loop page according to the loop call link to determine the loop call risk.

7. The method of claim 1, wherein the monitoring the service operation of the target applet according to the full link topology data comprises:

And determining a flow funnel corresponding to each page link according to the access quantity of each page and the page link.

8. The method of claim 1, wherein the monitoring the service operation of the target applet according to the full link topology data comprises:

And monitoring the interface calling condition of the target applet according to the calling quantity of each interface.

9. The method of claim 1, wherein the monitoring the service operation of the target applet according to the full link topology data comprises:

monitoring the states of all interfaces of the target applet; and

When an abnormal interface is detected, determining a page corresponding to the abnormal interface according to the interface corresponding to each page.

10. The method of claim 1, wherein the monitoring the service operation of the target applet according to the full link topology data comprises:

When the returned data corresponding to the target applet is abnormal, determining an interface corresponding to the abnormal page based on the abnormal page corresponding to the abnormal returned data according to the interfaces corresponding to the pages.

11. The method of claim 10, wherein when the returned data corresponding to the target applet is abnormal, determining the interface corresponding to the abnormal page according to the interface corresponding to each page based on the abnormal page corresponding to the abnormal returned data, including:

Detecting an abnormality of the returned data, and displaying the abnormal returned data;

Receiving the input abnormal page, wherein the abnormal page is obtained based on the return data playback; and

And responding to the received input abnormal pages, and determining the interfaces corresponding to the abnormal pages according to the interfaces corresponding to the pages.

12. The method of claim 1, wherein the monitoring the service operation of the target applet according to the full link topology data comprises:

determining a source channel page of the target page according to the page link; and

And determining the access amount of each source channel page according to the access amount of each page.

13. The method of claim 1, wherein the interface comprises at least one of a gateway interface, an application programming interface API, or a hypertext transfer protocol HTTP interface.

14. An operation monitoring system, comprising:

at least one storage medium storing at least one set of instructions for implementing operation monitoring; and

At least one processor communicatively coupled to the at least one storage medium,

Wherein the at least one processor reads the at least one instruction set and implements the operation monitoring method of any of claims 1-13 when the operation monitoring system is running.