JP2017045217A - Log management device, log management method, and log management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a log management device that enables efficient use of storage capacity by performing storage/deletion of logs corresponding to request from a user.SOLUTION: Three attenuation types rules for deleting logs are prepared ("period attenuation" in which logs are deleted sequentially from ones with lower importance levels according to lapse of period; "first execution frequency attenuation" in which logs are deleted sequentially from ones with lower importance levels according to increase of execution frequency of the same function; and "second execution frequency attenuation" in which logs are deleted sequentially from ones with lower importance levels according to increase of execution frequency of the function of the same group). A user uses a deletion condition setting file 126 to perform classification of logs to a plurality of importance levels and setting of log deletion condition by each importance level. A deletion part 43 deletes logs in a log file 122 according to setting contents of the deletion condition setting file 126.SELECTED DRAWING: Figure 4

Description

  The present invention relates to a log management device, a log management method, and a log management program that manage logs generated in various devices that perform processing using a computer.

  2. Description of the Related Art Conventionally, in various apparatuses that perform processing using a computer, logs are output and stored so that, for example, a past operation status of a process or a cause of a software defect can be investigated. For example, logs are output and stored in a substrate processing apparatus (such as a cleaning apparatus or an exposure apparatus) that performs processing on a substrate such as a semiconductor wafer. The substrate processing apparatus is schematically constituted by, for example, a main apparatus, a plurality of processing units, and a control board that controls the operation of each processing unit. A log (log data) indicating the operation status of each processing unit is stored in a storage unit provided on the control board, or sent from the control board to the main apparatus and stored in a storage unit in the main apparatus. . Logs are saved in this way, but there is a limit to the storage capacity. In addition, the amount of logs increases as the functionality of the device increases and the control specifications become more complex. Therefore, in general, each log stored in the storage unit has passed a predetermined period (a predetermined number of days or a predetermined time) from the output point so that the capacity of the storage unit is not excessively occupied by the log. It has been deleted later.

  In relation to the present invention, JP 2010-205128 A and JP 2013-168188 A disclose a robot control system invention capable of reducing the amount of logs stored in the storage unit. ing. This robot control system is provided with a temporary storage unit and a long-term storage unit. The log for one cycle of the program (the log for the latest cycle) is first held in the temporary storage unit. Then, a comparison is made between the log held in the temporary storage unit and the log corresponding to the log held in the temporary storage unit among the logs stored in the long-term storage unit. As a result, if they are different from each other, it is determined that long-term storage of the latest one period of log is necessary, and the log held in the temporary storage unit is written into the long-term storage unit. On the other hand, if both are the same, it is determined that long-term storage of the latest one period of log is unnecessary, and the log held in the temporary storage unit is deleted (deleted). In this way, the amount of logs stored in the long-term storage unit is reduced.

JP 2010-205128 A JP 2013-168188 A

  However, when logs are uniformly deleted based on the elapsed period (elapsed days or elapsed time) from the log output time, no logs before a certain time are left. For this reason, important information may be lost, and for example, the cause of the failure may not be sufficiently investigated. In addition, for logs in which a predetermined period has not elapsed since the output time point, a log from a high importance level to a low importance level is mixed in the storage unit. Due to the fact that logs with low importance remain unnecessarily, the cause investigation of malfunctions is rather inefficient. Therefore, there is a demand for development of a system that saves and deletes logs in response to a request from a user (user) of the apparatus. Note that JP 2010-205128 A and JP 2013-168188 A do not mention any deletion of logs stored in the long-term storage unit. Therefore, a log with high importance and a log with low importance are mixed in the long-term storage unit, and the cause investigation of the failure is not efficiently performed.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a log management apparatus that enables efficient use of storage capacity by storing and deleting logs according to user requests.

A first invention is a log management device,
Log classification means for classifying logs into multiple importance levels,
Deletion condition setting means for setting log deletion conditions, which are conditions used to determine whether or not to delete logs, according to importance,
Log deletion means for deleting a log based on the log deletion condition.

According to a second invention, in the first invention,
The deletion condition setting means includes a retention period setting means for setting a retention period from the log output time as the log deletion condition,
The log deleting unit deletes a log whose storage period set by the storage period setting unit has elapsed from the output time point.

According to a third invention, in the first or second invention,
The deletion condition setting unit includes a first execution number setting unit for setting a function execution number as the log deletion condition,
When a set of logs output when an arbitrary function is executed is defined as a function execution log group, the log deletion unit further includes the number of executions of the function set by the first execution number setting unit. Each time it is executed, the logs included in the function execution log group are deleted in descending order of importance.

According to a fourth invention, in the third invention,
The log classification means is configured to be able to classify importance into a plurality of categories so that one category includes one or more importance.
The log deleting means deletes logs included in the function execution log group in units of categories.

A fifth invention is the third or fourth invention, wherein
The deletion condition setting means is configured to be able to set a different number of executions for each function as the log deletion condition.

A sixth invention is the first or second invention, wherein
The deletion condition setting unit includes a second execution number setting unit for setting a function execution number as the log deletion condition,
When a set of logs output when a function included in an arbitrary group is executed in units of groups is defined as a group function execution log group, the log deletion unit is configured such that all functions included in the group are included in the second function group. Each time the number of executions set by the execution number setting means is further executed, the logs included in the group function execution log group are deleted in order of decreasing importance.

A seventh invention is the sixth invention, wherein
The log classification means is configured to be able to classify importance into a plurality of categories so that one category includes one or more importance.
The log deleting means deletes logs included in the group function execution log group in units of categories.

According to an eighth invention, in any one of the first to seventh inventions,
Each log is given an identifier to identify the importance,
The log deletion means determines whether or not the log is to be deleted based on an identifier attached to the log.

A ninth invention is a log management method,
A log classification step to classify logs into multiple importance levels;
A deletion condition setting step for setting log deletion conditions, which are conditions used to determine whether or not to delete logs, according to importance;
And a log deletion step of deleting a log based on the log deletion condition.

The tenth invention is a log management program,
A log classification step that accepts log classification to multiple importance levels;
A deletion condition setting step for accepting a setting according to the importance of a log deletion condition, which is a condition used for determining whether or not to delete a log;
The CPU of the computer executes a log deletion step of deleting a log based on the log deletion condition using a memory.

In an eleventh aspect based on the tenth aspect,
The deletion condition setting step includes a retention period setting step of accepting a retention period setting from the log output time as the log deletion condition,
In the log deletion step, a log in which the storage period set in the storage period setting step has elapsed from the output time point is deleted.

In a twelfth aspect based on the tenth or eleventh aspect,
The deletion condition setting step includes a first execution frequency setting step for accepting a setting of the number of executions of the function as the log deletion condition,
When a set of logs output when an arbitrary function is executed is defined as a function execution log group, in the log deletion step, the function is further executed by the number of executions set in the first execution number setting step. Each time it is performed, the logs included in the function execution log group are deleted in descending order of importance.

In a thirteenth aspect based on the twelfth aspect,
In the log classification step, it is possible to classify the importance into a plurality of categories so that one category includes one or more importance.
In the log deletion step, logs included in the function execution log group are deleted in units of categories.

In a fourteenth aspect based on the twelfth or thirteenth aspect,
In the deletion condition setting step, a different number of executions can be set for each function as the log deletion condition.

In a fifteenth aspect based on the tenth or eleventh aspect,
The deletion condition setting step includes a second execution frequency setting step for accepting setting of the function execution frequency as the log deletion condition,
When a set of logs output when a function included in an arbitrary group is executed in units of groups is defined as a group function execution log group, in the log deletion step, all the functions included in the group are added to the second function execution log group. Each time the number of executions set in the execution number setting step is further executed, the logs included in the group function execution log group are deleted in descending order of importance.

In a fifteenth aspect based on the fifteenth aspect,
In the log classification step, it is possible to classify the importance into a plurality of categories so that one category includes one or more importance.
In the log deletion step, logs included in the group function execution log group are deleted in units of categories.

According to a seventeenth aspect of the invention, in any one of the tenth to sixteenth aspects of the invention,
Each log is given an identifier to identify the importance,
In the log deletion step, it is determined whether or not the log is to be deleted based on an identifier attached to the log.

  According to the first aspect, the log is classified into a plurality of importance levels, and a condition for deleting the log is set for each importance level. For this reason, it is possible to delete the logs in order of decreasing importance. This makes it possible to quickly delete logs that are not required for investigating the cause of defects, and reducing the amount of storage capacity (resources) used to store logs without disturbing the cause of problems. Can be reduced. Further, by allowing the user to classify the log into a plurality of importance levels and to set the deletion condition, the user can estimate the usage amount of the storage capacity. Furthermore, since it is possible to save only important logs for a long time so that logs of various importance levels are not mixed, the cause of the failure is efficiently investigated, and the number of investigation steps when the failure occurs is reduced. Reduced.

  According to the second aspect of the present invention, it is possible to delete logs in descending order of importance as the period elapses based on the setting by the user.

  According to the third aspect of the invention, it is possible to delete logs in order of decreasing importance every time the same function is executed as many times as determined by the user.

  According to the fourth aspect, the log can be managed more finely.

  According to the fifth aspect, it is possible to change the way the logs are deleted, for example, according to the importance of the function.

  According to the sixth aspect, it is possible to delete logs in order from the least important every time all the functions included in one group are executed a number of times determined by the user.

  According to the seventh aspect, the log can be managed more finely.

  According to the eighth aspect, when the log deletion process is performed, it becomes possible to delete the deletion target log reliably and promptly.

  According to the ninth aspect, the same effect as that of the first aspect can be achieved in the invention of the log management method.

  According to the tenth to sixteenth inventions, the log management program invention can achieve the same effects as the first to eighth inventions.

It is a block diagram which shows schematic structure of the substrate processing apparatus which concerns on one Embodiment of this invention. In the said embodiment, it is a figure for demonstrating the function of a main apparatus. In the said embodiment, it is a block diagram which shows the hardware constitutions of the main apparatus which functions as a log management apparatus. In the said embodiment, it is a functional block diagram which shows the function structure of a log management apparatus. In the said embodiment, it is a figure which shows an example of the deletion condition setting file. In the said embodiment, it is a figure for demonstrating the condition setting area of a deletion condition setting file. In the said embodiment, it is a figure for demonstrating the setting of the conditions using a deletion condition setting file. In the said embodiment, it is a figure which shows the example of input to the data input area 54 of a deletion condition setting file. It is a flowchart which shows the procedure of the log deletion process in the said embodiment. In the said embodiment, it is a figure for demonstrating the deletion process by period attenuation | damping. In the said embodiment, it is a figure for demonstrating the deletion process by 1st execution frequency attenuation | damping. In the said embodiment, it is a figure for demonstrating the deletion process by 2nd execution frequency attenuation | damping. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by period decay is performed. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by period decay is performed. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by period decay is performed. In the said embodiment, it is a figure which shows an example of the deletion condition setting file for demonstrating the deletion process by 1st execution frequency attenuation | damping. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by 1st execution frequency attenuation | damping is performed. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by 1st execution frequency attenuation | damping is performed. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by 1st execution frequency attenuation | damping is performed. In the said embodiment, it is a figure for demonstrating the setting of the execution frequency according to a function. In the said embodiment, it is a figure which shows an example of the deletion condition setting file for demonstrating the deletion process by 2nd execution frequency attenuation | damping. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by 2nd execution frequency attenuation | damping is performed. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by 2nd execution frequency attenuation | damping is performed. In the said embodiment, it is a figure for demonstrating transition of a log when the deletion process by 2nd execution frequency attenuation | damping is performed.

  Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings.

<1. Schematic configuration>
FIG. 1 is a block diagram showing a schematic configuration of a substrate processing apparatus 1 according to an embodiment of the present invention. Specific examples of the substrate processing apparatus 1 include a cleaning apparatus, a heat treatment apparatus, and an exposure apparatus. As shown in FIG. 1, the substrate processing apparatus 1 includes a main apparatus 10, a plurality of control substrates 20, and a plurality of processing units 30. The plurality of control boards 20 and the plurality of processing units 30 correspond one-to-one. The main apparatus 10 controls the overall operation of the substrate processing apparatus 1. Specifically, the main apparatus 10 outputs various commands to each control board 20 so that desired processing is performed in each processing unit 30. The main apparatus 10 also manages a log indicating the operation status of each processing unit 30. As described above, the main apparatus 10 in the present embodiment typically functions as the processing control apparatus 102 that controls the operation of each processing unit 30 and also manages logs as shown in FIG. It also functions as the device 104.

  Each control board 20 controls the operation of the corresponding processing unit 30 based on a command given from the main apparatus 10. Each processing unit 30 performs a predetermined process based on control by the corresponding control board 20. For example, assume that a processing unit 30 includes a position control motor. In this case, for example, a pulse signal is given from the control board 20 to the processing unit 30, and a motor in the processing unit 30 is driven based on the pulse signal. When processing is performed by the processing unit 30 in this way, information indicating the operation status of the processing unit 30 is output as a log. In the present embodiment, the log is transmitted from the control board 20 to the main device 10 and stored in a storage unit (an auxiliary storage device 120 described later) in the main device 10. However, the log storage location is not particularly limited.

<2. Configuration of main unit>
FIG. 3 is a block diagram illustrating a hardware configuration of the main apparatus 10 (the main apparatus 10 in the substrate processing apparatus 1) functioning as the log management apparatus 104. The main device 10 includes a CPU 110, an auxiliary storage device 120, a display unit 130, an input unit 140, a memory 150, and a network interface unit 160. CPU110 performs various arithmetic processing etc. according to the provided command. The auxiliary storage device 120 stores various data. In connection with log management, a log file 122 in which logs are written, a log deletion program 124 for deleting logs, and a deletion condition setting file 126 used in the log deletion program 124 are stored in the auxiliary storage device 120. Stored. For example, the display unit 130 displays various screens for an operator (user) to perform work. The input unit 140 receives input from an operator using a mouse or a keyboard. The memory 150 temporarily stores data necessary for the arithmetic processing of the CPU 110. The network interface unit 160 functions so as to enable data communication between the main apparatus 10 and the control board 20 via the LAN 9 or the like.

  When the operation of the main apparatus 10 starts, the log deletion program 124 is read into the memory 150, and the CPU 110 executes the log deletion program 124 read into the memory 150. As a result, the main apparatus 10 functions as the log management apparatus 104, and a log deletion process described later is executed. The log deletion program 124 is provided in a form recorded on a recording medium such as a CD-ROM, DVD-ROM, or flash memory, or downloaded via a network.

<3. Overview of log deletion process>
An overview of log deletion processing in the present embodiment will be described. As described above, conventionally, logs are uniformly deleted based on an elapsed period (elapsed days or elapsed time) from the output time point. On the other hand, in this embodiment, logs are deleted at different timings according to importance. Further, the user can set three types of conditions as rules for deleting logs. In the present specification, such a kind of condition is referred to as “attenuation type”. In the present embodiment, there are provided three attenuation types: “period attenuation”, “first execution frequency attenuation”, and “second execution frequency attenuation”. Conditions regarding the deletion process by these three attenuation types are set by the user using the deletion condition setting file 126.

  The outline of the deletion process for each attenuation type is as follows. The deletion process by period attenuation is a process of deleting logs in descending order of importance as the period elapses based on a period (storage period) determined by the user according to importance. The deletion process by the first execution frequency decay is a process of deleting logs in order of decreasing importance every time the same function is executed a number of times (number of executions) determined by the user. The deletion process based on the second execution frequency attenuation is a process of deleting logs in order of decreasing importance every time all the functions included in one group are executed by the number of times determined by the user (number of executions). is there.

<4. Functional configuration of log management device>
As described above, the main device 10 functions as the log management device 104 when the CPU 110 of the main device 10 executes the log deletion program 124. FIG. 4 is a functional block diagram showing a functional configuration of the log management apparatus 104. As illustrated in FIG. 4, the log management device 104 functionally includes a log reading unit 41, a log update unit 42, and a deletion unit 43. The deletion unit 43 includes a period attenuation processing unit 431, a first execution number attenuation processing unit 432, and a second execution number attenuation processing unit 433. Note that a log deletion unit is realized by the deletion unit 43.

  The log reading unit 41 reads the log file 122 from the auxiliary storage device 120, and temporarily stores the data in the log file 122 (log written in the log file 122) in the memory 150. The deletion of the log by the deletion unit 43 is performed on the data held in the memory 150. The log update unit 42 updates the log file 122 with the data on the memory 150 that reflects the deletion of the log. Note that exclusive control is normally performed so that a new log is not written in the log file 122 based on the processing in each processing unit 30 during the period in which the log deletion processing is performed. Specifically, after the log file 122 is read by the log reading unit 41 after the exclusive control lock is applied to the log file 122, the log file 122 is updated by the log update unit 42 and the exclusive control is performed on the log file 122. Is unlocked. Logs output based on processing in each processing unit 30 during the period in which log deletion processing is performed are temporarily held in a buffer, for example, and written to the log file 122 after log deletion processing ends.

  The period attenuation processing unit 431 in the deletion unit 43 performs the deletion process based on the period attenuation described above based on the conditions set in the deletion condition setting file 126. The first execution number attenuation processing unit 432 in the deletion unit 43 performs the deletion process based on the first execution number attenuation described above based on the conditions set in the deletion condition setting file 126. The second execution frequency attenuation processing unit 433 in the deletion unit 43 performs the above-described deletion processing by the second execution frequency attenuation based on the conditions set in the deletion condition setting file 126. Details of the deletion process for each attenuation type will be described later.

<5. Deletion condition setting file>
The conditions for the deletion process for each attenuation type are set by the user using the deletion condition setting file 126. A specific method of setting the conditions will be described with reference to FIG. FIG. 5 is a diagram showing an example of the deletion condition setting file 126 in the present embodiment. However, a specific description of the data input area 54 described later is omitted. In the deletion condition setting file 126, an area (hereinafter referred to as “condition setting area”) 50 for performing log classification into a plurality of importance levels and setting the deletion conditions according to importance levels, and deletion processing for each attenuation type. And an area (hereinafter referred to as “attenuation type designation area”) 60 for designating whether or not to execute the above.

  The condition setting area 50 includes four data input areas 51 to 54. These four data input areas are distinguished by reference numerals. The data input area 51 is an area for inputting a code representing the importance of the log. The code input to the data input area 51 functions as an identifier for identifying a log to be deleted when log deletion processing is performed. The data input area 52 is an area that is referred to in the deletion process by period attenuation, and is an area for inputting the number of days that represents the log storage period of the corresponding importance level. The data input area 53 is an area referred to in the deletion process by the first execution frequency attenuation and the deletion process by the second execution frequency attenuation, and is an area for inputting the function execution frequency. The data input area 54 is an area for inputting a log type assigned to the corresponding importance level. In the data input area 52, time may be input instead of days.

  The attenuation type designation area 60 includes four data input areas 61 to 64. These four data input areas are distinguished by reference numerals. The data input area 61 is an area for inputting a code representing the attenuation type. The data input area 62 is an area for designating whether or not to execute deletion processing by the corresponding attenuation type. The data input area 63 is an area for inputting the name of the corresponding attenuation type. The data input area 64 is an area for designating what is counted in the deletion process by the corresponding attenuation type (first execution frequency attenuation or second execution frequency attenuation). For example, if the content of the deletion condition setting file 126 is as shown in FIG. 7, the execution is performed at the time of the deletion processing by the first execution frequency attenuation from the input content of the data input areas 51, 54, and 64. The number of executions for each process is counted, and the number of executions for each sub-process is counted in the deletion process by the second execution number attenuation.

  In the example shown in FIG. 5, the logs are classified into three categories (“high”, “medium”, and “low”), and the logs included in each category are further classified into three importance levels. In other words, the log is classified into nine importance levels, and the nine importance levels are classified into three categories so that each category includes three importance levels. As described above, the deletion condition setting file 126 according to the present embodiment is configured to be able to classify the importance levels into a plurality of categories so that one category includes one or more importance levels. However, classification by category is not necessarily performed, and the log may be simply classified into a plurality of importance levels.

  The log type corresponding to each importance is input to the data input area 54 as described above. In the data input area 54, for example, input as shown in FIG. 8 is performed. In the example illustrated in FIG. 8, logs indicating “acceleration / deceleration”, “Focus position”, and “number of repetitions” are assigned to the importance “c2”. In this way, using the data input area 51 and the data input area 54, the importance level and the log type are associated with each other.

  Focus on the data input area 52. In the example illustrated in FIG. 5, a numerical value “20” is input to the data input area 52 for the importance “b2”. Therefore, when the deletion process by the period decay is performed, the log whose importance is classified as “b2” is deleted after 20 days from the output.

  Focus on the data input area 53. The value input to the data input area 53 is valid only when a code representing the corresponding importance is input to the data input area 64. In the example illustrated in FIG. 5, a code “a1” is input to the data input area 64 for the first execution frequency attenuation, and “a2” is input to the data input area 64 for the second execution frequency attenuation. A code is input. Therefore, the value of the data input area 53 for the importance “a1” and the value of the data input area 53 for the importance “a2” are valid. In the example illustrated in FIG. 5, a numerical value “100” is input to the data input area 53 for the importance “a1”. Therefore, when the deletion process based on the first execution frequency attenuation is performed, each time the function associated with the importance “a1” is executed 100 times, the logs related to the function are deleted in descending order of importance. Is done. In the example illustrated in FIG. 5, a numerical value “100” is also input to the data input area 53 for the importance “a2”. Accordingly, when the deletion process by the second execution frequency attenuation is performed, every time all the functions associated with the importance “a2” are executed 100 times for each group, the functions included in each group are related. Logs are deleted in ascending order of importance.

  Focus on the data input area 62. In the present embodiment, only the deletion process based on the attenuation type in which “1” is input in the data input area 62 is executed. In the example illustrated in FIG. 5, “1” is input to the data input area 62 for the period attenuation, and “0” is input to the data input area 62 for the first execution frequency attenuation and the second execution frequency attenuation. Has been. Therefore, when the log deletion process is executed using the deletion condition setting file 126 shown in FIG. 5, only the deletion process due to period decay is executed.

  In this embodiment, the log classification means is realized by the data input area 51 and the data input area 54 of the deletion condition setting file 126, and the data input area 51, the data input area 52, and the data input area 53 of the deletion condition setting file 126. The deletion condition setting means is realized by the above. Further, the storage period setting means is realized by the data input area 52 of the deletion condition setting file 126, and the first execution number setting means and the second execution number setting means are realized by the data input area 53 of the deletion condition setting file 126. ing.

  The setting method described here is an example, and the present invention is not limited to this. That is, as long as conditions for deleting logs can be set according to importance, the configuration of the deletion condition setting file 126 is not limited to the configuration shown in FIG. 5, for example, a GUI for inputting a deletion condition is prepared. Then, an input to the GUI by the user may be accepted.

<6. Processing procedure>
A procedure for log deletion processing according to the present embodiment will be described with reference to the flowchart shown in FIG. First, the log is classified into a plurality of importance levels using the above-described deletion condition setting file 126 (step S10). Specifically, the user inputs to the data input area 51 and the data input area 54 of the deletion condition setting file 126. Next, the deletion condition is set using the deletion condition setting file 126 (step S20). Specifically, the user inputs to the data input area 51, the data input area 52, and the data input area 53 of the deletion condition setting file 126. Note that the processing of step S10 and step S20 is typically performed when the operation of each processing unit 30 is stopped. In addition, although it has been described here that step S10 and step S20 are separate processes, these processes are usually performed as one process for creating the deletion condition setting file 126.

  Thereafter, the log is deleted at an appropriate timing based on the setting contents of the deletion condition setting file 126 (step S30). The processing in step S30 is performed by the deletion unit 43 (see FIG. 4) of the log management device 104. Note that the process of step S30 may be performed while each processing unit 30 is operating, or may be performed when the operation of each processing unit 30 is stopped.

  In the present embodiment, the log classification step is realized by step S10, the deletion condition setting step is realized by step S20, and the log deletion step is realized by step S30.

<7. Details of deletion processing for each attenuation type>
<7.1 Attenuation>
According to the deletion process by period attenuation, logs are deleted in order of decreasing importance as the period elapses based on the numerical value (storage period) input in the data input area 52 of the deletion condition setting file 126.

  For example, it is assumed that the contents of the data input areas 51 to 54 of the deletion condition setting file 126 are as shown in FIG. That is, the log is classified into three importance levels of “high”, “medium”, and “low”, the retention period is set to 30 days for “high”, and the retention period is 10 for “medium”. It is assumed that the retention period is set to 3 days for “low”. In this case, paying attention to a plurality of logs output on the same day, first, a log whose importance is classified as “low” is deleted after 3 days from the output date, and then the importance is “medium”. Is deleted after 10 days from the output date, and finally, a log classified as “high” in importance is deleted after 30 days from the output date.

<7.2 Attenuation of first execution count>
According to the deletion process based on the first execution frequency decay, the degree of importance is low each time the same function is executed a number of times equal to the numerical value (execution frequency) input to the data input area 53 of the deletion condition setting file 126. Logs are deleted in order. More specifically, in the deletion process by the first execution frequency decay, when a set of logs output when an arbitrary function is executed is defined as a function execution log group, the function is input to the data input area 53. This is a process of deleting the logs included in the function execution log group in order from the lowest importance every time it is further executed by the number equal to the numerical value (number of executions).

  For example, it is assumed that the content of the deletion condition setting file 126 is as shown in FIG. That is, the logs are classified into three importance levels of “high”, “medium”, and “low”. In addition, data of importance “high” is input to the data input area 64 for the first execution frequency attenuation (actually, a sign is normally input), and data about the importance “high” is input. A numerical value “50” is input in the input area 53. In such a case, for example, the following deletion process is performed on the logs included in the function execution log group output when a certain function is executed at a certain point of time. First, when the function is executed 50 more times after the point of interest, logs whose importance is classified as “low” are deleted. After that, when the function is executed 50 more times, logs whose importance is classified as “medium” are deleted. After that, when the function is executed 50 more times, logs whose importance is classified as “large” are deleted. In this way, each time the same function is executed for the set number of executions, the logs are deleted in order of decreasing importance. It should be noted that the rule by which the log is deleted every time the same function is executed for the set number of executions is described in the log deletion program 124, for example. Accordingly, with respect to the above-described example, for example, it is possible to prevent a log whose importance is classified as “large” from being deleted.

  By the way, in order to enable the deletion process as described above, it is necessary to be able to identify a set of logs (function execution log group) output by executing a function once when executing log deletion. Therefore, information for identifying each function execution log group in the log file 122 is managed by a separately provided log management file (not shown in FIG. 3).

  When the importance is classified into a plurality of categories, logs included in the function execution log group can be deleted in units of categories.

<7.3 Second execution number decay>
According to the deletion process by the second execution frequency attenuation, all the functions included in one group are executed a number of times equal to the numerical value (execution frequency) input to the data input area 53 of the deletion condition setting file 126. Each time, logs are deleted in order of decreasing importance. More specifically, the deletion process by the second execution frequency decay is defined as a group function execution log group defined as a set of logs output when a function included in an arbitrary group is executed in units of groups. Every time all the functions included are further executed by the number equal to the numerical value (number of executions) input to the data input area 53, the logs included in the group function execution log group are deleted in order of decreasing importance. It is processing. If three functions are included in one group, the number of executions is counted for each function. When the number of executions of all three functions becomes equal to or greater than the numerical value input in the data input area 53, the first deletion process is executed.

  For example, it is assumed that the content of the deletion condition setting file 126 is as shown in FIG. That is, the logs are classified into three importance levels of “high”, “medium”, and “low”. In addition, a character of importance “medium” is input to the data input area 64 regarding the second execution frequency attenuation (actually, a sign is actually input), and data about the importance “medium” is input. A numerical value “50” is input in the input area 53. In such a case, regarding a log included in a group function execution log group output when a function (sub process) included in a group (execution process) at a certain point in time is executed in units of groups, for example, The deletion process is performed as follows. First, when all the functions included in the group are executed 50 more times after the point of interest, logs whose importance is classified as “low” are deleted. After that, when all the functions included in the group are executed 50 more times, logs whose importance is classified as “medium” are deleted. After that, when all the functions included in the group are executed 50 more times, logs whose importance is classified as “large” are deleted. In this way, each time all functions included in the same group are executed for the set number of executions, the logs are deleted in order from the lowest importance. Note that the rule for deleting a log every time all functions included in the same group are executed for the set number of executions is described in the log deletion program 124, for example. Similarly to the information for identifying each function execution log group described above, information for identifying each group function execution log group in the log file 122 is managed by the log management file.

  When the importance is classified into a plurality of categories, logs included in the group function execution log group can be deleted in units of categories.

<8. Specific example of log deletion processing by attenuation type>
<8.1 Decay period>
First, a specific example of the deletion process by period attenuation will be described. Here, the contents of the data input area 51 and the data input area 52 of the deletion condition setting file 126 are as shown in FIG. 5, and there is a certain function (referred to as “function Z” for convenience). It is assumed that the contents of the log file 122 after execution are as shown in FIG. The time point when the function Z is first executed is referred to as “initial time point” for convenience.

  As illustrated in FIG. 13, immediately after the execution of the function Z, the log files 122 include nine importance logs. FIG. 14 is a diagram showing the contents of the log file 122 after 7 days have passed since the initial time point. As shown in FIG. 5, the retention period for the log with the importance level “c3” is set to 3 days, and the retention period for the log with the importance level “c2” is set to 5 days. In addition, for logs with an importance level of “c1” or higher, the retention period is set to 10 days or longer. Therefore, as shown in FIG. 14, after seven days have elapsed from the initial time point, the logs with importance “c3” and “c2” are deleted from the log immediately after the execution of the function Z (see FIG. 13). FIG. 15 is a diagram showing the contents of the log file 122 after 30 days have passed since the initial time point. As shown in FIG. 5, the retention period is set to 25 days or less for all logs having an importance level of “b1” or less, and the retention period is set to all logs having an importance level of “a3” or more. It is set to 50 days or more. Therefore, as shown in FIG. 15, after 30 days from the initial time point, the log of importance “b1” or less is deleted from the log immediately after execution of the function Z (see FIG. 13). In other words, after 30 days have passed since the initial time point, only logs with importance “a3” or higher remain among the logs immediately after execution of the function Z (see FIG. 13). In this way, according to the deletion process by period attenuation, the log is gradually deleted from the one with the lower importance as the period elapses.

  By the way, as can be understood from FIGS. 13 to 15, each log is assigned with an identifier that is input to the data input area 51 corresponding thereto. When the log deletion process is performed, the deletion unit 43 (see FIG. 4) determines whether or not the log is a deletion target based on an identifier attached to the log. As a result, when the log deletion process is performed, it is possible to delete the deletion target log reliably and promptly.

<8.2 Attenuation of first execution count>
Next, a specific example of the deletion process by the first execution frequency attenuation will be described. Here, the contents of the deletion condition setting file 126 are as shown in FIG. 16, and the contents of the log file 122 after the function “single function X” is executed are as shown in FIG. Suppose that it is content. Also, “After each function is executed, if the function is executed for the set number of times for the first time, the log of the importance level included in the category“ low ”is deleted, and the function is executed for the set number of times next time. It is assumed that the log deletion program 124 describes a rule “delete log of importance included in category“ medium ”. The time point when the single function X is first executed is referred to as “initial time point” for convenience.

  As shown in FIG. 17, immediately after the execution of the single function X, the log files 122 include nine importance logs. FIG. 18 is a diagram showing the contents of the log file 122 after the single function X is executed 100 times after the single function X is executed at the initial time point. As described above, after each function is first executed, when the function is first executed a set number of times, the log of the importance level included in the category “low” is deleted. Accordingly, as shown in FIG. 18, after the single function X is executed 100 times after the single function X is executed at the initial time, the log immediately after the execution of the single function X at the initial time (see FIG. 17) Among them, logs with importance of “c1” or less are deleted. FIG. 19 is a diagram showing the contents of the log file 122 after the single function X is executed 200 times after the single function X is executed at the initial time point. As described above, after each function is executed first, when the function is executed a set number of times for the second time, the log of importance included in the category “medium” is deleted. Accordingly, as shown in FIG. 19, after the single function X is executed 200 times after the single function X is executed at the initial time, the log immediately after the execution of the single function X at the initial time (see FIG. 17) Among them, logs with importance “b1” or less are deleted. In other words, after the single function X is executed 200 times after the single function X is executed at the initial time point, the importance level of the log immediately after the execution of the single function X at the initial time point (see FIG. 17) is “ Only logs a3 "and above are left. In this way, according to the deletion process based on the first execution frequency attenuation, the log is gradually deleted from the least important log every time the same function is executed the number of times specified by the user.

  By the way, in the above-mentioned example, the log of any function is deleted in order of decreasing importance every time the corresponding function is executed 100 times. However, the present invention is not limited to this. For example, like the part denoted by reference numeral 59 in FIG. 20, a different number of executions may be set for each function in the deletion condition setting file 126. Thus, for example, in the example shown in FIG. 20, the log is deleted in order from the lowest importance every time the single function X is executed 100 times after the first execution, and the single function Y is executed first. Each time the log is executed 50 times, the logs are deleted in order of decreasing importance. In this way, for example, it is possible to change the way of deleting logs according to the importance of functions.

<8.3 Second Execution Frequency Decay>
Next, a specific example of the deletion process by the second execution frequency attenuation will be described. Note that the functions in this description correspond to the functions A, B, and C in FIG. Here, the contents of the deletion condition setting file 126 are as shown in FIG. 21, and the contents of the log file 122 after the “composite function Z” is executed are as shown in FIG. Assume that Also, “After a function included in a certain group is executed in units of groups, if all the functions included in the group are executed for the set number of times for the first time, the log of the importance level included in the category“ low ”is deleted. And the log deletion program 124 has a rule that “when all the functions included in the group are executed the set number of times next, the log of the importance level included in the category“ medium ”is deleted”. Assume. Note that a point in time when a function included in a certain group is first executed for each group is referred to as an “initial point” for convenience.

  As illustrated in FIG. 22, immediately after the execution of the composite function Z, the log files 122 include nine importance logs. FIG. 23 is a diagram showing the contents of the log file 122 after all the functions included in the composite function Z have been executed 100 more times after the composite function Z was executed at the initial time point. As described above, after the functions included in each group are executed in units of groups, when all the functions included in the group are executed for the set number of times for the first time, the log of the importance level included in the category “low” is displayed. Deleted. Therefore, as shown in FIG. 23, after all the functions included in the composite function Z are executed 100 times after the composite function Z is executed at the initial time, the log immediately after the execution of the composite function Z at the initial time is executed. Among the logs (see FIG. 22), logs having an importance level of “c1” or less are deleted. FIG. 24 is a diagram illustrating the contents of the log file 122 after all functions included in the composite function Z have been executed 200 more times since the composite function Z was executed at the initial time point. As described above, after the functions included in each group are executed in units of groups, when all the functions included in the group are executed a set number of times for the second time, the log of the importance level included in the category “medium” Is deleted. Therefore, as shown in FIG. 24, after all functions included in the composite function Z are executed 200 times after the composite function Z is executed at the initial time, the log immediately after the execution of the composite function Z at the initial time is executed. Among the logs (see FIG. 22), the logs having the importance of “b1” or less are deleted. In other words, after all the functions included in the composite function Z are executed 200 times after the composite function Z is executed at the initial time, the log immediately after the execution of the composite function Z at the initial time (see FIG. 22). Only logs with importance “a3” or higher are left. In this way, according to the deletion process based on the second execution frequency attenuation, the log is gradually increased from the least important every time all the functions included in the same group are executed the number of times specified by the user. Deleted.

<9. Effect>
According to the present embodiment, the log is classified into a plurality of importance levels according to the setting by the user, and the logs are deleted in descending order of importance. This makes it possible to quickly delete logs that are not required for investigating the cause of defects, and reducing the amount of storage capacity (resources) used to store logs without disturbing the cause of problems. Can be reduced. Further, since the user can classify the log into a plurality of importance levels and set the deletion condition, it is possible to estimate the usage amount of the storage capacity. Furthermore, since logs of various importance levels are not mixed and only important logs are stored for a long period of time, the cause of the failure is efficiently investigated, and the number of investigation steps when the failure occurs is reduced. As described above, according to the present embodiment, a log management device is realized that enables efficient use of storage capacity by storing and deleting logs according to user requests.

  By the way, in the substrate processing apparatus 1, a plurality of functions are often executed as a group. In this regard, according to the present embodiment, it is possible to efficiently delete logs of a plurality of functions by executing the deletion process based on the second execution frequency attenuation. In addition, the number of executions of one function among a plurality of functions may increase due to some circumstances. In this regard, according to the present embodiment, it is possible to efficiently delete a log of a function with a large number of executions by executing the deletion process based on the first execution number attenuation.

<10. Other>
In the above embodiment, an example in which the present invention is applied to log management in a substrate processing apparatus has been described. However, the present invention is not limited to this. The present invention can also be applied to log management in various apparatuses (various systems) that perform processing using a computer.

DESCRIPTION OF SYMBOLS 1 ... Substrate processing apparatus 10 ... Main apparatus 20 ... Control board 30 ... Processing unit 43 ... Deletion part 51-54, 61-64 ... Data input area 102 ... Processing control apparatus 104 ... Log management apparatus 122 ... Log file 124 ... Log deletion Program 126 ... Deletion condition setting file 431 ... Period attenuation processing unit 432 ... First execution frequency attenuation processing unit 433 ... Second execution frequency attenuation processing unit

Claims (17)

Log classification means for classifying logs into multiple importance levels,
Deletion condition setting means for setting log deletion conditions, which are conditions used to determine whether or not to delete logs, according to importance,
A log management device comprising log deletion means for deleting a log based on the log deletion condition. The deletion condition setting means includes a retention period setting means for setting a retention period from the log output time as the log deletion condition,
The log management apparatus according to claim 1, wherein the log deletion unit deletes a log whose storage period set by the storage period setting unit has elapsed from an output time point. The deletion condition setting unit includes a first execution number setting unit for setting a function execution number as the log deletion condition,
When a set of logs output when an arbitrary function is executed is defined as a function execution log group, the log deletion unit further includes the number of executions of the function set by the first execution number setting unit. 3. The log management apparatus according to claim 1, wherein a log included in the function execution log group is deleted in descending order of importance each time it is executed. The log classification means is configured to be able to classify importance into a plurality of categories so that one category includes one or more importance.
The log management apparatus according to claim 3, wherein the log deletion unit deletes a log included in the function execution log group in units of categories.   5. The log management apparatus according to claim 3, wherein the deletion condition setting unit is configured to be able to set a different number of executions for each function as the log deletion condition. The deletion condition setting unit includes a second execution number setting unit for setting a function execution number as the log deletion condition,
When a set of logs output when a function included in an arbitrary group is executed in units of groups is defined as a group function execution log group, the log deletion unit is configured such that all functions included in the group are included in the second function group. The log included in the group function execution log group is deleted in descending order of importance each time it is further executed by the execution number set by the execution number setting means. 2. The log management apparatus according to 2. The log classification means is configured to be able to classify importance into a plurality of categories so that one category includes one or more importance.
The log management apparatus according to claim 6, wherein the log deletion unit deletes a log included in the group function execution log group in units of categories. Each log is given an identifier to identify the importance,
The log according to any one of claims 1 to 7, wherein the log deletion means determines whether or not the log is to be deleted based on an identifier attached to the log. Management device. A log classification step to classify logs into multiple importance levels;
A deletion condition setting step for setting log deletion conditions, which are conditions used to determine whether or not to delete logs, according to importance;
And a log deletion step of deleting a log based on the log deletion condition. A log classification step that accepts log classification to multiple importance levels;
A deletion condition setting step for accepting a setting according to the importance of a log deletion condition, which is a condition used for determining whether or not to delete a log;
A log management program, wherein a CPU of a computer executes a log deletion step of deleting a log based on the log deletion condition using a memory. The deletion condition setting step includes a retention period setting step of accepting a retention period setting from the log output time as the log deletion condition,
The log management program according to claim 10, wherein in the log deletion step, a log whose storage period set in the storage period setting step has elapsed from an output time point is deleted. The deletion condition setting step includes a first execution frequency setting step for accepting a setting of the number of executions of the function as the log deletion condition,
When a set of logs output when an arbitrary function is executed is defined as a function execution log group, in the log deletion step, the function is further executed by the number of executions set in the first execution number setting step. 12. The log management program according to claim 10, wherein logs included in the function execution log group are deleted in descending order of importance each time the log is executed. In the log classification step, it is possible to classify the importance into a plurality of categories so that one category includes one or more importance.
The log management program according to claim 12, wherein in the log deletion step, logs included in the function execution log group are deleted in units of categories.   14. The log management program according to claim 12, wherein in the deletion condition setting step, a different number of executions can be set for each function as the log deletion condition. The deletion condition setting step includes a second execution frequency setting step for accepting setting of the function execution frequency as the log deletion condition,
When a set of logs output when a function included in an arbitrary group is executed in units of groups is defined as a group function execution log group, in the log deletion step, all the functions included in the group are added to the second function execution log group. The log included in the group function execution log group is deleted in descending order of importance each time the execution is further performed by the number of executions set in the execution number setting step. 11. The log management program according to 11. In the log classification step, it is possible to classify the importance into a plurality of categories so that one category includes one or more importance.
16. The log management program according to claim 15, wherein in the log deletion step, logs included in the group function execution log group are deleted in units of categories. Each log is given an identifier to identify the importance,
17. The log deletion step according to claim 10, wherein whether or not the log is a deletion target is determined based on an identifier attached to the log. 17. Log management program.

Images