CN115599758A - Cross-platform log frame and log information acquisition method - Google Patents
Cross-platform log frame and log information acquisition method Download PDFInfo
- Publication number
- CN115599758A CN115599758A CN202211184752.9A CN202211184752A CN115599758A CN 115599758 A CN115599758 A CN 115599758A CN 202211184752 A CN202211184752 A CN 202211184752A CN 115599758 A CN115599758 A CN 115599758A
- Authority
- CN
- China
- Prior art keywords
- log
- information
- module
- output
- cross
- 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
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a cross-platform log frame and a log information acquisition method, wherein the cross-platform log frame is built based on a cmake compiling tool, and a log configuration analysis module is used for loading and analyzing YML file configuration to obtain configuration information; the log recorder module is used for checking and creating a log recorder according to the name of the log recorder, and the log recorder is used for recording log information and sending the log information to the log output module; the log file control module is used for triggering the log output module when the grade of the currently output log information is greater than the log grade; and the log output module formats the log information sent by the log recording module according to the log output format after the log file control module is triggered, and writes the log information into a corresponding object of a log output path according to the current operating system environment after the log information is formatted. The invention provides a cross-platform and cross-language log framework implementation scheme.
Description
Technical Field
The invention belongs to the technical field of log acquisition and processing, and particularly relates to a cross-platform log frame and a log information acquisition method.
Background
The log is an indispensable important component of any system, all behaviors generated in the system can be recorded by using the log, the log is not limited to debugging, and the log can also be used for diagnosing whether the system functions normally run, collecting system error information and knowing the operation bottleneck of the system. If log information is lacked, the product side has to rely on a client or a support team to reproduce the problem through artificial description, but if log information is available, the product side can be helped to quickly locate the problem and solve the problem.
At present, an augmented reality product can run in operating systems such as android and Lunix, so that a cross-platform log frame is needed for unified management, code variables are monitored, the running condition of a multi-platform product is known, the running track of a code is mastered, and whether the multi-platform product runs according to a plan or not is judged. The existing common Log frameworks include JDK Logger, apache Log4j and Lodback, and the common point is that Log information is output by configuring Log levels, log output paths and the like, but the Log frameworks are mainly applied to servers of Java applications and are not completely adapted to APP and Lunix program applications at present.
For example, an existing Log framework Log4cxx is a C + + version of Log4j, and is used for providing a Log output function for a C + + program so that a developer debugs a product program, and the Log4cxx has three main components: the recorder, the output source and the layout, and the defined level log can be output to the defined position according to the defined format through the three components. It is clear that both log4cxx and the currently common log frameworks suffer from the following drawbacks: the method can not support a plurality of platforms such as android, iOS, lunix and Windows; the method can not support programs jointly developed by a plurality of development languages of C/C + +, java and C #.
Disclosure of Invention
One of the purposes of the invention is to provide a cross-platform log framework and provide an implementation scheme of the cross-platform and cross-language log framework.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
the utility model provides a cross platform log frame, cross platform log frame is based on cmake compiling tool and builds, cross platform log frame includes log configuration analysis module, log file control module, log record module and log output module, wherein:
the log configuration analysis module is used for loading and analyzing the YML file configuration to obtain configuration information, wherein the configuration information comprises a log recorder name, a log level, a log output path and a log output format;
the log recording module is used for checking and creating a log recorder according to the name of the log recorder, and the log recorder is used for recording log information and sending the log information to the log output module;
the log file control module is used for triggering the log output module when the level of the currently output log information is greater than the log level;
and the log output module is used for formatting the log information sent by the log recording module according to the log output format after the log file control module is triggered, and writing the log information into a corresponding object of the log output path according to the current operating system environment after the log information is formatted.
Several alternatives are provided below, but not as an additional limitation to the above general solution, but merely as a further addition or preference, each alternative being combinable individually for the above general solution or among several alternatives without technical or logical contradictions.
Preferably, the log configuration parsing module calls an open source component yaml-cpp to parse the YML file configuration.
Preferably, the logging module checks and creates a logger according to the logger name, and performs the following operations:
traversing the created log recorders according to the names of the log recorders, and ending if the log recorders with the same name exist; otherwise, a new log recorder is created according to the name of the log recorder.
Preferably, the corresponding object of the log output path is a database or a file.
Preferably, the configuration information further includes a maximum single-file duty space configuration, and the log file control module is further configured to calculate a reserved number of log files and a size of a single file according to the number of currently output log information and the maximum single-file duty space configuration, and send the reserved number of log files and the size of the single file to the log output module.
Preferably, the log output module writes the log information into a corresponding object of the log output path, and executes the following operations:
and writing the corresponding objects of the log output path according to the reserved number of the log files and the size of a single file.
Preferably, the current operating system environment is an android system, an IOS system, a Lunix system, or a Windows system.
Preferably, the log output module writes log information into a corresponding object of the log output path according to a current operating system environment, and executes the following operations:
judging whether the current operating system environment is an android system, if so, further judging whether a read-write permission exists, if so, writing the log information into a corresponding object of the android system configured on the log output path, and if not, ending;
if the current operating system environment is not the IOS system, judging whether the current operating system environment is the IOS system, if the current operating system environment is the IOS system, further judging whether a read-write permission exists, if the read-write permission exists, writing the log information into a corresponding object of the IOS system configured by the log output path, and if the read-write permission does not exist, ending the operation;
if the current operating system environment is not the Lunix system, judging whether the current operating system environment is the Lunix system, and if the current operating system environment is the Lunix system, writing the log information into a corresponding object of the Lunix system configured by the log output path;
if the log is not the Lunix system, judging whether the current operating system environment is a Windows system, and if the current operating system environment is the Windows system, writing the log information into a corresponding object of the Windows system configured by the log output path;
if not, the process is finished.
Preferably, the log output module is further configured to output log information to the program compiling console according to the current operating system environment after the log information is formatted.
The cross-platform log framework provided by the invention carries out cross-platform compilation through C/C + + compiling and cmake, judges the current operating system environment according to macro definition, provides a C language interface method to the outside and finally realizes a cross-platform and cross-language log solution.
The invention also aims to provide a log information acquisition method based on a cross-platform log frame, which realizes the acquisition of log information corresponding to multiple platforms and multiple languages.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
a method for collecting log information based on a cross-platform log frame is disclosed, the method for collecting log information is used for cross-platform compiling through a cmake compiling tool, the cross-platform log frame comprises a log configuration analysis module, a log file control module, a log recording module and a log output module, and the method for collecting log information comprises the following steps:
the log configuration analysis module loads and analyzes the YML file configuration to obtain configuration information, wherein the configuration information comprises a log recorder name, a log level, a log output path and a log output format;
the log recorder module checks and creates a log recorder according to the name of the log recorder, and the log recorder is used for recording log information and sending the log information to the log output module;
the log file control module triggers the log output module when the level of the currently output log information is greater than the log level;
and after being triggered by the log file control module, the log output module formats the log information sent by the log recording module according to the log output format, and writes the log information into a corresponding object of the log output path according to the current operating system environment after the log information is formatted.
The log information acquisition method provided by the invention realizes that one code is used on multiple platforms after being compiled by multiple platforms through cmake, greatly reduces the maintenance cost and the use cost, and supports multi-language call to output log information.
Drawings
FIG. 1 is a schematic structural diagram of a cross-platform journal framework of the present invention;
FIG. 2 is a schematic diagram of the content of a log file and the output information of a console output by a cross-platform log framework under an android system;
FIG. 3 is a schematic diagram of the content of the log file and the console output information output by the cross-platform log framework under the IOS system according to the present invention;
fig. 4 is a schematic diagram of the content of the log file and the output information of the console output by the Lunix system through the cross-platform log frame according to the present invention;
FIG. 5 is a schematic diagram of the content of the journal file and the console output information output by the cross-platform journal frame under Windows system according to the present invention;
FIG. 6 is a flowchart of a cross-platform log framework-based log information collection method according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
In order to overcome the defects of the Log frame in the prior art, the embodiment is based on the Log4j Log frame idea, and combines a common C/C + + program console with file output to realize a cross-platform Log frame, where the Log frame includes a Log level definition, a Log recorder, a Log formatting function, a Log output destination, a Log destination file control function, and the like, and the output Log information includes year, month, day, hour, minute and second, a thread name, a thread number, a file name, a Log code line number, a Log level, and Log information after Log formatting. The cross-platform log framework is used for configuring a plurality of platforms, so that the multiplexing of codes is enhanced, the use cost of developers is reduced, and the cross-platform log framework is greatly convenient for the developers and maintainers to master the operation condition of the system.
As shown in fig. 1, the cross-platform log framework of this embodiment includes a log configuration analysis module, a log file control module, a log recording module, and a log output module. And in order to realize cross-platform use, the cross-platform log frame is built based on a cmake compiling tool, and one code is realized to run on multiple platforms after being compiled on the multiple platforms through the cmake compiling tool.
1) And the log configuration analysis module is used for loading and analyzing the YML file configuration to obtain configuration information.
In this embodiment, the open source component yaml-cpp is called to analyze the configuration of the YML file, and the analyzed configuration information is cached in the memory of the program running device for use.
The configuration information includes the name of the log recorder, the log level (the level of the log information for controlling output), the log output path and the log output format (the format is that the log information is output after the whole log system data is formatted according to the configured format). It should be noted that the content included in the configuration information is only one conventional content listed in this embodiment, and in other embodiments, other parameter contents may also be provided as needed, for example, a single file duty cycle maximum configuration is further included in order to facilitate correct existence of data.
2) And the log recording module is responsible for creating and managing the log recorder through the configuration information.
The log recorder is an internal use interface of the whole log frame, realizes the classified recording of the logs through the interface, and sends the recorded log information to the log output module. In the embodiment, the log recorder is checked and created by the log recording module according to the name of the log recorder, the log system allows a plurality of log recorders to exist, and the life cycle of each log recorder is controlled by the log manager (log recording module).
It should be noted that, in order to avoid repeated creation of a log recorder, when the log recorder is checked and created by the log recording module, the created log recorder is traversed in advance according to the name of the log recorder, and if there are log recorders with the same name, the creation is not completed; otherwise, a new log recorder is created according to the name of the log recorder.
3) And the log file control module is used for triggering the log output module when the grade of the currently output log information is greater than the log grade.
When the log output object is a data block or a file, because the database storage page or the file has a specific size, the log file control module further needs to calculate the reserved number of log files and the size of a single file to send to the log output module according to the number of currently output log information and the maximum configuration of the occupied space of the single file.
4) And the log output module is used for formatting the log information sent by the log recording module according to the log output format after the trigger of the log file control module, and writing the log information into a corresponding object of a log output path according to the current operating system environment after the formatting.
In this embodiment, the corresponding object of the log output path is a database or a file, and when log information is output, the corresponding object of the log output path is written according to the reserved number of log files and the size of a single file. In order to facilitate program debugging by developers, it is also common to output log information to a program compilation console when outputting the log information.
In this embodiment, to improve cross-platform application, a current operating system environment is taken as an android system, an IOS system, a Lunix system, or a Windows system. In practical applications, according to the continuous innovative development of the operating system, the operating system environment related to the cross-platform application of the embodiment may be increased accordingly.
The embodiment further details a specific output process based on four operating systems, corresponding objects of log output paths, and a program compiling console:
judging whether the current operating system environment is an android system, if so, further judging whether a read-write permission exists, if so, writing log information into a corresponding object of the android system configured by the log output path, and simultaneously calling a _ android _ log _ print printing function to output the log to a console, and if not, ending the operation;
if the current operating system environment is not the IOS system, judging whether the current operating system environment is the IOS system, if the current operating system environment is the IOS system, further judging whether a read-write permission exists, if the read-write permission exists, writing the log information into a corresponding object of the IOS system configured by the log output path by using an os _ log _ with _ type method, simultaneously outputting the log information to a console, and if the read-write permission does not exist, ending;
if the current operating system environment is not the Lunix system, judging whether the current operating system environment is the Lunix system, if the current operating system environment is the Lunix system, calling an ostram type to write the log information into a corresponding object of the Lunix system configured by the log output path, and calling std: cout to output the log information to a console;
if the log is not a Lunix system, judging whether the current operating system environment is a Windows system, if the current operating system environment is the Windows system, calling an OStream class to write the log information into a corresponding object of the Windows system configured by the log output path, and calling std:: cout to output the log information to a console;
if not, the process is finished.
In order to facilitate the application of the log framework, various log system API interfaces are also provided in the log framework, so that log collection and output can be realized by calling corresponding modules. The log framework of the embodiment realizes a cross-platform and cross-language log framework solution by using a method of supporting a console by each operating system through yml configuration, realizes cross-platform and cross-language log acquisition and output, can also realize the configuration of the log system through json or xml in other embodiments, compiles a corresponding operating system through cmake file configuration variables, writes a cross-platform log output core part by using C, and realizes multiplexing of a log code.
In a specific example, when the cross-platform log framework of the present embodiment is run, the log file content and the console information output under the android system, the IOS system, the Lunix system, and the Windows system are shown in fig. 2 to 5. It can be seen that the cross-platform log framework of the embodiment can excellently realize cross-platform output.
In another embodiment, a method for collecting log information based on a cross-platform log framework is provided, the method for collecting log information is performed through a cmake compiling tool to perform cross-platform compiling, the cross-platform log framework includes a log configuration analysis module, a log file control module, a log recording module and a log output module, and the method for collecting log information includes:
the log configuration analysis module loads and analyzes the YML file configuration to obtain configuration information, wherein the configuration information comprises a log recorder name, a log level, a log output path and a log output format;
the log recorder module checks and creates a log recorder according to the name of the log recorder, and the log recorder is used for recording log information and sending the log information to the log output module;
the log file control module triggers the log output module when the level of the currently output log information is greater than the log level;
and the log output module formats the log information sent by the log recording module according to the log output format after the log file control module is triggered, and writes the log information into a corresponding object of the log output path according to the current operating system environment after the log information is formatted.
In one embodiment, the log configuration parsing module invokes the open source component yaml-cpp to parse the YML file configuration.
In a specific example, the logging module, checking and creating a logger according to the logger name, includes:
traversing the created log recorders according to the names of the log recorders, and ending if the log recorders with the same name exist; otherwise, a new log recorder is created according to the name of the log recorder.
In one embodiment, the corresponding object of the log output path is a database or a file.
In a specific example, the configuration information further includes a maximum single-file duty space configuration, and the log file control module is further configured to calculate a reserved number of log files and a size of a single file according to the number of currently output log information and the maximum single-file duty space configuration, and send the reserved number of log files and the size of the single file to the log output module.
In a specific example, the log output module writes log information into a corresponding object of the log output path, and includes:
and writing the corresponding objects of the log output path according to the reserved number of the log files and the size of a single file.
In a specific example, the current operating system environment is an android system, an IOS system, a Lunix system, or a Windows system.
In a specific example, the writing of the log information into the corresponding object of the log output path by the log output module according to the current operating system environment includes:
judging whether the current operating system environment is an android system, if so, further judging whether a read-write permission exists, if so, writing the log information into a corresponding object of the android system configured on the log output path, and if not, ending;
if the log is not an android system, judging whether the current operating system environment is an IOS system, if the current operating system environment is the IOS system, further judging whether a read-write permission exists, if the read-write permission exists, writing the log information into a corresponding object of the IOS system configured on the log output path, and if the read-write permission does not exist, ending;
if the current operating system environment is not the Lunix system, judging whether the current operating system environment is the Lunix system, and if the current operating system environment is the Lunix system, writing the log information into a corresponding object of the Lunix system configured by the log output path;
if the current operating system environment is not the Windows system, judging whether the current operating system environment is the Windows system, and if the current operating system environment is the Windows system, writing the log information into a corresponding object of the Windows system configured by the log output path;
if not, the process is finished.
In a specific example, the log output module is further configured to output log information to the program compiling console according to the current operating system environment after the log information is formatted.
For specific limitations of the method for acquiring log information based on the cross-platform log frame, reference may be made to the above limitations of the cross-platform log frame, which is not described in detail in this embodiment.
As shown in FIG. 6, in one embodiment, a method for providing cross-platform log framework based log information collection is provided as follows:
1. loading a configuration log YML file configuration, wherein the YML file configuration comprises a log recorder name, a log level, a log output path, a single file occupied space maximum configuration and a log output format;
2. parsing using the open source component yaml-cpp according to the YML file configuration;
3. caching the configuration information obtained by analysis into a memory;
4. checking and creating a log recorder according to the name of the log recorder;
5. the log recorder calls a log output module according to the configuration information to determine that the log information is output to a database or a file and the log information is output to the console;
6. judging whether the level of the currently output log information is greater than or equal to the configured log level, if so, continuing the next step, and if not, ending;
7. judging whether log information is output to a database or a file, and if the log information is output to the database or the file, taking up the maximum space configuration according to the number of the currently output log information and the single file;
8. formatting the log information according to the log output format;
9. according to whether the current operating system environment is an android or not, if so, further judging whether a read-write permission exists, if so, writing the log into a corresponding path of the configured android, and calling _ android _ log _ print to output and control the log; if no authority exists, ending;
if not, judging whether the system is an iOS system, if so, further judging whether the system has read-write permission, and if so, writing the log into a corresponding file of the configured iOS system by using os _ log _ with _ type and simultaneously outputting and controlling the log; if no authority exists, ending;
if not, judging whether the system is a Lunix system, if so, calling osteopream to write the log information into a corresponding file of Lunix configuration and calling std: cout to output the log to a console;
if not, judging whether the system is a Windows system, if so, calling the osteopream to write the log information into a corresponding file of the Windows configuration and calling std, wherein cout outputs the log to a console; otherwise, ending.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above examples are merely illustrative of several embodiments of the present invention, and the description thereof is more specific and detailed, but not to be construed as limiting the scope of the invention. It should be noted that various changes and modifications can be made by those skilled in the art without departing from the spirit of the invention, and these changes and modifications are all within the scope of the invention. Therefore, the protection scope of the present invention should be subject to the appended claims.
Claims (10)
1. The cross-platform log framework is built based on a cmake compiling tool, and comprises a log configuration analysis module, a log file control module, a log recording module and a log output module, wherein:
the log configuration analysis module is used for loading and analyzing the YML file configuration to obtain configuration information, wherein the configuration information comprises a log recorder name, a log level, a log output path and a log output format;
the log recording module is used for checking and creating a log recorder according to the name of the log recorder, and the log recorder is used for recording log information and sending the log information to the log output module;
the log file control module is used for triggering the log output module when the level of the currently output log information is greater than the log level;
and the log output module is used for formatting the log information sent by the log recording module according to the log output format after the log file control module is triggered, and writing the log information into a corresponding object of the log output path according to the current operating system environment after the log information is formatted.
2. The cross-platform log framework of claim 1, wherein the log configuration parsing module invokes an open source component yaml-cpp to parse YML file configurations.
3. The cross-platform logging framework of claim 1, wherein the logging module, based on the logger name, checks and creates a logger, performs the following operations:
traversing the created log recorders according to the names of the log recorders, and ending if the log recorders with the same name exist; otherwise, a new log recorder is created according to the name of the log recorder.
4. The cross-platform logging framework of claim 1, wherein the corresponding object of the log output path is a database or a file.
5. The cross-platform log framework of claim 1, wherein the configuration information further comprises a single file duty cycle maximum configuration, and the log file control module is further configured to calculate a log file reservation number and a single file size to send to the log output module based on the amount of currently output log information and the single file duty cycle maximum configuration.
6. The cross-platform log framework of claim 5, wherein the log output module writes log information into corresponding objects of the log output path, performing the following:
and writing the corresponding objects of the log output path according to the reserved number of the log files and the size of a single file.
7. The cross-platform log framework of claim 1, wherein the current operating system environment is an android system, an IOS system, a Lunix system, or a Windows system.
8. The cross-platform log framework of claim 7, wherein the log output module writes log information into corresponding objects of the log output path according to a current operating system environment, and performs the following operations:
judging whether the current operating system environment is an android system, if so, further judging whether a read-write permission exists, if so, writing the log information into a corresponding object of the android system configured by the log output path, and if not, ending the operation;
if the current operating system environment is not the IOS system, judging whether the current operating system environment is the IOS system, if the current operating system environment is the IOS system, further judging whether a read-write permission exists, if the read-write permission exists, writing the log information into a corresponding object of the IOS system configured by the log output path, and if the read-write permission does not exist, ending the operation;
if the current operating system environment is not the Lunix system, judging whether the current operating system environment is the Lunix system, and if the current operating system environment is the Lunix system, writing the log information into a corresponding object of the Lunix system configured by the log output path;
if the current operating system environment is not the Windows system, judging whether the current operating system environment is the Windows system, and if the current operating system environment is the Windows system, writing the log information into a corresponding object of the Windows system configured by the log output path;
if not, the process is finished.
9. The cross-platform log framework of claim 1, wherein the log output module is further configured to output log information to a program compilation console after formatting according to a current operating system environment.
10. A method for collecting log information based on a cross-platform log frame is characterized in that the method for collecting the log information carries out cross-platform compilation through a cmake compilation tool, the cross-platform log frame comprises a log configuration analysis module, a log file control module, a log recording module and a log output module, and the method for collecting the log information comprises the following steps:
the log configuration analysis module loads and analyzes the YML file configuration to obtain configuration information, wherein the configuration information comprises a log recorder name, a log level, a log output path and a log output format;
the log recorder module checks and creates a log recorder according to the name of the log recorder, and the log recorder is used for recording log information and sending the log information to the log output module;
the log file control module triggers the log output module when the level of the currently output log information is greater than the log level;
and the log output module formats the log information sent by the log recording module according to the log output format after the log file control module is triggered, and writes the log information into a corresponding object of the log output path according to the current operating system environment after the log information is formatted.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211184752.9A CN115599758A (en) | 2022-09-27 | 2022-09-27 | Cross-platform log frame and log information acquisition method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211184752.9A CN115599758A (en) | 2022-09-27 | 2022-09-27 | Cross-platform log frame and log information acquisition method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115599758A true CN115599758A (en) | 2023-01-13 |
Family
ID=84845634
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211184752.9A Pending CN115599758A (en) | 2022-09-27 | 2022-09-27 | Cross-platform log frame and log information acquisition method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115599758A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117742782A (en) * | 2024-02-19 | 2024-03-22 | 成都九洲电子信息系统股份有限公司 | Log data cross-language automatic recording method and system for software system |
-
2022
- 2022-09-27 CN CN202211184752.9A patent/CN115599758A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117742782A (en) * | 2024-02-19 | 2024-03-22 | 成都九洲电子信息系统股份有限公司 | Log data cross-language automatic recording method and system for software system |
| CN117742782B (en) * | 2024-02-19 | 2024-06-11 | 成都九洲电子信息系统股份有限公司 | Log data cross-language automatic recording method and system for software system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101132560B1 (en) | System and method for automatic interface testing based on simulation for robot software components | |
| US7689872B2 (en) | Autonomic program error detection and correction | |
| CN101739339B (en) | Program dynamic dependency relation-based software fault positioning method | |
| CN106325970A (en) | Compiling method and compiling system | |
| CN111459824B (en) | Test case processing method and device for concurrent service | |
| US20090037884A1 (en) | Method for Automatically Creating a Behavior Pattern of a Computer Program for Model-based Testing Techniques | |
| WO2002052411A1 (en) | Computer software run-time analysis systems and methods | |
| US20050223360A1 (en) | System and method for providing a generic user interface testing framework | |
| US7096339B2 (en) | System and method for detecting memory management programming errors | |
| US20050229161A1 (en) | Generic user interface testing framework with load-time libraries | |
| US8024706B1 (en) | Techniques for embedding testing or debugging features within a service | |
| CN114915643B (en) | Configuration method, device, equipment and medium of railway signal centralized monitoring system | |
| CN115599758A (en) | Cross-platform log frame and log information acquisition method | |
| CN112435072A (en) | Model creating method and device, electronic equipment and storage medium | |
| US20220297731A1 (en) | Train signal system and linkage method therefor | |
| CN113626317A (en) | Automatic driving software debugging system, method, medium and equipment | |
| CN113742215A (en) | Method and system for automatically configuring and calling test tool to perform test analysis | |
| US20050228644A1 (en) | Generic user interface testing framework with rules-based wizard | |
| CN109542444A (en) | Monitoring method, device, server and the storage medium of JAVA application | |
| CN112363897A (en) | Full link log tracking method, device and storage medium | |
| CN112612697A (en) | Software defect testing and positioning method and system based on byte code technology | |
| CN116795576A (en) | Log printing-based device driver debugging method and device and electronic device | |
| CN112162921B (en) | Industrial automation test and control system | |
| CN115080426A (en) | Program file detection method and device, storage medium and electronic equipment | |
| CN112732522A (en) | Configurable log storage and analysis method and system for vehicle-mounted MCU |
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 |