CN113590188A - Method, device and storage medium for application program crash stack aggregation - Google Patents
Method, device and storage medium for application program crash stack aggregation Download PDFInfo
- Publication number
- CN113590188A CN113590188A CN202110869019.XA CN202110869019A CN113590188A CN 113590188 A CN113590188 A CN 113590188A CN 202110869019 A CN202110869019 A CN 202110869019A CN 113590188 A CN113590188 A CN 113590188A
- Authority
- CN
- China
- Prior art keywords
- crash
- stack
- characteristic value
- collapse
- information
- 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
- 230000002776 aggregation Effects 0.000 title claims abstract description 121
- 238000004220 aggregation Methods 0.000 title claims abstract description 118
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000003860 storage Methods 0.000 title claims abstract description 15
- 210000001072 colon Anatomy 0.000 claims description 35
- 230000001419 dependent effect Effects 0.000 claims description 27
- 230000004931 aggregating effect Effects 0.000 claims description 17
- 238000000605 extraction Methods 0.000 claims description 10
- 238000012795 verification Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 4
- 238000012827 research and development Methods 0.000 abstract description 10
- 230000008569 process Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 4
- 238000004422 calculation algorithm Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006116 polymerization reaction Methods 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/72—Code refactoring
-
- 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/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
- G06F16/24554—Unary operations; Data partitioning operations
- G06F16/24556—Aggregation; Duplicate elimination
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/21—Design or setup of recognition systems or techniques; Extraction of features in feature space; Blind source separation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/22—Matching criteria, e.g. proximity measures
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Evolutionary Computation (AREA)
- Evolutionary Biology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Bioinformatics & Computational Biology (AREA)
- Artificial Intelligence (AREA)
- Life Sciences & Earth Sciences (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method, a device and a storage medium for application program crash stack aggregation, wherein the method comprises the following steps: acquiring collapse stack information of an application program; removing repeated operation is carried out on the application program crash stack information to obtain first crash stack information; extracting the characteristics of the first collapsed stack information to obtain a first collapsed stack characteristic value; and performing aggregation matching by using the first collapse stack characteristic value and the second collapse stack characteristic value. According to the embodiment of the invention, after duplicate removal and primary aggregation are carried out on the program collapse stack, the data volume is reduced, and the efficiency of extracting the stack characteristic value is improved; and matching and calculating with the existing stack characteristic value in the collapse stack management platform to finish stack aggregation. The method can improve the efficiency of stack collapse aggregation of the application program, avoid the problem that research and development personnel face a large number of repeated problems, and save labor cost.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for stack collapse aggregation for an application program, and a storage medium.
Background
Collapse stack information governance is the iterative important work of mobile internet era APP, and traditional problem governance life cycle includes the collection of the collapse stack information that APP produced, collapse stack information stack polymerization, collapse stack information show, collapse stack information modification, APP release and the change of collapse stack information state, and good collapse stack information platform can help the APP problem of converging fast, reduces the influence user number of problem, reduces the loss.
When a problem occurs, a plurality of users of the APP can be affected, a plurality of users can crash stack information for a plurality of times due to the problem, the collection SDK on the APP can report all the crash stack information to the crash stack management platform, and the crash stack information is aggregated into a problem by the platform to be displayed to research and development personnel.
The code module is often multiplexed to large-scale APP, and when the module of certain sharing goes wrong, the different pages of multiplexing this module in the APP all can take place collapse stack information, but in fact by this module production, lead to a problem a plurality of collapse stack information of appearing, need face a large amount of repetitive problems during research and development personnel location problem, cause a large amount of manpower resources extravagant.
Disclosure of Invention
The invention mainly aims to provide a method, a device and a storage medium for aggregating collapsed stacks of application programs, and aims to solve the problems that when one problem of one application program occurs in the prior art, a plurality of collapsed stack information stacks are submitted to a problem management platform, and a large amount of repeated problems need to be faced when research and development personnel locate the problem, so that a large amount of human resources are wasted.
In order to achieve the above object, the present invention provides a method for aggregating collapsed stacks of an application, including the following steps:
acquiring collapse stack information of an application program;
removing repeated operation on the application program crash stack information to obtain first crash stack information;
performing feature extraction on the first collapse stack information to obtain a first collapse stack feature value;
performing aggregation matching by using the first collapse stack characteristic value and the second collapse stack characteristic value;
when the aggregation and matching of the first collapse stack characteristic value and the second collapse stack characteristic value are successful, aggregating the first collapse stack information to second collapse stack information corresponding to the second collapse stack characteristic value;
and when the aggregation and matching of the first crashed stack characteristic value and the second crashed stack characteristic value are unsuccessful, saving the first crashed stack information as the newly added second crashed stack information.
Optionally, the removing repeated operation of the application program crash stack information, and obtaining the first crash stack information is implemented by the following steps:
performing MD5 verification on the application program crash stack information to obtain an MD5 verification value;
and merging the crash stack information of the application programs with the same MD5 check value to obtain the first crash stack information.
Optionally, the feature extraction is performed on the first crash stack information, and includes the following steps:
splitting the first collapsed stack information according to lines to obtain split information;
reading a first item of the splitting information as a first text, and judging whether the first text contains a colon; if the colon is contained, the first text is segmented according to the colon, the left side of the colon is a crash type, and the right side of the colon is crash content; if the colon is not included, the first text is the crash type;
reading the next item of the splitting information as a second text, and carrying out inclusion judgment on the second text; when the second text contains the service code characteristics of the application program, acquiring the weight corresponding to the service code of the application program; when the second text contains a third-party dependent library code, acquiring a weight corresponding to the third-party dependent library code; when the second text contains the Android frame code, acquiring a weight corresponding to the Android frame code; and when the second text contains Java framework codes, acquiring weights corresponding to the Java framework codes.
Optionally, the first crash stack characteristic value and/or the second crash stack characteristic value comprises:
the crash type, the crash content, the weight;
the crash content includes:
the application program service code, the third party dependent library code, the Android frame code and the Java frame code;
the weights include:
the weight corresponding to the application program service code, the weight corresponding to the third-party dependent library code, the weight corresponding to the Android frame code and the weight corresponding to the Java frame code.
Optionally, the aggregating and matching are performed by using the first crash stack characteristic value and the second crash stack characteristic value, and the matching is performed by the following steps:
judging whether the crash type of the first crash stack characteristic value is the same as the crash type of the second crash stack characteristic value, if not, the aggregation matching fails; if the two are the same, continuing the subsequent matching step;
judging whether the crash content of the first crash stack characteristic value is the same as the crash content of the second crash stack characteristic value line by line; if so, identifying that the crash content of the first crash stack characteristic value is successfully matched; if not, identifying that the crash content matching of the first crash stack characteristic value fails;
accumulating the weight corresponding to the crash content of the first crash stack characteristic value to obtain a denominator; accumulating the weight corresponding to the collapse content of the first collapse stack characteristic value which is identified as being successfully matched to obtain a molecule;
dividing the numerator by the denominator to obtain a weight matching value, and judging that the aggregation matching of the first collapse stack characteristic value and the second collapse stack characteristic value is successful when the weight matching value is larger than a preset value; and when the weight matching value is smaller than or equal to the preset value, judging that the aggregation matching between the first collapse stack characteristic value and the second collapse stack characteristic value fails.
Optionally, the second crash stack characteristic value comprises the crash type, the crash content, the weight, and is managed through manual configuration.
Optionally, the method further comprises the steps of:
the first collapse stack characteristic value and the second collapse stack characteristic value are subjected to aggregation matching one by one;
when the first collapse stack characteristic value is successfully aggregated and matched with 1 second collapse stack characteristic value, the first collapse stack characteristic value is not aggregated and matched with other second collapse stack characteristic values;
and when the aggregation matching of the first crash characteristic value and all the second crash stack characteristic values fails, identifying that the aggregation matching of the first crash characteristic value fails.
Optionally, the method further comprises the steps of:
the first collapse stack characteristic value and the second collapse stack characteristic value are subjected to aggregation matching one by one;
when the first crash stack characteristic value is successfully aggregated and matched with more than or equal to 1 second crash stack characteristic value, identifying that the aggregation and matching of the second crash stack characteristic value with the maximum weight matching value and the first crash stack characteristic value are successful;
and when the aggregation matching of the first crash characteristic value and all the second crash stack characteristic values fails, identifying that the aggregation matching of the first crash characteristic value fails.
In addition, to achieve the above object, the present invention further provides an apparatus for aggregating application crash stacks, including:
the acquiring unit is used for acquiring the crash stack information of the application program;
the duplication removing unit is used for performing duplication removing operation on the application program crash stack information to obtain first crash stack information;
the extracting unit is used for extracting the characteristics of the first collapsed stack information to obtain a first collapsed stack characteristic value;
the matching unit is used for performing aggregation matching by using the first collapse stack characteristic value and the second collapse stack characteristic value;
the aggregation unit is used for aggregating the first crash stack information to second crash stack information corresponding to the second crash stack characteristic value when the first crash stack characteristic value and the second crash stack characteristic value are successfully aggregated and matched; and the second crash stack information storage unit is further configured to, when the first crash stack characteristic value and the second crash stack characteristic value are unsuccessfully aggregated and matched, store the first crash stack information as the newly added second crash stack information.
Furthermore, to achieve the above object, the present invention further provides an electronic device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the method for application crash stack aggregation as described above when executing the computer program.
Furthermore, to achieve the above object, the present invention further proposes a computer readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the method for application crash stack aggregation as described above.
The method comprises the steps of extracting features of collapse stack information of an application program, configuring different weights for different feature values, and then matching by using the feature values; and aggregating the crash stack information of the application program with successfully matched characteristic value weight. The accuracy of the information aggregation of the application collapse stack of the problem management platform is improved, the difficulty of problem positioning of research and development personnel is effectively reduced, and the time of problem positioning of the research and development personnel is shortened.
Drawings
FIG. 1 is a flowchart illustrating a method for stack crash aggregation of an application according to the present invention.
FIG. 2 is a schematic diagram of a process of extracting crash stack feature values according to the present invention.
FIG. 3 is a diagram illustrating the contents of a crash stack of an application according to the present invention.
FIG. 4 is a flowchart illustrating aggregation and matching of crash stack characteristic values according to the present invention.
FIG. 5 is another flow chart illustrating aggregation matching of crash stack characteristic values according to the present invention.
FIG. 6 is another flow chart illustrating aggregation matching of crash stack characteristic values according to the present invention.
FIG. 7 is a block diagram of an embodiment of an application crash stack aggregation apparatus.
Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
In order to make the technical problems, technical solutions and advantageous effects to be solved by the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
In one embodiment, as shown in fig. 1, the present invention provides a method for stack aggregation in application crash, the method comprising:
In the embodiment of the application, when an application, such as an Android APP program, has a problem in an operation process, different devices all generate collapse stack information. A single piece of crash stack information is reported to the server, and the server stores the crash stack information in a database, such as an Ali cloud log service (SLS). And the crash stack management platform acquires the crash stack information from the Alice cloud log service.
And 102, performing repeated removing operation on the application program crash stack information to obtain first crash stack information.
When the APP has a problem, single crash stack information is independently reported to the server. Taking a million-day-alive APP as an example, at least hundreds of times of collapse stack information reporting occur every day under an error rate of three ten-thousandth, and the development team cannot check the collapse stack information one by one. In order to avoid repeated work, the same crash stack information needs to be removed and repeated, and only one piece of crash stack information is saved.
And after the crash stack management platform acquires the crash stack information from the Alice cloud log service, performing MD5 verification on the crash stack information to generate an MD5 verification value. Comparing the MD5 check value with the MD5 check value of the saved crash stack information in the crash stack management platform, if the same MD5 check value exists, indicating that the crash stack information is a repeated record, and directly discarding the crash stack information without saving the crash stack information acquired from the Ali cloud log service to the crash stack management platform; if the same MD5 check value does not exist, the crash stack information is not a repeated record and needs to be saved to a crash stack management platform, and meanwhile, the corresponding MD5 check value is saved.
| Serial number | Corrupted stack information | MD5 |
| 1 | duapp.crash | f2944ef100f8cbf3b69891e75b67c183 |
In order to avoid repeated work when research personnel locate problems, the influence of code problems needs to be objectively judged, and collapse stack information needs to be aggregated. And aggregating the collapse stack information caused by the same problem, and calculating the occurrence frequency of the problem and the number of the affected devices, thereby judging the grade of the problem. When the collapsed stack information is aggregated, the stack characteristic value of the collapsed stack information needs to be extracted, and then the collapsed stack information is aggregated by using the stack characteristic value.
The characteristic value of the crash stack information stack (the characteristic value of the crash stack) is configured to the crash stack management platform in a manual configuration mode. The crash stack characteristic values include: crash type, crash content, weight.
The types of collapse are mainly:
1) null pointer (NullPointerException)
2) Type conversion exception (ClassCastException)
3) Subscript out-of-bounds exception (IndexOutOfBoundsException)
4) No anomaly found (Activity NotFoundException Activity)
5) Illegal State Exception (IllegalStateException)
6) Array out-of-bounds exception (ArrayIndexOutOfBoundsException)
7) Security exception (SecurityException)
8) Service unregistered Exception (IllegalArgumentException: Service not registered)
The specific crash type can be added or deleted in the crash stack management platform according to the service requirement.
The crash contents mainly include: the system comprises application program service codes, third-party dependent library codes, Android frame codes and Java frame codes.
The application business codes, the third-party dependent library codes, the Android framework codes and the Java framework codes are all managed by adopting manual configuration, for example, the package names of the company business codes comprise duapp, the third-party dependent library comprises xxx. And respectively configuring the contents including the keywords of the application program service code, the third-party dependent library code, the Android frame code and the Java frame code in a crash stack management platform in a manual configuration mode. With the continuous update of the application program, the keyword corresponding to the crash content also needs to be continuously updated.
Each crash content has a corresponding weight, which is manually configured. In the weight configuration, the following rules are suggested for configuration: the application service code > third-party dependent library > Android framework > Java framework, and the four types can be independently configured with weights. The following weight configuration modes:
an internal class is the content in the application service code, a class defined primarily for implementing services. Such as Java class, CallBackRecord class.
Extracting the characteristic value of the crash stack is realized by the following steps, as shown in fig. 2:
After the crash stack management platform obtains the non-repeated crash stack information, text analysis is performed on the crash stack information (such as a duapp. crash stack information file), contents in the crash stack information are obtained line by line, then each obtained line of text contents is stored in an array or a queue or a database, and a specific storage mode is not limited. In this embodiment, each line of text content is saved in an array.
The crash stack governance platform acquires a line of text information from the first item in the array, such as: "java. lang. NullPointerException: Attempt to invoke virtual method". Then judging whether the text contains colon, if yes, using colon as a segmentation character to segment, and storing the content on the left side of colon as a crash type, such as java, lang, NullPointerException; the content to the right of the colon is saved as collapsed content, such as Attempt to invoke virtual method.
If the text information obtained in the first item includes: "java. lang. nullpointerexception". And if no colon is included, the whole text information is saved as a crash type, such as java.
The information after splitting the crash stack information is shown in FIG. 3.
And the crash stack management platform reads the text contents item by item from the second item in the array, and judges the read text contents. The judgment is carried out in the following order:
a. judging whether the document content contains a keyword corresponding to the application program service code, if so, identifying the text content as the application program service code, and acquiring the weight corresponding to the application program service code; if not, continuing the subsequent judgment.
The content of the text is such that,
such as: at com … duapp … LoaderHelper … $2.run (LoaderHelper. java:50)
b. Judging whether the document content contains a keyword corresponding to a third-party dependent library code, if so, identifying the text content as the third-party dependent library code, and acquiring the weight corresponding to the third-party dependent library code; if not, continuing the subsequent judgment.
The content of the text is such that,
such as: at com … xxx. xxx … onPreDraw (OneShoPterDrawListener. java:94)
c. Judging whether the document content contains keywords corresponding to the Android frame codes, if so, identifying the text content as the Android frame codes, and acquiring weights corresponding to the Android frame codes; if not, continuing the subsequent judgment.
The content of the text is such that,
such as: view, chord graphics $ … run (chord graphics java 1078)
d. Judging whether the document content contains keywords corresponding to Java frame codes, if so, identifying the text content as the Java frame codes, and acquiring weights corresponding to the Java frame codes; if not, the judgment is ended.
Text content, such as: lang, reflection, method, invoke (method, java)
For the content of the text, it is,
such as at com … duapp … loader helper … $2.run (loader helper. java: 50). The parenthesis part is removed and then the node $ symbol gets the inner class LoaderHelper.
And 104, performing aggregation matching by using the first crash stack characteristic value and the second crash stack characteristic value.
After the stack characteristic value containing the weight is extracted from the collapse stack information, a matching calculation algorithm is operated, so that whether the current collapse stack information is a problem existing in a collapse stack management platform or a newly generated problem is obtained.
The crash stack feature value aggregation matching algorithm flow is shown in fig. 4, and includes the following steps:
And after the collapse stack management platform extracts the characteristic value of the collapse stack information New, the collapse stack management platform takes out the collapse stack information corresponding to the existing problems from the database one by one to judge the collapse type. If the crash type of the crash stack information New is the same as that of the existing crash stack information A, continuing the subsequent matching step; if the crash types are different, the next existing crash stack information B is obtained, and then the crash type is judged until an existing crash stack information with the same crash type is found or all the existing crash stack information without the existing crash stack information with the same crash type is traversed.
If the crash types of an existing crash stack information are found to be the same, such as the crash stack information B, the subsequent matching step is continued.
If all the existing crash stack information is traversed and no existing crash stack information with the same crash type exists, the aggregation of the crash stack information in the crash stack management platform fails, and the crash stack information needs to be saved in the crash stack management platform as a new problem. And distributing a unique identifier for the crash stack information, storing the extracted crash stack characteristic value and the MD5 check value into a crash stack management platform when storing the crash stack information, and associating the values with the crash stack information through the unique identifier.
And the crash stack management platform carries out one-by-one matching on the crash stack information New successfully matched with the crash types and the crash contents of the existing crash stack information B. If the crash contents are taken out one by one from the crash stack information New and then compared with the crash contents in the crash stack information B, if the same crash contents exist, the corresponding crash contents in the crash stack information New are identified to be successfully matched, if FindFlag is set to be 1, and the weight of the crash contents is acquired at the same time.
Crash stack information New
There is already crash stack information B
| Text content | Code type | Weight of |
| at com…duapp…LoaderHelper…$2.run | Application service code | 4 |
| at com…xxx.xxx…onPreDraw | Third party dependent library code | 3 |
| at android.view.Choreogragpher$…run | Android framework code | 2 |
| at java.lang.reflect.Method.invoke | |
1 |
And acquiring the weight value of each crash content from the crash stack information New, and then accumulating the weight values as denominators. For example, the denominator is: 4+3+2+1 equals 10.
And acquiring the weight value of each successfully matched crash content (namely the weight value corresponding to the FindFlag being 1) from the crash stack information New, and then accumulating the weight values to be used as a molecule. For example, the molecule is 4+2 ═ 6.
The method comprises the steps that a collapse stack management platform configures a weight matching value for collapse stack information of each collapse type, and when the collapse stack management platform performs aggregation matching on newly received collapse stack information, if the weight matching value obtained by a matching result is larger than the weight matching value set by the same collapse stack management platform, the collapse stack information and the existing collapse stack information of the collapse stack management platform are successfully aggregated and matched; otherwise, the aggregation matching failure of the crash stack information and the existing crash stack information of the crash stack management platform is shown.
If the crash type does not have a corresponding weight match value, the crash stack governance platform defaults to configure a weight value, such as 50%.
Weight matching value of existing crash stack information B:
| crash type | Weight match |
| Null pointer | |
| 50％ |
The weight matching value of the crash stack information New and the existing crash stack information B of the crash stack management platform is as follows: 6/10 is 60% greater than the weight match value of the collapsed stack information B by 50%. The matching of the newly received crash stack information and the existing crash stack information B of the crash stack management platform is successful.
When the crash stack management platform matches the characteristic values of the crash stack, matching is performed according to the flow shown in fig. 7, and the specific steps are as follows:
And after receiving the collapse stack information New, the collapse stack management platform acquires the collapse characteristic value of the collapse stack information New, and takes out one piece of collapse stack information and the collapse stack information New from the existing collapse stack information one by one for aggregation matching.
When the crash stack management platform uses the received crash stack information New and the existing crash stack information to perform aggregation matching, as long as one existing crash stack information is successfully matched with the crash stack information New, subsequent matching is not performed, and the aggregation matching of the crash stack information New and the existing crash stack information is identified to be successful.
And when the collapse stack management platform uses the received collapse stack information New to perform aggregation matching with the existing collapse stack information, if all the existing collapse stack information on the collapse stack management platform is not successfully aggregated and matched with the collapse stack information New, identifying that the collapse stack information New is failed in aggregation matching.
And 105, when the first crashing stack characteristic value and the second crashing stack characteristic value are successfully aggregated and matched, aggregating the first crashed stack information to second crashed stack information corresponding to the second crashed stack characteristic value.
If the aggregation matching between the crash stack information New and the existing crash stack information B of the crash stack management platform is successful, it indicates that the problem corresponding to the newly received crash stack information New and the problem corresponding to the existing crash stack information B of the crash stack management platform are the same problem, and the newly received crash stack information New needs to be aggregated into the existing crash stack information B of the crash stack management platform. Saving the relevant information in the crash stack information New to the crash stack information B, such as: device information, APP version information, problem generation time and the like.
And 105, when the first crashed stack characteristic value and the second crashed stack characteristic value are unsuccessfully aggregated and matched, saving the first crashed stack information as the newly added second crashed stack information.
After the aggregation matching of the crash stack information New fails, the crash stack management platform processes the crash stack information New as a New problem, allocates a unique identifier id to the crash stack information New, and then stores a crash stack information file, a crash stack characteristic value, an MD5 check value and other related information of the crash stack information New to the crash stack management platform. Other relevant information includes: device information, APP version information, problem generation time and the like.
In the embodiment, repeated record removing operation is performed on the crash stack information reported by the terminal, then the crash characteristic value is extracted, and aggregation is performed through the crash characteristic value and the existing crash stack information of the crash stack management platform. Through the technical scheme, the efficiency and the accuracy of the collapse stack information aggregation can be improved, and the time for the research and development personnel to position the problems is saved.
In one embodiment, FIG. 8 provides a flow chart of one implementation of the embodiment 104 of FIG. 1. The embodiment relates to a specific process for performing aggregation matching on a first collapsed stack characteristic value and a second collapsed stack characteristic value.
And after receiving the collapse stack information New, the collapse stack management platform acquires the collapse characteristic value of the collapse stack information New, and takes out one piece of collapse stack information and the collapse stack information New from the existing collapse stack information one by one for aggregation matching.
When the crash stack management platform uses the received crash stack information New and the existing crash stack information to perform aggregation matching, after the existing crash stack information and the crash stack information New are successfully matched, the weight matching value of the existing crash stack information is stored in a file or a database, and then the subsequent matching process is continued until all the existing crash stack information in the crash stack management platform is aggregated and matched with the received crash stack information New.
And if a plurality of pieces of existing crash stack information and the crash stack information New are successfully matched, identifying the existing crash stack information and the crash stack information New with the maximum matching weight value, and aggregating and matching successfully. If the matching of the plurality of pieces of existing crash stack information and the crash stack information New shown in the following table is successful, the aggregation matching of the existing crash stack information D and the crash stack information New is identified to be successful.
| Existing crash stack information | Weight match value |
| Collapsed stack information A | 50％ |
| Collapsed stack information B | 60％ |
| Collapsed stack information C | 55％ |
| Collapsed stack information D | 80％ |
And when the collapse stack management platform uses the received collapse stack information New to perform aggregation matching with the existing collapse stack information, if all the existing collapse stack information on the collapse stack management platform is not successfully aggregated and matched with the collapse stack information New, identifying that the collapse stack information New is failed in aggregation matching.
In this embodiment, after receiving the crash stack information, the crash stack management platform matches all existing crash stack information of the platform, and then selects an existing crash stack information with the largest weight matching value as a record of successful aggregation and matching with the received crash stack information. By the technical scheme, the accuracy of the aggregation of the crash stack information can be improved, the problem that different codes are scattered to reference the same code is avoided, the misjudgment caused by the line-by-line similarity judgment can be avoided, and different problems under the same package cannot be aggregated together.
In addition, an embodiment of the present invention further provides an application crash stack aggregation apparatus, and with reference to fig. 7, the application crash stack aggregation apparatus includes:
an obtaining unit 10, configured to obtain application crash stack information;
a duplicate removal unit 20, configured to perform duplicate removal operation on the application program crash stack information to obtain first crash stack information;
an extracting unit 30, configured to perform feature extraction on the first collapsed stack information to obtain a first collapsed stack feature value;
a matching unit 40, configured to perform aggregation matching using the first collapsed stack characteristic value and the second collapsed stack characteristic value;
an aggregating unit 50, configured to aggregate the first collapsed stack information to second collapsed stack information corresponding to the second collapsed stack characteristic value when the first collapsed stack characteristic value and the second collapsed stack characteristic value are successfully aggregated and matched; and the second crash stack information storage module is further configured to store the newly added second crash stack information when the first crash stack characteristic value and the second crash stack characteristic value are unsuccessfully aggregated and matched.
According to the technical scheme, the repeated record removing operation is carried out on the application program crash stack information reported by the terminal, then the crash characteristic value is extracted, and the information of the existing crash stack of the crash stack management platform is aggregated through the crash characteristic value. Through the technical scheme, the efficiency and the accuracy of the collapse stack information aggregation can be improved, and the time for the research and development personnel to position the problems is saved.
It should be noted that each unit in the apparatus may be configured to implement each step in the method, and achieve the corresponding technical effect, which is not described herein again.
Referring to fig. 8, fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
As shown in fig. 8, the electronic device may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include standard wired interfaces, wireless interfaces (e.g., WI-FI, 4G, 5G interfaces). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration shown in fig. 8 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 8, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and an application crash stack aggregation program.
In the electronic apparatus shown in fig. 8, the network interface 1004 is mainly used for data communication with an external network; the user interface 1003 is mainly used for receiving input instructions of a user; the electronic device calls, through the processor 1001, a vehicle device control program stored in the memory 1005, and performs the following operations:
acquiring collapse stack information of an application program;
removing repeated operation on the application program crash stack information to obtain first crash stack information;
performing feature extraction on the first collapse stack information to obtain a first collapse stack feature value;
performing aggregation matching by using the first collapse stack characteristic value and the second collapse stack characteristic value;
when the aggregation and matching of the first collapse stack characteristic value and the second collapse stack characteristic value are successful, aggregating the first collapse stack information to second collapse stack information corresponding to the second collapse stack characteristic value;
and when the aggregation and matching of the first crashed stack characteristic value and the second crashed stack characteristic value are unsuccessful, saving the first crashed stack information as the newly added second crashed stack information.
Optionally, the removing repeated operation of the application program crash stack information, and obtaining the first crash stack information is implemented by the following steps:
performing MD5 verification on the application program crash stack information to obtain an MD5 verification value;
and merging the crash stack information of the application programs with the same MD5 check value to obtain the first crash stack information.
Optionally, the feature extraction is performed on the first crash stack information, and includes the following steps:
splitting the first collapsed stack information according to lines to obtain split information;
reading a first item of the splitting information as a first text, and judging whether the first text contains a colon; if the colon is contained, the first text is segmented according to the colon, the left side of the colon is a crash type, and the right side of the colon is crash content; if the colon is not included, the first text is the crash type;
reading the next item of the splitting information as a second text, and carrying out inclusion judgment on the second text; when the second text contains the service code characteristics of the application program, acquiring the weight corresponding to the service code of the application program; when the second text contains a third-party dependent library code, acquiring a weight corresponding to the third-party dependent library code; when the second text contains the Android frame code, acquiring a weight corresponding to the Android frame code; and when the second text contains Java framework codes, acquiring weights corresponding to the Java framework codes.
Optionally, the first crash stack characteristic value and/or the second crash stack characteristic value comprises:
the crash type, the crash content, the weight;
the crash content includes:
the application program service code, the third party dependent library code, the Android frame code and the Java frame code;
the weights include:
the weight corresponding to the application program service code, the weight corresponding to the third-party dependent library code, the weight corresponding to the Android frame code and the weight corresponding to the Java frame code.
Optionally, the aggregating and matching are performed by using the first crash stack characteristic value and the second crash stack characteristic value, and the matching is performed by the following steps:
judging whether the crash type of the first crash stack characteristic value is the same as the crash type of the second crash stack characteristic value, if not, the aggregation matching fails; if the two are the same, continuing the subsequent matching step;
judging whether the crash content of the first crash stack characteristic value is the same as the crash content of the second crash stack characteristic value line by line; if so, identifying that the crash content of the first crash stack characteristic value is successfully matched; if not, identifying that the crash content matching of the first crash stack characteristic value fails;
accumulating the weight corresponding to the crash content of the first crash stack characteristic value to obtain a denominator; accumulating the weight corresponding to the collapse content of the first collapse stack characteristic value which is identified as being successfully matched to obtain a molecule;
dividing the numerator by the denominator to obtain a weight matching value, and judging that the aggregation matching of the first collapse stack characteristic value and the second collapse stack characteristic value is successful when the weight matching value is larger than a preset value; and when the weight matching value is smaller than or equal to the preset value, judging that the aggregation matching between the first collapse stack characteristic value and the second collapse stack characteristic value fails.
Optionally, the type of crash, the content of the crash, and the weight included in the second crash stack characteristic value are managed by manual configuration.
Optionally, the method further comprises the steps of:
the first collapse stack characteristic value and the second collapse stack characteristic value are subjected to aggregation matching one by one;
when the first collapse stack characteristic value is successfully aggregated and matched with 1 second collapse stack characteristic value, the first collapse stack characteristic value is not aggregated and matched with other second collapse stack characteristic values;
and when the aggregation matching of the first crash characteristic value and all the second crash stack characteristic values fails, identifying that the aggregation matching of the first crash characteristic value fails.
Optionally, the method further comprises the steps of:
the first collapse stack characteristic value and the second collapse stack characteristic value are subjected to aggregation matching one by one;
when the first crash stack characteristic value is successfully aggregated and matched with more than or equal to 1 second crash stack characteristic value, identifying that the aggregation and matching of the second crash stack characteristic value with the maximum weight matching value and the first crash stack characteristic value are successful;
and when the aggregation matching of the first crash characteristic value and all the second crash stack characteristic values fails, identifying that the aggregation matching of the first crash characteristic value fails.
According to the technical scheme, the repeated record removing operation is carried out on the application program crash stack information reported by the terminal, then the crash characteristic value is extracted, and the information of the existing crash stack of the crash stack management platform is aggregated through the crash characteristic value. Through the technical scheme, the efficiency and the accuracy of the collapse stack information aggregation can be improved, and the time for the research and development personnel to position the problems is saved.
Furthermore, an embodiment of the present invention further provides a computer-readable storage medium, on which a vehicle device control program is stored, where the vehicle device control program, when executed by a processor, implements the following operations:
acquiring collapse stack information of an application program;
removing repeated operation on the application program crash stack information to obtain first crash stack information;
performing feature extraction on the first collapse stack information to obtain a first collapse stack feature value;
performing aggregation matching by using the first collapse stack characteristic value and the second collapse stack characteristic value;
when the aggregation and matching of the first collapse stack characteristic value and the second collapse stack characteristic value are successful, aggregating the first collapse stack information to second collapse stack information corresponding to the second collapse stack characteristic value;
and when the aggregation and matching of the first crashed stack characteristic value and the second crashed stack characteristic value are unsuccessful, saving the first crashed stack information as the newly added second crashed stack information.
Optionally, the removing repeated operation of the application program crash stack information, and obtaining the first crash stack information is implemented by the following steps:
performing MD5 verification on the application program crash stack information to obtain an MD5 verification value;
and merging the crash stack information of the application programs with the same MD5 check value to obtain the first crash stack information.
Optionally, the feature extraction is performed on the first crash stack information, and includes the following steps:
splitting the first collapsed stack information according to lines to obtain split information;
reading a first item of the splitting information as a first text, and judging whether the first text contains a colon; if the colon is contained, the first text is segmented according to the colon, the left side of the colon is a crash type, and the right side of the colon is crash content; if the colon is not included, the first text is the crash type;
reading the next item of the splitting information as a second text, and carrying out inclusion judgment on the second text; when the second text contains the service code characteristics of the application program, acquiring the weight corresponding to the service code of the application program; when the second text contains a third-party dependent library code, acquiring a weight corresponding to the third-party dependent library code; when the second text contains the Android frame code, acquiring a weight corresponding to the Android frame code; and when the second text contains Java framework codes, acquiring weights corresponding to the Java framework codes.
Optionally, the first crash stack characteristic value and/or the second crash stack characteristic value comprises:
the crash type, the crash content, the weight;
the crash content includes:
the application program service code, the third party dependent library code, the Android frame code and the Java frame code;
the weights include:
the weight corresponding to the application program service code, the weight corresponding to the third-party dependent library code, the weight corresponding to the Android frame code and the weight corresponding to the Java frame code.
Optionally, the aggregating and matching are performed by using the first crash stack characteristic value and the second crash stack characteristic value, and the matching is performed by the following steps:
judging whether the crash type of the first crash stack characteristic value is the same as the crash type of the second crash stack characteristic value, if not, the aggregation matching fails; if the two are the same, continuing the subsequent matching step;
judging whether the crash content of the first crash stack characteristic value is the same as the crash content of the second crash stack characteristic value line by line; if so, identifying that the crash content of the first crash stack characteristic value is successfully matched; if not, identifying that the crash content matching of the first crash stack characteristic value fails;
accumulating the weight corresponding to the crash content of the first crash stack characteristic value to obtain a denominator; accumulating the weight corresponding to the collapse content of the first collapse stack characteristic value which is identified as being successfully matched to obtain a molecule;
dividing the numerator by the denominator to obtain a weight matching value, and judging that the aggregation matching of the first collapse stack characteristic value and the second collapse stack characteristic value is successful when the weight matching value is larger than a preset value; and when the weight matching value is smaller than or equal to the preset value, judging that the aggregation matching between the first collapse stack characteristic value and the second collapse stack characteristic value fails.
Optionally, the type of crash, the content of the crash, and the weight included in the second crash stack characteristic value are managed by manual configuration.
Optionally, the method further comprises the steps of:
the first collapse stack characteristic value and the second collapse stack characteristic value are subjected to aggregation matching one by one;
when the first collapse stack characteristic value is successfully aggregated and matched with 1 second collapse stack characteristic value, the first collapse stack characteristic value is not aggregated and matched with other second collapse stack characteristic values;
and when the aggregation matching of the first crash characteristic value and all the second crash stack characteristic values fails, identifying that the aggregation matching of the first crash characteristic value fails.
Optionally, the method further comprises the steps of:
the first collapse stack characteristic value and the second collapse stack characteristic value are subjected to aggregation matching one by one;
when the first crash stack characteristic value is successfully aggregated and matched with more than or equal to 1 second crash stack characteristic value, identifying that the aggregation and matching of the second crash stack characteristic value with the maximum weight matching value and the first crash stack characteristic value are successful;
and when the aggregation matching of the first crash characteristic value and all the second crash stack characteristic values fails, identifying that the aggregation matching of the first crash characteristic value fails.
According to the technical scheme, the repeated record removing operation is carried out on the application program crash stack information reported by the terminal, then the crash characteristic value is extracted, and the information of the existing crash stack of the crash stack management platform is aggregated through the crash characteristic value. Through the technical scheme, the efficiency and the accuracy of the collapse stack information aggregation can be improved, and the time for the research and development personnel to position the problems is saved.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, a controller, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (11)
1. A method for application crash stack aggregation, the method comprising the steps of:
acquiring collapse stack information of an application program;
removing repeated operation on the application program crash stack information to obtain first crash stack information;
performing feature extraction on the first collapse stack information to obtain a first collapse stack feature value;
performing aggregation matching by using the first collapse stack characteristic value and the second collapse stack characteristic value;
when the aggregation and matching of the first collapse stack characteristic value and the second collapse stack characteristic value are successful, aggregating the first collapse stack information to second collapse stack information corresponding to the second collapse stack characteristic value;
and when the aggregation and matching of the first crashed stack characteristic value and the second crashed stack characteristic value are unsuccessful, saving the first crashed stack information as the newly added second crashed stack information.
2. The method of claim 1, wherein the step of de-duplicating the application crash stack information to obtain the first crash stack information is performed by:
performing MD5 verification on the application program crash stack information to obtain an MD5 verification value;
and merging the crash stack information of the application programs with the same MD5 check value to obtain the first crash stack information.
3. The method of claim 1, wherein performing feature extraction on the first collapsed stack information comprises:
splitting the first collapsed stack information according to lines to obtain split information;
reading a first item of the splitting information as a first text, and judging whether the first text contains a colon; if the colon is contained, the first text is segmented according to the colon, the left side of the colon is a crash type, and the right side of the colon is crash content; if the colon is not included, the first text is the crash type;
reading the next item of the splitting information as a second text, and carrying out inclusion judgment on the second text; when the second text contains the service code characteristics of the application program, acquiring the weight corresponding to the service code of the application program; when the second text contains a third-party dependent library code, acquiring a weight corresponding to the third-party dependent library code; when the second text contains the Android frame code, acquiring a weight corresponding to the Android frame code; and when the second text contains Java framework codes, acquiring weights corresponding to the Java framework codes.
4. The method of claim 3, wherein the first crash stack characteristic value and/or the second crash stack characteristic value comprises:
the crash type, the crash content, the weight;
the crash content includes:
the application program service code, the third party dependent library code, the Android frame code and the Java frame code;
the weights include:
the weight corresponding to the application program service code, the weight corresponding to the third-party dependent library code, the weight corresponding to the Android frame code and the weight corresponding to the Java frame code.
5. The method of claim 4, wherein the aggregate matching using the first crash stack characteristic value and the second crash stack characteristic value is performed by:
judging whether the crash type of the first crash stack characteristic value is the same as the crash type of the second crash stack characteristic value, if not, the aggregation matching fails; if the two are the same, continuing the subsequent matching step;
judging whether the crash content of the first crash stack characteristic value is the same as the crash content of the second crash stack characteristic value line by line; if so, identifying that the crash content of the first crash stack characteristic value is successfully matched; if not, identifying that the crash content matching of the first crash stack characteristic value fails;
accumulating the weight corresponding to the crash content of the first crash stack characteristic value to obtain a denominator; accumulating the weight corresponding to the collapse content of the first collapse stack characteristic value which is identified as being successfully matched to obtain a molecule;
dividing the numerator by the denominator to obtain a weight matching value, and judging that the aggregation matching of the first collapse stack characteristic value and the second collapse stack characteristic value is successful when the weight matching value is larger than a preset value; and when the weight matching value is smaller than or equal to the preset value, judging that the aggregation matching between the first collapse stack characteristic value and the second collapse stack characteristic value fails.
6. The method of claim 4, wherein the second crash stack characteristic value comprises the type of crash, the content of the crash, and the weight managed through manual configuration.
7. The method of claim 5, further comprising the steps of:
the first collapse stack characteristic value and the second collapse stack characteristic value are subjected to aggregation matching one by one;
when the first collapse stack characteristic value is successfully aggregated and matched with 1 second collapse stack characteristic value, the first collapse stack characteristic value is not aggregated and matched with other second collapse stack characteristic values;
and when the aggregation matching of the first crash characteristic value and all the second crash stack characteristic values fails, identifying that the aggregation matching of the first crash characteristic value fails.
8. The method of claim 5, further comprising the steps of:
the first collapse stack characteristic value and the second collapse stack characteristic value are subjected to aggregation matching one by one;
when the first crash stack characteristic value is successfully aggregated and matched with more than or equal to 1 second crash stack characteristic value, identifying that the aggregation and matching of the second crash stack characteristic value with the maximum weight matching value and the first crash stack characteristic value are successful;
and when the aggregation matching of the first crash characteristic value and all the second crash stack characteristic values fails, identifying that the aggregation matching of the first crash characteristic value fails.
9. An application crash stack aggregation apparatus, the apparatus comprising:
the acquiring unit is used for acquiring the crash stack information of the application program;
the duplication removing unit is used for performing duplication removing operation on the application program crash stack information to obtain first crash stack information;
the extracting unit is used for extracting the characteristics of the first collapsed stack information to obtain a first collapsed stack characteristic value;
the matching unit is used for performing aggregation matching by using the first collapse stack characteristic value and the second collapse stack characteristic value;
the aggregation unit is used for aggregating the first crash stack information to second crash stack information corresponding to the second crash stack characteristic value when the first crash stack characteristic value and the second crash stack characteristic value are successfully aggregated and matched; and the second crash stack information storage unit is further configured to, when the first crash stack characteristic value and the second crash stack characteristic value are unsuccessfully aggregated and matched, store the first crash stack information as the newly added second crash stack information.
10. An electronic device, characterized in that the electronic device comprises: memory, a processor and an application crash stack aggregation program stored on the memory and operable on the processor, the application crash stack aggregation program being configured to implement the steps of the method of application crash stack aggregation according to any of claims 1 to 8.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method for application crash stack aggregation according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110869019.XA CN113590188A (en) | 2021-07-30 | 2021-07-30 | Method, device and storage medium for application program crash stack aggregation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110869019.XA CN113590188A (en) | 2021-07-30 | 2021-07-30 | Method, device and storage medium for application program crash stack aggregation |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113590188A true CN113590188A (en) | 2021-11-02 |
Family
ID=78252274
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110869019.XA Pending CN113590188A (en) | 2021-07-30 | 2021-07-30 | Method, device and storage medium for application program crash stack aggregation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113590188A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110489345A (en) * | 2019-08-08 | 2019-11-22 | 北京字节跳动网络技术有限公司 | A kind of collapse polymerization, device, medium and equipment |
| WO2021036453A1 (en) * | 2019-08-28 | 2021-03-04 | 苏宁云计算有限公司 | Method and device for user identification, and computer device |
| CN113127320A (en) * | 2021-04-08 | 2021-07-16 | 支付宝(杭州)信息技术有限公司 | Application program abnormity detection method, device, equipment and system |
-
2021
- 2021-07-30 CN CN202110869019.XA patent/CN113590188A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110489345A (en) * | 2019-08-08 | 2019-11-22 | 北京字节跳动网络技术有限公司 | A kind of collapse polymerization, device, medium and equipment |
| WO2021036453A1 (en) * | 2019-08-28 | 2021-03-04 | 苏宁云计算有限公司 | Method and device for user identification, and computer device |
| CN113127320A (en) * | 2021-04-08 | 2021-07-16 | 支付宝(杭州)信息技术有限公司 | Application program abnormity detection method, device, equipment and system |
Non-Patent Citations (1)
| Title |
|---|
| 任君兰;曹浩;司吉兵;: "基于堆栈稀疏自编码器的齿轮箱故障诊断", 制造技术与机床, no. 05, pages 35 - 39 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109947789B (en) | Method, device, computer equipment and storage medium for processing data of multiple databases | |
| CN110347560B (en) | Method, device, system, equipment and medium for prompting abnormity of big data product | |
| CN111290916B (en) | Big data monitoring method, device and equipment and computer readable storage medium | |
| CN111240876B (en) | Fault positioning method and device for micro-service, storage medium and terminal | |
| CN111190551B (en) | Redis data migration system, migration method, migration device and terminal | |
| CN113420537B (en) | Method, device, equipment and storage medium for processing electronic form data | |
| CN108694108B (en) | iOS crash data classification and statistics method and device | |
| CN109445768B (en) | Database script generation method and device, computer equipment and storage medium | |
| CN110688096A (en) | Method, device, medium and electronic equipment for constructing application program containing plug-in | |
| US9390073B2 (en) | Electronic file comparator | |
| CN112328631A (en) | Production fault analysis method and device, electronic equipment and storage medium | |
| CN112256517B (en) | Log analysis method and device of virtualization platform based on LSTM-DSSM | |
| CN110688305A (en) | Test environment synchronization method, device, medium and electronic equipment | |
| CN111538542B (en) | System configuration method and related device | |
| CN110727565B (en) | Network equipment platform information collection method and system | |
| CN109597702B (en) | Root cause analysis method, device, equipment and storage medium for message bus abnormity | |
| CN113590188A (en) | Method, device and storage medium for application program crash stack aggregation | |
| CN113094088A (en) | Database configuration information acquisition method and device, computer equipment and storage medium | |
| CN113468076A (en) | Application program exception testing method, device, equipment and storage medium | |
| CN110737707A (en) | Multi-system log searching method and device and computer readable storage medium | |
| CN106776704A (en) | Statistical information collection method and device | |
| CN113110870A (en) | Resource packaging management method, device, equipment and storage medium | |
| CN110674119A (en) | Data processing method, system and computer readable storage medium | |
| CN113591980A (en) | Application program crash stack assignment method, device and storage medium | |
| CN115794788A (en) | Data deduplication method, device, equipment 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 |