CN115858483A - Log analysis and management method, terminal and computer readable storage medium - Google Patents
Log analysis and management method, terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN115858483A CN115858483A CN202111117689.2A CN202111117689A CN115858483A CN 115858483 A CN115858483 A CN 115858483A CN 202111117689 A CN202111117689 A CN 202111117689A CN 115858483 A CN115858483 A CN 115858483A
- Authority
- CN
- China
- Prior art keywords
- log
- output
- target
- management method
- analysis
- 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
- 238000004458 analytical method Methods 0.000 title claims abstract description 52
- 238000007726 management method Methods 0.000 title claims abstract description 39
- 238000000034 method Methods 0.000 claims abstract description 46
- 230000008569 process Effects 0.000 claims abstract description 32
- 230000015654 memory Effects 0.000 claims description 36
- 238000004590 computer program Methods 0.000 claims description 13
- 230000005764 inhibitory process Effects 0.000 claims description 3
- 230000002401 inhibitory effect Effects 0.000 claims 1
- 238000012544 monitoring process Methods 0.000 abstract description 5
- 230000001360 synchronised effect Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 4
- 238000004422 calculation algorithm Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000012216 screening Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000002411 adverse Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The application discloses a log analysis and management method, a terminal and a computer readable storage medium, wherein the log analysis and management method comprises the following steps of determining a target log according to a log to be output; and adjusting the output decision of the log to be output according to the historical output frequency of the target log and the output prohibited times. According to the log analysis and management method, the terminal and the computer readable storage medium, log output is effectively improved by monitoring and managing the log output process, the log can be effectively prevented from influencing the system performance, and the user experience is improved.
Description
Technical Field
The present application relates to the field of log analysis and management, and in particular, to a log analysis and management method, a terminal, and a computer-readable storage medium.
Background
When a terminal developer develops an application program, logs are often printed on some important modules and methods, so that the problem can be conveniently positioned and analyzed and solved at the later stage. At present, logs are mainly output through a log tool, but when a developer uses the log tool, due to the reasons that the print logs are not standardized, the print log codes are incorrect, temporarily debugged logs are not deleted, and the like, the following problems are easily caused to occur: 1) A large number of repeated logs are output intermittently in a very short time; 2) The same log is continuously output for a long time and the interval time is very short.
The above problems can cause some adverse effects:
1) For other developers, because some modules output a large amount of logs, the log files are very large, a small amount of logs of the modules are mixed in the logs, the analysis difficulty is increased, and sometimes a terminal system discards part of logs because the logs are too many to output in time, so that the analysis and positioning problems are influenced;
2) For a terminal system, a large number of logs are printed in a short time, which may cause overflow of log cache, system log progress is blocked, and logs cannot be printed any more, so that the logs cannot be obtained any more after the system has a problem;
3) For an actual user, if the system frequently inputs logs for a long time, file reading and writing resources of the system are always occupied, the performance of the system is reduced, and in severe cases, the terminal is heated, the system is jammed, the screen is blacked, and the system can only be restarted.
Disclosure of Invention
In view of the above technical problems, the present application provides a log analysis and management method, a terminal, and a computer-readable storage medium, which can effectively avoid the log from affecting the system performance, and improve the user experience.
In a first aspect, the present application provides a log analysis and management method, including the following steps:
determining a target log according to the log to be output;
and adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of forbidden output times.
In a second aspect, the present application further provides a terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the log analysis and management method when executing the computer program.
In a third aspect, the present application further provides a computer-readable storage medium, which stores a computer program, and the computer program, when executed by a processor, implements the steps of the log analysis and management method.
According to the log analysis and management method, the terminal and the computer readable storage medium, log output is effectively improved by monitoring and managing the log output process, the log can be effectively prevented from influencing the system performance, and the user experience is improved.
Drawings
Fig. 1 is a schematic flowchart of a log analysis and management method according to an embodiment of the present application;
fig. 2 is a first flowchart illustrating a specific log analysis and management method according to an embodiment of the present disclosure;
fig. 3 is a schematic specific flowchart of a log analysis and management method according to an embodiment of the present application;
fig. 4 is a schematic flowchart illustrating a specific flow of a log analysis and management method according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
In the following description, 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 application belongs. The terminology used herein in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items and includes such combinations.
As used in this specification and the appended claims, the terms "if", and "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
The technical solution of the present application is further described in detail with reference to the drawings and specific embodiments of the specification.
Fig. 1 is a schematic flowchart of a log analysis and management method provided in an embodiment of the present application, where the log analysis and management method may be executed by a log analysis and management device provided in an embodiment of the present application, and the log analysis and management device may be implemented in a software and/or hardware manner, and the log analysis and management device may specifically be a mobile terminal, a fixed terminal, and a terminal such as a car machine of a vehicle-mounted electronic device, as shown in fig. 1, where the log analysis and management method may include the following steps:
step S101: determining a target log according to the log to be output;
it should be noted that the target log may include the log to be output, and may also include a log with high content similarity to the log to be output. Optionally, the determining a target log according to the log to be output includes: acquiring a log file output by an application program corresponding to the log to be output according to the log information to be output; and acquiring the content similarity between each log included in the log file and the log to be output, and determining the log to be output and the log with the content similarity greater than or equal to a preset similarity threshold as target logs. The log information to be output may include information such as process information and an application package name corresponding to the log to be output, where the application package name is used to identify an application program corresponding to the log. The process is an example of a running program in a narrow sense, and is a running activity of a program with certain independent functions about a certain data set in a broad sense, each process has an independent process number, and process information carries an application packet name of a running application program. Here, the obtaining of the log file output by the application program corresponding to the log to be output according to the log information to be output may be searching according to a process number of the log to be output to obtain an application packet name corresponding to the process number of the log to be output, and further obtaining the log file corresponding to the application packet name, that is, the log file output by the application program corresponding to the log to be output. After the log file output by the application program corresponding to the log to be output is obtained, the content similarity of each log included in the log file and the log to be output can be calculated, and whether the content similarity is larger than or equal to a preset similarity threshold value or not is further judged. The similarity threshold may be set according to actual needs, for example, the similarity threshold may be set to 90%, 95%, or the like. In addition, the content similarity can be calculated by a method of string comparison, and the calculation method adopted includes but is not limited to: cosine similarity algorithm, matrix similarity algorithm, character string edit distance algorithm, etc. Therefore, the log similar to the content of the log to be output is selected as the target log, so that the log is accurately and comprehensively managed, and the log output is further improved.
Step S102: and adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of forbidden output times.
It is understood that the historical output frequency of the target log is used to characterize the output condition of the target log before the log to be output is obtained, for example, whether the output is frequent or not, etc. Optionally, before the adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of times of prohibited output, the method further includes: counting the output times of the target log within a preset historical time length; and acquiring the historical output frequency of the target log according to the preset historical duration and the output times. The historical time length may be set according to actual needs, for example, the historical time length may be set to be within 1 hour before the current time, within 24 hours before the current time, 72 hours before the current time, and the like. Based on the ratio of the output times to the preset historical duration, the historical output frequency of the target log, such as the number of output logs per minute or second, can be obtained. Therefore, the historical output frequency of the log is determined based on the output times of the log in the historical time, and the method is simple and convenient to operate and high in accuracy.
Optionally, the adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of times of prohibited output includes at least one of:
if the historical output frequency is lower than or equal to a preset frequency, allowing the log to be output;
and if the historical output frequency of the target log is higher than the preset frequency and/or the number of times of the target log which is forbidden to be output is higher than the preset number of times, forbidding the output of the log to be output.
It can be understood that if the historical output frequency of the target log is lower than or equal to the preset frequency, which indicates that the output of the target log is less before, the output of the log to be output does not need to be controlled, that is, the log to be output is allowed to be output. If the historical output frequency of the target log is higher than the preset frequency, which indicates that the target log is output more before, the output of the log to be output needs to be controlled at the moment, namely, the output of the log to be output is prohibited. If the number of times that the target log is prohibited from being output is higher than the preset number of times, it is indicated that the log output is already managed and controlled before, and at this time, the log output to be output can be continuously prohibited.
In summary, in the log analysis and management method provided in the foregoing embodiment, log output is effectively improved by monitoring and managing the log output process, which can effectively avoid the log from affecting system performance, and improve user experience.
Optionally, before the adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of times of prohibited output, the method further includes:
detecting whether the log length of the log to be output is greater than or equal to a preset length threshold value;
and when the log length of the log to be output is determined to be greater than or equal to a preset length threshold, executing a step of adjusting an output decision of the log to be output according to the historical output frequency of the target log and the number of times of output inhibition.
The length threshold may be set according to actual needs, and is not specifically limited herein. It can be understood that when the log length of the log to be output is greater than or equal to the preset length threshold, it indicates that the log length of the log to be output is longer, and accordingly, outputting the similar log may need to occupy more resources, thereby affecting the system performance, and when the log length of the log to be output is smaller than the preset length threshold, it indicates that the log length of the log to be output is shorter, and accordingly, outputting the similar log may not need to occupy more resources, thereby affecting the system performance less. Therefore, when the length of the log to be output is determined to be greater than or equal to the preset length threshold, the output decision of the log to be output is adjusted according to the historical output frequency of the target log and the output prohibited times, the log can be further effectively prevented from influencing the system performance, and the use experience of a user is further improved.
Optionally, after the output of the log to be output is prohibited, the method further includes the following steps: and recording the log to be output to a log report. Therefore, after the output of the log is forbidden, the log is correspondingly recorded into the log report so as to be convenient for analyzing the log in the following process, and the analysis efficiency is improved.
Optionally, the log analysis and management method provided by the present application further includes the following steps:
acquiring an application package name corresponding to a process of an output log;
classifying the output logs according to the application package names so as to divide the output logs with the same application package names into the same log file;
and counting the file length of each generated log file, the average interval time of log output, the log content similarity and the log printing frequency, and generating a corresponding log packet analysis report.
Specifically, firstly, for a log file packet which is stored in a local system and consists of output logs, acquiring process numbers of all the output logs in the log file packet; then, according to the process number of each output log, starting the process log through a process state viewing command and/or an activity manager to obtain the application package name corresponding to the process of each output log; classifying the output logs according to the application package names so as to divide the output logs with the same application package names into the same log file, namely each application corresponds to a separate log file; and finally, counting the file length, the log output average interval time, the log content similarity and the log printing frequency of each log file aiming at each log file, and generating a corresponding log packet analysis report. It should be noted that only log information with a log printing frequency greater than a preset frequency may be added to the log packet analysis report. Of course, an analysis report for a single log file may also be generated for each log file. Therefore, a corresponding analysis report is generated according to the log output condition, so that the actual condition of the log output process is presented in a data form, the log is conveniently analyzed subsequently, the problems in the log output process are discovered and improved in time, and the analysis efficiency is further improved.
Optionally, the log analysis and management method provided by the present application further includes the following steps:
acquiring the resource occupancy of a log output process;
and when the resource occupancy exceeds a preset occupancy threshold, outputting warning information.
Wherein the resource occupancy includes at least one of a CPU occupancy and a file read/write (IO) occupancy. Different occupancy threshold values may be set for CPU occupancy and file read/write (IO) occupancy. And the output form of the warning information comprises at least one of pop-up window reminding, warning sound reminding and preset light reminding. Therefore, when the resource occupancy rate of the log output process is high, early warning is timely carried out so as to timely control the condition that the load of the log output process is high, and the user experience is further improved.
Based on the same inventive concept of the foregoing embodiment, the log analysis and management method is applied to a car machine, and is described in detail through specific scenarios and examples.
Scenario one, intermittent output of large (repeated) logs in very short time
The car machine monitors when the log is output, and when a certain application continuously outputs a large number of repeated logs in a very short time, the application log output is reduced at a first frequency. When the number of times of reduction of the log output also exceeds the threshold, the log output is prohibited and the log report is recorded.
Based on the foregoing scenario, referring to fig. 2, the log analysis and management method provided in the embodiment of the present application may include the following steps:
step S201: acquiring log information to be printed and output by the vehicle-mounted application;
step S202: detecting whether the length of the log exceeds a length threshold, if so, executing a step S203, otherwise, executing a step S208;
step S203: judging whether the output frequency before the log is greater than a frequency threshold value or not according to the application packet name corresponding to the log, if so, executing a step S204, otherwise, executing a step S208;
step S204: judging whether the discarding times reaches a time threshold, if so, executing a step S205, otherwise, executing a step S207;
step S205: setting an output prohibition identifier;
step S206: generating a log exception report;
step S207: discarding the log;
step S208: the log is output.
Scene two, monitoring and managing the log which continuously outputs the same for a long time
The car machine monitors when the log is output, and when the frequency of continuously outputting the same log for a long time by a certain application exceeds a threshold value, the log output is gradually reduced. If the frequency still exceeds the threshold value after the reduction, the log output is prohibited, and the log report is recorded.
Based on the foregoing scenario, referring to fig. 3, the log analysis and management method provided in the embodiment of the present application may include the following steps:
step S301: acquiring log information to be printed and output by the vehicle-mounted application;
step S302: judging whether the log is output before according to the name of the application packet corresponding to the log, if so, executing a step S303, otherwise, executing a step S308;
step S303: judging whether the log output frequency is greater than a frequency threshold value, if so, executing a step S304, otherwise, executing a step S308;
step S304: judging whether the discarding frequency reaches a frequency threshold value, if so, executing a step S305, otherwise, executing a step S307;
step S305: setting an output prohibition identifier;
step S306: generating a log exception report;
step S307: discarding the log;
step S308: the log is output.
Scene three, analyzing vehicle-mounted system logs
The method comprises the steps of obtaining a local log file packet of the vehicle-mounted system, analyzing system logs in a period of time, screening logs according to application packet names, and calculating the total amount of printed logs, log similarity, logs with high printing frequency, average interval time of log output and the like so as to be referred by developers and modified item by item.
Based on the foregoing scenario, referring to fig. 4, the log analysis and management method provided in the embodiment of the present application may include the following steps:
step S401: acquiring a local log file packet of a vehicle-mounted system;
step S402: acquiring all processes of a log file;
step S403: acquiring a corresponding application package name through the process number;
step S404: screening logs according to the application package names so that each application package corresponds to one log file;
step S405: analyzing the log of each application package;
step S406: generating a log analysis result of each application package;
step S407: and summarizing and generating the analysis result of the log packet.
Scene four, monitoring the progress state of the vehicle-mounted log
And acquiring the log process file state of the vehicle-mounted system, and popping up a warning interface when the CPU or IO occupancy of the log process exceeds a threshold value to inform development and testing personnel of high log file process load.
In summary, the log analysis and management method provided by the embodiment of the application can perform layer-by-layer closing check on the log to be output, effectively avoid the situation of continuous output of a large amount of and/or repeated logs, improve the log output of a vehicle-mounted system, improve the problem analysis efficiency of technicians, improve the performance of a vehicle-mounted device, and improve the user experience.
Based on the same inventive concept as the foregoing embodiment, an embodiment of the present invention provides a terminal, as shown in fig. 5, including: a processor 310 and a memory 311 storing computer programs; the processor 310 illustrated in fig. 5 is not used to refer to the number of the processors 310 as one, but is only used to refer to the position relationship of the processor 310 relative to other devices, and in practical applications, the number of the processors 310 may be one or more; similarly, the memory 311 shown in fig. 5 is also used in the same sense, i.e. it is only used to refer to the position relationship of the memory 311 with respect to other devices, and in practical applications, the number of the memory 311 may be one or more. When the processor 310 runs the computer program, the log analysis and management method applied to the terminal is implemented.
The terminal may further include: at least one network interface 312. The various components in the terminal are coupled together by a bus system 313. It will be appreciated that the bus system 313 is used to enable communications among the components of the connection. The bus system 313 includes a power bus, a control bus, and a status signal bus in addition to the data bus. For clarity of illustration, however, the various buses are labeled as bus system 313 in FIG. 5.
The memory 311 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile Memory may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic random access Memory (FRAM), a magnetic random access Memory (Flash Memory), a magnetic surface Memory, an optical Disc, or a Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), synchronous Static Random Access Memory (SSRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), synchronous Dynamic Random Access Memory (SLDRAM), direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 311 described in connection with the embodiments of the present invention is intended to comprise, without being limited to, these and any other suitable types of memory.
The memory 311 in the embodiment of the present invention is used to store various types of data to support the operation of the terminal. Examples of such data include: any computer program for operation on the terminal, such as operating systems and application programs; contact data; telephone book data; a message; a picture; video, etc. The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application programs may include various application programs such as a Media Player (Media Player), a Browser (Browser), etc. for implementing various application services. Here, the program that implements the method of the embodiment of the present invention may be included in an application program.
Based on the same inventive concept of the foregoing embodiments, this embodiment further provides a computer storage medium, in which a computer program is stored, where the computer storage medium may be a Memory such as a magnetic random access Memory (FRAM), a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical Disc, or a Compact Disc Read Only Memory (CD-ROM), and the like; or may be a variety of devices including one or any combination of the above memories, such as a mobile phone, computer, tablet device, personal digital assistant, etc. When the computer program stored in the computer storage medium is run by a processor, the log analysis and management method applied to the terminal is implemented. Please refer to the description of the embodiment shown in fig. 1 for a specific step flow realized when the computer program is executed by the processor, which is not described herein again.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by functions and internal logic of the process, and should not constitute any limitation to the implementation process of the embodiments of the present application.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative methods and steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the embodiments of the present application, and they should be construed as being included in the present application.
Claims (10)
1. A log analysis and management method is characterized by comprising the following steps:
determining a target log according to the log to be output;
and adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of forbidden output times.
2. The log analysis and management method of claim 1, wherein the determining a target log according to the log to be output comprises:
acquiring a log file output by an application program corresponding to the log to be output according to the log information to be output;
and acquiring the content similarity between each log included in the log file and the log to be output, and determining the log to be output and the log with the content similarity greater than or equal to a preset similarity threshold as target logs.
3. The log analyzing and managing method according to claim 1, wherein before the adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of times of being prohibited from being output, the method further comprises:
detecting whether the log length of the log to be output is greater than or equal to a preset length threshold value;
and when the log length of the log to be output is determined to be greater than or equal to a preset length threshold, executing a step of adjusting an output decision of the log to be output according to the historical output frequency of the target log and the number of times of output inhibition.
4. The log analyzing and managing method according to claim 1, wherein before the adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of times of being prohibited from being output, the method further comprises:
counting the output times of the target log within a preset historical time;
and acquiring the historical output frequency of the target log according to the preset historical duration and the output times.
5. The log analysis and management method according to any one of claims 1 to 4, wherein the adjusting the output decision of the log to be output according to the historical output frequency of the target log and the number of times of output inhibition comprises at least one of:
if the historical output frequency is lower than or equal to a preset frequency, allowing the log to be output;
and if the historical output frequency of the target log is higher than the preset frequency and/or the number of times of the target log which is forbidden to be output is higher than the preset number of times, forbidding the output of the log to be output.
6. The log analyzing and managing method according to claim 1, further comprising, after said inhibiting of said log to be outputted, the steps of:
and recording the log to be output to a log report.
7. The log analysis and management method of claim 1, further comprising the steps of:
acquiring an application package name corresponding to a process of an output log;
classifying the output logs according to the application package names so as to divide the output logs with the same application package names into the same log file;
and counting the file length of each generated log file, the average interval time of log output, the log content similarity and the log printing frequency, and generating a corresponding log packet analysis report.
8. The log analysis and management method of claim 1, further comprising the steps of:
acquiring the resource occupancy of a log output process;
and outputting warning information when the resource occupancy exceeds a preset occupancy threshold.
9. A terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the log analysis and management method according to any one of claims 1 to 8 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out the steps of the log analysis and management method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111117689.2A CN115858483A (en) | 2021-09-23 | 2021-09-23 | Log analysis and management method, terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111117689.2A CN115858483A (en) | 2021-09-23 | 2021-09-23 | Log analysis and management method, terminal and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115858483A true CN115858483A (en) | 2023-03-28 |
Family
ID=85652395
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111117689.2A Pending CN115858483A (en) | 2021-09-23 | 2021-09-23 | Log analysis and management method, terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115858483A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117407315A (en) * | 2023-11-13 | 2024-01-16 | 镁佳(北京)科技有限公司 | Log optimization test method and device, computer equipment and storage medium |
-
2021
- 2021-09-23 CN CN202111117689.2A patent/CN115858483A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117407315A (en) * | 2023-11-13 | 2024-01-16 | 镁佳(北京)科技有限公司 | Log optimization test method and device, computer equipment and storage medium |
| CN117407315B (en) * | 2023-11-13 | 2024-04-12 | 镁佳(北京)科技有限公司 | Log optimization test method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5211751B2 (en) | Calculator, dump program and dump method | |
| CN110865888A (en) | Resource loading method and device, server and storage medium | |
| CN112346829A (en) | Method and equipment for task scheduling | |
| US20070022321A1 (en) | Exception analysis methods and systems | |
| CN112486966A (en) | Expired data cleaning method and device and electronic equipment | |
| CN115858483A (en) | Log analysis and management method, terminal and computer readable storage medium | |
| CN112130759A (en) | Parameter configuration method, system and related device of storage system | |
| CN113780163B (en) | Page loading time detection method and device, electronic equipment and medium | |
| CN110069217B (en) | Data storage method and device | |
| CN109388617B (en) | Method and device for judging reliability of file timestamp | |
| CN116719696A (en) | Method, device, equipment and storage medium for monitoring application program interface data | |
| CN115904589A (en) | Application program window watermark processing method and device and electronic equipment | |
| CN114510300A (en) | Method and equipment for embedding target object in derived class | |
| US11386206B2 (en) | Alerting unusual activities in an enterprise production environment | |
| CN113761524A (en) | Active window auditing method and system | |
| CN113971977A (en) | Method, device and equipment for detecting read interference influence of memory and storage medium | |
| CN112463048A (en) | Compact processing speed adjusting method and device, electronic equipment and medium | |
| CN113961968B (en) | Method and device for carrying out data desensitization interrupt post-processing on file | |
| CN117556146B (en) | Network data information processing system, method, equipment and medium | |
| CN114238419B (en) | Data caching method and device based on multi-tenant SaaS application system | |
| CN117435385B (en) | Log recording method and device, electronic equipment and storage medium | |
| CN112559052B (en) | Instruction set calling method, device, terminal and storage medium | |
| US10198342B1 (en) | Advanced binary instrumentation for debugging and performance enhancement | |
| US20230069336A1 (en) | Method of optimizing schedule for storage resource, server, and computer readable storage medium applying method | |
| CN111695159B (en) | Data processing method, device and equipment |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Country or region after: China Address after: Room 3701, No. 866 East Changzhi Road, Hongkou District, Shanghai, 200080 Applicant after: Botai vehicle networking technology (Shanghai) Co.,Ltd. Address before: Room 208, building 4, 1411 Yecheng Road, Jiading District, Shanghai, 201821 Applicant before: Botai vehicle networking technology (Shanghai) Co.,Ltd. Country or region before: China |