CN112306871A - Data processing method, device, equipment and storage medium - Google Patents

Data processing method, device, equipment and storage medium Download PDF

Info

Publication number
CN112306871A
CN112306871A CN202011183075.XA CN202011183075A CN112306871A CN 112306871 A CN112306871 A CN 112306871A CN 202011183075 A CN202011183075 A CN 202011183075A CN 112306871 A CN112306871 A CN 112306871A
Authority
CN
China
Prior art keywords
type
file
program
target application
application program
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
Application number
CN202011183075.XA
Other languages
Chinese (zh)
Inventor
李成会
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Boguan Information Technology Co Ltd
Original Assignee
Guangzhou Boguan Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangzhou Boguan Information Technology Co Ltd filed Critical Guangzhou Boguan Information Technology Co Ltd
Priority to CN202011183075.XA priority Critical patent/CN112306871A/en
Publication of CN112306871A publication Critical patent/CN112306871A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3604Software analysis for verifying properties of programs
    • G06F11/3608Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/362Software debugging
    • G06F11/366Software debugging using diagnostics

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application provides a data processing method, a device, equipment and a storage medium, wherein the abnormality of a target application program is determined; acquiring identification information corresponding to a target application program; determining the file type according to the identification information, wherein the file type is a full type or a partial type; and generating a program exception file corresponding to the target application program according to the file type. Because the file type corresponding to the target application program is determined according to the identification information of the target application program, and the program exception file of the full type or the partial type is generated according to the file type, the full dump of the target application program with the requirement is realized, and the small dump of the target application program without the requirement is realized, thereby not only improving the effectiveness and the accuracy of the program exception capture and analysis, but also avoiding the waste of storage resources and network resources caused by the full dump, improving the efficiency of the program exception capture and analysis, and improving the quality and the stability of a program product.

Description

Data processing method, device, equipment and storage medium
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a data processing method, a data processing device, data processing equipment and a storage medium.
Background
During the running process of a software program, the program often crashes due to various uncertain reasons. The crash capturing and reporting analysis are functions which are necessary for complete software, and particularly for commercialized software, the crash condition after the program is abnormal is captured and analyzed, and corresponding debugging and upgrading are carried out, so that the product quality and stability can be obviously improved, and the user satisfaction is improved.
At present, general commercialized software has a program crash capture function, for example, by capturing program crash information, saving the program crash information as a mini dump file, and uploading the mini dump file to a server, a developer analyzes the mini dump file uploaded to the server, so as to improve and reduce the occurrence of program crash.
However, in the above scheme, although the mini dump file can save the storage space and the transmission bandwidth, since the mini dump file only retains a small part of the key information, the analysis work after the program crash, which can be completed only by using the full amount of the storage file, cannot be realized in many scenarios, which results in the effect of affecting the program crash capture function and reduces the quality and stability of the program product.
Disclosure of Invention
Embodiments of the present application provide a data processing method, apparatus, device, and storage medium, so as to solve the problems of poor effect of a program crash capture function and reduction in quality and stability of a program product.
According to a first aspect of an embodiment of the present application, there is provided a data processing method applied to a terminal device, including:
determining that the target application program is abnormal; acquiring identification information corresponding to the target application program; determining a file type according to the identification information, wherein the file type is a full type or a partial type; and generating a program exception file corresponding to the target application program according to the file type.
In a possible implementation manner, determining a file type according to the identification information includes: acquiring an identification list, wherein the identification list comprises identification information corresponding to a full-size type file; and determining the file type according to the identification list and the identification information.
In one possible implementation, the identification information includes at least one of: user identification, equipment identification and type identification; the user identification is used for representing an identification corresponding to a user logging in the target application program; the device identifier is used for representing an identifier corresponding to the terminal device; the type identifier is used for indicating an identifier corresponding to the equipment type of the terminal equipment;
in a possible implementation manner, determining the file type according to the identifier list and the identifier information includes: judging whether the identification list comprises the identification information or not; if so, determining the file type to be a full type; if not, determining that the file type is a partial type.
In a possible implementation manner, generating a program exception file corresponding to the target application program according to the file type includes: if the file type is a full type, generating the program exception file according to all exception information when the target application program is abnormal; and if the file type is a partial type, generating the program exception file according to partial exception information when the target application program is abnormal.
In one possible implementation, the method further includes: generating abnormal alarm information; and sending the abnormal alarm information to a server.
In one possible implementation, the method further includes: if the file type is a partial type, the program exception file is sent to a server; and if the file type is a full type, storing the program exception file, and sending notification information to preset equipment, wherein the notification information is used for indicating the terminal equipment to store the program exception file.
According to a second aspect of the embodiments of the present application, there is provided a data processing method applied to a server, including:
receiving abnormal alarm information of a target application program sent by terminal equipment, wherein the abnormal alarm information comprises identification information corresponding to the target application program; acquiring an identification list, wherein the identification list comprises a plurality of identification information; and if the identification list comprises identification information corresponding to the target application program, sending a notification message to a preset device, wherein the notification message is used for indicating that the target application program is abnormal.
In a possible implementation manner, the identification information includes at least one of the following: user identification, equipment identification and type identification; the user identification is used for representing an identification corresponding to a user logging in the target application program; the device identifier is used for representing an identifier corresponding to the terminal device; the type identifier is used for indicating an identifier corresponding to the device type of the terminal device.
According to a third aspect of the embodiments of the present application, there is provided a data processing apparatus, applied to a terminal device, including:
the exception determining module is used for determining the exception of the target application program;
the information acquisition module is used for acquiring identification information corresponding to the target application;
the type determining module is used for determining the file type according to the identification information, wherein the file type is a full type or a partial type;
and the file generation module is used for generating a program exception file corresponding to the target application program according to the file type.
In a possible implementation manner, the type determining module is specifically configured to: acquiring an identification list, wherein the identification list comprises identification information corresponding to a full-size type file; and determining the file type according to the identification list and the identification information.
In a possible implementation manner, the identification information includes a user identification, and/or a device identification, and/or a type identification; the user identification is used for representing an identification corresponding to a user logging in the target application program; the device identifier is used for representing an identifier corresponding to the terminal device; the type identifier is used for indicating an identifier corresponding to the equipment type of the terminal equipment; the type determining module, when determining the file type according to the identifier list and the identifier information, is specifically configured to: judging whether the user identifier, the equipment identifier and/or the type identifier are included in the identifier list; if so, determining the file type to be a full type; if not, determining that the file type is a partial type.
In a possible implementation manner, the file generating module is specifically configured to: if the file type is a full type, generating the program exception file according to all exception information when the target application program is abnormal; and if the file type is a partial type, generating the program exception file according to partial exception information when the target application program is abnormal.
In a possible implementation manner, the data processing apparatus further includes an alarm module, configured to: generating abnormal alarm information; and sending the abnormal alarm information to a server.
In a possible implementation manner, the data processing apparatus further includes a sending module, configured to: if the file type is a partial type, the program exception file is sent to a server; and if the file type is a full type, storing the program exception file, and sending notification information to preset equipment, wherein the notification information is used for indicating the terminal equipment to store the program exception file.
According to a fourth aspect of the embodiments of the present application, there is provided a data processing apparatus, applied to a server, including:
the alarm receiving module is used for receiving abnormal alarm information of a target application program, which is sent by terminal equipment, wherein the abnormal alarm information comprises identification information corresponding to the target application program;
an identifier obtaining module, configured to obtain an identifier list, where the identifier list includes a plurality of pieces of identifier information;
and a notification sending module, configured to send a notification message to a preset device if the identifier list includes identifier information corresponding to the target application program, where the notification message is used to indicate that the target application program is abnormal.
In a possible implementation manner, the identification information includes: a user identification, and/or a device identification, and/or a type identification; the user identification is used for representing an identification corresponding to a user logging in the target application program; the device identifier is used for representing an identifier corresponding to the terminal device; the type identifier is used for indicating an identifier corresponding to the device type of the terminal device.
According to a fifth aspect of embodiments of the present application, there is provided a terminal device, including: a memory, a processor, and a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the data processing method as provided by the first aspect of the embodiments of the present application.
According to a sixth aspect of embodiments of the present application, there is provided a server, including: a memory, a processor, and a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the data processing method as provided by the second aspect of the embodiments of the present application.
According to a seventh aspect of embodiments of the present application, there is provided a computer-readable storage medium having stored therein computer-executable instructions, which when executed by a processor, are configured to implement a data processing method as provided in the first or second aspect of embodiments of the present application.
According to the data processing method, the data processing device, the data processing equipment and the data processing storage medium, the abnormality of the target application program is determined; acquiring identification information corresponding to the target application program; determining a file type according to the identification information, wherein the file type is a full type or a partial type; and generating a program exception file corresponding to the target application program according to the file type. The file type corresponding to the target application program is determined according to the identification information of the target application program, and the program exception file of the full type or the partial type is generated according to the file type, so that the full dump of the target application program with the requirement is realized, and the small dump of the target application program without the requirement is realized, thereby meeting the requirements of exception capture and analysis of the target application program, improving the effectiveness and the accuracy of the exception capture and analysis of the program, avoiding the waste of storage resources and network resources caused by the full dump, improving the efficiency of the exception capture and analysis of the program, and improving the quality and the stability of a program product.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic view of an application scenario of a data processing method according to an embodiment of the present application;
FIG. 2 is a flow chart of a data processing method according to an embodiment of the present application;
FIG. 3 is a flow chart of a data processing method according to another embodiment of the present application;
FIG. 4 is a flow chart of a data processing method provided by an embodiment of the present application;
fig. 5 is a signaling interaction flowchart corresponding to a data processing method according to an embodiment of the present application;
FIG. 6 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a data processing apparatus according to another embodiment of the present application;
FIG. 8 is a block diagram of a data processing apparatus according to an embodiment of the present application;
fig. 9 is a schematic block diagram of a terminal device according to an embodiment of the present application;
fig. 10 is a schematic block diagram of a server provided in one embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For ease of understanding, first, the concepts related to the present application will be explained.
1) The full dump, i.e., FullDump, is an operation of storing all relevant files containing program information that ends due to an Unhandled exception (Unhandled exception), and a file having a large volume is usually generated after the full dump.
2) The mini dump, MiniDump, is an operation for storing program information including an end due to an unprocessed exception, and generates a mini dump file including partial exception information such as memory information and stack information when the program ends.
3) "plurality" means two or more, and other terms are analogous. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
4) "correspond" may refer to an association or binding relationship, and a corresponds to B refers to an association or binding relationship between a and B.
Fig. 1 is a schematic view of an application scenario of a data processing method according to an embodiment of the present application, as shown in fig. 1, in a related art, after an exception capture process of a software program, generally, a client program in a terminal device runs, an exception capture Hook (Hook) is installed, and when an exception occurs in the software program, program information generated by an unexpected end of the program is stored as a program exception file and is uploaded to a server synchronously or asynchronously. The server side analyzes the program abnormal file at intervals through a task running at regular time to obtain a summary report for a software program developer to analyze, so as to try to locate the abnormal reason of the software program and repair the software.
However, in the above related art, the program exception file is usually a mini dump file, and although the mini dump file can save storage space and transmission bandwidth, since the mini dump file only retains a small part of key information when the software program ends abnormally, the information amount is small, and for many scenarios, the analysis work after the program exception, which can be completed by using a full amount of storage files, cannot be implemented, so that a developer cannot accurately locate the reason for the abnormality of the software program according to the mini dump file. The effect of the abnormal capturing function of the program is influenced, and the quality and the stability of the program product are reduced.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of a data processing method according to an embodiment of the present application, where the method is applied to a terminal device, more specifically, a personal computer or a smart phone, for example. As shown in fig. 2, the method comprises the following steps:
step S101, determining that the target application program is abnormal.
The target application may be, for example, a software program, an operating system, a service, or another form of application that runs on the terminal device, and after the target application is started, the target application may run continuously on the terminal device, or may be triggered to run under a specific instruction or condition, so as to implement a function corresponding to the target application. Here, the type, content, and other implementation manners of the target application are not particularly limited.
When the target application program continuously runs or runs in a triggering mode, unexpected ending, namely program exception or program crash, can be triggered under specific conditions or unknown conditions. When the target application program is abnormal, the terminal device may obtain information that the target application program is abnormal through, for example, an operating system, so as to determine that the target application program is abnormal.
Further, there are various ways to determine the abnormality of the target application, for example, capturing the failure information of memory allocation failure or the failure information of illegal operation by the operating system in the terminal device, which is not illustrated here.
Step S102, obtaining identification information corresponding to the target application program.
Illustratively, the identification information of the target application is information for locating the target application, and the identification information is, for example, a user identification for logging in the target application, a device identification of the terminal device, a type identification of the terminal device, and the like. The target application program can be positioned through the identification information of the target application program, and then the subsequent collection, analysis and processing of the abnormal information of the target application program are realized.
The user identifier may be, for example, a user name, a user ID, a user phone number, a user mailbox, or other unique identification information, and according to the user identifier, the user information of the login target application program may be confirmed. The device identifier of the terminal device may be, for example, unique identifier information such as a MAC address, an IP address, and a device identifier of the terminal device. The type identifier of the terminal device is, for example, a model of the terminal device, or identification information of a model and a category of a specific device unit in the terminal device.
Further, the identification information may include at least one of a user identifier, a device identifier, and a type identifier, and a specific implementation manner of the identification information may be set according to a specific need, which is not limited herein.
And step S103, determining the file type according to the identification information, wherein the file type is a full type or a partial type.
Illustratively, the file type refers to a type of a record file generated when an exception occurs to a program, and the type of the record file includes a full type or a partial type, where the full type of the record file is a full dump file, and the partial type of the record file is a mini dump file.
The identification information includes data representing user information and/or device information, and the difference of the user information and/or the device information is a main cause of the program exception.
For example, in a scenario where the software program is live software, user a is the anchor, and user B, user C, user D, and the like are all viewers. In the actual operation process of the live broadcast software, because the user a is the anchor and needs to interact with numerous audiences such as the user B, the user C, the user D and the like at the same time, the interaction logic involved in the process and the allocation strategy of the memory and the network bandwidth are more complex compared with the live broadcast software used by common users such as the user B, the user C, the user D and the like, and therefore the problems of program abnormity, abnormity and the like are more easily caused. In this case, in order to solve the problem of program abnormality of live broadcast software used by the user a as the anchor, it is possible to collect as much abnormality information as possible, that is, to determine that the file type is the full type. The success rate and the efficiency of problem location of program abnormity are improved. For live broadcast software used by a user B, a user C, a user D and the like, because the probability of program abnormity is low, only part of key information when the program is abnormal can be collected, namely the file type can be determined to be a part of type, so that the storage space and the bandwidth resource are saved.
Similarly, for example, in a scenario where the software program is live broadcast software, when configuration information, such as a memory, a CPU, a hard disk, or network conditions, of a terminal device running the live broadcast software are different, program exceptions of different reasons may be generated, for example, program exceptions caused by compatibility problems of the terminal device, program exceptions caused by a current limiting policy of a network operator, and the like. In this case, for terminal devices which are prone to program abnormality, more corresponding device information is collected, and success rate and efficiency of problem location for program abnormality can be improved. For the device which is not easy to be abnormal, only partial key information when the program is abnormal can be collected, that is, the file type can be determined to be partial type, so as to save storage space and bandwidth resources. Furthermore, the type identifier, such as the type of the display card in the terminal device, may cause the occurrence frequency and severity of the crash to be different due to different types and types of different terminal devices and specific device units in the terminal device, so that the targeted identification and screening may be performed accordingly, the corresponding device information may be collected, and the success rate and efficiency of the abnormal program problem location may be improved.
Of course, it should be noted that the file type may be determined according to any one of the user identifier, the device identifier, and the type information in the identifier information, or may be determined according to the user identifier, the device identifier, and the type identifier in the identifier information, and may be set according to specific needs, which is not limited herein.
And step S104, generating a program exception file corresponding to the target application program according to the file type.
For example, the file type may be implemented by a configuration file, after the configuration file is determined, when a target application program is abnormal, an operating system running in the terminal device may protect the system according to a protection mechanism set inside the operating system, and generate corresponding program abnormal information, which is used to indicate a cause of the program abnormal, such as a memory allocation error, an illegal operation, and the like, and the program abnormal information includes information for recording operating conditions of the memory and the stack. The information can be used for further analyzing the reasons of the program abnormity by a user so as to better locate the reasons of the program abnormity. And solidifying and storing the program exception information containing the content to form a program exception file corresponding to the target application program. Illustratively, the correspondence of the program exception file to the target application program is achieved by setting an identification in the program exception file corresponding to the identification of the target application program.
In the embodiment, the target application program is determined to be abnormal; acquiring identification information corresponding to a target application program; determining the file type according to the identification information, wherein the file type is a full type or a partial type; and generating a program exception file corresponding to the target application program according to the file type. The file type corresponding to the target application program is determined according to the identification information of the target application program, and the program exception file of the full type or the partial type is generated according to the file type, so that the full dump of the target application program with the requirement is realized, and the small dump of the target application program without the requirement is realized, thereby meeting the requirements of exception capture and analysis of the target application program, improving the effectiveness and the accuracy of the exception capture and analysis of the program, avoiding the waste of storage resources and network resources caused by the full dump, improving the efficiency of the exception capture and analysis of the program, and improving the quality and the stability of a program product.
Fig. 3 is a flowchart of a data processing method according to another embodiment of the present application, and as shown in fig. 3, the data processing method according to this embodiment further refines S103 to S104 on the basis of the data processing method according to the embodiment shown in fig. 2, and adds a step of sending an abnormal alarm message to a server, so that the data processing method according to this embodiment includes the following steps:
step S201, determining that the target application program is abnormal.
Step S202, acquiring identification information corresponding to the target application program.
Step S203, an identification list is obtained, and the identification list comprises user identifications and/or equipment identifications corresponding to the full-size type files.
Illustratively, the identifier list is a configuration file preset in the terminal device or downloaded by the terminal device from a server via a network, and the identifier list includes different user identifiers and/or device identifiers corresponding to the full-size type file. Table 1 is an example of an identification list, and as shown in table 1, the identification list may include a user identification alone, a device identification alone, or a combination of the user identification and the device identification. That is, when the user identifier, or the device identifier, or the combination of the user identifier and the device identifier shown in table 1 is included in the identifier list, the user identifier, or the device identifier, or the user identifier and the device identifier in the identifier list correspond to the full-size type file, that is, the identifier list is equivalent to a white list of the full-size type file.
TABLE 1
Numbering Device identification User identification
1 Dev_01
2 #user_01
3 #user_02
4 Dev_02 #user_03
And step S204, determining the file type according to the identification list and the identification information.
Specifically, the identification information includes a user identifier and/or an equipment identifier, and when the user identifier included in the identification information and/or the equipment identifier matches with a certain item of content in the identification list, as shown in table 1, a row corresponding to one number is one item, which indicates that a target application program corresponding to the identification information is in a full-size file white list represented by the identification list, and further, the file type of the target application program can be determined as a full-size type; otherwise, if the device identifier is not matched with any content in the identifier list, it indicates that the target application program corresponding to the identifier information is not in the full-size file white list represented by the identifier list, and at this time, the file type of the target application program may be determined as a partial type.
Specifically, whether the identifier list comprises a user identifier and/or an equipment identifier is judged, and if yes, the file type is determined to be a full type; if not, determining that the file type is a partial type.
Step S205, if the file type is a full type, generating a program abnormal file according to all abnormal information when the target application program is abnormal; and if the file type is a partial type, generating a program exception file according to partial exception information when the target application program is abnormal.
For example, when a program exception occurs, the operating system may generate a large amount of information for recording operation data of the program exception, such as memory usage information, thread execution information, and the like, i.e., exception information. When the file type is a partial type, partial key information in all the abnormal information is stored to generate a small dump file which is small in size and convenient to store and transmit, namely, a program abnormal file is generated by partial abnormal information, so that the system operation efficiency is improved, and system resources are saved. And when the file type is a full type, storing all the abnormal information to generate a full dump file with a larger volume, namely generating a program abnormal file by all the abnormal information. The effectiveness and the accuracy of the subsequent program exception location are improved.
And step S206, generating abnormal alarm information and sending the abnormal alarm information to the server.
When detecting that the program is abnormal, the terminal equipment can send abnormal alarm information to the server in real time. When a program is abnormal, the abnormal end of the program or the stopping of functions and the like are often caused, and the reason for the abnormal program is often a time-sensitive factor, for example, the abnormal condition is more frequent in the noon and noon or afternoon in the evening, and the reason for the abnormal program is caused by network factors, access factors and the like in the time period. In the prior art, information after a program exception occurs is generally periodically uploaded to a server, or the server periodically analyzes the information, so that instantaneity is poor, and after a developer user locates a position where the program exception occurs, due to the timeliness problem, an operating environment where the exception occurs does not exist, so that the exception problem cannot be reproduced, and the problem of program exception and program crash is located and solved.
In the embodiment, when the terminal device detects that the program is abnormal, the abnormal alarm information is sent to the server in real time, and the server can receive the abnormal alarm information at the first time, so that a developer user can timely know the abnormality of the program, and timely analyze and locate the problem in the running environment where the program is abnormal, thereby improving the effectiveness and accuracy of program abnormality capturing and analyzing.
Step S207, sending a program exception file or a notification message to the server.
Specifically, if the file type is a partial type, a program exception file is sent to a server; and if the file type is the full type, storing the program abnormal file, and sending notification information to the preset device, wherein the notification information is used for indicating the terminal device to store the program abnormal file.
Specifically, because the volume of the full dump file corresponding to the full type file is large, if the program abnormal file is uploaded by the server in real time, a large network bandwidth is occupied, and the normal use of the target application program by the user is affected. Therefore, if the file type is the full type, the terminal device stores the program exception file, and sends notification information for indicating the terminal device to store the program exception file to the preset device. The preset device may be a server, or may be other terminal devices and network devices connected to the terminal device. The preset device is not particularly limited herein. After the preset device acquires the notification information, the program exception file may be acquired through other ways, and may be specifically set according to an actual situation, which is not limited herein. And the volume of the small dump file corresponding to part of the type files is small, so that the small dump file can be uploaded in real time without influencing the normal operation of the terminal equipment, and the program abnormal file can be directly sent to the server.
In this embodiment, the implementation manners of step S201 to step S202 are the same as the implementation manners of step S101 to step S102 in the embodiment shown in fig. 2 of this application, and are not described again.
In this embodiment, different processing methods are determined according to the types of the program exception files, and the program exception files are transmitted or stored in real time, so that reasonable utilization of network resources of the terminal device can be achieved.
Fig. 4 is a flowchart of a data processing method according to an embodiment of the present application, where the method is applied to a server, and as shown in fig. 4, the method includes the following steps:
step S301, receiving abnormal alarm information of the target application program sent by the terminal device, wherein the abnormal alarm information comprises identification information corresponding to the target application program.
Illustratively, after receiving the abnormality alarm information of the target application program sent by the terminal device, the server may obtain the information that the program abnormality of the target application program occurs. The abnormality warning information includes at least one of the following information: the method comprises the steps of logging in a user identifier of a target application program, a device identifier of terminal equipment and a type identifier of the terminal equipment, wherein the user identifier of the target application program and the device identifier of the terminal equipment are used for positioning the target application program. That is, the server may determine the target application program according to the user identifier of the login target application program, the device identifier of the terminal device, and the type identifier of the terminal device.
Step S302, an identification list is obtained, where the identification list includes a plurality of identification information.
The identification list includes different user identifications and/or device identifications corresponding to the full-size type files. The list of identifications may comprise a single user identification, or a single device identification, or a combination of user identifications and device identifications. That is, when the program exception file corresponding to the user identifier, the device identifier, or the combination of the user identifier and the device identifier in the identifier list is a full-size file, that is, the identifier list is equivalent to a white list of the full-size file.
Step S303, if the identifier list includes identifier information corresponding to the target application program, sending a notification message to the preset device, where the notification message is used to indicate that the target application program is abnormal.
The volume of the full-volume type program exception file, i.e. the full-volume dump file, is larger, and the obtaining manner is more complicated, so the cost for obtaining the full-volume dump file is higher than that of the partial type program exception file, i.e. the mini dump file. Therefore, when the target application needs to use the full amount of program exception files for analysis, it often means that the target application has more serious or important problems.
The abnormal alarm information of the target application program is compared through the identification list, when the abnormal alarm information of the target application program is matched with the identification list, namely, the program abnormal file of the target application program is dumped in a full amount, at the moment, it is important that the target application program occurs, and the program abnormality needing attention is caused, so that a notification message needs to be sent to the preset device to notify the preset device of the abnormality of the target application program. The preset device may be a server, or other network devices or terminal devices, and the developer user may further process the abnormality occurring in the preset device or the target application program through the abnormality occurring in the preset device, so as to improve the processing timeliness and the processing efficiency of the important program abnormality.
Illustratively, the notification message includes a user identification of the login target application program and/or a device identification of the terminal device. After obtaining the notification message, the preset device may determine a specific user identifier of the target application program and/or a device identifier of the terminal device running the target application program by analyzing the notification message. And furthermore, the information is displayed or generated to a developer user, so that the developer user can timely process the program exception of the target application program.
Fig. 5 is a signaling interaction flowchart corresponding to the data processing method provided in an embodiment of the present application, and as shown in fig. 5, the data processing method provided in the embodiment of the present application includes the following steps:
in step S401, the terminal device determines that the target application is abnormal.
Step S402, the terminal device obtains identification information corresponding to the target application program.
In step S403, the terminal device obtains the identifier list.
And step S404, the terminal equipment determines the file type according to the identification list and the identification information.
Step S405, the terminal device generates a corresponding program exception file according to the file type.
And step S406, the terminal equipment generates abnormal alarm information and sends the abnormal alarm information to the server.
In step S407, the terminal device sends a program exception file or a notification message to the server.
Step S408, the server receives the abnormal alarm information of the target application program sent by the terminal equipment.
In step S409, the server acquires an identifier list.
And step S410, the server sends a notification message to the preset equipment according to the abnormal alarm information and the identification list.
In step S411, the preset device receives the notification message and outputs the notification message.
For example, after receiving the notification message, the preset device may display the notification message through its own display device, or may serve as an intermediate node to forward the notification message to other terminal devices or network devices connected to the preset device, so as to implement transmission of the notification message.
The specific implementation methods of steps S401 to S410 are the same as the implementation methods of corresponding steps in the embodiments corresponding to fig. 3 and fig. 4, and are not described herein again.
Fig. 6 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application, which is applied to a terminal device, and as shown in fig. 6, a data processing apparatus 5 according to this embodiment includes:
and an exception determining module 51, configured to determine that the target application is abnormal.
And an information obtaining module 52, configured to obtain identification information corresponding to the target application.
And a type determining module 53, configured to determine a file type according to the identification information, where the file type is a full type or a partial type.
And the file generating module 54 is configured to generate a program exception file corresponding to the target application program according to the file type.
The abnormality determining module 51, the information acquiring module 52, the type determining module 53, and the file generating module 54 are connected in sequence. The data processing apparatus 5 provided in this embodiment may execute the technical solution of the method embodiment shown in fig. 2, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 7 is a schematic structural diagram of a data processing apparatus according to another embodiment of the present application, and as shown in fig. 7, the data processing apparatus 6 according to this embodiment further includes an alarm module 61 and a sending module 62 on the basis of the data processing apparatus according to the embodiment shown in fig. 6, where:
in a possible implementation manner, the type determining module 53 is specifically configured to: acquiring an identification list, wherein the identification list comprises identification information corresponding to the full-amount type file; and determining the file type according to the identification list and the identification information.
In a possible implementation manner, the identification information includes a user identification, and/or a device identification, and/or a type identification; the user identification is used for representing the identification corresponding to the user logging in the target application program; the device identifier is used for representing an identifier corresponding to the terminal device; the type identifier is used for indicating an identifier corresponding to the equipment type of the terminal equipment; when determining the file type according to the identifier list and the identifier information, the type determining module 53 is specifically configured to: judging whether the identification list comprises a user identification, and/or an equipment identification, and/or a type identification; if so, determining the file type as a full type; if not, determining that the file type is a partial type.
In a possible implementation manner, the file generating module 54 is specifically configured to: if the file type is a full type, generating a program exception file according to all exception information when the target application program is abnormal; and if the file type is a partial type, generating a program exception file according to partial exception information when the target application program is abnormal.
In a possible implementation, the data processing apparatus further includes an alarm module 61 configured to: generating abnormal alarm information; and sending abnormal alarm information to a server.
In a possible implementation manner, the data processing apparatus further includes a sending module 62, configured to: if the file type is a partial type, sending a program abnormal file to a server; and if the file type is the full type, storing the program abnormal file, and sending notification information to the preset device, wherein the notification information is used for indicating the terminal device to store the program abnormal file.
The anomaly determination module 51, the information acquisition module 52, the type determination module 53, the file generation module 54, the alarm module 61 and the sending module 62 are connected in sequence. The data processing apparatus 5 provided in this embodiment may execute the technical solution of the method embodiment shown in fig. 2, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 8 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application, which is applied to a server, and as shown in fig. 8, a data processing apparatus 7 according to this embodiment includes:
the alarm receiving module 71 is configured to receive abnormal alarm information of the target application program, which is sent by the terminal device, where the abnormal alarm information includes identification information corresponding to the target application program;
an identifier obtaining module 72, configured to obtain an identifier list, where the identifier list includes a plurality of pieces of identifier information;
and a notification sending module 73, configured to send a notification message to the preset device if the identifier list includes identifier information corresponding to the target application program, where the notification message is used to indicate that the target application program is abnormal.
In one possible implementation manner, the identification information includes: a user identification, and/or a device identification, and/or a type identification; the user identification is used for representing the identification corresponding to the user logging in the target application program; the device identifier is used for representing an identifier corresponding to the terminal device; the type identifier is used for indicating an identifier corresponding to the device type of the terminal device.
The alarm receiving module 71, the identifier obtaining module 72, and the notification sending module 73 are connected in sequence. The data processing apparatus 7 provided in this embodiment may execute the technical solution of the method embodiment shown in fig. 4, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 9 is a schematic block diagram of a terminal device according to an embodiment of the present application, and as shown in fig. 9, a terminal device 8 according to this embodiment includes: a memory 81, a processor 82 and a computer program.
The computer program is stored in the memory 81 and configured to be executed by the processor 82 to implement the data processing method provided in any one of the embodiments corresponding to fig. 2 to fig. 3 in the present application.
The memory 81 and the processor 82 are connected by a bus 83.
The relevant description may be understood by referring to the relevant description and effect corresponding to the steps in the embodiments corresponding to fig. 2 to fig. 3, and redundant description is not repeated here.
Fig. 10 is a schematic block diagram of a server according to an embodiment of the present application, and as shown in fig. 10, a server 9 according to this embodiment includes: a memory 91, a processor 92 and a computer program.
The computer program is stored in the memory 91 and configured to be executed by the processor 92 to implement the data processing method provided by any embodiment of fig. 4.
The memory 91 and the processor 92 are connected by a bus 93.
The relevant description may be understood by referring to the relevant description and effect corresponding to the step in the embodiment corresponding to fig. 4, and redundant description is not repeated here.
One embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the data processing method provided in any one of the embodiments corresponding to fig. 2 to fig. 4 of the present application.
The computer readable storage medium may be, among others, ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (14)

1. A data processing method is applied to a terminal device, and the method comprises the following steps:
determining that the target application program is abnormal;
acquiring identification information corresponding to the target application program;
determining a file type according to the identification information, wherein the file type is a full type or a partial type;
and generating a program exception file corresponding to the target application program according to the file type.
2. The method of claim 1, wherein determining the file type according to the identification information comprises:
acquiring an identification list, wherein the identification list comprises identification information corresponding to a full-size type file;
and determining the file type according to the identification list and the identification information.
3. The method of claim 2, wherein determining the file type according to the identification list and the identification information comprises:
judging whether the identification list comprises the identification information or not;
if so, determining the file type to be a full type;
if not, determining that the file type is a partial type.
4. The method of claim 1, wherein the identification information comprises at least one of:
a user identification;
a device identification;
identifying the type;
the user identification is used for representing an identification corresponding to a user logging in the target application program; the device identifier is used for representing an identifier corresponding to the terminal device; the type identifier is used for indicating an identifier corresponding to the device type of the terminal device.
5. The method of claim 1, wherein generating a program exception file corresponding to the target application program according to the file type comprises:
if the file type is a full type, generating the program exception file according to all exception information when the target application program is abnormal;
and if the file type is a partial type, generating the program exception file according to partial exception information when the target application program is abnormal.
6. The method according to any one of claims 1-5, further comprising:
generating abnormal alarm information;
and sending the abnormal alarm information to a server.
7. The method according to any one of claims 1-5, further comprising:
if the file type is a partial type, the program exception file is sent to a server;
and if the file type is a full type, storing the program exception file, and sending notification information to preset equipment, wherein the notification information is used for indicating the terminal equipment to store the program exception file.
8. A data processing method is applied to a server, and the method comprises the following steps:
receiving abnormal alarm information of a target application program sent by terminal equipment, wherein the abnormal alarm information comprises identification information corresponding to the target application program;
acquiring an identification list, wherein the identification list comprises a plurality of identification information;
and if the identification list comprises identification information corresponding to the target application program, sending a notification message to a preset device, wherein the notification message is used for indicating that the target application program is abnormal.
9. The method of claim 8, wherein the identification information comprises at least one of:
a user identifier, or a device identifier, and a type identifier;
the user identification is used for representing an identification corresponding to a user logging in the target application program; the device identifier is used for representing an identifier corresponding to the terminal device; the type identifier is used for indicating an identifier corresponding to the device type of the terminal device.
10. A data processing device, applied to a terminal device, includes:
the exception determining module is used for determining the exception of the target application program;
the information acquisition module is used for acquiring identification information corresponding to the target application;
the type determining module is used for determining the file type according to the identification information, wherein the file type is a full type or a partial type;
and the file generation module is used for generating a program exception file corresponding to the target application program according to the file type.
11. A data processing apparatus, applied to a server, includes:
the alarm receiving module is used for receiving abnormal alarm information of a target application program, which is sent by terminal equipment, wherein the abnormal alarm information comprises identification information corresponding to the target application program;
an identifier obtaining module, configured to obtain an identifier list, where the identifier list includes a plurality of pieces of identifier information;
and a notification sending module, configured to send a notification message to a preset device if the identifier list includes identifier information corresponding to the target application program, where the notification message is used to indicate that the target application program is abnormal.
12. A terminal device, comprising: a memory, a processor, and a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the data processing method of any one of claims 1 to 7.
13. A server, comprising: a memory, a processor, and a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the data processing method of claim 8 or 9.
14. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, are configured to implement the data processing method of any one of claims 1 to 9.
CN202011183075.XA 2020-10-29 2020-10-29 Data processing method, device, equipment and storage medium Pending CN112306871A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011183075.XA CN112306871A (en) 2020-10-29 2020-10-29 Data processing method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011183075.XA CN112306871A (en) 2020-10-29 2020-10-29 Data processing method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112306871A true CN112306871A (en) 2021-02-02

Family

ID=74331992

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011183075.XA Pending CN112306871A (en) 2020-10-29 2020-10-29 Data processing method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112306871A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113010481A (en) * 2021-03-18 2021-06-22 成都欧珀通信科技有限公司 File capture method, device, terminal and storage medium
CN115001931A (en) * 2022-05-25 2022-09-02 湖南亚信软件有限公司 Message processing method, device, equipment, medium and program product

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017032244A1 (en) * 2015-08-27 2017-03-02 阿里巴巴集团控股有限公司 Method and device for storing behavior record
CN106681930A (en) * 2017-01-23 2017-05-17 北京思特奇信息技术股份有限公司 Distributed automatic application operation abnormity detecting method and system
CN109800101A (en) * 2019-02-01 2019-05-24 北京字节跳动网络技术有限公司 Report method, device, terminal device and the storage medium of small routine abnormal conditions
CN110764977A (en) * 2019-09-27 2020-02-07 赛诺贝斯(北京)营销技术股份有限公司 Alarm method and device for realizing system safety
CN111475334A (en) * 2020-03-05 2020-07-31 平安科技(深圳)有限公司 TiDB database maintenance method and device, computer equipment and storage medium
CN111611145A (en) * 2020-05-29 2020-09-01 北京字节跳动网络技术有限公司 Breakdown information collection method and device, storage medium and electronic equipment
CN111786828A (en) * 2020-06-29 2020-10-16 百度在线网络技术(北京)有限公司 Log processing method executed in network device and network device

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017032244A1 (en) * 2015-08-27 2017-03-02 阿里巴巴集团控股有限公司 Method and device for storing behavior record
CN106681930A (en) * 2017-01-23 2017-05-17 北京思特奇信息技术股份有限公司 Distributed automatic application operation abnormity detecting method and system
CN109800101A (en) * 2019-02-01 2019-05-24 北京字节跳动网络技术有限公司 Report method, device, terminal device and the storage medium of small routine abnormal conditions
CN110764977A (en) * 2019-09-27 2020-02-07 赛诺贝斯(北京)营销技术股份有限公司 Alarm method and device for realizing system safety
CN111475334A (en) * 2020-03-05 2020-07-31 平安科技(深圳)有限公司 TiDB database maintenance method and device, computer equipment and storage medium
CN111611145A (en) * 2020-05-29 2020-09-01 北京字节跳动网络技术有限公司 Breakdown information collection method and device, storage medium and electronic equipment
CN111786828A (en) * 2020-06-29 2020-10-16 百度在线网络技术(北京)有限公司 Log processing method executed in network device and network device

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113010481A (en) * 2021-03-18 2021-06-22 成都欧珀通信科技有限公司 File capture method, device, terminal and storage medium
CN113010481B (en) * 2021-03-18 2023-06-09 成都欧珀通信科技有限公司 File capturing method, device, terminal and storage medium
CN115001931A (en) * 2022-05-25 2022-09-02 湖南亚信软件有限公司 Message processing method, device, equipment, medium and program product

Similar Documents

Publication Publication Date Title
CN110224858B (en) Log-based alarm method and related device
CN112311617A (en) Configured data monitoring and alarming method and system
CN107704360B (en) Monitoring data processing method, equipment, server and storage medium
JP6160064B2 (en) Application determination program, failure detection apparatus, and application determination method
CN110362455B (en) Data processing method and data processing device
US20200327045A1 (en) Test System and Test Method
CN112256542B (en) eBPF-based micro-service system performance detection method, device and system
CN111046011A (en) Log collection method, system, node, electronic device and readable storage medium
CN111190755B (en) Application program function exception handling method and device
CN112783725B (en) Index collection method and device
CN107800783B (en) Method and device for remotely monitoring server
CN114077525A (en) Abnormal log processing method and device, terminal equipment, cloud server and system
CN112636979B (en) Cluster alarm method and related device
CN112698915A (en) Multi-cluster unified monitoring alarm method, system, equipment and storage medium
CN110231998B (en) Detection method and device for distributed timing task and storage medium
CN112306871A (en) Data processing method, device, equipment and storage medium
CN114356499A (en) Kubernetes cluster alarm root cause analysis method and device
CN110505177B (en) Information collection system, terminal equipment and remote host
CN113568878A (en) Method and device for collecting and exporting system logs and vehicle
CN112464238A (en) Vulnerability scanning method and electronic equipment
CN111431733A (en) Service alarm coverage information evaluation method and device
CN108880920B (en) Cloud service management method and device and electronic equipment
CN114338347A (en) Ampere platform-based fault information out-of-band acquisition method and device
CN110362464B (en) Software analysis method and equipment
CN113806195A (en) Data processing method, device, equipment, system and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination