Log collection method, device, terminal device and readable storage medium

Abstract

The present application discloses a log collection method, apparatus, terminal device and readable storage medium. The present application obtains the type of a target program; obtains the version of the target program and / or the status of the target program; collects the running log of the target program according to the type of the target program and the version of the target program, and / or collects the running log of the target program according to the type of the target program and the status of the target program, thereby realizing the collection of the running program of the terminal device by using multiple log collection methods, thereby avoiding the performance of the terminal device being affected by the log collection process.

Description

Technical Field

[0001] The present invention relates to the technical field of log data storage, and in particular to a log collection method, device, terminal equipment and readable storage medium. Background Art

[0002] At present, terminal devices such as mobile phones and tablets generally include multiple programs, which can be divided into system programs and ordinary programs based on permissions. Under normal circumstances, system programs are always running and have relatively high permissions, while ordinary programs will only run when users use them, and have relatively low permissions and are limited to ordinary internal programs.

[0003] The existing operation log collection method for common programs and system programs has a frequent collection process and collects too many operation logs, which in turn occupies more system resources of the terminal device, reduces the performance of the terminal device, and seriously affects the user's use. Summary of the invention

[0004] In view of the above problems, the present application proposes a log collection method, apparatus, terminal device and readable storage medium to reduce excessive consumption of terminal device resources by log collection and improve the performance of the terminal device.

[0005] The present application embodiment provides a log collection method, the method comprising:

[0006] Get the type of the target program;

[0007] Obtaining a version of the target program and / or a status of the target program;

[0008] The operation log of the target program is collected according to the type of the target program and the version of the target program, and / or the operation log of the target program is collected according to the type of the target program and the status of the target program.

[0009] The log collection method described in the embodiment of the present application, wherein the operation log of the target program is collected according to the type of the target program and the version of the target program, comprises:

[0010] If the type of the target program is a common program and the version of the target program is a test version, using a common log collection program to collect all common operation logs of the target program;

[0011] If the type of the target program is a common program and the version of the target program is not a test version, a common log collection program is used to filter and collect common operation logs of the target program according to log levels and / or log tags.

[0012] The log collection method described in the embodiment of the present application, wherein the ordinary log collection program is used to filter and collect the ordinary operation log of the target program according to the log level and / or log tag, comprises:

[0013] Get preset levels and / or preset tag sets;

[0014] When the log level of the operation log of the target program is greater than or equal to the preset level, the ordinary log collection program is used to collect ordinary operation logs with log levels greater than or equal to the preset level; and / or, when the log tag of the operation log of the target program belongs to the preset tag set, the ordinary log collection program is used to collect ordinary operation logs with log tags belonging to the preset tag set.

[0015] The log collection method described in the embodiment of the present application, wherein the operation log of the target program is collected according to the type of the target program and the state of the target program, comprises:

[0016] If the type of the target program is a common program and the state of the target program is abnormal operation, determining whether the system log collection program is in a running state;

[0017] When the system log collection program is in operation, the system operation logs collected by the system log collection program and the ordinary operation logs collected by the ordinary log collection program are packaged and compressed for storage;

[0018] When the system log collection program is not in operation, the system log collection program is started, the system operation logs collected by the system log collection program and the ordinary operation logs collected by the ordinary log collection program are packaged and compressed for storage, and then the system log collection program is controlled to stop running.

[0019] The log collection method described in the embodiment of the present application, wherein the operation log of the target program is collected according to the type of the target program and the version of the target program, comprises:

[0020] If the type of the target program is a system program and the version of the target program is a test version, then starting a system log collection program, and using the system log collection program to collect the system operation log of the target program;

[0021] If the type of the target program is a system program and the version of the target program is not a test version, the system log collection program is kept in a stopped state.

[0022] The log collection method described in the embodiment of the present application also includes:

[0023] When the automatic log cleaning function is turned on, a predetermined number of operation logs with earlier storage dates are automatically deleted from the folder storing the operation logs according to a preset cleaning cycle.

[0024] The log collection method described in the embodiment of the present application also includes:

[0025] When collecting the operation log of the target program, determining whether the size of the folder used to store the operation log exceeds a preset threshold;

[0026] If the preset threshold is exceeded, a predetermined number of operation logs with earlier storage dates are deleted from the folder.

[0027] The present application also provides a log collection device, which includes:

[0028] A first acquisition module, used to acquire the type of the target program;

[0029] A second acquisition module, used to acquire the version of the target program and / or the status of the target program;

[0030] The log collection module is used to collect the operation log of the target program according to the type of the target program and the version of the target program, and / or to collect the operation log of the target program according to the type of the target program and the status of the target program.

[0031] An embodiment of the present application further provides a terminal device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program runs on the processor, the log collection method described in the embodiment of the present application is executed.

[0032] The embodiment of the present application further provides a readable storage medium storing a computer program, which executes the log collection method described in the embodiment of the present application when running on a processor.

[0033] The present application obtains the type of the target program; obtains the version and / or the status of the target program; collects the operation log of the target program according to the type of the target program and the version of the target program, and / or collects the operation log of the target program according to the type of the target program and the status of the target program, thereby realizing the collection of the running programs of the terminal device using multiple log collection methods, thereby avoiding the performance of the terminal device being affected by the log collection process. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solution of the present invention, the following will briefly introduce the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present invention and should not be regarded as limiting the scope of protection of the present invention. In each of the drawings, similar components are numbered similarly.

[0035] Figure 1 A schematic diagram of the process of the first log collection method proposed in the embodiment of the present application is shown;

[0036] Figure 2 The following is a flow chart of the log collection process in the first scenario proposed in the embodiment of the present application;

[0037] Figure 3 A schematic diagram of the flow of the log collection process in the second scenario proposed in the embodiment of the present application is shown;

[0038] Figure 4 A schematic diagram of the process of the second log collection method proposed in the embodiment of the present application is shown;

[0039] Figure 5 The following is a flow chart of the log collection process in the third scenario proposed in the embodiment of the present application;

[0040] Figure 6 A schematic diagram of the process of the third log collection method proposed in the embodiment of the present application is shown;

[0041] Figure 7 A schematic diagram of the structure of a log collection device proposed in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0042] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments.

[0043] The components of the embodiments of the present invention generally described and shown in the drawings herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0044] Hereinafter, the terms "including", "having" and their cognates, which may be used in various embodiments of the present invention, are intended only to indicate specific features, numbers, steps, operations, elements, components or combinations of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components or combinations of the foregoing items or adding the possibility of one or more features, numbers, steps, operations, elements, components or combinations of the foregoing items.

[0045] Furthermore, the terms “first”, “second”, “third”, etc. are merely used for distinguishing descriptions and are not to be understood as indicating or implying relative importance.

[0046] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meanings as those generally understood by those skilled in the art to which the various embodiments of the present invention belong. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meanings as the contextual meanings in the relevant technical field and will not be interpreted as having idealized meanings or overly formal meanings unless clearly defined in the various embodiments of the present invention.

[0047] Example 1

[0048] See also Figure 1 The first embodiment of the present application provides a log collection method, which includes the following steps:

[0049] Step S100, obtaining the type of the target program.

[0050] It can be understood that terminal devices such as mobile phones and tablets generally include multiple programs, which can be divided into system programs and ordinary programs according to permissions. Obtaining the type of the target program means determining whether the target program is a system program or an ordinary program.

[0051] Step S200, obtaining the version of the target program.

[0052] In this embodiment, in order to ensure that the log collection process of the test version of the target program is carried out normally, the version of the target program is divided into a test version and a non-test version, so as to implement different log collection methods based on the test version and the non-test version.

[0053] Step S300: collecting the running log of the target program according to the type of the target program and the version of the target program.

[0054] For example, see Figure 2 , step S300 may include the following steps:

[0055] Step S301, when the type of the target program is a common program, determining whether the version of the common program is a test version.

[0056] If the version of the common program is a test version, step S302 is executed; if the version of the target program is not a test version, step S303 is executed.

[0057] Step S302: Collect all common operation logs of the common program using a common log collection program.

[0058] Step S303: using a common log collection program to filter and collect common operation logs of the common program according to log levels and / or log tags.

[0059] The preset level can be obtained from a predetermined storage location of the terminal device. When the log level of the operation log of the common program is greater than or equal to the preset level, the common operation log with a log level greater than or equal to the preset level is collected using the common log collection program.

[0060] It can be understood that the log level can be divided into 6 levels from low to high: Verbose, Debug, Info, Warning, Error, and Assert. Verbose can mean detailed, indicating all possible logs, Debug can mean debugging, indicating all reasonable debugging logs, Info can be understood as information, indicating logs during normal use, Warning can be understood as warning, indicating that there may be a problem but no error has occurred, Error can be understood as error, indicating that there is a problem and causing an error), and Assert can be understood as assertion, indicating fatal and unrecoverable errors.

[0061] Exemplarily, if the preset level is Warning, then the operation log with the log level of Warning, Error or Assert is saved. It can be understood that the preset level can be set as needed.

[0062] A preset tag set may be obtained from a predetermined storage location of the terminal device, and when the log tag of the operation log of the common program belongs to the preset tag set, the common operation log whose log tag belongs to the preset tag set is collected by the common log collection program.

[0063] It can be understood that a log tag is a "keyword" of a log, and one or more words can be selected as log tags to mark a log. For example, if the log tags include important, easy, and hard, important and hard are saved in the preset tag set, and the ordinary log collection program is used to collect the operation logs with log tags of important or hard. The preset tag set can be set according to the requirements.

[0064] For example, see Figure 3 , step S300 may further include the following steps:

[0065] Step S304: when the type of the target program is a system program, determine whether the version of the system program is a test version.

[0066] If the version of the system program is a test version, step S305 is executed; if the version of the system program is not a test version, step S306 is executed.

[0067] Step S305, starting a system log collection program, and using the system log collection program to collect the system operation log of the system program.

[0068] Step S306, keeping the system log collection program in a stopped state.

[0069] It should be noted that the collection process corresponding to the above steps S301 to S303 and the collection process corresponding to the above steps S304 to S306 can be executed simultaneously, or only the collection process corresponding to the above steps S301 to S303 can be executed, or only the collection process corresponding to the above steps S304 to S306 can be executed.

[0070] This embodiment uses different log collection methods according to the version of the common program. When the version of the common program is not a test version, only specific logs can be collected as needed. Moreover, when the system program is not a test version, the operation log of the system program is not collected, thereby reducing the frequency of log collection and reducing log data, which can effectively ensure that the performance of the terminal device is not affected by the log collection process. When the common program or the system program is a test version, all operation log programs are collected, which does not affect the testing of the common program or the system program, thereby ensuring that the testing process can proceed normally.

[0071] Example 2

[0072] See also Figure 4 The second embodiment of the present application proposes another log collection method, which includes the following steps:

[0073] Step S100, obtaining the type of the target program.

[0074] Step S210, obtaining the status of the target program.

[0075] In this embodiment, the state of the target program includes normal operation and abnormal operation. By obtaining the state of the target program, logs can be collected using different log collection methods under different states.

[0076] Step S310: collecting the running log of the target program according to the type of the target program and the status of the target program.

[0077] For example, see Figure 5 , step S310 may include the following steps:

[0078] Step S311: If the type of the target program is a common program and the state of the target program is abnormal operation, it is determined whether the system log collection program is in a running state.

[0079] If the system log collection program is in the running state, step S312 is executed; if the system log collection program is not in the running state, step S313 is executed.

[0080] Step S312: Pack and compress the system operation logs collected by the system log collection program and the common operation logs collected by the common log collection program for storage.

[0081] Step S313, starting the system log collection program, packaging and compressing the system operation logs collected by the system log collection program and the common operation logs collected by the common log collection program, and then controlling the system log collection program to stop running.

[0082] Considering that when an ordinary program runs abnormally, it may be affected by its own program or by the system program. If only the ordinary operation log of the ordinary program is collected when the ordinary program is abnormal, it may not be able to fully reflect the abnormal problem. Therefore, when the ordinary program is abnormal, if the system log collection program is not started, the system log collection program will be awakened to ensure that the operation log of the ordinary program and the operation log of the system program are collected at the same time when the abnormality occurs, so as to facilitate the repair personnel to analyze the abnormal problem based on the operation log of the ordinary program and the operation log of the system program when the abnormality occurs, and ensure the repair efficiency of the abnormal program. In addition, after the system operation log collected by the system log collection program and the ordinary operation log collected by the ordinary log collection program are packaged and compressed for storage, the system log collection program is controlled to stop running, which can ensure that the resources of the terminal device are not wasted and the performance of the terminal device is not affected.

[0083] It should be noted that the compressed files can be named with the date, hour, minute and second to facilitate user reference.

[0084] Example 3

[0085] See also Figure 6 The third embodiment of the present application provides another log collection method, which includes the following steps:

[0086] Step S100, obtaining the type of the target program.

[0087] Step S200, obtaining the version of the target program.

[0088] Step S210, obtaining the status of the target program.

[0089] Step S300: collecting the running log of the target program according to the type of the target program and the version of the target program.

[0090] Step S310: collecting the running log of the target program according to the type of the target program and the status of the target program.

[0091] In this embodiment, the terminal device can simultaneously collect the operation log of the target program according to the type of the target program and the version of the target program, and collect the operation log of the target program according to the type of the target program and the state of the target program. In this embodiment, on the one hand, when the version of the common program is not a test version, only specific logs can be collected as needed, and when the system program is not a test version, the operation log of the system program is not collected, the frequency of log collection is reduced, and the reduced log data can effectively ensure that the performance of the terminal device is not affected by the log collection process. When the common program or the system program is a test version, all operation log programs are collected, which does not affect the test of the common program or the system program, and ensures that the test process can proceed normally; on the other hand, when the common program is abnormal, if the system log collection program is not started, the system log collection program will be awakened to ensure that the operation log of the common program and the operation log of the system program are collected at the same time when the abnormality occurs, so that the repair personnel can analyze the abnormal problem based on the operation log of the common program and the operation log of the system program when the abnormality occurs, and ensure the repair efficiency of the abnormal program.

[0092] Furthermore, in this embodiment, when the automatic log cleaning function is turned on, a predetermined number of operation logs with earlier storage dates are automatically deleted from the folder storing the operation logs according to a preset cleaning cycle, thereby avoiding other problems caused by too many logs occupying too much system storage.

[0093] Although regular log cleaning can reduce the storage space occupied by logs, in some cases, for example, a program abnormality lasts for a long time in a certain period of time, and a large number of logs may be saved in a short period of time. If only regular cleaning is relied upon, it may not be able to solve the problem of saving a large number of logs in a short period of time. Therefore, in this embodiment, when collecting the operation logs of the target program, it is determined whether the size of the folder used to save the operation logs exceeds a preset threshold; if it exceeds the preset threshold, a predetermined number of operation logs with earlier storage dates are deleted from the folder to avoid a large number of logs saved in a short period of time occupying too many resources and affecting system performance.

[0094] Exemplarily, each folder used to save the running log of the system program has a size limit of 500M. After the folder exceeds the size, half of the files in the folder will be deleted, the running log of the system program will continue to be written, and a scheduled task for daily regular cleanup will be started. The system log will be saved for a maximum of 3 days.

[0095] For example, each folder used to save the running log of the test version of the common program has a limit size of 100M. When the folder exceeds the size, half of the files will be deleted from the folder, and the running log of the common program will continue to be written, and the scheduled task of regular daily cleanup will be started. The common log will be saved for a maximum of 5 days. Each folder used to save the running log of the non-test version of the common program has a limit size of 10M. When the folder exceeds the size, half of the files will be deleted from the folder, and the running log of the common program will continue to be written, and the scheduled task of regular daily cleanup will be started. The common log will be saved for a maximum of 7 days.

[0096] Example 4

[0097] See also Figure 7 The fourth embodiment of the present application provides a log collection device 10 , which includes: a first acquisition module 11 , a second acquisition module 12 and a log collection module 13 .

[0098] The first acquisition module 11 is used to acquire the type of the target program; the second acquisition module 12 is used to acquire the version of the target program and / or the status of the target program; the log collection module 13 is used to collect the operation log of the target program according to the type of the target program and the version of the target program, and / or to collect the operation log of the target program according to the type of the target program and the status of the target program.

[0099] The log collection device 10 disclosed in this embodiment is used to execute the log collection method described in the above embodiment through the cooperation of the first acquisition module 11, the second acquisition module 12 and the log collection module 13. The implementation scheme and beneficial effects involved in the above embodiment are also applicable to this embodiment and will not be repeated here.

[0100] Example 5

[0101] The fifth embodiment of the present application provides a terminal device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program runs on the processor, the log collection method described in the above embodiment of the present application is executed.

[0102] Example 6

[0103] A sixth embodiment of the present application provides a readable storage medium storing a computer program, wherein the computer program, when running on a processor, executes the log collection method described in the above embodiments of the present application.

[0104] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or the flow chart, and the combination of boxes in the structure diagram and / or the flow chart, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0105] In addition, the functional modules or units in the various embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0106] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned readable storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0107] The above description is only a specific implementation mode of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A log collection method, characterized in that: The method comprises: Get the type of the target program; Obtaining a version of the target program and / or a status of the target program; Collecting the operation log of the target program according to the type of the target program and the version of the target program, and / or collecting the operation log of the target program according to the type of the target program and the status of the target program; Wherein, collecting the operation log of the target program according to the type of the target program and the state of the target program includes: If the type of the target program is a common program and the state of the target program is abnormal operation, determining whether the system log collection program is in a running state; When the system log collection program is in operation, the system operation logs collected by the system log collection program and the ordinary operation logs collected by the ordinary log collection program are packaged and compressed for storage; When the system log collection program is not in operation, the system log collection program is started, the system operation logs collected by the system log collection program and the ordinary operation logs collected by the ordinary log collection program are packaged and compressed for storage, and then the system log collection program is controlled to stop running.

2. The log collection method according to claim 1, characterized in that: The collecting the operation log of the target program according to the type of the target program and the version of the target program includes: If the type of the target program is a common program and the version of the target program is a test version, using a common log collection program to collect all common operation logs of the target program; If the type of the target program is a common program and the version of the target program is not a test version, a common log collection program is used to filter and collect common operation logs of the target program according to log levels and / or log tags.

3. The log collection method according to claim 2, characterized in that: The using of a common log collection program to filter and collect the common operation logs of the target program according to the log level and / or log tag includes: Get preset levels and / or preset tag sets; When the log level of the operation log of the target program is greater than or equal to the preset level, the ordinary log collection program is used to collect ordinary operation logs with log levels greater than or equal to the preset level; and / or, when the log tag of the operation log of the target program belongs to the preset tag set, the ordinary log collection program is used to collect ordinary operation logs with log tags belonging to the preset tag set.

4. The log collection method according to claim 1, characterized in that: The collecting the operation log of the target program according to the type of the target program and the version of the target program includes: If the type of the target program is a system program and the version of the target program is a test version, then starting a system log collection program, and using the system log collection program to collect the system operation log of the target program; If the type of the target program is a system program and the version of the target program is not a test version, the system log collection program is kept in a stopped state.

5. The log collection method according to any one of claims 1 to 4, characterized in that: Also includes: When the automatic log cleaning function is turned on, a predetermined number of operation logs with earlier storage dates are automatically deleted from the folder storing the operation logs according to a preset cleaning cycle.

6. The log collection method according to any one of claims 1 to 4, characterized in that: Also includes: When collecting the operation log of the target program, determining whether the size of the folder used to store the operation log exceeds a preset threshold; If the preset threshold is exceeded, a predetermined number of operation logs with earlier storage dates are deleted from the folder.

7. A log collection device, characterized in that: The device comprises: A first acquisition module, used to acquire the type of the target program; A second acquisition module, used to acquire the version of the target program and / or the status of the target program; A log collection module, used to collect the operation log of the target program according to the type of the target program and the version of the target program, and / or to collect the operation log of the target program according to the type of the target program and the status of the target program; Wherein, collecting the operation log of the target program according to the type of the target program and the state of the target program includes: If the type of the target program is a common program and the state of the target program is abnormal operation, determining whether the system log collection program is in a running state; When the system log collection program is in operation, the system operation logs collected by the system log collection program and the ordinary operation logs collected by the ordinary log collection program are packaged and compressed for storage; When the system log collection program is not in operation, the system log collection program is started, the system operation logs collected by the system log collection program and the ordinary operation logs collected by the ordinary log collection program are packaged and compressed for storage, and then the system log collection program is controlled to stop running.

8. A terminal device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and when the computer program is run on the processor, the log collection method according to any one of claims 1 to 6 is executed.

9. A readable storage medium, characterized in that: It stores a computer program, which executes the log collection method according to any one of claims 1 to 6 when running on a processor.

Images