CN110519126A - A kind of mobile terminal behavior monitoring method - Google Patents
A kind of mobile terminal behavior monitoring method Download PDFInfo
- Publication number
- CN110519126A CN110519126A CN201910886051.1A CN201910886051A CN110519126A CN 110519126 A CN110519126 A CN 110519126A CN 201910886051 A CN201910886051 A CN 201910886051A CN 110519126 A CN110519126 A CN 110519126A
- Authority
- CN
- China
- Prior art keywords
- crash
- mobile terminal
- log
- developer
- sdk
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
- H04L63/1425—Traffic logging, e.g. anomaly detection
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Alarm Systems (AREA)
Abstract
The present invention provides a kind of mobile terminal behavior monitoring method, belongs to mobile terminal behavior monitoring technical field, and the present invention is listened to by the abnormality processing Handler of change system, is then acquired to the Crash thread stacks of generation, then Crash is polymerize.And the Crash of this acquisition is synchronized and stores and reports.Log aggregation is handled and generates backstage log information.By this method the behavior of collapse case and user can be used with effective monitoring app.
Description
Technical field
The present invention relates to mobile terminal behavior monitoring technology more particularly to a kind of mobile terminal behavior monitoring methods.
Background technique
App is generally divided into personal user app and enterprise-level app.Individual with the family APP app be towards individual consumer, and
Enterprise-level app is developed towards enterprise customer.When internet enters mobile internet era, numerous enterprises and personal development
Person wishes therefrom Denver Nuggets, but the sight of majority has focused on the enterprise-level movement that has ignored using upper towards personal user and answered
With.
Nowadays the competition in personal market has been reached the decisive stage the stage, and development speed has tended to slowly, projected market in 2013
Scale is 110.9 hundred million.In contrast, enterprise market at this time is just started to walk, and projected market scale will be up within 2013
124.4 hundred million, and just with 50% amplification high speed development.
Under this market environment, third party's service is needed to solve the problems, such as enterprise and developer both sides, plays two-way need
The effectiveness for asking convergence, marketing distribution, improved efficiency, cost to reduce, and corresponding service can be provided for both sides.It is using factory
Such a role is acted as, polymerize upstream and downstream resource and becomes domestic first enterprise-level mobile application one-stop service platform.
After mobile terminal app is online, developer is difficult to reappear when app collapses, and user feedback is different
It is fixed to be consistent with what developer understood, it cannot be repaired in time so as to cause problem, expend a large amount of manpower and material resources.You Meng, it rises
There is also the SDK of open source to carry out collapse monitoring by news bugly etc., but has the following problems in open source SDK:
1, some information or datas may will be leaked
2, data generate harm for interests there may be being tampered
3, the certain demands of project may not be able to be met
4, it can not effectively be statisticallyd analyze
5, it can not effectively position and reappear problem.
Summary of the invention
In order to solve the above technical problems, the invention proposes a kind of convenience, the mobile terminal behavior monitoring method of safety, it can
The behavior of collapse case and user are used with effective monitoring app.
The technical scheme is that
A kind of mobile terminal behavior monitoring method,
Abnormality processing Handler by changing system is listened to, and is then adopted to the Crash thread stacks of generation
Collection, then Crash is polymerize, and is synchronized to the Crash of this acquisition and stored and report, to log aggregation processing
And generate backstage log information.
Mainly include 3 steps:
(1) monitoring SDK encapsulation
(2) SDK is called to be disposed
(3) monitored results solve follow-up.
Further,
The monitoring SDK encapsulation
Abnormality processing Handler by changing system is listened to, and is then adopted to the Crash thread stacks of generation
Collection carries out duplicate removal, truncation finally by Crash of the algorithm to acquisition.
Further,
This Crash acquired is synchronized using local data base simultaneously and stores and reports, can not reported such as
Function is then opened asynchronous thread after next App starting and is reported, reports and successfully delete database purchase afterwards.
Further,
Offset is analyzed and calculated to the Crash destination address collapsed by algorithm, analysis data are polymerize
And generate backstage log information.
Further,
The calling SDK is disposed
First in platform application account, and it is called the API of needs in mobile terminal, developer's login account is in platform
The alarm strategy of Crash is set.
Further,
Exception level and alarm strategy can be set in Crash, according to number of users, influence user's ratio is influenced, to sentence
Disconnected alarm of whether setting out, while developer and administrative staff can be sent to by enterprise's mailbox and wechat enterprise.
Further,
The tactful threshold values of the alarm is arranged 1.5 or so.
Further,
The monitored results solve follow-up
The information that developer is provided by Crash log restores scene of the accident orientation problem, and closing after having handled should
Crash log;The summary self-examination for carrying out weekly, monthly magazine interim simultaneously.
The beneficial effects of the invention are as follows
1) it can customize alarm strategy, better meet the demand of developer;
2) accident reduction can help developer's orientation problem;
3) the contradiction value that server resource and log recycle is reduced to minimum by polymerization log;
4) simulation reproduction problem can be made by oneself, developer is not required to and goes to test.
Detailed description of the invention
Fig. 1 is Crash capture flow diagram of the invention.
Specific embodiment
In order to make the object, technical scheme and advantages of the embodiment of the invention clearer, below in conjunction with the embodiment of the present invention
In attached drawing, technical scheme in the embodiment of the invention is clearly and completely described, it is clear that described embodiment is
A part of the embodiment of the present invention, instead of all the embodiments, based on the embodiments of the present invention, those of ordinary skill in the art
Every other embodiment obtained without making creative work, shall fall within the protection scope of the present invention.
The present invention monitors existing main problem for mobile terminal log, provides the log monitoring side an of convenience, safety
Method preferably carries out log monitoring and statistical analysis.
Its technology realizes that process is as follows:
(1) monitoring SDK encapsulation
Abnormality processing Handler by changing system is listened to, and is then adopted to the Crash thread stacks of generation
Then collection carries out duplicate removal, truncation by Crash of certain algorithm to acquisition.
And this Crash acquired is synchronized using local data base simultaneously and stores and reports, it such as reports not
Success is then opened asynchronous thread after next App starting and is reported, reports and successfully delete database purchase afterwards.
Offset is analyzed and is calculated to the Crash destination address collapsed by certain algorithm, to a large amount of analysis numbers
According to being polymerize and generate backstage log information.
(2) SDK is called to be disposed
First in platform application account, and it is called the API of needs in mobile terminal, developer's login account is in platform
The alarm strategy of Crash is set.
Exception level and alarm strategy can be set in Crash, joins according to number of users, influence user's ratio etc. is influenced
Number, to determine whether alarm of setting out (tactful threshold values of usually alarming is arranged 1.5 or so), while enterprise's mailbox and enterprise can be passed through
Industry wechat is sent to developer and administrative staff.
(3) monitored results solve follow-up
The information that developer is provided by Crash log restores scene of the accident orientation problem, and closing after having handled should
Crash log.The summary self-examination for carrying out weekly, monthly magazine interim simultaneously.
The foregoing is merely presently preferred embodiments of the present invention, is only used to illustrate the technical scheme of the present invention, and is not intended to limit
Determine protection scope of the present invention.Any modification, equivalent substitution, improvement and etc. done all within the spirits and principles of the present invention,
It is included within the scope of protection of the present invention.
Claims (9)
1. a kind of mobile terminal behavior monitoring method, which is characterized in that
Abnormality processing Handler by changing system is listened to, and is then acquired to the Crash thread stacks of generation,
Then Crash is polymerize, and is synchronized to the Crash of this acquisition and stored and report, simultaneously to log aggregation processing
Generate backstage log information.
2. the method according to claim 1, wherein
Including 3 steps:
(1) monitoring SDK encapsulation
(2) SDK is called to be disposed
(3) monitored results solve follow-up.
3. according to the method described in claim 2, it is characterized in that,
The monitoring SDK encapsulation
Abnormality processing Handler by changing system is listened to, and is then acquired to the Crash thread stacks of generation,
Duplicate removal, truncation are carried out finally by Crash of the algorithm to acquisition.
4. according to the method described in claim 3, it is characterized in that,
Simultaneously using local data base to this Crash acquire synchronize storage and report, such as report it is unsuccessful, then
Asynchronous thread is opened after next App starting to be reported, and is reported and is successfully deleted database purchase afterwards.
5. according to the method described in claim 4, it is characterized in that,
Offset is analyzed and calculated to the Crash destination address collapsed by algorithm, analysis data are polymerize and given birth to
At backstage log information.
6. the method according to claim 1, wherein
The calling SDK is disposed
First in platform application account, and it is called the API of needs in mobile terminal, developer's login account is arranged in platform
The alarm strategy of Crash.
7. according to the method described in claim 6, it is characterized in that,
Exception level and alarm strategy can be set in Crash, according to number of users, influence user's ratio is influenced, to judge to be
No alarm of setting out, while developer and administrative staff can be sent to by enterprise's mailbox and wechat enterprise.
8. the method according to the description of claim 7 is characterized in that
The tactful threshold values of the alarm is arranged 1.5 or so.
9. the method according to the description of claim 7 is characterized in that
The monitored results solve follow-up
The information that developer is provided by Crash log restores scene of the accident orientation problem, the Crash is closed after having handled
Log;The summary self-examination for carrying out weekly, monthly magazine interim simultaneously.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910886051.1A CN110519126A (en) | 2019-09-19 | 2019-09-19 | A kind of mobile terminal behavior monitoring method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910886051.1A CN110519126A (en) | 2019-09-19 | 2019-09-19 | A kind of mobile terminal behavior monitoring method |
Publications (1)
Publication Number | Publication Date |
---|---|
CN110519126A true CN110519126A (en) | 2019-11-29 |
Family
ID=68631446
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201910886051.1A Pending CN110519126A (en) | 2019-09-19 | 2019-09-19 | A kind of mobile terminal behavior monitoring method |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110519126A (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107168773A (en) * | 2017-06-12 | 2017-09-15 | 郑州云海信息技术有限公司 | Positioning problems and the processing method and processing device of application recovery after a kind of JVM collapses |
CN107491383A (en) * | 2017-08-17 | 2017-12-19 | 杭州师范大学 | Catching method, device and the mobile terminal of application crashes Operation Log |
US20180322016A1 (en) * | 2017-05-05 | 2018-11-08 | Dell Products L.P. | System and method to capture stored data following system crash |
CN109634838A (en) * | 2018-10-25 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Position method, apparatus, storage medium and the electronic equipment of application failure |
CN110048888A (en) * | 2019-04-16 | 2019-07-23 | 深圳市致宸信息科技有限公司 | A kind of method based on zabbix monitoring alarm, server, equipment and storage medium |
-
2019
- 2019-09-19 CN CN201910886051.1A patent/CN110519126A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180322016A1 (en) * | 2017-05-05 | 2018-11-08 | Dell Products L.P. | System and method to capture stored data following system crash |
CN107168773A (en) * | 2017-06-12 | 2017-09-15 | 郑州云海信息技术有限公司 | Positioning problems and the processing method and processing device of application recovery after a kind of JVM collapses |
CN107491383A (en) * | 2017-08-17 | 2017-12-19 | 杭州师范大学 | Catching method, device and the mobile terminal of application crashes Operation Log |
CN109634838A (en) * | 2018-10-25 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Position method, apparatus, storage medium and the electronic equipment of application failure |
CN110048888A (en) * | 2019-04-16 | 2019-07-23 | 深圳市致宸信息科技有限公司 | A kind of method based on zabbix monitoring alarm, server, equipment and storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015074540A1 (en) | Method and apparatus for processing page operation data | |
CN103246735B (en) | A kind of method for processing abnormal data and system | |
US20170061248A1 (en) | System and Method of Detecting Offensive Content Sent or Received on a Portable Electronic Device | |
Li et al. | Generic and robust localization of multi-dimensional root causes | |
CN110413488B (en) | Server utilization rate early warning method and device | |
CA2873834A1 (en) | System and method for creating structured event objects | |
CN105812554A (en) | Method and system for intelligently managing text messages in mobile phones | |
CN106231074A (en) | A kind of method and device of Message Processing | |
CN107146012A (en) | Risk case processing method and system | |
CN105022815A (en) | Information interception method and device | |
CN110705926A (en) | Method, device and system for acquiring logistics object distribution information | |
CN111865673A (en) | Automatic fault management method, device and system | |
CN113961465A (en) | Method, device and program product for processing reproduction of program crash scene | |
CN108572949A (en) | A kind of houseclearing search processing method and device | |
CN110519126A (en) | A kind of mobile terminal behavior monitoring method | |
CN105897498A (en) | Business monitoring method and device | |
CN108335236A (en) | A kind of source of houses leakage broker's detection method and device | |
CN110516066B (en) | Text content safety protection method and device | |
CN109039695B (en) | Service fault processing method, device and equipment | |
CN112035287B (en) | Method, device, storage medium and equipment for testing data cleaning result | |
CN112446619B (en) | Power distribution network rush-repair processing method and device | |
CN106789271B (en) | Fault reporting processing method and system | |
CN106649343B (en) | Network data information processing method and equipment | |
CN111178943B (en) | Advertisement real-time bidding method and device and electronic equipment | |
CN113010339A (en) | Method and device for automatically processing fault in online transaction test |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191129 |
|
RJ01 | Rejection of invention patent application after publication |