CN111459764A - Log management method and terminal - Google Patents
Log management method and terminal Download PDFInfo
- Publication number
- CN111459764A CN111459764A CN202010273030.5A CN202010273030A CN111459764A CN 111459764 A CN111459764 A CN 111459764A CN 202010273030 A CN202010273030 A CN 202010273030A CN 111459764 A CN111459764 A CN 111459764A
- Authority
- CN
- China
- Prior art keywords
- log
- file
- folder
- writing
- configuration file
- 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.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 45
- 238000004590 computer program Methods 0.000 claims description 8
- 230000006870 function Effects 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 3
- 239000002699 waste material Substances 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3013—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/865—Monitoring of software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a log management method and a terminal, wherein a corresponding configuration file is set for each application program; receiving a log writing request, and determining a corresponding configuration file according to the type of the log; writing the log according to the configuration file; the log file attribute and the log writing are restrained by setting the configuration file, so that logs generated by different application programs in the embedded system can be uniformly managed, meanwhile, the corresponding configuration file is determined according to the log category, the configuration file is more flexibly set, meanwhile, a uniform writing interface is set for performing the log writing operation, the uniform format of the logs is ensured, the log file can be conveniently searched and read in the later period, the file is positioned by updating the log file handle, the interface does not need to be reset when a new log file needs to be written, only the corresponding handle needs to be updated, and the system resources are saved.
Description
Technical Field
The present invention relates to the field of log management, and in particular, to a log management method and a terminal.
Background
Whether the system is an unmanned system or other embedded systems, only systematic management is performed on the system logs, and the management of the logs of the application program is messy, which causes two problems, namely, the logs are not easy to check, retrieve and delete, useless and expired logs waste storage space, and long-time accumulation causes storage consumption, thereby causing application program function abnormity, system breakdown or downtime, which also affects the service life of the system, causes the task to be unable to be smoothly executed, affects user experience, and further costs more maintenance to maintain the system.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the log management method and the terminal are provided, unified management of log files of application programs is achieved, various operations on the log files are facilitated, and system stability is guaranteed.
In order to solve the technical problems, the invention adopts a technical scheme that:
a log management method, comprising the steps of:
s1, setting a corresponding configuration file for each application program;
s2, receiving a log writing request, and determining a corresponding configuration file according to the type of the log;
and S3, writing the log according to the configuration file.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a log management terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
s1, setting a corresponding configuration file for each application program;
s2, receiving a log writing request, and determining a corresponding configuration file according to the type of the log;
and S3, writing the log according to the configuration file.
The invention has the beneficial effects that: the log management method has the advantages that the corresponding configuration file is set for each application program, the log is written according to the corresponding configuration file when written, unified management of the log files of the application programs is achieved, the log files of the application programs are standardized, independence of log management of different application programs is guaranteed, mutual influence is avoided, operation on the log files is facilitated, management operation on the log files of the application programs is facilitated, expansion and development of the application programs are facilitated, and stability of a system is guaranteed.
Drawings
FIG. 1 is a flowchart illustrating steps of a log management method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a log management terminal according to an embodiment of the present invention;
FIG. 3 is a flowchart of the steps for creating a log storage path according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating log file name generation steps according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating the steps of deleting a log file according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating steps for writing a log file according to an embodiment of the present invention;
description of reference numerals:
1. a log management terminal; 2. a processor; 3. a memory;
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
Referring to fig. 1, a log management method includes the steps of:
s1, setting a corresponding configuration file for each application program;
s2, receiving a log writing request, and determining a corresponding configuration file according to the type of the log;
and S3, writing the log according to the configuration file.
From the above description, the beneficial effects of the present invention are: the log management method has the advantages that the corresponding configuration file is set for each application program, the log is written according to the corresponding configuration file when written, unified management of the log files of the application programs is achieved, the log files of the application programs are standardized, independence of log management of different application programs is guaranteed, mutual influence is avoided, operation on the log files is facilitated, management operation on the log files of the application programs is facilitated, expansion development of the application programs is facilitated, and stability of a system is guaranteed.
Further, the configuration file comprises a log storage path and a log category;
the S2 includes:
receiving a log writing request, and matching a configuration file with the same log type according to the log type contained in the log writing request;
the S3 includes:
s31, reading a log storage path in the configuration file, judging whether a log folder exists according to the log storage path, if not, creating the log folder, and executing S32, otherwise, executing S32;
s32, reading the log category in the configuration file, obtaining the current time, determining the name of the log file according to the log category and the current time, creating a log file corresponding to the name of the log file in the log folder, and writing the log in the log file.
According to the description, the configuration files are matched according to the log types, the logs of the same type have the same storage path, later retrieval and checking are facilitated, the log file is created according to the log types and the current time, the uniqueness of the log file name is guaranteed, and various operations on the log file in the later period are facilitated.
Further, the configuration file comprises a log level;
setting corresponding log levels for the log levels in the corresponding configuration files according to different versions of the application program;
the S3 includes:
reading the log grade of the configuration file;
and judging whether the log grade is a preset grade, if so, allowing the log to be written, and otherwise, disallowing the log to be written.
According to the description, the log level allowing the log file to be written is set in the configuration file, the threshold for writing the log is set, the log writing amount can be controlled, the storage space of the system is saved, the updating speed of the log is slowed down, the stability of the system is guaranteed, and the log with high importance degree can be conveniently checked.
Further, the configuration file further comprises a log folder size threshold and a log folder number threshold;
the step S32 further includes:
s321, reading a log folder size threshold in the configuration file, judging whether the size of the log folder is smaller than the log folder size threshold, if so, executing the step S322, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S321;
s322, reading a log folder file number threshold value in the configuration file, judging whether the file number in the log folder is smaller than the log folder file number threshold value or not, if so, executing S323, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S322;
s323, reading the log category in the configuration file, acquiring the current time, determining the log file name according to the log category and the current time, creating a log file corresponding to the log file name in the log folder, and writing the log in the log file.
It can be known from the above description that the total system storage space that can be utilized by the log files is limited, it is ensured that the system storage space of other functions is not occupied due to excessive generation of the log files, the stability of the system is improved, the size of the log folder and the number of the log files therein are detected before the log is written each time, and compared with a preset threshold, if the log folder size exceeds the threshold, the oldest log is deleted according to the log file name, and it is ensured that the space occupied by the log files is always within the limited range.
Further, the writing the log in the log file includes:
calling a log writing interface;
writing the log into the log file through the log writing interface;
and after the log writing is finished, updating the log writing interface.
According to the description, the log writing interface is called to complete the log writing operation, so that the format of the log is unified, various operations on the log file at the later stage are facilitated, and after the log writing is completed, the log writing interface is updated instead of creating a new interface, so that the system resources are saved.
Referring to fig. 2, a log management terminal includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the following steps:
s1, setting a corresponding configuration file for each application program;
s2, receiving a log writing request, and determining a corresponding configuration file according to the type of the log;
and S3, writing the log according to the configuration file.
The invention has the beneficial effects that: the log management method has the advantages that the corresponding configuration file is set for each application program, the log is written according to the corresponding configuration file when written, unified management of the log files of the application programs is achieved, the log files of the application programs are standardized, independence of log management of different application programs is guaranteed, mutual influence is avoided, operation on the log files is facilitated, management operation on the log files of the application programs is facilitated, expansion development of the application programs is facilitated, and stability of a system is guaranteed.
Further, the configuration file comprises a log storage path and a log category;
the S2 includes:
receiving a log writing request, and matching a configuration file with the same log type according to the log type contained in the log writing request;
the S3 includes:
s31, reading a log storage path in the configuration file, judging whether a log folder exists according to the log storage path, if not, creating the log folder, and executing S32, otherwise, executing S32;
s32, reading the log category in the configuration file, obtaining the current time, determining the name of the log file according to the log category and the current time, creating a log file corresponding to the name of the log file in the log folder, and writing the log in the log file.
According to the description, the configuration files are matched according to the log types, the logs of the same type have the same storage path, later retrieval and checking are facilitated, the log file is created according to the log types and the current time, the uniqueness of the log file name is guaranteed, and various operations on the log file in the later period are facilitated.
Further, the configuration file comprises a log level;
setting corresponding log levels for the log levels in the corresponding configuration files according to different versions of the application program;
the S3 includes:
reading the log grade of the configuration file;
and judging whether the log grade is a preset grade, if so, allowing the log to be written, and otherwise, disallowing the log to be written.
According to the description, the log level allowing the log file to be written is set in the configuration file, the threshold for writing the log is set, the log writing amount can be controlled, the storage space of the system is saved, the updating speed of the log is slowed down, the stability of the system is guaranteed, and the log with high importance degree can be conveniently checked.
Further, the configuration file further comprises a log folder size threshold and a log folder number threshold;
the step S32 further includes:
s321, reading a log folder size threshold in the configuration file, judging whether the size of the log folder is smaller than the log folder size threshold, if so, executing the step S322, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S321;
s322, reading a log folder file number threshold value in the configuration file, judging whether the file number in the log folder is smaller than the log folder file number threshold value or not, if so, executing S323, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S322;
s323, reading the log category in the configuration file, acquiring the current time, determining the log file name according to the log category and the current time, creating a log file corresponding to the log file name in the log folder, and writing the log in the log file.
It can be known from the above description that the total system storage space that can be utilized by the log files is limited, it is ensured that the system storage space of other functions is not occupied due to excessive generation of the log files, the stability of the system is improved, the size of the log folder and the number of the log files therein are detected before the log is written each time, and compared with a preset threshold, if the log folder size exceeds the threshold, the oldest log is deleted according to the log file name, and it is ensured that the space occupied by the log files is always within the limited range.
Further, the writing the log in the log file includes:
calling a log writing interface;
writing the log into the log file through the log writing interface;
and after the log writing is finished, updating the log writing interface.
According to the description, the log writing interface is called to complete the log writing operation, so that the format of the log is unified, various operations on the log file at the later stage are facilitated, and after the log writing is completed, the log writing interface is updated instead of creating a new interface, so that the system resources are saved.
Referring to fig. 1, a first embodiment of the present invention is:
a log management method specifically comprises the following steps:
s1, setting a corresponding configuration file for each application program;
the configuration file comprises a log storage path, a day type, a log grade, a log folder size threshold, a log folder file number threshold and a single log file maximum line number;
wherein, the log file name consists of a log category and a creation time;
the log types comprise can bus logs, task logs, tracking algorithm logs and the like;
the log levels comprise DEBUG, INFO, WARNING and ERROR, the levels are sequentially increased according to the sequence, and the higher the level is, the higher the importance degree is;
preferably, when the application program test version is used, the log level can be set to DEBUG, all logs can be checked conveniently, and then various debugging can be carried out on the application program, when the application program version is stable, the level can be increased, if the log level is set to WARNING, only the log with the log level of WARNING or ERROR can be written into a log file, the output quantity of the log can be controlled effectively, and unnecessary resource waste is avoided;
the format of each log is [ time ] [ log level ] [ calling function name ] [ line ] log content;
setting corresponding log levels for the log levels in the corresponding configuration files according to different versions of the application program;
s2, receiving a log writing request, and determining a corresponding configuration file according to the type of the log;
the S2 includes:
receiving a log writing request, and matching a configuration file with the same log type according to the log type contained in the log writing request;
and S3, writing the log according to the configuration file.
The writing of the log comprises:
calling a log writing interface;
l ogPrint (int log _ type, int log _ level, char _ fun _ name, int line _ n, char _ log _ msg), wherein int log _ type corresponds to the log category, int log _ level corresponds to the log level, char _ fun _ name corresponds to the function name of the current call log write interface, int line _ n corresponds to the number of rows of log files of the current call log write interface, and char _ log _ msg is the content of the log to be written;
writing the log into the log file through the log writing interface;
storing all log file handles by using an FI L E log _ handle [ MAX ] pointer, determining a corresponding log file through a log _ type log category when a L ogPrint () interface is called, further determining a corresponding handle, writing log content into the log file, and recording the number of log lines;
after the log writing is finished, updating the log writing interface;
after the log writing is finished, updating the number of log file lines in the log writing interface;
when a new log file is created, only the handle in the log _ handle needs to be updated, and a new interface is not created.
Referring to fig. 3, fig. 4, fig. 5 and fig. 6, a second embodiment of the present invention is:
a log management method, which is different from the first embodiment in that the S3 includes:
s31, referring to FIG. 3, reading the log storage path in the configuration file, judging whether a log folder exists according to the log storage path, if not, creating the log folder, finishing initializing the log folder, and executing S32, otherwise, executing S32;
if the log storage path is failed to be established, jumping out of the response prompt and finishing the operation;
s32, please refer to fig. 4, reading the log category in the configuration file, obtaining the current time, determining the log file name according to the log category and the current time, creating a log file corresponding to the log file name in the log folder, and writing the log in the log file through a log writing interface;
preferably, a default log file name generation rule is set in the configuration file, and if the current time fails to be acquired, a default log file name is generated according to the default log file name generation rule;
further comprising:
reading the log grade of the configuration file;
judging whether the log grade is a preset grade or not, if so, allowing the log to be written in, and otherwise, not allowing the log to be written in;
referring to fig. 5, the step S32 further includes:
s321, reading a log folder size threshold in the configuration file, judging whether the size of the log folder is smaller than the log folder size threshold, if so, executing the step S322, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S321;
s322, reading a log folder file number threshold value in the configuration file, judging whether the file number in the log folder is smaller than the log folder file number threshold value or not, if so, executing S323, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S322;
s323, reading the log category in the configuration file, acquiring the current time, determining the log file name according to the log category and the current time, creating a log file corresponding to the log file name in the log folder, and writing the log in the log file;
referring to fig. 6, preferably, when log writing is performed, it is determined whether each line written is the tenth line written at this time, if yes, the log file line number threshold in the configuration file is read, it is determined whether the line number of the log file being written is smaller than the log file line number threshold in the configuration file, if yes, the writing operation is continued, and the number of times of writing is cleared;
otherwise, closing the currently written log file, determining the name of a new log file and creating the new log file according to the category and the current time of the currently written log file, opening the new log file, and continuing the writing operation;
if the line number of the log file is larger than the threshold value of the line number of the log file in the configuration file, calling a close () function to close the current log file, calling an open () function to open the created new log file, and updating a handle in the log _ handle.
Referring to fig. 2, a third embodiment of the present invention is:
a log management terminal 1, the terminal 1 comprising a processor 2, a memory 3 and a computer program stored on the memory 3 and operable on the processor 2, the processor 2 implementing the steps of the first or second embodiment when executing the computer program.
In summary, the present invention provides a log management method and a terminal, where the log management method and the terminal perform unified management on application logs by setting a corresponding configuration file for each application program, determine a corresponding configuration file according to a type of the log when the log is written, and write the log into the log file according to the configuration file, so that logs of different application programs can be managed in an integrated manner, and operations such as searching and checking the log file are facilitated; a specific log storage path and a name mode of a log file are set in a configuration file, so that the log file is conveniently searched, and the log file is searched in a mode of log category and log file creation time, so that the uniqueness of the log file name is ensured; the log grade, the log folder size threshold, the log folder file number threshold and the log file maximum line number threshold are set to limit the storage mode and the occupied storage space of the log files in many ways, so that the system resources occupied by log management are ensured to be within a preset range, the use of other modules of the system is not influenced, the system resources of the embedded system can be utilized to the maximum extent, and the stability of the system is ensured; the log is written into the log file in an interface mode, a plurality of interfaces are not required to be created by matching with file handles, the writing operation can be completed only by updating one interface, and system resources are further saved.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (10)
1. A log management method, comprising the steps of:
s1, setting a corresponding configuration file for each application program;
s2, receiving a log writing request, and determining a corresponding configuration file according to the type of the log;
and S3, writing the log according to the configuration file.
2. The log management method of claim 1, wherein the configuration file comprises a log storage path and a log category;
the S2 includes:
receiving a log writing request, and matching a configuration file with the same log type according to the log type contained in the log writing request;
the S3 includes:
s31, reading a log storage path in the configuration file, judging whether a log folder exists according to the log storage path, if not, creating the log folder, and executing S32, otherwise, executing S32;
s32, reading the log category in the configuration file, obtaining the current time, determining the name of the log file according to the log category and the current time, creating a log file corresponding to the name of the log file in the log folder, and writing the log in the log file.
3. The log management method of claim 1, wherein the configuration file comprises a log level;
setting corresponding log levels for the log levels in the corresponding configuration files according to different versions of the application program;
the S3 includes:
reading the log grade of the configuration file;
and judging whether the log grade is a preset grade, if so, allowing the log to be written, and otherwise, disallowing the log to be written.
4. The log management method of claim 2, wherein the configuration file further comprises a log folder size threshold and a log folder number threshold;
the step S32 further includes:
s321, reading a log folder size threshold in the configuration file, judging whether the size of the log folder is smaller than the log folder size threshold, if so, executing the step S322, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S321;
s322, reading a log folder file number threshold value in the configuration file, judging whether the file number in the log folder is smaller than the log folder file number threshold value or not, if so, executing S323, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S322;
s323, reading the log category in the configuration file, acquiring the current time, determining the log file name according to the log category and the current time, creating a log file corresponding to the log file name in the log folder, and writing the log in the log file.
5. A log management method according to any one of claims 2 to 4, wherein said writing the log in the log file comprises:
calling a log writing interface;
writing the log into the log file through the log writing interface;
and after the log writing is finished, updating the log writing interface.
6. A log management terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:
s1, setting a corresponding configuration file for each application program;
s2, receiving a log writing request, and determining a corresponding configuration file according to the type of the log;
and S3, writing the log according to the configuration file.
7. The log management terminal of claim 6, wherein the configuration file comprises a log storage path and a log category;
the S2 includes:
receiving a log writing request, and matching a configuration file with the same log type according to the log type contained in the log writing request;
the S3 includes:
s31, reading a log storage path in the configuration file, judging whether a log folder exists according to the log storage path, if not, creating the log folder, and executing S32, otherwise, executing S32;
s32, reading the log category in the configuration file, obtaining the current time, determining the name of the log file according to the log category and the current time, creating a log file corresponding to the name of the log file in the log folder, and writing the log in the log file.
8. The log management terminal of claim 6, wherein the configuration file comprises a log level;
setting corresponding log levels for the log levels in the corresponding configuration files according to different versions of the application program;
the S3 includes:
reading the log grade of the configuration file;
and judging whether the log grade is a preset grade, if so, allowing the log to be written, and otherwise, disallowing the log to be written.
9. The log management terminal of claim 7, wherein the configuration file further comprises a log folder size threshold and a log folder number threshold;
the step S32 further includes:
s321, reading a log folder size threshold in the configuration file, judging whether the size of the log folder is smaller than the log folder size threshold, if so, executing the step S322, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S321;
s322, reading a log folder file number threshold value in the configuration file, judging whether the file number in the log folder is smaller than the log folder file number threshold value or not, if so, executing S323, otherwise, reading all log file names of the log folder, determining the earliest log file according to the log file names, deleting the log file, and returning to the step S322;
s323, reading the log category in the configuration file, acquiring the current time, determining the log file name according to the log category and the current time, creating a log file corresponding to the log file name in the log folder, and writing the log in the log file.
10. A log management terminal according to any one of claims 7 to 9, wherein the writing of the log in the log file comprises:
calling a log writing interface;
writing the log into the log file through the log writing interface;
and after the log writing is finished, updating the log writing interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010273030.5A CN111459764B (en) | 2020-04-09 | 2020-04-09 | Log management method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010273030.5A CN111459764B (en) | 2020-04-09 | 2020-04-09 | Log management method and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111459764A true CN111459764A (en) | 2020-07-28 |
| CN111459764B CN111459764B (en) | 2023-12-29 |
Family
ID=71685178
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010273030.5A Active CN111459764B (en) | 2020-04-09 | 2020-04-09 | Log management method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111459764B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111966655A (en) * | 2020-08-18 | 2020-11-20 | 中国银行股份有限公司 | Method and device for managing file objects in memory in log collection process |
| CN113448818A (en) * | 2021-07-01 | 2021-09-28 | 山东浪潮通软信息科技有限公司 | Log tracking method, device and medium based on probability |
| CN115543949A (en) * | 2022-09-27 | 2022-12-30 | 北京北方华创微电子装备有限公司 | Log processing method and semiconductor process equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106326082A (en) * | 2015-06-16 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for recording log in network system |
| CN106406771A (en) * | 2016-10-20 | 2017-02-15 | 福建天泉教育科技有限公司 | Log recording method and log recorder |
| CN109508246A (en) * | 2018-06-25 | 2019-03-22 | 广州多益网络股份有限公司 | Log recording method, system and computer readable storage medium |
-
2020
- 2020-04-09 CN CN202010273030.5A patent/CN111459764B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106326082A (en) * | 2015-06-16 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for recording log in network system |
| CN106406771A (en) * | 2016-10-20 | 2017-02-15 | 福建天泉教育科技有限公司 | Log recording method and log recorder |
| CN109508246A (en) * | 2018-06-25 | 2019-03-22 | 广州多益网络股份有限公司 | Log recording method, system and computer readable storage medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111966655A (en) * | 2020-08-18 | 2020-11-20 | 中国银行股份有限公司 | Method and device for managing file objects in memory in log collection process |
| CN111966655B (en) * | 2020-08-18 | 2023-10-24 | 中国银行股份有限公司 | Method and device for managing file objects in memory in log acquisition process |
| CN113448818A (en) * | 2021-07-01 | 2021-09-28 | 山东浪潮通软信息科技有限公司 | Log tracking method, device and medium based on probability |
| CN115543949A (en) * | 2022-09-27 | 2022-12-30 | 北京北方华创微电子装备有限公司 | Log processing method and semiconductor process equipment |
| CN115543949B (en) * | 2022-09-27 | 2023-09-08 | 北京北方华创微电子装备有限公司 | Log processing method and semiconductor process equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111459764B (en) | 2023-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110147411B (en) | Data synchronization method, device, computer equipment and storage medium | |
| CN111459764A (en) | Log management method and terminal | |
| US8396840B1 (en) | System and method for targeted consistency improvement in a distributed storage system | |
| WO2013016054A1 (en) | A system and method for identifying fault prone computer code files | |
| CN107800757B (en) | User behavior recording method and device | |
| US9104567B2 (en) | Memory-leak identification | |
| CN108446224B (en) | Performance analysis method of application program on mobile terminal and storage medium | |
| CN111694684B (en) | Abnormal construction method and device of storage device, electronic device and storage medium | |
| US20210026756A1 (en) | Deriving software application dependency trees for white-box testing | |
| CN111061802A (en) | Power data management processing method and device and storage medium | |
| CN112000971B (en) | File permission recording method, system and related device | |
| EP0883061A1 (en) | Debugging method for a microcomputer system and recording medium on which debug program is recorded | |
| CN113312322A (en) | STDF file reading and writing method, medium, equipment and device | |
| CN110119351B (en) | Test case execution method and device | |
| CN110166326B (en) | Real-time automatic tracking system for communication protocol data | |
| CN112114987B (en) | Abnormality detection method and device for operation environment, intelligent terminal and storage medium | |
| CN113238901A (en) | Multi-device automatic testing method and device, storage medium and computer device | |
| CN111694727A (en) | Network card firmware upgrading and downgrading test method, system, terminal and storage medium | |
| CN110795297B (en) | Electronic equipment testing method and device | |
| CN114116291B (en) | Log detection method, log detection device, computer device and storage medium | |
| CN112732816B (en) | Data export method and system | |
| CN116700763B (en) | Version upgrading method and device for Clickhouse database | |
| CN112866218B (en) | Processing method for remotely collecting system information and related equipment | |
| CN109299036B (en) | Label generation method, device, server and computer readable storage medium | |
| CN114281760A (en) | Registration method and system of data item file, electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |