Mobile terminal APM loose coupling architecture method

Abstract

The invention discloses a mobile terminal APM loose coupling architecture method. The method comprises the following steps: step 1, obtaining monitoring data; step 2, pre-filtering the monitoring data through a pre-storage filter; step 3, storing the pre-filtered data into a database, and acquiring information from an apm-persistent module into the database; step 4, performing post-filtering on the data acquired from the data; and step 5, uploading the post-filtered data through an uploading manager.

Description

Technical Field

[0001] The present invention relates to the field of application performance indicator management and monitoring of mobile terminals, and in particular to a loosely coupled architecture method of APM for mobile terminals. Background Art

[0002] APM (Application Performance Management) is an application performance monitoring tool that aggregates real-time data from various processing links of the business system, analyzes the transaction path and processing time of each transaction in the business system, and achieves full-link performance monitoring of the application. The common mobile APM systems on the market cannot fully cover all mobile platforms and all monitoring indicators. They are tightly coupled in architecture; for example, if my mobile project uses APM product A for crash monitoring, then network monitoring, memory monitoring, and freeze monitoring must also use APM product A, and not APM product B. Summary of the invention

[0003] In response to the above problems and the shortcomings of existing solutions, this patent proposes a new loosely coupled architecture design to achieve the following goals: covering all mobile platforms and all monitoring indicators; mobile products can only use our APM products and monitor only one performance indicator, or they can monitor multiple indicators; the monitoring modules of each performance indicator can work independently or be combined at will without interfering with each other. Figure 1-2 Shows decoupled architectural evolution. Figure 1 In the middle, the coupling degree is high. When users use Uploader, Http, and Lifecycle modules, the Persistent module will be introduced. The customization degree is low. Users can only use the storage service and uploader provided by the XyyApm library. Figure 2 The acquisition module no longer depends on the Persistent module, reducing the coupling degree; the collected data can be processed by itself or using the built-in PersistentObserver+Uploader, and the flexibility is enhanced. Therefore, the present invention proposes a mobile terminal APM loose coupling architecture method, including the following steps: Step 1: Obtain monitoring data; Step 2, pre-filtering the monitoring data through a pre-storage filter; Step 3, storing the pre-filtered data into a database and acquiring information from the apm-persistent module into the database; Step 4, post-filtering the data obtained from the data; Step 5: The post-filtered data is uploaded through the upload manager. Preferably, the upload manager includes a working upload manager and a real-time upload manager. Preferably, the pre-storage filter also filters the information from ApmOkHttpPersistentCollector and ApmLifecyclePersistentCollector. Preferably, the monitoring data acquired in step 1 includes apm-okhttp and apm-lifecycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 The coupling of APM in the prior art is shown; Figure 2 An embodiment of decoupling of an APM is shown; Figure 3 The preferred embodiment of the mobile terminal APM loosely coupled architecture method of the present invention is shown; DETAILED DESCRIPTION

[0005] like Figure 2 As shown, a mobile APM loosely coupled architecture method includes the following steps: Step 1: Obtain monitoring data; Step 2, pre-filtering the monitoring data through a pre-storage filter; Step 3, storing the pre-filtered data into a database and acquiring information from the apm-persistent module into the database; Step 4, post-filtering the data obtained from the data; Step 5: The post-filtered data is uploaded through the upload manager. Preferably, the upload manager includes a working upload manager and a real-time upload manager. Preferably, the pre-storage filter also filters the information from ApmOkHttpPersistentCollector and ApmLifecyclePersistentCollector. Preferably, the monitoring data acquired in step 1 includes apm-okhttp and apm-lifecycle. Therefore, those skilled in the art can understand that through the present invention, the monitoring components such as Crash, Freeze, Startup, Network, Memory, etc. have their own independent collection, analysis, filtering and reporting modules without interfering with each other; through pre- and post-filters, useless monitoring information is greatly reduced; different monitoring components can customize their own filtering rules. It can be seen that the present invention provides a one-stop APM system, covering all mobile platforms and all monitoring indicators. Zero intrusion to business projects. Adopting a loose coupling approach and minimizing module granularity, the business end can select any module for integration as needed, reducing the integration cost of business projects. Through flexibly customizable pre- and post-filters, the reporting traffic of mobile devices is reduced by 80%; the concurrency performance of the APM server is improved by more than 80%. The preferred embodiments of the present invention are exemplarily introduced above with the aid of the accompanying drawings. Those skilled in the art should know that within the protection scope defined by the claims of the present invention, different technical solutions can be formed by adding, deleting and combining technical features.

Claims

1. A mobile terminal APM loosely coupled architecture method, characterized in that: The steps include: Step 1: Obtain monitoring data; Step 2, pre-filtering the monitoring data through a pre-storage filter; Step 3, storing the pre-filtered data into a database and acquiring information from the apm-persistent module into the database; Step 4, post-filtering the data obtained from the data; Step 5: The post-filtered data is uploaded through the upload manager.

2. The mobile terminal APM loosely coupled architecture method according to claim 1, characterized in that: The upload manager includes a working upload manager and a real-time upload manager.

3. The mobile terminal APM loosely coupled architecture method according to claim 2, characterized in that: The pre-storage filter also filters the information from ApmOkHttpPersistentCollector and ApmLifecyclePersistentCollector.

4. The mobile terminal APM loosely coupled architecture method according to claim 3, characterized in that: The monitoring data obtained in step 1 includes apm-okhttp and apm-lifecycle.

Images