App external jump monitoring method and related device

Abstract

The present invention discloses an app external jump monitoring method and related devices. The method can obtain a monitoring strategy for a first SDK, wherein the first SDK is a software development kit pre-connected to the app platform, and the monitoring strategy involves monitoring indicators at different levels, including: a module layer involving jump behavior, a functional class layer involving jump behavior, a method layer involving jump behavior, and a parameter layer involving jump behavior, each level corresponding to one monitoring indicator; according to the monitoring strategy, turn on the switch of the corresponding pre-established monitoring logic, wherein the monitoring logic corresponds one-to-one with the monitoring strategy; and call the monitoring logic to monitor the external jump behavior of the first SDK. The present invention can turn on the corresponding monitoring logic according to the monitoring strategy, thereby monitoring the external jump behavior of the corresponding SDK, and can monitor the external jump behavior of the SDK more accurately.

Description

Technical Field

[0001] The present invention relates to the field of mobile applications, and in particular to a method and related device for monitoring external jumps of an app. Background Art

[0002] Mobile client applications are categorized as native client apps, WeChat mini-programs, and quick apps. They support business scenarios of varying complexity, and the system provides a set of rules for navigating between them. However, large apps, often containing tens or even millions of lines of code, require a series of software development kits (SDKs) to implement external redirection due to their complex business models. Effectively monitoring and controlling these SDKs' external redirection behavior presents a technical challenge. Summary of the Invention

[0003] In view of the above problems, the present invention provides an app external jump monitoring method and related devices that overcome the above problems or at least partially solve the above problems.

[0004] In a first aspect, a method for monitoring external jumps of an app includes:

[0005] Obtaining a monitoring strategy for a first SDK, wherein the first SDK is a software development kit pre-connected to an app platform, the monitoring strategy involving monitoring indicators at different levels, the levels comprising: a module level involving jump behavior, a function level involving jump behavior, a method level involving jump behavior, and a parameter level involving jump behavior, each level corresponding to one monitoring indicator;

[0006] According to the monitoring strategy, turning on the switch of the corresponding pre-established monitoring logic, wherein the monitoring logic corresponds to the monitoring strategy one-to-one;

[0007] The monitoring logic is called to monitor the external jump behavior of the first SDK.

[0008] In conjunction with the first aspect, in certain optional implementations, turning on a switch of a corresponding pre-established monitoring logic according to the monitoring strategy includes:

[0009] According to each of the monitoring indicators involved in the monitoring strategy, a switch of a corresponding pre-established monitoring logic is turned on, wherein one monitoring logic corresponds to a plurality of the monitoring indicators.

[0010] In combination with the previous embodiment, in some optional embodiments, calling the monitoring logic to monitor the external jump behavior of the first SDK includes:

[0011] The monitoring logic is called to monitor the data of each monitoring indicator involved in the monitoring strategy for the external jump behavior of the first SDK.

[0012] In conjunction with the first aspect, in some optional implementations, after calling the monitoring logic to monitor the external jump behavior of the first SDK, the method further includes:

[0013] Obtaining monitoring results of the external jump behavior of the first SDK;

[0014] The monitoring indicators involved in the monitoring strategy are adjusted according to the monitoring results.

[0015] In combination with the previous embodiment, in some optional embodiments, after obtaining the monitoring result of monitoring the external jump behavior of the first SDK, the method further includes:

[0016] Based on the monitoring results, the external jump behavior of the first SDK is controlled accordingly.

[0017] Optionally, in certain optional implementations, after obtaining the monitoring result of monitoring the external jump behavior of the first SDK, the method further includes:

[0018] Query the log file to obtain context information corresponding to the external jump behavior of the first SDK;

[0019] The adjusting the monitoring indicators involved in the monitoring strategy according to the monitoring results includes:

[0020] The monitoring indicators involved in the monitoring strategy are adjusted according to the monitoring results and the context information, thereby updating the monitoring strategy.

[0021] In a second aspect, an app external jump monitoring device includes: a policy acquisition unit, a switch opening unit, and a monitoring unit;

[0022] The strategy obtaining unit is configured to obtain a monitoring strategy for a first SDK, wherein the first SDK is a software development kit pre-connected to an app platform, the monitoring strategy involving monitoring indicators at different levels, the levels comprising: a module level involving jump behavior, a function level involving jump behavior, a method level involving jump behavior, and a parameter level involving jump behavior, each level corresponding to one monitoring indicator;

