CN116049115B - Software log processing method - Google Patents
Software log processing method Download PDFInfo
- Publication number
- CN116049115B CN116049115B CN202310075747.2A CN202310075747A CN116049115B CN 116049115 B CN116049115 B CN 116049115B CN 202310075747 A CN202310075747 A CN 202310075747A CN 116049115 B CN116049115 B CN 116049115B
- Authority
- CN
- China
- Prior art keywords
- log
- service
- record
- recording
- business
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 16
- 238000000034 method Methods 0.000 claims abstract description 53
- 230000008569 process Effects 0.000 claims abstract description 44
- 238000003860 storage Methods 0.000 claims abstract description 12
- 238000004458 analytical method Methods 0.000 claims description 13
- 238000001514 detection method Methods 0.000 claims description 7
- 230000006870 function Effects 0.000 claims description 5
- 239000003999 initiator Substances 0.000 claims description 4
- 241000208340 Araliaceae Species 0.000 claims description 3
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 claims description 3
- 235000003140 Panax quinquefolius Nutrition 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 claims description 3
- 238000004140 cleaning Methods 0.000 claims description 3
- 235000008434 ginseng Nutrition 0.000 claims description 3
- 238000003825 pressing Methods 0.000 claims description 3
- 230000015556 catabolic process Effects 0.000 claims 1
- 238000011161 development Methods 0.000 abstract description 14
- 238000012423 maintenance Methods 0.000 abstract description 12
- 238000012545 processing Methods 0.000 abstract description 5
- 230000000694 effects Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000739 chaotic effect Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to the technical field of software log processing, in particular to a software log processing method. The invention has the advantages that: according to the unique business codes, all log contents are automatically connected in series to form a log block, the system can count the execution time, warning, error number and the like generated by each process, so that the quick positioning of the business processes and the unique process codes can be conveniently and quickly realized when the business and development personnel handle problems in the later period, the unique business processes and the unique process codes are introduced to enable the log records to penetrate through the whole business processes or processes, so that the log records have the characteristics of business consistency and sortability, the purpose that operation and maintenance personnel or development personnel can quickly position the problems is achieved, logs scattered on each system can be unified to a log platform for storage in a distributed mode, a micro-service mode and other scenes through the unique business coding mode, the execution time sequences in each system can be connected in series, the problem processing efficiency in the micro-service or the distributed system is greatly improved, and the maintainability of the distributed system or the micro-service is improved.
Description
Technical Field
The invention relates to the technical field of software log processing, in particular to a software log processing method.
Background
In the running process of the application program, the running result is inconsistent with the expected running result frequently, and the operation and maintenance personnel and the developer need to check the settings, loopholes and the like in the program to adjust or repair so as to realize the expected running result. Generally, an operation or developer needs to call a program operation log to locate a problem to be solved according to the log. However, in the scenes of complex business logic, complex algorithm, concurrency, investigation performance, big data, distributed, micro-service and the like, the operation and maintenance or development personnel need to locate problems in massive logs with various and complicated types, because the operation and development personnel need to locate for a long time, the production environment is difficult to reproduce, the input required by the program is not recorded and the like, great influence is easily brought to business, operation and maintenance or program debugging, and long-time interruption of key business may be caused when serious.
At present, in the technical field of computer software log, a section of text content is written in program codes in a grading manner at a place where errors are easy to occur or log is required to be recorded, then the log is written into a file, a database, a console, a page and the like, so that the purpose of log recording is realized, and the method has the following problems in actual use:
if all logs are recorded, in a formal environment of software operation, massive log data can be recorded due to dense business or huge number of users, so that storage pressure is brought, and if the logs are stored in a grading manner, for example, only error logs are stored, the logs are stored in a complex business scene; if the performance, configuration and program problems need to be checked, detailed log information can be lost, so that the system cannot be reproduced; positioning the logs in a large number of logs is difficult and a large amount of time is required to be consumed; the software production environment is difficult to reproduce in the log; the log record specification of the development team is not standard or uniform; the log cannot be recorded according to the service flow, and is very chaotic in the situations of complex service, complex algorithm (such as artificial intelligence), high concurrency and the like, so that the log is difficult to read; the log problems with higher levels cannot automatically provide corresponding problem processing schemes; after the system has the advantages that the code maintenance is difficult due to the non-uniformity of development team coding specifications, code annotation specifications, log records and the like, other team members take over codes and are difficult to change or take a lot of time to read related data, the business is known, and even if the business is known, a lot of holes are brought by the change of the subsequent codes, so that the robustness and the stability of the system are poor; specific system loopholes are required to be generated under certain preconditions, and even if logs are recorded, the system problems are difficult to find, so that the security aspect is particularly outstanding.
Disclosure of Invention
The object of the present invention is to solve at least one of the technical drawbacks.
Therefore, an object of the present invention is to provide a software log processing method, which solves the problems mentioned in the background art, and overcomes the shortcomings in the prior art.
In order to achieve the above object, an embodiment of an aspect of the present invention provides a software log processing method, including the steps of:
s1, starting log record, starting a business process, and creating a log record queue;
s2, creating a service unique code;
s3, collecting environment related information, and collecting related requests and Web server related information for calling requests such as method calling and HTTP, HTTPS, socket;
s4, creating a log set, and temporarily storing the log in a file, a database, a memory and other media;
s5, recording logs, detecting thread information, and finding concurrent and multi-thread problems;
s6, finishing log recording, finishing the current business flow and process, and informing a log system of finishing log recording requirements;
s7, automatically sorting log records, analyzing the flow and time consumption in the process according to requirements, and sorting different route logs according to the sequence;
s8, storing, determining whether to record a log according to the configuration condition, and writing the log into a designated storage medium;
and S9, finishing, cleaning the temporary content, and deleting the temporary content from the queue.
In any of the above embodiments, it is preferable that in the step S1, logging is started at the program entry at the latest, and the requirement of the business process is recorded.
The technical effect achieved by adopting the scheme is as follows: the method is convenient for developers, operation and maintenance parties and users to understand and check the whole business.
Preferably, in step S2, the unique code is created at the latest before the logging is started, and the logging and the link analysis may be completed in the distributed, micro-service system.
The technical effect achieved by adopting the scheme is as follows: through unique coding, the method and the system penetrate through the whole business flow or process, so that the log records have business consistency and classifiable characteristics, and the purpose that operation and maintenance personnel or developers can quickly locate the problem is achieved.
Preferably, in any of the above schemes, the service initiator in the distributed and micro service system is responsible for creating the service as a code, transmitting the unique code of the service in each system, and the log system is responsible for collecting, sorting, analyzing and storing the log according to the unique code of the service.
The technical effect achieved by adopting the scheme is as follows: the method and the system enable the log records to penetrate through the whole business flow or process, enable the log records to have business consistency and sortable characteristics, and achieve the purpose that operation and maintenance personnel or developers can quickly locate problems.
By any of the above-mentioned schemes, it is preferable that the client-side related information is collected for the C/S program in the step S3, the thread-related information is also collected in the step S3, and the collection of the environment-related information in the step S3 further includes the steps of:
c1, requesting to enter a ginseng;
c2, collecting information related to a transmission protocol;
c3, collecting configuration information affecting the flow;
and C4, collecting relevant information of the operating system.
The technical effect achieved by adopting the scheme is as follows: by collecting the client information, the relevant environment information is conveniently analyzed according to the client information, wherein the relevant information of the operating system comprises hardware information such as a memory, a CPU and the like.
It is preferable in any of the above-described schemes that a log set is created separately from the service unique code and added to the record queue in the step S4.
The technical effect achieved by adopting the scheme is as follows: according to the unique service codes, all log contents are automatically connected in series to form a log block, and meanwhile, the system can count the execution time, warning, error number and the like generated by each flow, so that the system is convenient for quick positioning when the fortune dimension developer processes the problem in the later stage.
It is preferred by any of the above-mentioned schemes that each log record in step S5 is required to carry a service unique code so that the service unique code runs through the entire service flow, that in step S5 but for system warning, error and crash situations, the problem solution is logged when logging is required, and that in step S5 each function of the code is logged in.
The technical effect achieved by adopting the scheme is as follows: the service unique code penetrates through the whole service flow, so that the problem can be conveniently and rapidly found out, and meanwhile, the problem can be conveniently and rapidly solved.
In any of the above schemes, preferably, the end of logging in step S6 needs to be called by the caller and the requester when the parameter is returned to the business process, and when logging is needed in step S8, the log related to the whole process is recorded together, and the storage medium in step S8 includes a file, a database and a log platform.
The technical effect achieved by adopting the scheme is as follows: the data is conveniently recorded, and the subsequent calling is convenient.
Preferably, in any of the above embodiments, the process information detection in step S5 includes the following detection analysis steps:
a1, using an analysis flow;
a2, analyzing a calling link;
a3, analyzing the direct time difference between the previous record and the analysis;
a4, judging whether warning and error exist or not, if yes, performing step A5, and if no, performing step A6;
a5, counting the number and recording the flow state;
a6, checking whether multithreading is called, if yes, performing step A7, and if not, ending the flow;
a7, pressing the sub-link, and re-entering the step A2.
The technical effect achieved by adopting the scheme is as follows: the influence on the main program is reduced to be almost 0 state by optimizing the thread pool during multithreading, and the time consumption for executing the business process can be rapidly positioned by analyzing the direct time difference from the last record, so that decision support is provided for system optimization, and the automatic analysis capability according to the need can be realized.
It is preferable in any of the above aspects that the log recording in step S5 includes the steps of:
b1, recording logs;
b2, identifying according to the calling interface and the log level, if the warning and the error are found, performing the step B3, and if the error is not found, performing the step B5;
b3, checking the record specification, if the record specification is in accordance with the specification, performing the step B5, and if the record specification is not in accordance with the specification, performing the step B4;
b4, throwing out errors, and carrying out the step B1 again after recording the errors according to the specification;
b5, collecting the thread ID of the log;
b6, recording calling party information;
b7, storing the service codes into a log queue corresponding to the service codes;
and B8, ending the step.
The technical effect achieved by adopting the scheme is as follows: through the steps, the recorded error log can be recorded according to the specification, and the error log can be found and tidied conveniently.
Compared with the prior art, the invention has the following advantages and beneficial effects:
1. according to the software log processing method, all log contents are automatically connected in series to form a log block according to the unique service codes, meanwhile, the system can count the execution time, warning, error number and the like generated by each process, so that the quick positioning of operation and development personnel in the later period can be facilitated when the operation and development personnel deal with problems, the unique service processes and the unique process codes are introduced, the whole service processes or the whole processes are penetrated, the log records have the characteristics of service continuity and classification, and the purpose that operation and maintenance personnel or development personnel can quickly position the problems is achieved.
2. According to the software log processing method, a solution is provided for log records such as warning, errors and the like in advance through forced specification, so that the aim of rapidly solving the problems is fulfilled.
3. According to the software log processing method, the storage amount of the log is reduced through selective log recording, and detailed logs required by troubleshooting are not lost.
4. According to the software log processing method, the debugging efficiency of developers is improved through the environment information and the function entry records, logs scattered on each system can be unified to a log platform for storage in a service unique coding mode under the scenes of distributed service, micro service and the like, and execution time sequences in each system can be connected in series, so that the problem processing efficiency in the micro service or the distributed system is greatly improved, and the maintainability of the distributed system or the micro service is improved.
Drawings
FIG. 1 is a schematic flow chart of the method of the present invention;
FIG. 2 is a schematic diagram of a distributed microservice system of the present invention;
FIG. 3 is a logic flow diagram of thread information detection according to the present invention;
FIG. 4 is a schematic diagram of a logic flow of a log record according to the present invention;
FIG. 5 is a schematic diagram showing the steps of collecting the environmental related information according to the present invention.
Detailed Description
The present invention will be further described with reference to the accompanying drawings, but the scope of the present invention is not limited to the following.
Embodiment one: as shown in fig. 1 to 2, a software log processing method includes the steps of:
s1, starting log record, starting a business process, and creating a log record queue;
s2, creating a service unique code;
s3, collecting environment related information, and collecting related requests and Web server related information for calling requests such as method calling and HTTP, HTTPS, socket;
s4, creating a log set, and temporarily storing the log in a file, a database, a memory and other media;
s5, recording logs, detecting thread information, and finding concurrent and multi-thread problems;
s6, finishing log recording, finishing the current business flow and process, and informing a log system of finishing log recording requirements;
s7, automatically sorting log records, analyzing the flow and time consumption in the process according to requirements, and sorting different route logs according to the sequence;
s8, storing, determining whether to record a log according to the configuration condition, and writing the log into a designated storage medium;
and S9, finishing, cleaning the temporary content, and deleting the temporary content from the queue.
As an alternative technical scheme of the invention, in step S1, log recording is started at the program entrance at the latest, and the requirements of the business process are recorded.
As an alternative technical scheme of the invention, in step S2, the unique code is created at the latest before the beginning of the log record, and the log record and the link analysis can be completed in a distributed micro-service system before the beginning of the log record.
As an alternative technical scheme of the invention, a service initiator in the distributed and micro-service system is responsible for creating a service as a code, transmitting the unique code of the service in each system, a log system is responsible for collecting, arranging, analyzing and storing logs according to the unique code of the service, the logs in each system are consistent with those in FIG. 2, and finally, data are uniformly stored in a log platform when stored, and a general forced specification developer provides an expected solution for warning, error and the like in a specific development process, so that later operation and maintenance personnel can conveniently process the problem, if the service is not intercepted by a compiler according to the specification code, the service cannot be compiled, and the forced specification can be compiled and passed.
As an optional technical solution of the present invention, in step S3, client related information is collected for the C/S program, in step S3, thread related information is also collected, and the collecting of the environment related information in step S3 further includes the following steps:
c1, requesting to enter a ginseng;
c2, collecting information related to a transmission protocol;
c3, collecting configuration information affecting the flow;
and C4, collecting relevant information of the operating system.
As an alternative technical scheme of the invention, in step S4, a log set is independently created according to the unique service codes and added into a record queue, a service initiator is responsible for creating the unique service codes, transmitting the unique service codes in each system, and a log system is responsible for collecting, sorting, analyzing and storing logs according to the unique service codes, wherein the log records in each system are consistent with FIG. 4, and finally, data are uniformly stored in a log platform during storage.
As an alternative technical scheme of the invention, each time the log record in step S5 is required to carry a service unique code, the service unique code is enabled to penetrate through the whole service flow, in step S5, but for the system warning, error and crash conditions, when the log record is required, the problem solution is recorded into the log, and in step S5, each function of the code is recorded into the reference.
As an optional technical scheme of the invention, the end of the log record in step S6 needs to be called by the calling party and the requesting party when the service flow returns parameters, and the related log of the whole flow is recorded together when the log record is needed in step S8, and the storage medium in step S8 comprises a file, a database and a log platform.
As an alternative solution of the present invention, the thread information detection in step S5 includes the following detection analysis steps:
a1, using an analysis flow;
a2, analyzing a calling link;
a3, analyzing the direct time difference between the previous record and the analysis;
a4, judging whether warning and error exist or not, if yes, performing step A5, and if no, performing step A6;
a5, counting the number and recording flow states, such as states of successful execution, error occurrence, warning occurrence and the like, and providing real-time warning for operation and maintenance personnel;
a6, checking whether multithreading is called, if yes, performing step A7, and if not, ending the flow;
a7, pressing the sub-link, and re-entering the step A2.
As an optional aspect of the present invention, the log recording in step S5 includes the steps of:
b1, recording logs;
b2, identifying according to the calling interface and the log level, if the warning and the error are found, performing the step B3, and if the error is not found, performing the step B5;
b3, checking the record specification, if the record specification is in accordance with the specification, performing the step B5, and if the record specification is not in accordance with the specification, performing the step B4;
b4, throwing out errors, after recording the errors according to the specification, re-performing the step B1, and realizing the specification recording and throwing out of the errors through a compiler of the development language;
b5, collecting the thread ID of the log;
b6, recording calling party information;
b7, storing the service codes into a log queue corresponding to the service codes;
and B8, ending, namely ending one record and waiting for ending the next record or flow.
In summary, according to the software log processing method, all log contents are automatically connected in series into one log block according to the unique service codes, meanwhile, the system can count the execution time, warning, error number and the like generated by each process, so that the later stage can be positioned quickly when operation and development personnel handle problems, the unique service codes of the service processes and the process are introduced to enable the service processes and the process to penetrate through the whole service processes or the process, the log records have the characteristics of service continuity and classification, the purpose that operation and maintenance personnel or development personnel can position problems quickly is achieved, the purpose of quickly solving the problems is achieved by providing a solution for the warning, error and the like in advance through forced specification, the purpose of reducing the storage capacity of the log through selective log records, and the required detail log is not lost when the problem is checked, the debugging efficiency of the development personnel is improved through the record of environment information and functions, the logs scattered on each system can be unified to a log platform to be stored through the unique service coding mode under the conditions of distributed, the micro service and the like, the execution time sequence in each system can be connected in series, and the service efficiency or the distributed service system can be greatly improved, and the service efficiency or the distributed service system can be slightly maintained, and the problem of the distributed system is slightly maintained is greatly improved.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
It will be readily understood by those skilled in the art that the present invention, including any combination of parts described in the summary and detailed description of the invention above and shown in the drawings, is limited in scope and does not constitute a complete description of the various aspects of these combinations for the sake of brevity. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Although embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the invention, and that variations, modifications, alternatives, and variations may be made in the above embodiments by those skilled in the art without departing from the spirit and principles of the invention. The scope of the invention is defined by the appended claims and equivalents thereof.
Claims (4)
1. A software log processing method is characterized in that: the method comprises the following steps:
s1, starting log record, starting a business process, and creating a log record queue;
s2, creating a service unique code;
s3, collecting environment related information, and collecting related requests and Web server related information for method call and HTTP, HTTPS, socket call requests;
s4, creating a log set, and temporarily storing the log into a file, a database and a memory medium;
s5, recording logs, detecting thread information, and finding concurrent and multi-thread problems;
s6, finishing log recording, finishing the current business flow and process, and informing a log system of finishing log recording requirements;
s7, automatically sorting log records, analyzing the flow and time consumption in the process according to requirements, and sorting different route logs according to the sequence;
s8, storing, determining whether to record a log according to the configuration condition, and writing the log into a designated storage medium;
s9, finishing, cleaning temporary content, and deleting the temporary content from the queue;
the step S3 is to collect client related information by using a C/S program, the step S3 is to collect thread related information, and the step S3 is to collect environment related information further comprises the following steps:
c1, requesting to enter a ginseng;
c2, collecting information related to a transmission protocol;
c3, collecting configuration information affecting the flow;
collecting relevant information of an operating system;
in the step S4, a log set is independently created according to the unique service code and added into a record queue;
each time the log record in the step S5 is required to carry a service unique code so that the service unique code runs through the whole service flow, the problem solution is recorded into the log when the log record is required in the step S5 for system warning, error and breakdown conditions, and each function of the code is recorded into the reference in the step S5;
the end of the log record in the step S6 is required to be called by a calling party and a requesting party when the parameter is returned to the business process, the log related to the whole process is recorded together when the log is required to be recorded in the step S8, and the storage medium in the step S8 comprises a file, a database and a log platform;
the process information detection in step S5 includes the following detection analysis steps:
a1, using an analysis flow;
a2, analyzing a calling link;
a3, analyzing the direct time difference between the previous record and the analysis;
a4, judging whether warning and error exist or not, if yes, performing step A5, and if no, performing step A6;
a5, counting the number and recording the flow state;
a6, checking whether multithreading is called, if yes, performing step A7, and if not, ending the flow;
a7, pressing in the sub-link, and re-entering step A2
The log recording in step S5 includes the steps of:
b1, recording logs;
b2, identifying according to the calling interface and the log level, if the warning and the error are found, performing the step B3, and if the error is not found, performing the step B5;
b3, checking the record specification, if the record specification is in accordance with the specification, performing the step B5, and if the record specification is not in accordance with the specification, performing the step B4;
b4, throwing out errors, and carrying out the step B1 again after recording the errors according to the specification;
b5, collecting the thread ID of the log;
b6, recording calling party information;
b7, storing the service codes into a log queue corresponding to the service codes;
and B8, ending the step.
2. A software log processing method according to claim 1, wherein: in step S1, log recording is started at the program entry at the latest, and the requirements of the business process are recorded.
3. A software log processing method according to claim 1, wherein:
in the step S2, the unique code is created at the latest before the log record starts; and logging and link analysis completed in the distributed and microservice systems is recorded before logging begins.
4. A software log processing method according to claim 3, wherein: the service initiator in the distributed and micro service system is responsible for creating a service unique code, transmitting the service unique code in each system, and the log system is responsible for collecting, sorting, analyzing and storing logs according to the service unique code.
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310075747.2A CN116049115B (en) | 2023-01-13 | 2023-01-13 | Software log processing method |
| US18/541,063 US12099431B2 (en) | 2023-01-13 | 2023-12-15 | Software log processing method |
| PCT/CN2024/070074 WO2024149107A1 (en) | 2023-01-13 | 2024-01-02 | Software log processing method |
| EP24151293.8A EP4471602A1 (en) | 2023-01-13 | 2024-01-11 | Software log processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310075747.2A CN116049115B (en) | 2023-01-13 | 2023-01-13 | Software log processing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116049115A CN116049115A (en) | 2023-05-02 |
| CN116049115B true CN116049115B (en) | 2023-12-01 |
Family
ID=86120171
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310075747.2A Active CN116049115B (en) | 2023-01-13 | 2023-01-13 | Software log processing method |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US12099431B2 (en) |
| EP (1) | EP4471602A1 (en) |
| CN (1) | CN116049115B (en) |
| WO (1) | WO2024149107A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116049115B (en) * | 2023-01-13 | 2023-12-01 | 深圳安科百腾科技有限公司 | Software log processing method |
| CN118606067B (en) * | 2024-04-15 | 2025-02-07 | 湖南长银五八消费金融股份有限公司 | A method, device, equipment and storage medium for implementing a retry mechanism |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105224445A (en) * | 2015-10-28 | 2016-01-06 | 北京汇商融通信息技术有限公司 | Distributed tracking system |
| CN111625431A (en) * | 2019-02-28 | 2020-09-04 | 华为技术有限公司 | Log information generation method and device and electronic equipment |
| CN113254309A (en) * | 2021-05-25 | 2021-08-13 | 厦门市易联众易惠科技有限公司 | Active early warning system and method for errors of service system |
| CN113986669A (en) * | 2021-10-28 | 2022-01-28 | 北京航天云路有限公司 | Call chain tracking and business analysis method based on AOP annotation |
| CN114610689A (en) * | 2022-03-17 | 2022-06-10 | 焦点科技股份有限公司 | Method for recording and analyzing request log in distributed environment |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090031250A1 (en) * | 2007-07-27 | 2009-01-29 | Jesse Boudreau | Administration of wireless devices in a wireless communication system |
| US20110083123A1 (en) * | 2009-10-05 | 2011-04-07 | Microsoft Corporation | Automatically localizing root error through log analysis |
| US9081628B2 (en) * | 2011-05-27 | 2015-07-14 | Intel Corporation | Detecting potential access errors in a multi-threaded application |
| US9081898B1 (en) * | 2012-06-29 | 2015-07-14 | Emc Corporation | Automatic capture of minimal portable executable bug repros |
| US8914680B2 (en) * | 2012-07-02 | 2014-12-16 | International Business Machines Corporation | Resolution of system hang due to filesystem corruption |
| US9836354B1 (en) * | 2014-04-28 | 2017-12-05 | Amazon Technologies, Inc. | Automated error detection and recovery for GPU computations in a service environment |
| US9430355B2 (en) * | 2014-09-18 | 2016-08-30 | Sap Se | System diagnostics with thread dump analysis |
| CN111459766B (en) * | 2019-11-14 | 2024-01-12 | 国网浙江省电力有限公司信息通信分公司 | Micro-service system-oriented call chain tracking and analyzing method |
| CN112612675B (en) * | 2020-12-25 | 2023-02-28 | 山东经伟晟睿数据技术有限公司 | Distributed big data log link tracking method and system under micro-service architecture |
| CN116049115B (en) * | 2023-01-13 | 2023-12-01 | 深圳安科百腾科技有限公司 | Software log processing method |
-
2023
- 2023-01-13 CN CN202310075747.2A patent/CN116049115B/en active Active
- 2023-12-15 US US18/541,063 patent/US12099431B2/en active Active
-
2024
- 2024-01-02 WO PCT/CN2024/070074 patent/WO2024149107A1/en unknown
- 2024-01-11 EP EP24151293.8A patent/EP4471602A1/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105224445A (en) * | 2015-10-28 | 2016-01-06 | 北京汇商融通信息技术有限公司 | Distributed tracking system |
| CN111625431A (en) * | 2019-02-28 | 2020-09-04 | 华为技术有限公司 | Log information generation method and device and electronic equipment |
| CN113254309A (en) * | 2021-05-25 | 2021-08-13 | 厦门市易联众易惠科技有限公司 | Active early warning system and method for errors of service system |
| CN113986669A (en) * | 2021-10-28 | 2022-01-28 | 北京航天云路有限公司 | Call chain tracking and business analysis method based on AOP annotation |
| CN114610689A (en) * | 2022-03-17 | 2022-06-10 | 焦点科技股份有限公司 | Method for recording and analyzing request log in distributed environment |
Also Published As
| Publication number | Publication date |
|---|---|
| EP4471602A1 (en) | 2024-12-04 |
| WO2024149107A1 (en) | 2024-07-18 |
| US20240111655A1 (en) | 2024-04-04 |
| US12099431B2 (en) | 2024-09-24 |
| CN116049115A (en) | 2023-05-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN116049115B (en) | Software log processing method | |
| US10102113B2 (en) | Software test automation systems and methods | |
| CN111737127B (en) | Method and apparatus for testing map services | |
| JP4436036B2 (en) | Information processing apparatus, trace processing method, program, and recording medium | |
| US8473919B2 (en) | System and method for repeating program flow for debugging and testing | |
| CN110795257A (en) | Method, device and equipment for processing multi-cluster operation records and storage medium | |
| US8108234B2 (en) | System and method for deriving business processes | |
| CN111881014B (en) | System test method, device, storage medium and electronic equipment | |
| US20040153837A1 (en) | Automated testing | |
| CN110096419A (en) | Acquisition methods, interface log management server and the service server of interface log | |
| US20200117587A1 (en) | Log File Analysis | |
| CN111666217B (en) | Method and apparatus for testing code | |
| US20180143897A1 (en) | Determining idle testing periods | |
| CN116405412B (en) | Method and system for verifying cluster effectiveness of simulation server based on chaotic engineering faults | |
| US20050114838A1 (en) | Dynamically tunable software test verification | |
| CN109409948B (en) | Transaction abnormality detection method, apparatus, device, and computer-readable storage medium | |
| CN107423090B (en) | Flash player abnormal log management method and system | |
| CN115114064A (en) | Microservice fault analysis method, system, device and storage medium | |
| CN111400171B (en) | Interface testing method, system and device and readable storage medium | |
| CN114092246A (en) | Problem locating method and device for financial transaction link | |
| CN117632718A (en) | Bank counter channel system transaction service testing method and device | |
| Rabkin et al. | A graphical representation for identifier structure in logs | |
| CN112181759A (en) | Method for monitoring micro-service performance and diagnosing abnormity | |
| CN113010406A (en) | Management method, device, equipment and medium of code analysis tool | |
| CN119003217A (en) | Fault analysis method based on webhook uploading dump file |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |