CN111309511A - Application running data processing method and device and terminal - Google Patents
Application running data processing method and device and terminal Download PDFInfo
- Publication number
- CN111309511A CN111309511A CN202010120800.2A CN202010120800A CN111309511A CN 111309511 A CN111309511 A CN 111309511A CN 202010120800 A CN202010120800 A CN 202010120800A CN 111309511 A CN111309511 A CN 111309511A
- Authority
- CN
- China
- Prior art keywords
- fault
- array
- data
- target data
- application
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application is applicable to the technical field of application monitoring, and provides a method, a device and a terminal for processing application running data, wherein the method comprises the following steps: acquiring operation data of an application in local; generating a fault description array based on the operating data, wherein the fault description array comprises: the method comprises the following steps of (1) operating fault types and fault descriptions corresponding to the operating fault types; generating a target data identifier corresponding to the operation fault type in the fault description array according to the fault description array; when the target data identifier is not stored in the local configuration information, the target data identifier and the fault description array are sent to a server, so that the complexity of problem follow-up troubleshooting in the application running process is improved, and the complexity of background data aggregation cleaning is reduced.
Description
Technical Field
The application belongs to the technical field of application monitoring, and particularly relates to a method and a device for processing application running data and a terminal.
Background
The reporting of application monitoring data is a very common technical behavior, and when the current application is not in accordance with the expected condition in the running process, the related key log data is reported to a background, then thousands of client application reported data are aggregated and cleaned in the background, and a sorted report and data are output.
Data of a single application in operation is usually repeated, and the repetition amount is large. However, the common processing mode in the industry is to collect and report all kinds of application exceptions to the background, which causes that the client will report some same data to the background repeatedly. The background carries out aggregation cleaning on thousands of even over billions of application reported data, and a lot of repeated and repeated work exists. This causes a small resource overhead for the application itself, and also has a high requirement for hardware resources and software processing capabilities of the foreground terminal and the background server. Not only is a great deal of waste of application resources and background equipment resources, but also the complexity of subsequent maintenance work is increased.
Disclosure of Invention
The embodiment of the application provides a method, a device and a terminal for processing application running data, and aims to solve the problems that in the prior art, a lot of repeated and repeated work exists in aggregation and cleaning of a large amount of application reported data, and a lot of waste of application resources and background equipment resources is generated.
A first aspect of an embodiment of the present application provides a method for processing application running data, including:
acquiring operation data of an application in local;
generating a fault description array based on the operating data, wherein the fault description array comprises: the method comprises the following steps of (1) operating fault types and fault descriptions corresponding to the operating fault types;
generating a target data identifier corresponding to the operation fault type in the fault description array according to the fault description array;
and when the target data identifier is not stored in the local configuration information, sending the target data identifier and the fault description array to a server.
A second aspect of the embodiments of the present application provides an apparatus for processing application execution data, including:
the acquisition module is used for acquiring the local operation data of the application;
a first generating module, configured to generate a fault description array based on the operation data, where the fault description array includes: the method comprises the following steps of (1) operating fault types and fault descriptions corresponding to the operating fault types;
the second generation module is used for generating a target data identifier corresponding to the operation fault type in the fault description array according to the fault description array;
and the sending module is used for sending the target data identifier and the fault description array to a server when the target data identifier is not stored in the local configuration information.
A third aspect of embodiments of the present application provides a terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method according to the first aspect when executing the computer program.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, in which a computer program is stored, which, when executed by a processor, performs the steps of the method according to the first aspect.
A fifth aspect of the present application provides a computer program product, which, when run on a terminal, causes the terminal to perform the steps of the method of the first aspect described above.
As can be seen from the above, in the embodiment of the present application, a fault description array is generated based on the operation data applied locally, and according to the fault description array, a target data identifier corresponding to an operation fault type in the fault description array is generated; when the target data identifier is not stored in the local configuration information, the target data identifier and the fault description array are sent to the server, the process realizes that a duplicate removal mechanism is added at the application terminal, the fault description array and the corresponding target data identifier can be utilized, repeated data are combined and processed to the maximum extent, intelligent reporting and duplicate removal of application operation monitoring data in the terminal are realized, the processing capacity of a background is improved by hundreds of times, the equipment overhead is greatly reduced, the memory and storage resource overhead of the application is reduced, the complexity of problem follow-up and troubleshooting in the application operation process is greatly improved, the complexity of background to data aggregation cleaning is reduced, and the development and subsequent maintenance cost in the early stage are greatly reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a first flowchart of a method for processing application running data according to an embodiment of the present application;
fig. 2 is a second flowchart of a method for processing application running data according to an embodiment of the present application;
fig. 3 is a flowchart three of a processing method for application running data according to an embodiment of the present application;
fig. 4 is a block diagram of a processing device for applying operation data according to an embodiment of the present application;
fig. 5 is a structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In particular implementations, the terminals described in embodiments of the present application include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers having touch sensitive surfaces (e.g., touch screen displays and/or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but is a desktop computer having a touch-sensitive surface (e.g., a touch screen display and/or touchpad).
In the discussion that follows, a terminal that includes a display and a touch-sensitive surface is described. However, it should be understood that the terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and/or joystick.
The terminal supports various applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disc burning application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, an exercise support application, a photo management application, a digital camera application, a web browsing application, a digital music player application, and/or a digital video player application.
Various applications that may be executed on the terminal may use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal can be adjusted and/or changed between applications and/or within respective applications. In this way, a common physical architecture (e.g., touch-sensitive surface) of the terminal can support various applications with user interfaces that are intuitive and transparent to the user.
It should be understood that, the sequence numbers of the steps in this embodiment do not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic of the process, and should not constitute any limitation to the implementation process of the embodiment of the present application.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
Referring to fig. 1, fig. 1 is a first flowchart of a method for processing application running data according to an embodiment of the present application. As shown in fig. 1, a method for processing application running data includes the following steps:
The step mainly realizes the operation monitoring of the application. Specifically, the method is to collect states and data in the application running process, and then report the states and data to a background server at a certain time point or a plurality of time points in the running process.
The obtaining of the local operation data of the application may specifically be: the client acquires operation data in the terminal application, and the operation data comprises the following steps: user basic data, application starting time, central processing unit operation speed, application operation fluency (frame number of pictures in set time), file transmission data, input/output, memory operation data, application non-response, running data, background access abnormal data, webpage access abnormal data and the like.
And 102, generating a fault description array based on the operation data.
Wherein, the fault description array comprises: the fault analysis method comprises an operation fault type and a fault description corresponding to the operation fault type. Wherein, the one operation fault type and the fault description may be in a one-to-one correspondence relationship. For example, if the operation fault type is a, the fault description in the fault description array is a specific description of the fault content corresponding to the type a.
When the fault description array is generated, simple noise point processing can be performed on the data of the same type, and the fault description array is generated based on the operation data after the noise point processing.
The failure description array is specifically an array for describing failures occurring in the running process of the application. Such as no response by the application, running, input/output exception, file transfer exception, etc.
Here, it is necessary to generate a target data identifier corresponding to the operation failure type therein based on the failure description array.
The target data identifier may be specifically a data identifier obtained by performing md5 processing on useful information related to the operation failure type and outputting the processed information. The target data identifier is used as a basis for application-side deduplication. The data identifier is the same only if the type of operational failure is the same. Therefore, it is possible to determine which of the large amount of operating data is identical repeated failure data based on the data identifier, and then deduplication of the large amount of repeating data can be achieved based on the data identifier.
When the application acquires data through monitoring in the running process, the data is dried, the dried data forms a fault description array, and md5 processing is carried out on the basis of the fault description array to obtain a unique identification code (namely a data identifier) of information. In the specific implementation process, an md5 identifier corresponds to an array, and a mode of key value pairs { key, value } is arranged in the array, namely a fault description array, wherein key represents a fault type, and value represents a fault description corresponding to the fault type.
When a specific deduplication operation is performed, and a corresponding md5 value is generated based on the value, the client removes application time such as time and a drive letter and content related to device information from data acquired from the system, for example, there is such a log: "08-1520: 35: 22.4821136-1136/? I/TrapacMonitor: amplified array.level: -1 "is removed time and device related information and then" TrapacMonitor: amplified array.level: -1 "is left to ensure that the information is program log information which is not related to the device, and then the information is processed by md5 to obtain an encrypted character string (identifier), and the identifier is the same for the same information. Based on the fault description array, namely the corresponding data identifier, the data is deduplicated, and the data deduplication effect is realized.
And 104, when the target data identifier is not stored in the local configuration information, sending the target data identifier and the fault description array to a server.
The local configuration information stores data identifiers corresponding to different fault types. The configuration file may be obtained by accumulating target data identifiers generated for different fault types based on the local terminal, or obtained by pushing the target data identifiers by a background server or other terminals, where the other terminals are specifically other terminals of the same type.
When the target data identifier is not stored in the local configuration information, it is indicated that the fault type corresponding to the target data identifier occurs for the first time, and at this time, the fault description array corresponding to the fault type occurring for the first time and the corresponding target data identifier need to be sent to the server for fault information reporting. The server obtains the fault type and the fault description, and simultaneously obtains the data identifier capable of representing the fault, so that the generated data identifier is used as an application terminal for removing the duplicate, and the background server side aggregates and generates the rule for removing the reconfiguration of the same type of equipment.
Correspondingly, as an optional implementation manner, when the target data identifier is not stored in the local configuration information, the method further includes:
and associating and storing the target data identifier and the fault description array into the local configuration information.
When the target data identifier is not stored in the local configuration information, it is indicated that the fault type corresponding to the target data identifier appears for the first time, and the target data identifier and the fault description array need to be stored in the local configuration information in an associated manner, so that the local configuration information is updated in time.
Correspondingly, as an optional implementation manner, after generating, according to the failure description array, a target data identifier corresponding to an operation failure type in the failure description array, the method further includes:
and when the target data identifier is stored in the local configuration information, sending the target data identifier to a server.
Wherein the data identifier is sent to the server, whether the terminal is local or other terminals of the same type need to do so. The difference is that when new operation data exists and a fault description array is obtained based on the operation data, a data identifier corresponding to the new fault description array needs to be matched with locally stored configuration data, if the data identifier exists in the local configuration data, the fault does not occur for the first time, and for a reported fault, only the data identifier needs to be reported, the corresponding fault information does not need to be reported, and if the data identifier does not exist, the data identifier and the corresponding fault description array description information are reported.
Further, as an optional implementation manner, the method further includes:
displaying an operation display interface of the application; and the operation display interface is connected with the server through an interface, and the operation monitoring results applied to the same type of equipment are displayed on the operation display interface.
The application terminal can provide an operation display interface to display the aggregation cleaning result of the application operation data reported by different clients and collected by the server, so as to display the operation monitoring result applied to the same type of equipment.
Specifically, on the background side, the background collects data reported by different clients, then performs aggregation cleaning on the collected data, and if the application running state and the data are found to be abnormal, performs early warning in time, and simultaneously stores the sorted data on the background and provides an interface for calling the aggregated cleaned data to the outside, so that the front end can be conveniently displayed.
In the embodiment of the application, a fault description array is generated based on the operation data applied to the local, and a target data identifier corresponding to the operation fault type in the fault description array is generated according to the fault description array; when the target data identifier is not stored in the local configuration information, the target data identifier and the fault description array are sent to the server, the process realizes that a duplicate removal mechanism is added at the application terminal, the fault description array and the corresponding target data identifier can be utilized, repeated data are combined and processed to the maximum extent, intelligent reporting and duplicate removal of application operation monitoring data in the terminal are realized, the processing capacity of a background is improved by hundreds of times, the equipment overhead is greatly reduced, the memory and storage resource overhead of the application is reduced, the complexity of problem follow-up and troubleshooting in the application operation process is greatly improved, the complexity of background to data aggregation cleaning is reduced, and the development and subsequent maintenance cost in the early stage are greatly reduced.
The embodiment of the application also provides different implementation modes of the processing method of the application running data.
Referring to fig. 2, fig. 2 is a second flowchart of a processing method for application running data according to an embodiment of the present application. As shown in fig. 2, a method for processing application running data includes the following steps:
Wherein, the background configuration information includes: and the fault description arrays uploaded by the same type of equipment and the corresponding data identifiers.
The corresponding identifier generated by the terminal based on the abnormal condition is uploaded to the background server, so that the background server synchronously issues the abnormal label to each terminal after abnormal data integration is carried out, and when the terminals of the same type upload the abnormal data, the repeated uploading of the data can be reduced, and the data volume is reduced.
After receiving the data reported by the application terminal, the background performs device correlation analysis and sorting on the reported content, for example, performs cluster integration on the information of devices belonging to the same type, and issues background configuration information formed after sorting to the terminal devices of the same type.
The background configuration information includes a fault description array uploaded by the same type of equipment and a corresponding data identifier. The fault description array uploaded by the same type of equipment refers to the fault description array uploaded to the server by the same type of equipment including the execution terminal of the method and the corresponding data identifier.
In a specific implementation process, after receiving the failure description arrays and the corresponding data identifiers uploaded by the multiple application terminals of the same type, the server needs to aggregate and generate reconfiguration removal of devices of the same type when aggregating and cleaning the reported data. The method specifically includes classifying the fault description arrays and the corresponding data identifiers according to different equipment types, and after the fault description arrays and the corresponding data identifiers uploaded by the same type of equipment are obtained, pushing the fault description arrays and the corresponding data identifiers uploaded by the same type of equipment to the same type of application terminal, so that the same type of terminal can locally perform fault description and storage of the corresponding data identifiers, unification of fault description and corresponding identifiers in the same type of equipment is achieved, further intelligent duplicate removal of local fault description information of the same type of equipment is facilitated, accurate and timely reporting of information is guaranteed, and meanwhile, repeated information reporting amount is greatly reduced.
To illustrate, for example, the same handset [ such as: and merging the target data identifier and the fault description array uploaded by a certain mobile phone P20 ]. Taking the combination of the target data identifier and the fault description array uploaded by a certain two mobile phone P20 terminals as an example, the information uploaded by the first mobile phone P20 terminal and the information uploaded by the second mobile phone P20 terminal are acquired in the background, whether the two mobile phones belong to the same type of equipment is judged according to the equipment identifiers in the information uploaded by the two mobile phones, and when the two mobile phones are determined to be the same type of equipment, the fault description arrays with the same data identifier md5 in the information uploaded by the two mobile phones are combined. And the background aggregation generates reconfiguration removing information of the same type of equipment, and the sorted configuration file is issued to other same type of equipment for application.
The aforementioned devices of the same type may specifically refer to batch devices of the same series and version of a uniform manufacturer.
The background server receives the running data reported by countless application devices, classifies and sorts the devices of the same type, the device information of the same type has a configuration file which records the description information of faults and corresponding data identifiers md5, the configuration file is issued to the device when the devices of the same type are started, so that the device can combine the background configuration information with the local configuration information based on the background configuration information, the information which is acquired by the server can be filtered when the devices of the same type report the fault information to the background, thereby reducing the repeated reporting of the running data, combining and processing the repeated data to the maximum extent, reducing the content volume reported integrally by a great amount, combining the technical scheme with the downstream server, and improving the processing capacity of the background by hundreds of times through the configuration of the terminal and the background server, compared with the same situation, the device overhead of the background can be reduced by more than 90% in terms of resource consumption.
The implementation process of this step is the same as that of step 101 in the foregoing embodiment, and is not described here again.
And step 204, generating a fault description array based on the operation data.
Wherein, the fault description array comprises: the fault analysis method comprises an operation fault type and a fault description corresponding to the operation fault type.
The implementation process of this step is the same as that of step 102 in the foregoing embodiment, and is not described here again.
The implementation process of this step is the same as that of step 103 in the foregoing embodiment, and is not described here again.
The implementation process of this step is the same as that of step 104 in the foregoing embodiment, and is not described here again.
In the embodiment of the application, the integration of background configuration information and local configuration information pushed by a server is acquired, a fault description array is generated based on operation data applied to the local, a target data identifier corresponding to an operation fault type in the fault description array is generated according to the fault description array, and the target data identifier and the fault description array are sent to the server when the target data identifier is not stored in the local configuration information, so that a deduplication mechanism is added to an application terminal in the process, repeated data can be combined to the maximum extent by using the fault description array and the corresponding target data identifier, the intelligent reporting deduplication of application operation monitoring data in the terminal is realized, the processing capacity of the background is improved by hundreds of times, the equipment overhead is greatly reduced, and the memory and storage resource overhead of the application is reduced, the complexity of problem follow-up examination in the application running process is greatly improved, the complexity of background for data aggregation cleaning is reduced, and the early development and subsequent maintenance cost is greatly reduced.
The embodiment of the application also provides different implementation modes of the processing method of the application running data.
Referring to fig. 3, fig. 3 is a second flowchart of a processing method for application running data according to an embodiment of the present application. As shown in fig. 3, a method for processing application running data includes the following steps:
The implementation process of this step is the same as that of step 101 in the foregoing embodiment, and is not described here again.
The fault description array comprises: the fault analysis method comprises an operation fault type and a fault description corresponding to the operation fault type.
The implementation process of this step is the same as that of step 102 in the foregoing embodiment, and is not described here again.
The implementation process of this step is the same as that of step 103 in the foregoing embodiment, and is not described here again.
The implementation process of this step is the same as that of step 104 in the foregoing embodiment, and is not described here again.
Further, optionally, a data identifier array is recorded in the local configuration information, where the data identifier array includes: the data identification device comprises a data identification and a fault counting unit corresponding to the data identification.
Wherein, an md5 data identifier corresponds to a fault description array, and the array is internally provided with a mode of key value pairs { key, value }, wherein key represents a fault type, and value represents a fault description corresponding to the fault type. And obtaining corresponding { md5, count } based on the { key, value }, wherein md5 represents a data identifier obtained by correspondingly performing md5 processing on the value, and count is a count value of the number of times of occurrence of the fault.
When the terminal where the application is located obtains the monitoring information and reports the monitoring information to the background, the terminal compares whether the local configuration has the same md5, if so, the terminal performs deduplication processing, and the count is added with 1, so that repeated information can be filtered inside the application, and the times are put into the subsequent count.
For example, after acquiring the md5 data identifier, the mobile phone terminal may filter out the same information for uploading, when uploading the fault information, compare the fault description array with the configuration information of the local record, and for the fault information existing in the local and background servers, directly upload the md5 identifier corresponding to the fault description array and the count value obtained by local statistics, when the fault information does not exist in the configuration information of the local record, upload the fault description array, the md5 identifier corresponding to the fault description array and the count corresponding to the fault description array, which may reduce the transfer of a lot of text information.
When the fault description array uploaded by the same type of device and the corresponding data identifier are added to the local configuration information, the data identifier array including the data identifier may be added to the local configuration information.
As an optional implementation manner, the sending the target data identification array to the server includes: and sending the equipment identifier of the terminal and the target data identification array to the server together.
When the fault problems are multiple, and the equipment identifier of the terminal and the target data identifier array are jointly sent to the server, the format of the information content is as follows: "device identifier, { { md5, count }, { md5, count }, { md5, count }, … }, where the device identifier is an ID, i.e., an identification code, that identifies the terminal where the current application is located.
That is, the format of the content in the local configuration information is: "device identifier" { { unique identification code, number of times of first failure information }, { unique identification code, number of times of second failure information }, { unique identification code, number of times of third failure information }, … } ". And realizing the duplicate removal of the duplicate information.
And when the server merges the fault description arrays with the same md5, modifying the corresponding count value, realizing data merging, and counting the occurrence times of the fault in each terminal.
In the embodiment of the application, a fault description array is generated based on operation data applied to the local, a target data identifier corresponding to an operation fault type in the fault description array is generated according to the fault description array, when the target data identifier is not stored in local configuration information, the target data identifier and the fault description array are sent to a server, a duplication elimination mechanism is added to an application terminal, a fault counting unit is added in the process, repeated data can be combined to the maximum extent by using the fault description array and the corresponding target data identifier, intelligent reporting and duplication elimination of application operation monitoring data in the terminal are realized, the processing capacity of a background is improved by hundreds times, the equipment overhead is greatly reduced, the memory and storage resource overhead of the application is reduced, and the complexity of problem follow-up troubleshooting in the application operation process is greatly improved, the complexity of the background for data aggregation cleaning is reduced, and the development and subsequent maintenance costs in the early stage are greatly reduced.
Referring to fig. 4, fig. 4 is a structural diagram of a processing device for applying operation data according to an embodiment of the present application, and for convenience of description, only a part related to the embodiment of the present application is shown.
The processing device 400 for the application running data comprises:
an obtaining module 401, configured to obtain local operation data;
a first generating module 402, configured to generate a failure description array based on the operation data, where the failure description array includes: the method comprises the following steps of (1) operating fault types and fault descriptions corresponding to the operating fault types;
a second generating module 403, configured to generate, according to the fault description array, a target data identifier corresponding to an operation fault type in the fault description array;
a sending module 404, configured to send the target data identifier and the failure description array to a server when the target data identifier is not stored in the local configuration information.
The device also includes:
and the storage module is used for associating and storing the target data identifier and the fault description array into the local configuration information.
The device also includes:
a receiving module, configured to obtain background configuration information sent by the server, where the background configuration information includes: the fault description arrays uploaded by the devices of the same type and corresponding data identifiers;
and the updating module is used for adding the fault description array uploaded by the same type of equipment and the corresponding data identifier to the local configuration information if the local configuration information does not contain the data identifier uploaded by the same type of equipment based on the background configuration information.
Wherein, a data identifier array is recorded in the local configuration information, and the data identifier array includes: the data identification device comprises a data identification and a fault counting unit corresponding to the data identification.
The device also includes:
the counting module is used for adding one to the counting value of the target fault counting unit in the target data identification array when the local configuration information stores the target data identification array corresponding to the target data identifier;
and the output module is used for sending the target data identification array to the server.
Wherein, the output module is specifically configured to:
and sending the equipment identifier of the terminal and the target data identification array to the server together.
The device also includes:
the display module is used for displaying the running display interface of the application;
and the operation display interface is connected with the server through an interface, and the operation monitoring results applied to the same type of equipment are displayed on the operation display interface.
The processing device for application running data provided in the embodiment of the present application can implement each process of the above-mentioned embodiment of the processing method for application running data, and can achieve the same technical effect, and for avoiding repetition, details are not repeated here.
Fig. 5 is a structural diagram of a terminal according to an embodiment of the present application. As shown in the figure, the terminal 5 of this embodiment includes: at least one processor 50 (only one shown in fig. 5), a memory 51, and a computer program 52 stored in the memory 51 and executable on the at least one processor 50, the steps of any of the various method embodiments described above being implemented when the computer program 52 is executed by the processor 50.
The terminal 5 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal 5 may include, but is not limited to, a processor 50, a memory 51. It will be appreciated by those skilled in the art that fig. 5 is only an example of a terminal 5 and does not constitute a limitation of the terminal 5 and may include more or less components than those shown, or some components in combination, or different components, for example the terminal may also include input output devices, network access devices, buses, etc.
The Processor 50 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 51 may be an internal storage unit of the terminal 5, such as a hard disk or a memory of the terminal 5. The memory 51 may also be an external storage device of the terminal 5, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) and the like provided on the terminal 5. Further, the memory 51 may also include both an internal storage unit and an external storage device of the terminal 5. The memory 51 is used for storing the computer program and other programs and data required by the terminal. The memory 51 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal and method may be implemented in other ways. For example, the above-described apparatus/terminal embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be 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 units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The present application realizes all or part of the processes in the method of the above embodiments, and may also be implemented by a computer program product, when the computer program product runs on a terminal, the steps in the above method embodiments may be implemented when the terminal executes the computer program product.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A processing method of application running data is characterized by comprising the following steps:
acquiring operation data of an application in local;
generating a fault description array based on the operating data, wherein the fault description array comprises: the method comprises the following steps of (1) operating fault types and fault descriptions corresponding to the operating fault types;
generating a target data identifier corresponding to the operation fault type in the fault description array according to the fault description array;
and when the target data identifier is not stored in the local configuration information, sending the target data identifier and the fault description array to a server.
2. The processing method according to claim 1, wherein when the target data identifier is not stored in the local configuration information, further comprising:
and associating and storing the target data identifier and the fault description array into the local configuration information.
3. The processing method according to claim 1 or 2, wherein before acquiring the running data of the application locally, the method further comprises:
obtaining background configuration information sent by the server, wherein the background configuration information comprises: the fault description arrays uploaded by the devices of the same type and corresponding data identifiers;
based on the background configuration information, if the local configuration information does not contain the data identifiers uploaded by the devices of the same type, adding the fault description array uploaded by the devices of the same type and the corresponding data identifiers to the local configuration information.
4. The processing method according to claim 1, wherein a data identification array is recorded in the local configuration information, and the data identification array includes: the data identification device comprises a data identification and a fault counting unit corresponding to the data identification.
5. The processing method according to claim 4, wherein after generating the target data identifier corresponding to the operation fault type in the fault description array according to the fault description array, the processing method further comprises:
when a target data identification array corresponding to the target data identifier is stored in the local configuration information, adding one to the count value of a target fault counting unit in the target data identification array;
and sending the target data identification array to the server.
6. The processing method of claim 5, wherein sending the target data identification array to the server comprises:
and sending the equipment identifier of the terminal and the target data identification array to the server together.
7. The processing method according to claim 1, characterized in that the method further comprises:
displaying an operation display interface of the application;
and the operation display interface is connected with the server through an interface, and the operation monitoring results applied to the same type of equipment are displayed on the operation display interface.
8. An apparatus for processing application execution data, comprising:
the acquisition module is used for acquiring the local operation data of the application;
a first generating module, configured to generate a fault description array based on the operation data, where the fault description array includes: the method comprises the following steps of (1) operating fault types and fault descriptions corresponding to the operating fault types;
the second generation module is used for generating a target data identifier corresponding to the operation fault type in the fault description array according to the fault description array;
and the sending module is used for sending the target data identifier and the fault description array to a server when the target data identifier is not stored in the local configuration information.
9. A terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010120800.2A CN111309511A (en) | 2020-02-26 | 2020-02-26 | Application running data processing method and device and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010120800.2A CN111309511A (en) | 2020-02-26 | 2020-02-26 | Application running data processing method and device and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111309511A true CN111309511A (en) | 2020-06-19 |
Family
ID=71159465
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010120800.2A Pending CN111309511A (en) | 2020-02-26 | 2020-02-26 | Application running data processing method and device and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309511A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112799905A (en) * | 2021-01-05 | 2021-05-14 | 杭州涂鸦信息技术有限公司 | Software operation monitoring method, system and related device |
| CN116149235A (en) * | 2023-04-03 | 2023-05-23 | 艾欧史密斯(中国)热水器有限公司 | Data processing method of household appliance system, controller and household appliance system |
-
2020
- 2020-02-26 CN CN202010120800.2A patent/CN111309511A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112799905A (en) * | 2021-01-05 | 2021-05-14 | 杭州涂鸦信息技术有限公司 | Software operation monitoring method, system and related device |
| CN116149235A (en) * | 2023-04-03 | 2023-05-23 | 艾欧史密斯(中国)热水器有限公司 | Data processing method of household appliance system, controller and household appliance system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110708204B (en) | Abnormity processing method, system, terminal and medium based on operation and maintenance knowledge base | |
| US20240195833A1 (en) | System for automated capture and analysis of business information for security and client-facing infrastructure reliability | |
| WO2021129367A1 (en) | Method and apparatus for monitoring distributed storage system | |
| CN107248927B (en) | Generation method of fault positioning model, and fault positioning method and device | |
| US11164402B2 (en) | Vehicle data stream displaying method and system, and vehicle diagnostic device | |
| CN111240876B (en) | Fault positioning method and device for micro-service, storage medium and terminal | |
| US20110029581A1 (en) | Load-Balancing and Scaling for Analytics Data | |
| CN111339073A (en) | Real-time data processing method and device, electronic equipment and readable storage medium | |
| CN110362455B (en) | Data processing method and data processing device | |
| CN109543891B (en) | Method and apparatus for establishing capacity prediction model, and computer-readable storage medium | |
| CN111309511A (en) | Application running data processing method and device and terminal | |
| CN111078695B (en) | Method and device for calculating association relation of metadata in enterprise | |
| WO2020012579A1 (en) | Log analysis device, log analysis method, and program | |
| CN111274256A (en) | Resource control method, device, equipment and storage medium based on time sequence database | |
| CN112434238A (en) | Webpage quality detection method and device, electronic equipment and storage medium | |
| CN110807050B (en) | Performance analysis method, device, computer equipment and storage medium | |
| CN114091704A (en) | Alarm suppression method and device | |
| CN107423090B (en) | Flash player abnormal log management method and system | |
| US20150066965A1 (en) | Data processing, data collection | |
| CN111241048A (en) | Web terminal log management method, device, medium and electronic equipment | |
| CN111274032A (en) | Task processing system and method, and storage medium | |
| CN111694810A (en) | Data warehouse creation method and device, electronic equipment and readable storage medium | |
| CN114745452B (en) | Equipment management method and device and electronic equipment | |
| CN110569172B (en) | Performance monitoring system of service level | |
| CN110020166A (en) | A kind of data analysing method and relevant device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210125 Address after: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant after: Shenzhen saiante Technology Service Co.,Ltd. Address before: 1-34 / F, Qianhai free trade building, 3048 Xinghai Avenue, Mawan, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong 518000 Applicant before: Ping An International Smart City Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |