CN114816415A - Method and system for packet manager to analyze third-party dependence based on maven architecture - Google Patents
Method and system for packet manager to analyze third-party dependence based on maven architecture Download PDFInfo
- Publication number
- CN114816415A CN114816415A CN202210335645.5A CN202210335645A CN114816415A CN 114816415 A CN114816415 A CN 114816415A CN 202210335645 A CN202210335645 A CN 202210335645A CN 114816415 A CN114816415 A CN 114816415A
- Authority
- CN
- China
- Prior art keywords
- analysis
- dependency
- pom
- command
- module
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/43—Checking; Contextual analysis
- G06F8/433—Dependency analysis; Data or control flow analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/577—Assessing vulnerabilities and evaluating computer system security
-
- 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/75—Structural analysis for program understanding
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/03—Indexing scheme relating to G06F21/50, monitoring users, programs or devices to maintain the integrity of platforms
- G06F2221/033—Test or assess software
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method and a system for analyzing third-party dependence by a packet manager based on a maven architecture, wherein the method comprises the following steps: analyzing the dependency relationship of each third-party component in the project by adopting a dependency analysis command, if the current analysis command cannot be continuously executed due to the occurrence of an abnormal condition, if the current analysis command is directly dependent and abnormal, eliminating the direct dependency relationship list to ensure that the analysis work can be continuously executed, if the current analysis command is indirectly dependent and abnormal, separating and analyzing each dependency relationship list independently, then eliminating analysis failure, combining analysis success and then carrying out comprehensive analysis, wherein the comprehensive analysis result and the eliminated direct dependency information are the analysis result to be obtained; by the method, the correctness of the analysis result can be effectively ensured, and when the analysis process is abnormal, a countermeasure can be timely taken for the abnormality, so that the analysis process can be continuously executed, and the defect of depending on the analysis command in the packet manager is effectively overcome.
Description
Technical Field
The invention relates to the technical field of analysis of third-party dependency components of software projects, in particular to a method and a system for analyzing third-party dependency by a packet manager based on a maven architecture.
Background
Software project development is a systematic project, each software project uses a plurality of source code components, and in order to effectively improve software development efficiency, most of the software development nowadays uses existing open source components, however, although the software development efficiency is improved, the open source components also bring more risk vulnerabilities to the software project, and therefore open source components in the software project, namely, third-party dependence, need to be detected.
Currently, in the market, a Software Composition Analysis (SCA) tool is generally used to analyze third-party component components in a project and display information such as vulnerabilities and permissions of the component components. How to find out a third party dependent component in an item and application is directed to the item with a package manager, such as the package manager maven in java language, the package manager npm in gradle, js language. Generally, the information that the third party depends on is obtained by executing the command of the packet manager, but the analysis is performed by directly using the command of the packet manager, so that many limitations and defects exist, for example, in the execution process of the analysis command of the existing packet manager, if an unknown error occurs in a certain dependency, the whole analysis process cannot be continuously executed, a corresponding analysis result cannot be given, and it is inconvenient to find the dependent component in which the error occurs, but the accuracy is difficult to guarantee if the dependent component is analyzed in other ways without using the command analysis of the packet manager. Therefore, under the condition of ensuring the third party dependence of correct analysis, the method can solve the limitation and defect caused by the command line.
Disclosure of Invention
The invention aims to provide a method and a system for analyzing third-party dependence by a packet manager based on a maven architecture, which can not only effectively ensure that third-party dependence is accurately analyzed, but also solve the problem of abnormity in the existing command analysis process.
In order to achieve the above object, the present invention discloses a method for a packet manager to resolve third party dependencies based on a maven architecture, which comprises:
analyzing a dependency relationship list in a total pom file under the current project through a dependency analysis command in a package manager based on a maven architecture, and monitoring the analysis process in real time;
when error information occurs in the analysis process, judging whether the error information is directly dependent, if so, removing a dependency relationship list corresponding to the error information from the pom file; if not, separating all the dependency relationship lists in the total pom files under the current project, and respectively and independently storing to generate a plurality of temporary pom files with single dependency relationship lists;
analyzing each temporary pom file separately through the dependency analysis command, if the analysis is successful, recording the analysis success information, and if the analysis is failed, rejecting the dependency relationship list;
merging a plurality of temporary pom files which are analyzed successfully independently to generate a new comprehensive pom file;
and adopting the dependent parsing command to comprehensively parse the comprehensive pom file and recording a parsing result.
Preferably, in the process of monitoring the analysis process, if the same piece of downloaded information stays beyond a preset value, the execution of the current dependent analysis command is interrupted, all dependency relationship lists in the total pom file under the current project are separated and stored separately, so as to generate a plurality of temporary pom files with single dependency relationship lists;
analyzing each temporary pom file through the dependency analysis command, if the analysis is successful, recording analysis success information, and if the analysis is failed, removing the dependency relationship list;
merging a plurality of temporary pom files which are analyzed successfully independently to generate a new comprehensive pom file;
and adopting the dependent parsing command to comprehensively parse the comprehensive pom file and recording a parsing result.
Preferably, the number of the removed dependency relationship lists is accumulated and recorded, if the number of the removed dependency relationship lists exceeds a preset value, the execution of the current dependent analysis command is interrupted, and the temporary pom files which are successfully analyzed independently are merged to generate a new comprehensive pom file;
and adopting the dependent parsing command to comprehensively parse the comprehensive pom file and recording a parsing result.
Preferably, the execution process of the dependent parsing command is monitored through a log file to record the parsing process information.
The invention also discloses a system for analyzing the third-party dependence by the packet manager based on the maven architecture, which comprises an analyzing module, a monitoring module, a first processing module, a second processing module and a merging module;
the analysis module is used for analyzing a dependency relationship list in the pom file under the current project through a dependency analysis command in the package manager based on the maven architecture;
the monitoring module is used for monitoring the analysis process of the analysis module in real time;
the first processing module is used for removing the dependency relationship list corresponding to the error information from the pom file when the error occurs in the execution process of the analysis module and the error information comes from direct dependency;
the second processing module is used for separating all the dependency relationship lists in the total pom files under the current project and respectively and independently storing the dependency relationship lists when an error occurs in the execution process of the analysis module and the error information comes from indirect dependency so as to generate a plurality of temporary pom files with single dependency relationship lists;
and the merging module is used for merging the temporary pom files which are successfully analyzed independently to generate a new comprehensive pom file.
Preferably, the system further comprises a third processing module, and the third processing module is configured to, in the process of monitoring the analysis process through the monitoring module, interrupt execution of the current dependent analysis command if the same piece of downloaded information stays beyond a preset value, and call the second processing module and the merging module to process the current item.
Preferably, the system further comprises a counting module, wherein the counting module is used for performing accumulation recording on the number of the removed dependency relationship lists; and if the number recorded by the counting module exceeds a preset value, interrupting the execution of the current interrupted dependent analysis command, and calling the second processing module and the merging module to process the current item.
Preferably, the monitoring module monitors an execution process of the dependent parsing command through a log file to record parsing process information.
The invention also discloses a system for analyzing the third-party dependence by the packet manager based on the maven architecture, which particularly comprises the following steps:
one or more processors;
a memory;
and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the programs comprising instructions for performing the method for a maven architecture based package manager to resolve third party dependencies as described above.
The present invention also discloses a computer readable storage medium comprising a computer program executable by a processor to perform the method for a maven architecture based packet manager to resolve third party dependencies as described above.
Compared with the prior art, the method for analyzing the third-party dependence by the package manager adopts the dependence analysis command in the package manager to analyze the dependence relationship of each third-party component in the project, when the current analysis command cannot be continuously executed due to the occurrence of abnormal conditions in the analysis process, if the current analysis command is directly dependent and abnormal, the direct dependence relationship list can be removed, so that the analysis work can be continuously executed, if the indirect dependence is abnormal, each dependence relationship list is separated and analyzed independently, then the analysis failure is removed, the analysis success is combined and is comprehensively analyzed, and the comprehensive analysis result and the removed direct dependence information are the analysis result to be obtained; therefore, by the method, the correctness of the analysis result can be effectively ensured, when the analysis process is abnormal, corresponding treatment measures can be timely taken for the abnormality, the abnormal dependency information lists are removed one by one, the analysis process can be continuously executed, and the defect of the dependency analysis command in the packet manager is effectively overcome.
Drawings
FIG. 1 is a flowchart of a method for a packet manager to resolve third party dependencies in an embodiment of the invention.
Detailed Description
In order to explain technical contents, structural features, and objects and effects of the present invention in detail, the following detailed description is given with reference to the accompanying drawings in conjunction with the embodiments.
The embodiment discloses a method for analyzing a third party dependency by a packet manager based on a maven architecture, which is used for analyzing the third party dependency (open source component) in a project for software development based on the maven architecture.
In the prior art, to ensure the correctness of the third-party dependent parsing, a pom file in a project is parsed by a dependent parsing command (mvn dependency: tree) of a package manager, where the pom file is information of third-party dependency used for recording a current project, and is generally inside a tag of dependencies, each dependency (hereinafter, abbreviated as dy) inside the tag is a dependency list, but only directly depends on the dependency, and the dy may also depend on other dependency information, which is also configured by a pom file, that is, in a root directory in a project, there is a total pom file, which records all direct dependency information under the project, and in each module in the project, there is a pom file that records indirect dependency information.
The execution process of the dependent parsing command is as follows:
the method comprises the steps of firstly analyzing a first dy, then downloading a pom file and a jar package of indirect dependence needed by the first dy, then traversing in sequence, finally analyzing all dependence of the first dy, then sequentially solving a second dy to obtain all dependence information of the second dy, and similarly obtaining all the dependence information of the dy, and then removing repeated dependence through a maven package manager mechanism (for example, the indirect dependence of the first dependency dependence is the same as that of the second dependency but different in version, and at this time, the repetition is removed according to the priority and the dependence level, which is a rule of the maven dependency management).
It is worth noting that each time the indirect dependency is analyzed, the pom file and jar package of the indirect dependency are downloaded from the warehouse, at this time, if the pom file and jar package cannot be downloaded, the jam is waited for all the time, and after waiting for several minutes, if the pom file and jar package cannot be downloaded, the whole command execution fails, and the user cannot obtain any analysis information, so that the command analysis efficiency is low. To solve this problem, as shown in fig. 1, the method for the packet manager to resolve the third-party dependency in this embodiment includes the following steps:
s1: analyzing a dependency relationship list in a total pom file under the current project through a dependency analysis command in a package manager based on a maven architecture, and monitoring the analysis process in real time;
s2: when error information occurs in the analysis process, judging whether the error information comes from direct dependence, if so, entering S3, and if not, entering S4;
s3: removing the dependency relationship list corresponding to the error information from the pom file;
s4: separating all dependency relationship lists in the total pom files under the current project, and respectively and independently storing the dependency relationship lists to generate a plurality of temporary pom files with single dependency relationship lists;
s5: analyzing each temporary pom file separately through a dependent analysis command, if the analysis is successful, recording analysis success information, and if the analysis is failed, rejecting the dependent relationship list;
s6: merging a plurality of temporary pom files which are analyzed successfully independently to generate a new comprehensive pom file;
s7: and comprehensively analyzing the comprehensive pom file by adopting the dependent analysis command, and recording an analysis result.
By the method for analyzing the third-party dependence through the package manager, the dependence relationship of each third-party component in the project is analyzed by adopting the dependence analysis command in the package manager, so that the accuracy of the analysis result is effectively ensured. And when the current analysis command cannot be continuously executed due to the occurrence of abnormal conditions in the analysis process, if the current analysis command is directly dependent abnormally, the direct dependency relationship list can be removed, so that the analysis work can be continuously executed, if the current analysis command is indirectly dependent abnormally, each dependency relationship list is separated and analyzed independently, then the analysis is failed to be removed, the analysis is successfully combined for comprehensive analysis, and the comprehensive analysis result and the removed direct dependency information are the analysis result to be obtained. Therefore, when the analysis process is abnormal, the method can take a measure for dealing with the abnormality in time, and remove the abnormal dependency information list one by one, so that the analysis process can be continuously executed, thereby effectively solving the defect of the dependency analysis command in the packet manager.
In the command line execution process, on the premise that no error information occurs, if the same piece of download information stays beyond a preset value and indicates that the current direct dependency-dependent pom package and jar package cannot be downloaded, the same countermeasure as that when the indirect dependency is abnormal is executed, namely the execution of the current dependency analysis command is interrupted, all dependency lists in the total pom file under the current project are separated and stored separately to generate a plurality of temporary pom files of a single dependency list, each temporary pom file is analyzed through the dependency analysis command, if the analysis is successful, the analysis success information is recorded, and if the analysis is failed, the dependency list is removed. Then, the temporary pom files that are successfully parsed individually are merged to generate a new comprehensive pom file. And finally, comprehensively analyzing the comprehensive pom file by adopting the dependent analysis command, and recording an analysis result.
Normally, the command line resolution of a project is definitely related to the environment if there are 5 compilation failures, for example, the project cannot be connected with an external network or configuration information is wrong, and the follow-up dependence does not need to be processed in time. Therefore, in another preferred embodiment of the method for the packet manager to analyze the third party dependency, the number of the removed dependency lists is recorded in an accumulated manner, if the number of the removed dependency lists exceeds a preset value, for example, five dependency lists, the execution of the current dependent analysis command is interrupted, the temporary pom files which are analyzed successfully individually are merged to generate a new comprehensive pom file, the comprehensive analysis is performed on the comprehensive pom file by using the dependent analysis command, and the analysis result is recorded.
Furthermore, the execution process of the dependent parsing command is monitored through the log file to record the parsing process information.
The invention also discloses a system for analyzing the third-party dependence by the packet manager based on the maven architecture, which particularly comprises an analyzing module, a monitoring module, a first processing module, a second processing module and a merging module.
And the analysis module is used for analyzing the dependency relationship list in the pom file under the current project through a dependency analysis command in the package manager based on the maven architecture.
And the monitoring module is used for monitoring the analysis process of the analysis module in real time.
And the first processing module is used for removing the dependency relationship list corresponding to the error information from the pom file when the error occurs in the execution process of the analysis module and the error information comes from direct dependency.
And the second processing module is used for separating all the dependency relationship lists in the total pom files under the current project and respectively and independently storing the dependency relationship lists when an error occurs in the execution process of the analysis module and the error information comes from indirect dependency so as to generate a plurality of temporary pom files with single dependency relationship lists.
And the merging module is used for merging the temporary pom files which are successfully analyzed independently to generate a new comprehensive pom file.
Furthermore, the system further comprises a third processing module, wherein the third processing module is configured to interrupt execution of the current dependent parsing command and call the second processing module and the merging module to process the current item if the same piece of downloaded information stays beyond a preset value in the process of monitoring the parsing process through the monitoring module.
Furthermore, the system also comprises a counting module, wherein the counting module is used for accumulating and recording the number of the removed dependency relationship lists; and if the number recorded by the counting module exceeds a preset value, interrupting the execution of the current interrupted dependent analysis command, and calling a second processing module and a merging module to process the current item.
Further, the monitoring module monitors the execution process of the dependent parsing command through the log file to record the parsing process information.
The present invention also discloses another system for a package manager to resolve third party dependencies, comprising one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the programs comprising instructions for performing the method for a package manager to resolve third party dependencies as described above. The processor may be a general-purpose Central Processing Unit (CPU), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement functions that the packet manager in the embodiment of the present Application needs to perform in analyzing the module in the system that the third party depends on, or to execute the method that the packet manager in the embodiment of the present Application analyzes the third party dependence.
The present invention also discloses a computer readable storage medium comprising a computer program executable by a processor to perform a method for a package manager to resolve third party dependencies as described above. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a read-only memory (ROM), or a Random Access Memory (RAM), or a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, a magnetic disk, or an optical medium, such as a Digital Versatile Disk (DVD), or a semiconductor medium, such as a Solid State Disk (SSD).
The embodiment of the application also discloses a computer program product or a computer program, which comprises computer instructions, and the computer instructions are stored in a computer readable storage medium. The processor of the electronic device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, so that the electronic device executes the method for resolving the third-party dependency by the package manager.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the scope of the present invention, therefore, the present invention is not limited by the appended claims.
Claims (10)
1. A method for a packet manager to resolve third party dependencies based on a maven architecture is characterized by comprising the following steps:
analyzing a dependency relationship list in a total pom file under the current project through a dependency analysis command in a package manager based on a maven architecture, and monitoring the analysis process in real time;
when error information occurs in the analysis process, judging whether the error information is directly dependent, if so, removing a dependency relationship list corresponding to the error information from the pom file; if not, separating all the dependency relationship lists in the total pom files under the current project, and respectively and independently storing to generate a plurality of temporary pom files with single dependency relationship lists;
analyzing each temporary pom file separately through the dependency analysis command, if the analysis is successful, recording the analysis success information, and if the analysis is failed, rejecting the dependency relationship list;
merging a plurality of temporary pom files which are analyzed successfully independently to generate a new comprehensive pom file;
and adopting the dependent parsing command to comprehensively parse the comprehensive pom file and recording a parsing result.
2. The method for analyzing the third party dependence of the package manager based on the maven architecture as claimed in claim 1, wherein in the process of monitoring the analyzing process, if the same piece of downloaded information stays beyond a preset value, the execution of the current dependence analyzing command is interrupted, and all the dependence relationship lists in the total pom file under the current project are separated and stored separately to generate temporary pom files of a plurality of single dependence relationship lists;
analyzing each temporary pom file through the dependency analysis command, if the analysis is successful, recording analysis success information, and if the analysis is failed, removing the dependency relationship list;
merging a plurality of temporary pom files which are analyzed successfully independently to generate a new comprehensive pom file;
and adopting the dependent parsing command to comprehensively parse the comprehensive pom file and recording a parsing result.
3. The method for analyzing the third party dependence of the packet manager based on the maven architecture as claimed in claim 1, wherein the number of the removed dependency relationship lists is recorded in an accumulated manner, if the number of the removed dependency relationship lists exceeds a preset value, the execution of the current interrupted dependency analysis command is interrupted, and the temporary pom files which are successfully analyzed individually are merged to generate a new comprehensive pom file;
and adopting the dependent parsing command to comprehensively parse the comprehensive pom file and recording a parsing result.
4. The method for parsing a third party dependency by using a maven-architecture-based package manager as claimed in claim 1, wherein the execution process of the dependency parsing command is monitored by a log file to record parsing process information.
5. A system for analyzing third-party dependence based on a maven architecture is characterized by comprising an analyzing module, a monitoring module, a first processing module, a second processing module and a merging module;
the analysis module is used for analyzing a dependency relationship list in the pom file under the current project through a dependency analysis command in the package manager based on the maven architecture;
the monitoring module is used for monitoring the analysis process of the analysis module in real time;
the first processing module is used for removing the dependency relationship list corresponding to the error information from the pom file when the error occurs in the execution process of the analysis module and the error information comes from direct dependency;
the second processing module is used for separating all the dependency relationship lists in the total pom files under the current project and respectively and independently storing the dependency relationship lists when an error occurs in the execution process of the analysis module and the error information comes from indirect dependency so as to generate a plurality of temporary pom files with single dependency relationship lists;
and the merging module is used for merging the temporary pom files which are successfully analyzed independently to generate a new comprehensive pom file.
6. The system for resolving a third party dependency of a packet manager based on a maven architecture as claimed in claim 5, further comprising a third processing module, wherein the third processing module is configured to interrupt the execution of the current dependency resolution command and invoke the second processing module and the merging module to process the current item if the same piece of downloaded information stays beyond a preset value during the monitoring of the resolution process by the monitoring module.
7. The system for parsing third party dependencies by a packet manager based on a maven architecture as claimed in claim 5, further comprising a counting module, wherein the counting module is configured to perform cumulative recording on the number of the removed dependency relationship lists; and if the number recorded by the counting module exceeds a preset value, interrupting the execution of the current interrupted dependent analysis command, and calling the second processing module and the merging module to process the current item.
8. The maven architecture-based package manager parsing system of third party dependencies of claim 5, wherein the monitoring module monitors execution of the dependency parse command through a log file to record parse process information.
9. A system for a packet manager to resolve third party dependencies based on a maven architecture, comprising:
one or more processors;
a memory;
and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the programs comprising instructions for performing the method of resolving third party dependencies of a maven architecture based package manager of any one of claims 1 to 4.
10. A computer-readable storage medium comprising a computer program executable by a processor to perform the method of a maven architecture based package manager resolving third party dependencies of any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210335645.5A CN114816415A (en) | 2022-03-31 | 2022-03-31 | Method and system for packet manager to analyze third-party dependence based on maven architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210335645.5A CN114816415A (en) | 2022-03-31 | 2022-03-31 | Method and system for packet manager to analyze third-party dependence based on maven architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114816415A true CN114816415A (en) | 2022-07-29 |
Family
ID=82531815
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210335645.5A Pending CN114816415A (en) | 2022-03-31 | 2022-03-31 | Method and system for packet manager to analyze third-party dependence based on maven architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114816415A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115543410A (en) * | 2022-11-29 | 2022-12-30 | 深圳开源互联网安全技术有限公司 | Component dependency relationship analysis method, device and medium |
-
2022
- 2022-03-31 CN CN202210335645.5A patent/CN114816415A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115543410A (en) * | 2022-11-29 | 2022-12-30 | 深圳开源互联网安全技术有限公司 | Component dependency relationship analysis method, device and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9256517B1 (en) | Display of aggregated stack traces in a source code viewer | |
| US8250543B2 (en) | Software tracing | |
| CN108459962B (en) | Code normalization detection method and device, terminal equipment and storage medium | |
| CN108388489B (en) | Server fault diagnosis method, system, equipment and storage medium | |
| US7913233B2 (en) | Performance analyzer | |
| CN108038039B (en) | Method for recording log and micro-service system | |
| US9621679B2 (en) | Operation task managing apparatus and method | |
| US9880897B2 (en) | Failure mode identification and reporting | |
| US11422880B1 (en) | Methods and systems for determining crash similarity based on stack traces and user action sequence information | |
| US8489938B2 (en) | Diagnostic data capture in a computing environment | |
| CN114816415A (en) | Method and system for packet manager to analyze third-party dependence based on maven architecture | |
| US9009537B2 (en) | Diagnostic data capture in a computing environment | |
| CN113377719B (en) | System abnormal shutdown time acquisition method and system | |
| CN113708986A (en) | Server monitoring apparatus, method and computer-readable storage medium | |
| US20150089482A1 (en) | Automated Identification of Redundant Method Calls | |
| CN110990179B (en) | Task processing method, device and equipment | |
| CN112596938A (en) | Abnormity monitoring method and device | |
| US10496520B2 (en) | Request monitoring to a code set | |
| CN110011845B (en) | Log collection method and system | |
| JP2009245154A (en) | Computer system, method, and computer program for evaluating symptom | |
| CN112650613B (en) | Error information processing method and device, electronic equipment and storage medium | |
| CN115080012A (en) | class file conflict recognition method and device, electronic equipment and storage medium | |
| CN112948202A (en) | Application program monitoring method, device, equipment and readable storage medium | |
| JP5578487B2 (en) | Failure analysis apparatus, failure analysis method, and program | |
| CN117909907B (en) | High-throughput computing platform, and anomaly removal method, device and storage medium thereof |
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 |