[0023] The switch opening unit is configured to open a switch corresponding to a pre-established monitoring logic according to the monitoring strategy, wherein the monitoring logic corresponds to the monitoring strategy in a one-to-one manner;

[0024] The monitoring unit is used to call the monitoring logic to monitor the external jump behavior of the first SDK.

[0025] In conjunction with the second aspect, in certain optional embodiments, the switch opening unit includes: a switch opening subunit;

[0026] The switch opening subunit is used to open the switch of the corresponding pre-established monitoring logic according to each monitoring indicator involved in the monitoring strategy, wherein one monitoring logic corresponds to multiple monitoring indicators.

[0027] In a third aspect, a computer-readable storage medium stores a program thereon, which, when executed by a processor, implements any of the above-mentioned methods for monitoring external jumps of an app.

[0028] In a fourth aspect, an electronic device includes at least one processor, and at least one memory and bus connected to the processor; wherein the processor and the memory communicate with each other through the bus; the processor is used to call program instructions in the memory to execute any of the above-mentioned app external jump monitoring methods.

[0029] By means of the above technical solution, the app external jump monitoring method and related device provided by the present invention can obtain a monitoring strategy for the first SDK, wherein the first SDK is a software development kit pre-connected to the app platform, and the monitoring strategy involves monitoring indicators at different levels, the levels including: a module layer involving jump behavior, a functional class layer involving jump behavior, a method layer involving jump behavior, and a parameter layer involving jump behavior, and one of the levels corresponds to one monitoring indicator; according to the monitoring strategy, turn on the switch of the corresponding pre-established monitoring logic, wherein the monitoring logic corresponds one-to-one with the monitoring strategy; call the monitoring logic to monitor the external jump behavior of the first SDK. It can be seen from this that the present invention can turn on the corresponding monitoring logic according to the monitoring strategy, thereby monitoring the external jump behavior of the corresponding SDK, and can monitor the external jump behavior of the SDK more accurately.

[0030] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present invention. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0032] Figure 1 The flowchart of the first method for monitoring external jumps of an app provided by the present invention is shown;

[0033] Figure 2 A schematic diagram of an atomization combination configuration provided by the present invention is shown;

[0034] Figure 3 The flowchart of the second method for monitoring external jumps of an app provided by the present invention is shown;

[0035] Figure 4 The flowchart of the third method for monitoring external jumps of an app provided by the present invention is shown;

[0036] Figure 5 The flowchart of the fourth method for monitoring external jumps of an app provided by the present invention is shown;

[0037] Figure 6 The figure shows a schematic structural diagram of an app external jump monitoring device provided by the present invention;

[0038] Figure 7 A schematic structural diagram of an electronic device provided by the present invention is shown. DETAILED DESCRIPTION

[0039] Mobile client applications are categorized as native client apps, WeChat mini-programs, and quick apps. They support business scenarios of varying complexity, and the system provides a set of rules for navigating between them. However, large apps, often containing tens or even millions of lines of code, require a series of SDKs for external redirection due to their complex business models. Effectively monitoring and controlling these SDKs' external redirection behavior presents a technical challenge.

[0040] To this end, the present invention provides an app external jump monitoring method. After the app is running, the monitoring logic of the external jump behavior can be controlled through a dynamic monitoring strategy, so that the jump behavior can be managed and reported in context. The client can be modified at the minimum cost, and the monitoring strategy can be flexibly configured to achieve maximum supervision and control of the external jump behavior, and the monitoring results are relatively accurate.

[0041] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0042] like Figure 1 As shown, the present invention provides an app external jump monitoring method, including: S100, S200 and S300;

[0043] S100: Obtain a monitoring strategy for the first SDK;

[0044] The first SDK is a software development kit pre-connected to the app platform, and the monitoring strategy involves monitoring indicators at different levels, including: a module level involving jump behavior, a function level involving jump behavior, a method level involving jump behavior, and a parameter level involving jump behavior, each level corresponding to one monitoring indicator;

[0045] Optionally, the present invention can pre-establish at least one set of monitoring strategies for each SDK connected to the app platform. When executing the present invention, the corresponding monitoring strategies can be issued to the execution subject of the present invention as needed, and the present invention does not limit this.

[0046] Optionally, after connecting to the app platform, each SDK is first assigned a key that can be used for external redirection. This key is used to apply for authentication and, upon successful authentication, a public key is returned. When performing external redirection, the SDK can use the public key to encrypt some parameters (such as time and SDK name). The encrypted value is used as the source ID for transmission, including for Intent, URL, and deeplink transmission methods, which are not limited by the present invention.

[0047] Optionally, the present invention does not impose any specific restrictions on the type of SDK. For example, the SDK referred to in the present invention may be an advertising, game, or platform SDK, and the present invention does not impose any restrictions on this.

[0048] Optionally, the jump behavior mentioned in the present invention involves the module layer, the function class layer, the method layer and the parameter layer, that is, the module layer, the function class layer, the method layer and the parameter layer will all have corresponding jump behaviors. Therefore, the monitoring strategy of the present invention can set corresponding monitoring indicators from four levels: the module layer, the function class layer, the method layer and the parameter layer. Among them, when establishing a monitoring strategy, the module layer, the function class layer, the method layer and the parameter layer under the same set of monitoring strategies are each set with only one monitoring indicator, and the module layer, the function class layer, the method layer and the parameter layer of different monitoring strategies can each be set with different monitoring indicators, and the present invention does not limit this.

[0049] Optionally, in a specific set of monitoring strategies, the specific content of each layer is involved. That is, the specific content of each layer in the monitoring strategy can be understood as the monitoring indicators mentioned in the present invention. For example, at the module layer, the specific content including "webview related", "socket related", "Intent related" and "UIApplication" can be understood as monitoring indicators of the module layer.

[0050] The monitoring indicators at any module level can be further broken down into different functions as functional level monitoring indicators. For example, "webview-related" can be broken down into functional level monitoring indicators such as "webview" and "webviewClient."

[0051] For any functional class layer, you can also break it down into different methods as method-level monitoring indicators. For example, "webview-related" can be broken down into monitoring indicators for the "constructor," "loadurl," "loadData," and "loadDataWithBaseURL" methods.

[0052] Similarly, any method-level monitoring indicator can be broken down into different parameters as parameter-level monitoring indicators. For example, "constructor" can be broken down into parameter-level monitoring indicators such as "stack," "param1," "param2," "param3," ..., and "paramN." This is not a limitation of the present invention.

[0053] Optionally, the monitoring strategies described in the present invention can be roughly divided into downgrade strategies, normal strategies, and upgrade strategies. Generally speaking, model information, system version, and app version information can be freely combined, and a set of monitoring strategies (including downgrade strategies, normal strategies, and upgrade strategies) can be pre-established for any combination. The normal strategy is used in non-abnormal situations; the downgrade strategy is used when compatibility issues arise; and the upgrade strategy is used when users report that they encounter external jump behaviors that do not meet product expectations. The device ID can be configured on the server so that it can use the deepest monitoring strategy with the most complete information when it requests again.

[0054] Optionally, the software development kit (SDK) is a well-known concept in the art, and the present invention will not elaborate on it in detail. For details, please refer to the relevant description in the art.

[0055] S200: Turn on the switch of the corresponding pre-established monitoring logic according to the monitoring strategy;

[0056] Wherein, the monitoring logic corresponds to the monitoring strategy one by one;

[0057] Optionally, the present invention can configure monitoring logic specifically for different operating systems. For example, while official documentation only provides two methods for redirecting to quick apps on Android, deeplink redirection and URL redirection, the corresponding underlying system interface calls fall into three categories: redirecting to quick apps through a webview, where the system dispatches and invokes specific domain keywords; implicitly launching a quick app through an Intent, where the system invokes the quick app; and intercepting the third method, where a socket connection is monitored. Therefore, to ensure accurate monitoring and complete traceability, the present invention can record all information at the module, function, method, and parameter levels, including the entire call stack, call time, and process ID, and create a dynamically configurable switch, thereby balancing performance and effective monitoring. For users and scenarios requiring specific replication, the switch can be fully enabled to collect as much information as possible for analysis and location analysis. For monitoring a large user base, a coordinated dynamic switch is used. iOS, on the other hand, is relatively simple. Since it lacks the concept of redirecting to quick apps, and only third-party native apps and WeChat mini-programs exist, monitoring the UIApplication openurl method is sufficient, and this is not a limitation of the present invention.

[0058] Optionally, the monitoring strategy reflects the atomic combination configuration for monitoring external jump behavior. Figure 2 As an example, the atomic combination configuration diagram shown in FIG is used to represent an atomic combination configuration, where the highest bit represents the major category (module layer), that is, the first layer surrounding the "Mobile APP Platform" (" ①webview related"," ② socket related"," ③ Intent related" and ④ UIApplication”), the second highest level represents the middle class (functional class layer), which is the second layer surrounding the “mobile APP platform” (“ ① webview related"," ② socket related"," ③ Intent related" and ④ UIApplication" are connected to the next layer respectively), the third highest bit is the subclass (method layer), that is, the third layer surrounding the "mobile APP platform", and the lowest bit is the fine class (parameter layer), that is, the fourth layer surrounding the "mobile APP platform".

[0059] For example, if a certain atomic combination is configured as "1111", it means that monitoring is required. Figure 2 The webview in the webview is related, the webview class is used, and the constructor needs to be monitored and the call stack is printed. The two can be equated; by analogy, "1112" means: monitoring webview related, webview class, the first input parameter of the constructor, the present invention does not limit this.

[0060] Optionally, different atomic combination configurations require monitoring of different indicators at different layers, i.e., corresponding switches need to be turned on for monitoring. Therefore, the present invention sets different monitoring logics for different monitoring strategies, and the activation of the monitoring logic is controlled by the switch, which is not limited by the present invention.

[0061] For example, combined with Figure 1 In some optional embodiments, the step S200 includes:

[0062] According to each of the monitoring indicators involved in the monitoring strategy, a switch of a corresponding pre-established monitoring logic is turned on, wherein one monitoring logic corresponds to a plurality of the monitoring indicators.

[0063] Optionally, the above-mentioned deeplink, url, webview, domain, domain, connect, UIApplication and openurl are all well-known concepts in this field. For details, please refer to the relevant description in this field.

[0064] S300: Call the monitoring logic to monitor the external jump behavior of the first SDK.

[0065] Optionally, as previously described, the monitoring logic involves external redirection behaviors at the module, function, method, and parameter levels. Therefore, by invoking the monitoring logic, the external redirection behaviors of the first SDK can be monitored. The first SDK is merely an example for describing the present invention; the present invention is applicable to any SDK and is not limited thereto.

[0066] Optionally, the present invention does not limit the process of calling the monitoring logic to monitor the external jump behavior of the first SDK. For example, in combination with the previous embodiment, in some optional embodiments, S300 includes: calling the monitoring logic to monitor the data of each monitoring indicator involved in the monitoring policy for the external jump behavior of the first SDK.

[0067] Optionally, different monitoring logics are specific to different monitoring indicators at different layers, so the data of the corresponding monitoring indicators should be monitored, and the present invention does not impose any limitation on this.

[0068] Optionally, after each SDK is connected to the app platform, it is first assigned a key that can be used for external jump. This key is used to apply for authentication. After the authentication is passed, a public key will be returned. The SDK will encrypt some parameters (such as time and SDK name, etc.) when performing external jump. The encrypted value is used as the source ID for transmission, including Intent, URL and deeplink, etc. The present invention does not limit this.

[0069] like Figure 3 As mentioned above, combined Figure 1 In the embodiment shown, in certain optional embodiments, after S300, the method further includes: step 1.1 and step 1.2;

[0070] Step 1.1, obtaining monitoring results of the external jump behavior of the first SDK;

[0071] Step 1.2: Adjust the monitoring indicators involved in the monitoring strategy according to the monitoring results.

[0072] Optionally, the monitoring indicators involved in the monitoring strategy are adjusted based on the feedback of the monitoring results, and the corresponding atomic combination configuration is adjusted accordingly, thereby adjusting the corresponding monitoring logic. By adjusting the monitoring strategy, the monitoring strategy can be upgraded or downgraded, which is not limited by the present invention.

[0073] For example, when users report that the system is severely stuck, crashes, or has other problems that affect usage, it means that the current monitoring strategy occupies too many resources to monitor external jump behaviors, seriously affecting the normal operation of the system, so the monitoring strategy can be downgraded. The present invention does not limit this.

[0074] Optionally, after obtaining monitoring results for any SDK, the present invention can check whether corresponding historical monitoring results exist in the historical monitoring data. If so, the rationality of the monitoring results obtained can be determined based on the rationality of the SDK in the historical data. If so, no adjustment to the monitoring indicators is necessary; if not, adjustments can be made accordingly.

[0075] If no corresponding historical data is saved for the SDK, the monitoring indicators can be adjusted accordingly based on the problems reported by users regarding the SDK and the monitoring results of this time. The present invention does not impose any restrictions on this.

[0076] like Figure 4 As shown, in combination with the previous embodiment, in some optional embodiments, after step 1.1, the method further includes: step 2.1;

[0077] Step 2.1: Based on the monitoring results, the external jump behavior of the first SDK is controlled accordingly.

[0078] The aforementioned monitoring of external jumps is intended to be data-focused. However, in practice, the present invention can also manage and control external jumps based on actual needs. This includes intervening in external jumps, such as restricting them, though this is not a limitation of the present invention.

[0079] like Figure 5 As shown, in some optional embodiments, after step 1.1, the method further includes: step 3.1;

[0080] Step 3.1: query the log file to obtain context information corresponding to the external jump behavior of the first SDK;

[0081] The step 1.2 includes: step 3.2;

[0082] Step 3.2: According to the monitoring result and the context information, adjust the monitoring indicators involved in the monitoring strategy, thereby updating the monitoring strategy.

[0083] like Figure 6 As shown, the present invention provides an app external jump monitoring device, including: a strategy acquisition unit 100, a switch opening unit 200 and a monitoring unit 300;

[0084] The strategy obtaining unit 100 is configured to obtain a monitoring strategy for a first SDK, wherein the first SDK is a software development kit pre-connected to an app platform, the monitoring strategy involving monitoring indicators at different levels, the levels including: a module level involving jump behavior, a function level involving jump behavior, a method level involving jump behavior, and a parameter level involving jump behavior, each level corresponding to one monitoring indicator;

[0085] The switch opening unit 200 is configured to open a switch corresponding to a pre-established monitoring logic according to the monitoring strategy, wherein the monitoring logic corresponds to the monitoring strategy in a one-to-one manner;

[0086] The monitoring unit 300 is used to call the monitoring logic to monitor the external jump behavior of the first SDK.

[0087] Combine Figure 6 In the illustrated embodiment, in certain optional embodiments, the switch opening unit 200 includes: a switch opening subunit;

[0088] The switch opening subunit is used to open the switch of the corresponding pre-established monitoring logic according to each monitoring indicator involved in the monitoring strategy, wherein one monitoring logic corresponds to multiple monitoring indicators.

[0089] In combination with the previous embodiment, in some optional embodiments, the monitoring unit 300 includes: a monitoring subunit;

[0090] The monitoring subunit is used to call the monitoring logic to monitor the data of each monitoring indicator involved in the monitoring strategy for the external jump behavior of the first SDK.

[0091] Combine Figure 6 In the illustrated embodiment, in certain optional embodiments, the apparatus further comprises: a result obtaining unit and a strategy adjusting unit;

[0092] a result obtaining unit, configured to obtain a monitoring result of monitoring the external jump behavior of the first SDK after the monitoring logic is called to monitor the external jump behavior of the first SDK;

[0093] A strategy adjustment unit is used to adjust the monitoring indicators involved in the monitoring strategy according to the monitoring results.

[0094] In combination with the previous embodiment, in some optional embodiments, the device further includes: a management and control unit;

[0095] The management and control unit is used to perform corresponding management and control on the external jump behavior of the first SDK according to the monitoring result after obtaining the monitoring result of monitoring the external jump behavior of the first SDK.

[0096] Optionally, in certain optional embodiments, the apparatus further comprises: a query unit;

[0097] a query unit, configured to query a log file after obtaining a monitoring result of monitoring the external jump behavior of the first SDK, thereby obtaining context information corresponding to the external jump behavior of the first SDK;

[0098] The policy adjustment unit includes: a policy adjustment subunit;

[0099] The strategy adjustment subunit is used to adjust the monitoring indicators involved in the monitoring strategy according to the monitoring results and the context information, thereby updating the monitoring strategy.

[0100] The present invention provides a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements any of the above-mentioned methods for monitoring external jumps of an app.

[0101] like Figure 7 As shown, the present invention provides an electronic device 70, which includes at least one processor 701, and at least one memory 702 and a bus 703 connected to the processor 701; wherein the processor 701 and the memory 702 communicate with each other through the bus 703; the processor 701 is used to call the program instructions in the memory 702 to execute any of the above-mentioned app external jump monitoring methods.

[0102] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus comprising the element.

[0103] Each embodiment in this specification is described in a related manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiment is generally similar to the method embodiment, so the description is relatively simple. For related parts, refer to the description of the method embodiment.

[0104] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

[0105] The above description is only a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention are included in the scope of protection of the present invention.

Claims

1. A method for monitoring external jumps of an app, characterized in that: include: Obtain a monitoring strategy for a first SDK, wherein the first SDK is a software development kit pre-connected to an app platform, and the software development kit pre-connected to the app platform pre-establishes at least one set of monitoring strategies, wherein the monitoring strategy involves monitoring indicators at different levels, and the levels include: a module layer involving jump behavior, a functional class layer involving jump behavior, a method layer involving jump behavior, and a parameter layer involving jump behavior, and each level corresponds to one monitoring indicator; the monitoring strategy is used to reflect an atomic combination configuration for monitoring external jump behavior, and different atomic combination configurations require turning on the corresponding monitoring logic switch to monitor different indicators at different layers; and different operating systems are provided with corresponding monitoring logic; According to each of the monitoring indicators involved in the monitoring strategy, turning on a switch of a corresponding pre-established monitoring logic, wherein one monitoring logic corresponds to multiple monitoring indicators; The monitoring logic is called to monitor the external jump behavior of the first SDK.

2. The method according to claim 1, characterized in that The calling of the monitoring logic to monitor the external jump behavior of the first SDK includes: The monitoring logic is called to monitor the data of each monitoring indicator involved in the monitoring strategy for the external jump behavior of the first SDK.

3. The method according to claim 1, characterized in that After calling the monitoring logic to monitor the external jump behavior of the first SDK, the method further includes: Obtaining monitoring results of the external jump behavior of the first SDK; The monitoring indicators involved in the monitoring strategy are adjusted according to the monitoring results.

4. The method according to claim 3, characterized in that After obtaining the monitoring result of monitoring the external jump behavior of the first SDK, the method further includes: Based on the monitoring results, the external jump behavior of the first SDK is controlled accordingly.

5. The method according to claim 3, characterized in that After obtaining the monitoring result of monitoring the external jump behavior of the first SDK, the method further includes: Query the log file to obtain context information corresponding to the external jump behavior of the first SDK; The adjusting the monitoring indicators involved in the monitoring strategy according to the monitoring results includes: The monitoring indicators involved in the monitoring strategy are adjusted according to the monitoring results and the context information, thereby updating the monitoring strategy.

6. An app external jump monitoring device, characterized in that: include: policy acquisition unit, switch opening unit, and monitoring unit; The policy acquisition unit is used to obtain a monitoring policy for a first SDK, wherein the first SDK is a software development kit pre-connected to an app platform, and the software development kit pre-connected to the app platform pre-establishes at least one set of monitoring policies, and the monitoring policies involve monitoring indicators at different levels, and the levels include: a module layer involving jump behavior, a functional class layer involving jump behavior, a method layer involving jump behavior, and a parameter layer involving jump behavior, and each level corresponds to one monitoring indicator; the monitoring policy is used to reflect an atomic combination configuration for monitoring external jump behavior, and different atomic combination configurations require turning on the corresponding monitoring logic switch to monitor different indicators at different layers; different operating systems are provided with corresponding monitoring logic; The switch opening unit is configured to open the switch of the corresponding pre-established monitoring logic according to each of the monitoring indicators involved in the monitoring strategy, wherein one monitoring logic corresponds to multiple monitoring indicators; The monitoring unit is used to call the monitoring logic to monitor the external jump behavior of the first SDK.

7. A computer-readable storage medium having a program stored thereon, characterized in that: When the program is executed by a processor, the app external jump monitoring method according to any one of claims 1 to 5 is implemented.

8. An electronic device, characterized in that: The electronic device includes at least one processor, and at least one memory and bus connected to the processor; wherein the processor and the memory communicate with each other through the bus; the processor is used to call program instructions in the memory to execute the app external jump monitoring method according to any one of claims 1 to 5.

Images