JP2007034416A - Information processing system, log data management method and program for managing log data - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To effectively use the storage area of a disk drive. <P>SOLUTION: A free capacity detecting part 104 monitors the free capacity of a disk drive designated by disk switching information stored in a disk switching information storage part 101, and detects that the free capacity is less than a threshold shown by reference free capacity information. When the free capacity of the disk drive is less than the threshold shown by the reference free capacity information, a switching part 110a switches the currently used disk drive to the disk drive designated by the disk switching information as a disk drive to be used for storing log data. A log data output part 111 stores log data adopted by a log collecting part 109 in the disk drive currently used for storing the log data. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an information processing system for managing log data, a log data management method, and a program.

  In general, in various information processing systems, processing of storing a program execution status or user operation contents as log data in a storage device such as a disk array device is performed. The amount of log data stored in this storage device is increasing with the passage of time. For this reason, the ratio of the log data in the storage area of the storage apparatus increases remarkably and the storage area of the storage apparatus is compressed without the system user noticing.

  Therefore, it is necessary to manage the log data so that the storage area of the storage device is not occupied by the log data. In this log data management, log data stored in a storage device is saved to another storage device, or deleted under certain conditions (for example, whether the log data exceeds a predetermined retention period). Processing is performed. In order to realize this processing, a special program (for example, a log data saving / deleting tool) is required. In addition, a backup storage device for saving log data (backup) is required.

Thus, for example, Patent Document 1 describes a technique that eliminates the need for a backup storage device. In the technique described in Patent Document 1 (hereinafter referred to as the prior art), when the partial log information storage unit secured in the log information storage unit is full, the partial log information storage unit stores the partial log information storage unit. Log information is managed according to the log information retention period. Specifically, when log information that has passed a predetermined storage period exists in the partial log information storage unit, new log information is overwritten on the log information. In addition, when the log information whose retention period has passed does not exist in the partial log information storage unit, a new partial log information storage unit is secured in the log information storage unit, and the new partial log information storage unit New log information is stored. According to this prior art, it is possible to prevent an unlimited increase in the storage amount of log information and deletion of new information.
JP 10-11330 A (paragraph 0005)

  However, in the above prior art, the new partial log information storage unit is secured in the log information storage unit in which the old partial log information storage unit is secured. In this case, even if there is a vacancy in another area of the storage device, the vacant area cannot be used effectively for storing log information. Therefore, in the prior art, when log information that has passed a predetermined storage period exists in the partial log information storage unit, the log information is overwritten with new log information, so that the free space in the log information storage unit Compensates for the few conditions. However, there is no guarantee that the old information is not important, and it is a log management problem that the log information is overwritten with new log information just because the log information has passed the retention period. is there.

  The present invention has been made in consideration of the above circumstances, and an object of the present invention is to provide an information processing system, log data management method, and program for managing log data that can effectively use a storage area of a disk drive used in a storage device. It is to provide.

  According to one aspect of the present invention, an information processing system for managing log data is provided. The system includes detection target designation information for designating a disk drive used for storing log data as a target for monitoring free capacity, reference free capacity information indicating a lower limit value of the free capacity of the disk drive, and the detection. Disk switching information storage means for storing in advance disk switching information including switching destination designation information for designating a disk drive to be used in place of the disk drive designated by the target designation information, and a disk drive designated by the detection target designation information The free space is monitored to detect that the free space has fallen below the threshold indicated by the reference free space information, and the free space of the disk drive specified by the detection target specifying information is the reference That the free space information means falls below the threshold value indicated by the free space information If it is detected, the disk drive used for storing log data is switched from the currently used disk drive specified by the detection target specifying information to the disk drive specified by the switching destination specifying information. Switching means, log collecting means for collecting log data, and log output means for storing the log data collected by the log collecting means in a disk drive currently used for storing log data .

  According to the present invention, the free capacity of a disk drive currently used to store log data is monitored, and the disk drive (log output path) used to store log data is flexible based on the free capacity. Changed to For this reason, log data can be prevented from being stored in a specific disk drive (fixed path), and log data can be stored without squeezing the storage area by effectively using the storage area of the specific disk drive. can do.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention. This information processing system is applied to a management system of a certain company, for example, and includes a server (server computer) 10 and n terminals 20-1, 20-2,... 20-n. In the present embodiment, for example, the terminal 20-1 among the terminals 20-1 to 20-n is used as a terminal of an administrator of the information processing system. Server 10 and terminals 20-1 to 20-n are interconnected by a network NW. The network NW may be a local area network (LAN) or a wide area network (WAN) composed of a plurality of networks. A public line may be included in the wide area network.

  The server 10 has a database (DB) 11. The database 11 is constructed using, for example, a storage device composed of at least one hard disk drive (HDD). The database 11 stores, for example, personal information of employees of the company in a table format. The user (employee) can access the personal information stored in the database 11 from the terminal 20-i (i = 1, 2,... N) under certain restrictions. The database 11 further stores log data representing a log (history) of access to personal information by the user.

  The server 10 includes a log management unit 100 that manages log data. A block configuration of the log management unit 100 is shown in FIG. The log management unit 100 includes a disk switching information storage unit 101, a log output destination information storage unit 102, a log management information setting unit 103, a free capacity detection unit 104, a failure detection unit 105, a failure recovery detection unit 106, a mail transmission unit 107, It includes an event detection unit 108, a log collection unit 109, a log output destination determination unit 110, a log output unit 111, a table / file generation determination unit 112, a table generation unit 113, and a file generation unit 114.

  The disk switching information storage unit 101 stores disk switching information indicating conditions for switching a disk drive used for storing log data. In the present embodiment, the disk drive used for storing log data is a logical disk drive to which a part of the storage area of the hard disk drive included in the storage device constituting the database 11 is allocated. The log output destination information storage unit 102 stores information (log output destination information) that specifies an output destination of log data. In the present embodiment, either a table (log table) or a file (log file) can be specified as an output destination of log data. Also, the output destination of log data can be switched (for example, switching from a table to a file).

  Each of the disk switching information and log output destination information is used as log management information for managing log data. The log management information setting unit 103 sets log management information designated by the administrator in the disk switching information storage unit 101 or the log output destination information storage unit 102, for example, in accordance with the operation of the terminal 20-1 by the administrator. That is, when the log management information specified by the administrator is disk switching information, the log management information setting unit 103 sets the disk switching information in the disk switching information storage unit 101, and the log management information specified by the administrator In the case of log output destination information, the log output destination information is set in the log output destination information storage unit 102.

  The free capacity detection unit 104 detects the free capacity of a disk drive (logical disk drive) used for storing log data. The failure detection unit 105 detects the occurrence of a failure related to log output. The failure recovery detection unit 106 detects failure recovery related to log output. In response to the failure detection (detection of failure occurrence) by the failure detection unit 105, the detection of failure recovery by the failure recovery detection unit 106, and the switching of the log output destination by the log output destination determination unit 110, the mail transmission unit 107 notifies that fact. The e-mail shown is transmitted to the administrator's terminal 20-1, for example.

  The event detection unit 108 detects the occurrence of a predetermined event for which log data is to be collected and stored. The log collection unit 109 collects log data corresponding to the event in response to detection of event occurrence by the event detection unit 108.

  The log output destination determination unit 110 determines whether the output destination of the log data collected by the log collection unit 109 is a table or a file, the log output destination information stored in the log output destination information storage unit 102, and the failure The determination is made based on the detection result of the detection unit 105. The log output destination determination unit 110 includes a switching unit 110a. Based on the disk switching information stored in the disk switching information storage unit 101 and the detection result of the failure detection unit 105, the switching unit 110a switches a disk drive (a path that specifies) used to store log data. . The switching unit 110a may be provided independently from the log output destination determination unit 110.

  The log output unit 111 outputs the log data collected by the log collection unit 109 to the determined log output destination in a data format specific to the log output destination determined by the log output destination determination unit 110. The table / file generation determination unit 112 determines whether the data format of the collected log data is a table format or a file format based on the determination result by the log output destination determination unit 110. The table / file generation determination unit 112 also determines whether it is necessary to generate a new table or file from the size of the currently used table or file.

  The table generation unit 113 receives the log data collected by the log collection unit 109 via, for example, the log output destination determination unit 110, and generates log data in a table format from the log data. The table generation unit 113 also generates a new table when the table / file generation determination unit 112 determines the generation of a new table.

  The file generation unit 114 receives the log data collected by the log collection unit 109 via, for example, the log output destination determination unit 110, thereby generating log data in a file format from the log data. The file generation unit 114 also generates the new file when the table / file generation determination unit 112 determines the generation of a new file.

  In the present embodiment, among the components of the log management unit 100 described above, the components other than the disk switching information storage unit 101 and the log output destination information storage unit 102 are the special software programs installed in the server 10. 10 (internal CPU) reads and executes. This program can be stored in advance in a computer-readable storage medium and distributed. Further, this program may be downloaded (distributed) via a network.

  FIG. 3 shows an example of the disk switching information 30 stored in the disk switching information storage unit 101. The disk switching information 30 includes information on a detection target path 301, a threshold (Limit) 302, and a switching path 303. In this embodiment, the location of a file or the like in the system is managed by a hierarchical directory and is represented by information called a path. The detection target path 301 is detection target designation information indicating the location of a disk drive (here, a logical disk drive) that is a target for monitoring (detecting) free space and that is currently used for storing log data. A threshold 302 indicates a condition for switching a disk drive used for storing log data to another disk drive. In the present embodiment, the threshold 302 is reference free capacity information indicating the lower limit of the free capacity allowed for the disk drive (logical disk drive) represented by the detection target path 301. The switching path 303 is a switching destination designation that represents a path to another disk drive that is newly used for storing log data when the free space of the disk drive specified by the detection target path 301 falls below a threshold (Limit) 302. Information.

  4A and 4B show examples of log output destination information 41 and 42 stored in the log output destination information storage unit 102, respectively. In the present embodiment, log output destination information 41 and 42 are stored in the log output destination information storage unit 102. The log output destination information 41 and 42 are respectively provided with flags (flag information) F1 and F2 indicating whether the information 41 and 42 are used in a normal state where no failure is detected by the failure detection unit 105. Yes. Here, when one of the flags F1 and F2 is set to “ON” indicating “use”, for example, the other flag is set to “OFF” indicating “not used”. Which of the flags F1 and F2 is set to the “ON” state, that is, which of the log output destination information 41 and 42 is set to the “used” state is determined by the user (administrator) via the log management information setting unit 103. Can be set arbitrarily.

  Log output destination information (first log output destination information) 41 includes log table / file designation information 411, RDBMS name 412, user name (user ID) 413, password 414, connection name (TNS) 415, and maximum size 416. Contains each piece of information.

  The log table / file designation information 411 designates a table (log table) or a file (log file) as a log output destination. The RDBMS name 412 is RDBMS designation information that designates a special database management system that operates the log table, for example, a relational database management system (RDBMS). Here, “XXXX” is designated as the RDBMS.

  A user name 413, a password 414, and a connection name (TNS) 415 indicate a user ID (user name), a password, and a connection name of a user connected to the RDBMS specified by the RDBMS name 412, respectively. The log output unit 111 can connect to the RDBMS specified by the RDBMS name 412 by using the user name 413, the password 414, and the connection name 415.

  The maximum size 416 indicates the maximum allowable size of a table used as a log output destination. That is, the maximum size 416 indicates a generation condition for generating a new table. When the size of the currently used table exceeds the maximum size, a new table is generated by the table generation unit 113.

  On the other hand, the log output destination information (second log output destination information) 42 includes log table / file designation information 421, path 422, file name 423, and maximum size 424 information.

  The log table / file designation information 421 designates a file of a table (log table) or a file (log file) as a log output destination. The path 422 and the file name 423 are file designation information for designating the path and file name indicating the location of the file currently used as the log output destination, respectively. However, in this embodiment, the path 422 (log \ in the example of FIG. 4B) indicates only a path lower than the disk drive in which the file specified by the file name 423 is stored. This is indicated by the detection target path 301 (D: \ in the example of FIG. 3) of the switching information 30. Therefore, the path of the file specified by the file name 423 is indicated by “D: \ log \”.

  The maximum size 424 indicates the maximum allowable size of a file used as a log output destination. That is, the maximum size 424 indicates a generation condition for generating a new file. When the size of the currently used file exceeds the maximum size, a new table is generated by the file generation unit 114.

  FIG. 5 shows a data structure example of a table 51 for registering log data in a table format, a data structure example of log data in a file format, and an example of a file 52 that includes log data in a file format.

  As shown in FIG. 5A, each entry of the table 51 includes an operation date 511 (for example, YYY / MM /) indicating the date when the operation that triggered the event occurrence, that is, the operation for accessing the personal information is performed. Operation date expressed in date using DD format), operation time 512 (for example, time expressed in hours, minutes and seconds using HH: MM: SS format), name of the department to which the operator belongs (Operator department signature) 513, operator name (operator name) 514, name of the screen used for the operation (operation screen name) 515, operation name 516 indicating the type of operation (search, registration, update, etc.) And status 517 items (fields). The status 515 includes “T” indicating that the operation has been successful, “F” indicating that the operation has failed, and “C” indicating that the operation has been canceled.

  On the other hand, as shown in FIG. 5 (b), the log data in the file format includes information on operation date, operation time, operator part signature, operator name, operation screen name, operation name, and status in single-byte commas. Described by separating. In this case, the data structure of the file 52 including the log data in this file format is as shown in FIG.

  Next, the operation of this embodiment will be described. First, in the log management unit 100 of the server 10, the event detection unit 108 monitors the occurrence of a predetermined event for collecting and storing log data. Here, the user operates any one of the terminals 20-1 to 20-n (i = 1, 2,... N) to store personal information stored in the database 11 of the server 10. The operation of accessing the is monitored as a predetermined event. When the event detection unit 108 detects the occurrence of this type of event, the event detection unit 108 notifies the log collection unit 109 to that effect (event detection).

  The log collection unit 109 collects log data related to the corresponding event in accordance with the event detection notification from the event detection unit 108. When the log collection unit 109 collects log data, the log output destination determination unit 110 is activated. Then, the log output destination determination unit 110 executes log output destination determination processing for determining (determining) the output destination of the log data collected by the log collection unit 109. This log output destination determination process includes a process of determining whether or not to switch the disk drive used to store the log data.

  Hereinafter, the log output destination determination processing by the log output destination determination unit 110 will be described with reference to the flowchart of FIG. First, the log output destination determination unit 110 (the switching unit 110a thereof) inquires of the free space detection unit 104 and detects the detection target path 301 (see FIG. 3) of the disk switching information 30 stored in the disk switching information storage unit 101. In the example, it is determined whether or not the free capacity of the disk drive (logical disk drive) specified by D: \ is less than the capacity LIMIT indicated by the threshold (Limit) 302 included in the disk switching information 30. (Step S1).

  If the free capacity of the disk drive (logical disk drive) specified by the detection target path 301 is less than the LIMIT, the log output destination determination unit 110 (the switching unit 110a thereof) is used to store log data. It is determined that the disk drive to be switched needs to be switched, and a path (switching path) pointing to the disk drive that becomes the log data storage destination is newly determined (step S2). Here, the disk drive (logical disk drive) designated by the switching path 303 (E: \ in the example of FIG. 3) of the disk switching information 30 is the disk drive (logical disk drive) that is the new log data storage destination. ).

  The log output destination determination unit 110 (the switching unit 110a thereof) switches the disk drive serving as the log data storage destination to the disk drive specified by the path determined from the current disk drive (step S3). For this switching, for example, the detection target path 301 of the disk switching information 30 (see FIG. 3) stored in the disk switching information storage unit 101 is changed from the current path (D: \) to the path (E: \). The update is performed by updating the switching path 303 of the disk switching information 30 from the current path (E: \) to a new path (for example, F: \).

  The log output destination determination unit 110 proceeds to step S4 after executing step S3. If the free space of the disk drive specified by the detection target path 301 is not less than LIMIT (step S1), the log output destination determination unit 110 skips steps S2 and S3 and proceeds to step S4. In step S <b> 4, the log output destination determination unit 110 performs log output based on the log output destination information in the “used” state among the log output destination information 41 and 42 stored in the log output destination information storage unit 102. Determine whether the destination is a table or a file.

  The log output destination determination unit 110 displays the path to the disk drive to be used for storing log data (information indicating) and the information indicating the log output destination determined in step S5. / The file generation determination unit 112 is notified (step S5). Here, as the information indicating the determined log output destination, the log output destination information in the “used” state among the log output destination information 41 and 42 stored in the log output destination information storage unit 102 is notified. .

  When the log output destination information is notified by the log output destination determination unit 110, the table / file generation determination unit 112 determines whether the format of the log data collected by the log collection unit 109 is a table format or a file format. Determination (determination) is made based on the log output destination information. Here, when the log output destination information 41 is notified, that is, when a table is notified as the log output destination, it is determined that the log data is in a table format. On the other hand, when the log output destination information 42 is notified, that is, when a file is notified as the log output destination, the log data is determined to be in the file format.

  When the table format is determined, the table / file generation determination unit 112 passes the log data collected by the log collection unit 109 to the table generation unit 113. The table generation unit 113 generates table format log data from the log data passed by the table / file generation determination unit 112.

  On the other hand, when the file format is determined, the table / file generation determination unit 112 passes the log data collected by the log collection unit 109 to the file generation unit 114. The file generation unit 114 generates file format log data from the log data passed by the table / file generation determination unit 112. The generated log data in the table format or file format is passed to the log output unit 111.

  In addition, when the log output destination determination unit 110 is notified of a path (switching path) to a new disk drive associated with path switching by the log output destination determination unit 110, if the log output destination is a table, the table / file generation determination unit 112 creates a new table. It is determined that generation is necessary. Similarly, the table / file generation determination unit 112 determines that a new file needs to be generated if the log output destination is a file when a switching path is notified. When the table / file generation determination unit 112 determines that a new table needs to be generated, the table / file generation determination unit 112 requests the table generation unit 113 to generate a new table on the new disk drive specified by the switching path. To do. Similarly, when the table / file generation determination unit 112 determines that a new file needs to be generated, the table / file generation determination unit 112 generates a new file on the new disk drive specified by the switching path with respect to the file generation unit 114. Request.

  In response to the table generation request from the table / file generation determination unit 112, the table generation unit 113 connects to the RDBMS “XXXX” specified by the RDBMS name 412 of the log output destination information 41, thereby switching the switching path (E :), a new table is generated by the RDBMS “XXXX” in the new disk drive designated by (:).

  In response to the file generation request from the table / file generation determination unit 112, the file generation unit 114 transfers the path 422 (log) of the log output destination information 42 to the new disk drive specified by the switching path (E: \). \) And a file name 423 (logfile.txt), a new file is generated. Here, assuming that the latest file name at the time when a new file is generated is “logfile.txt”, for example, a new file with the file name “logfile1.txt” is generated. In this case, the table / file generation determination unit 112 updates the file name 423 of the log output destination information 42 from “logfile.txt” to “logfile1.txt”. Similarly, each time the path is switched (as described later, every time the size of the currently used file exceeds the maximum size 424 of the log output destination information 42), the file name is “logfile12. Files of "txt", "logfile3.txt" ... are generated sequentially. In order to access the disk drive (logical disk drive) specified by the switching path, the login account and password of the disk drive (that is, the mount destination disk drive) specified by the switching path are stored in the disk switching information 30. It should be possible to specify.

  When the log output unit 111 receives the log data from the table generation unit 113 or the file generation unit 114, the log output unit 111 converts the log data to the log output destination determination unit based on the log output destination information notified by the log output destination determination unit 110. Processing for storing in the disk drive designated by the path notified by 110 is performed. Here, if the log output destination indicated by the notified log output destination information is a table, the log output unit 111 is connected to the RDBMS “XXXX” specified by the RDBMS name 412 of the log output destination information 41, and the RDBMS “ XXX ″ adds log data (records) in a table format to the table 51 shown in FIG. 5A, for example. On the other hand, if the log output destination indicated by the notified log output destination information is a file, the log output unit 111 adds log data in a file format to the file 52 shown in FIG. 5C, for example. The path for specifying the location of the file 52 includes the path to the disk drive (detection target designation information) notified by the log output destination determination unit 110 and the log output destination information 42 specified by the log output destination determination unit 110. Are represented by a path 422 and a file name 423 (file designation information).

  As described above, in this embodiment, the free capacity of the disk drive currently used for storing log data (that is, the disk drive specified by the detection target path 301) is monitored, and the log is flexibly determined by the free capacity. The output path (disk drive used to store log data) is changed. This change in the log output path prevents the log table or log file from being stored in a specific disk drive (fixed path) unlike the conventional technology, thereby compressing the storage area of the specific disk drive. Log data can be stored without doing so. In addition, in the present embodiment, whether the log output destination is a table or a file can be set according to the designation of the user (administrator). On the other hand, in the prior art, since log data is stored in a specific disk drive, the storage area of the specific disk drive is compressed without the user (administrator) being aware.

  In the present embodiment, when log data is managed in a table, an existing RDB tool is used to extract data from the table without introducing a new RDB (relational database) tool. Thus, it is possible to refer to, extract, and delete log data.

  The failure detection unit 105 monitors whether the log output by the log output unit 111 is normally performed. When the log output destination determination unit 110 determines a table as a log output destination (step S6), for example, after a predetermined time has passed, the log output unit 111 inquires of the fault detection unit 105, and whether a log output by the log output unit 111 has failed Is determined (step S7). If the log output by the log output unit 111 is a failure in which log output is not normally performed due to a network disconnection, RDB tool service stop, or the like, the log output destination determination unit 110 sets the log output destination information 41 to “ The log output destination information 42 is changed from the “unused” state to the “used” state from the “used” state to the “unused” state (step S8). This change is made by changing the state of the flag F1 attached to the log output destination information 41 from “ON” to “OFF”, and changing the state of the flag F2 attached to the log output destination information 42 from “OFF” to “ON”. In addition, it is realized by changing each. With this change, the log output destination is changed from the table to the file. That is, the process in step S8 is equivalent to changing the log output destination from the table to the file.

  Next, the log output destination determination unit 110 displays the log output destination information in the “used” state set in the log output destination information storage unit 102, that is, the log output destination information 42 indicating the file as the log output destination. 111 and the table / file generation determination unit 112 are notified (step S9). In this case, the table / file generation determination unit 112 requests the file generation unit 114 to generate a new file table. In response to this request, the file generation unit 114 uses the disk drive (that is, the disk specified by the detection target path 301 (D: \) of the disk switching information 30) that has been used to store the log data in the table format until then. A new file is generated in the drive) based on the path 422 (log \) of the log output destination information 42 and the file name 423 (logfile.txt).

  Further, the data collected by the log collection unit 109 and not output normally is transferred from the table / file generation determination unit 112 to the file generation unit 114. The file generation unit 114 generates file format log data from the log data. The generated log data in the file format is passed to the log output unit 111.

  When the log output unit 111 receives the log data in the file format from the file generation unit 114, the log output unit 111 is specified by the path 422 and the file name 423 of the log output destination information 42 notified by the log output destination determination unit 110. File, that is, a file newly generated by the file generation unit 114 (for example, the file 52 shown in FIG. 5C).

  As described above, in the present embodiment, even when the log data is set in advance to be output in the table format, the log output in the set table format is not performed normally, and when the failure occurs, Log data can be automatically changed to a file format and output.

  When a failure occurrence is detected by the failure detection unit 105, the mail transmission unit 107 transmits, for example, an e-mail indicating the occurrence of the failure to the administrator's terminal 20-1. Thus, the administrator can grasp the status of the occurrence of the failure by receiving the mail from the mail transmitting unit 107.

  The failure recovery detection unit 106 detects the failure recovery by monitoring the recovery state of the failure related to the log output. When the failure recovery detection unit 106 detects failure recovery, the mail transmission unit 107 transmits an email indicating failure recovery to the administrator's terminal 20-1. The administrator can grasp the situation of the occurrence of the failure by receiving the mail from the mail transmitting unit 107 by the terminal 20-1.

  As described above, in this embodiment, when a log output failure occurs in a state where a table is specified as an output destination, the log output destination is automatically switched from the table to the file, and the log data in the file format Is added to the file. This can prevent log data from being lost.

  In the present embodiment, the failure recovery detection unit 106 detects failure recovery. In this case, an e-mail indicating failure recovery is transmitted from the mail transmitting unit 107 to the administrator's terminal 20-1. The administrator can grasp the failure recovery by receiving the mail from the mail transmitting unit 107 by the terminal 20-1. Here, it is conceivable that the log output destination is restored from the file to the original text in response to the detection of the failure recovery by the failure recovery detection unit 106. However, if this is done, the time series of log data is in the order of “table” → “file” → “table”, which is not preferable for managing log data in time series. Therefore, in this embodiment, so that the time series of log data is maintained between the “table” and “file”, the log output destination is not restored from the file to the original text even if the failure is recovered. Managed.

  Next, generation of a new table or file based on the currently used table or file size will be described. The table / file generation determination unit 112 has a maximum size indicated by the log output destination information in the “used” state set in the log output destination information storage unit 102 (the log output destination information 41 has the maximum size 416, and the log output The maximum size 424 in the previous information 42) is compared with the size of the currently used table or file (hereinafter referred to as the table / file size).

  If the table / file size exceeds the specified maximum size (maximum table size or maximum file size), the table / file generation determination unit 112 sends the current log data to the table generation unit 113 or the file generation unit 114. Request to create a new table or file in the disk drive used as the storage location. Then, a new table or file is automatically generated by the table generation unit 113 or the file generation unit 114 in the disk drive currently used as the storage destination of the log data.

  Here, details of the automatic generation of a table or file will be described by taking automatic generation of a file as an example. In the log output destination information 42 shown in FIG. 4B, “logfile.txt” is specified as the file name 423. In this case, the file generation unit 114 generates a new file whose file name is “logfile1.txt” based on the file name 423, for example. Then, the file name 423 of the table / file generation determination unit 112 and the log output destination information 42 is updated from “logfile.txt” to “logfile1.txt”. Similarly, each time the path is switched or the size of the currently used file exceeds the maximum size 424 of the log output destination information 42, the file names are “logfile12.txt”, “logfile3.txt”,... Files are generated sequentially.

  As described above, in this embodiment, the size of a file in use is monitored, and a new file is generated each time the size of the file exceeds a certain size (maximum size). It is possible to avoid the situation that the log file) is too large to be referenced.

  Similarly, when the log output destination is “table”, each time the size (or number of records) of the currently used table exceeds the size (or number of records) specified by the maximum size 416 of the log output destination information 41. The file generation unit 114 is activated by the table / file generation determination unit 112. Accordingly, the file generation unit 114 generates a new table using the RDBMS “XXXX” specified by the RDBMS name 412 of the log output destination information 41.

  As described above, in this embodiment, the size of a table in use is monitored, and a new table is generated each time the size of the table exceeds a certain size (maximum size). It is possible to avoid the situation that the size of the log table) is too large to be referred to.

  In the present embodiment, as a condition for generating a new file or table, it is applied that the size of the file or table being used exceeds the maximum size. However, period information can be used as a condition for generating a new file or table, for example, every day or every hour. Further, as a condition for generating a table, it may be applied that the number of records in the table in use exceeds the maximum number of records.

  In the present embodiment, the content of the operation for accessing the personal information by the user is collected as log data. However, the operation content of the user for the information processing system may be collected as log data without being limited to the content of the operation for accessing the personal information. In addition to the contents of user operations, the contents of various events that occur in the system, such as program execution status in the information processing system, may be collected as log data. That is, the present invention is not limited to the type of log data collected.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. In addition, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. For example, information such as the creation date may be used as a method for naming the log data.

The block diagram which shows the structure of the information processing system which concerns on one Embodiment of this invention. The figure which shows the block configuration of the log management part 100 in FIG. The figure which shows an example of the disk switching information 30 stored in the disk switching information 30 in FIG. The figure which shows an example of the log output destination information 41 and 42 stored in the log output destination information storage part 102 in FIG. The figure which shows the data structure example of the table 51 which registers the log data of a table format applied in the embodiment, the data structure example of the log data of a file format, and an example of the file 52 containing the log data of a file format . 6 is a flowchart illustrating a procedure of log output destination determination processing by a log output destination determination unit 110;

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... Server, 11 ... Database, 20-1 to 20-n ... Terminal, 30 ... Disk switching information, 41 ... Log output destination information (first log output destination information), 42 ... Log output destination information (second Log output destination information), 51 ... Table (log table), 52 ... File (log file), 100 ... Log management unit, 101 ... Disk switching information storage unit, 102 ... Log output destination information storage unit, 103 ... Log management information Setting unit 104 ... Free capacity detection unit 105 ... Fault detection unit 109 ... Log collection unit 110 ... Log output destination determination unit 110a ... Switching unit 111 ... Log output unit 112 ... Table / file generation determination unit 113: Table generation unit, 114: File generation unit.

Claims (7)

In an information processing system that manages log data,
Detection target specification information for specifying a disk drive used for storing log data as a target for monitoring free capacity, reference free capacity information indicating a lower limit value of the free capacity of the disk drive, and detection target specification information Disk switching information storage means for storing in advance disk switching information including switching destination designation information for specifying a disk drive to be used instead of the specified disk drive;
Free space detection means for monitoring the free space of the disk drive specified by the detection target specifying information and detecting that the free space is below a threshold value indicated by the reference free space information;
The disk drive used for storing log data when the free capacity detecting means detects that the free capacity of the disk drive specified by the detection target specifying information has fallen below the threshold indicated by the reference free capacity information Switching means for switching from the currently used disk drive designated by the detection target designation information to the disk drive designated by the switching destination designation information;
Log collection means for collecting log data;
An information processing system for managing log data, comprising: log output means for storing log data collected by the log collecting means in a disk drive used to store current log data. Log output destination information storage means for preliminarily storing first log output destination information for specifying log data to be output in a table format and second log output destination information for specifying log data to be output in a file format And log output destination information storage means for setting only one of the first and second log output destination information to be usable.
Table generating means for generating log data in a table format from log data collected by the log collecting means;
File generation means for generating log data in a file format from log data collected by the log collection means;
Collected by the log collecting means based on the log output destination information set in a usable state among the first and second log output destination information stored in the log output destination information storage means Log output destination determination means for determining whether a log output destination as a log data output destination is a log table or a log file, and
The log output unit stores the log data in the table format or the log data in the file format on the disk drive currently used to store the log data based on the determination result of the log output destination by the log output destination determination unit The information processing system according to claim 1, wherein processing for adding to the log table or log file being performed is performed. The first log output destination information includes database management system designation information for designating a database management system for operating a log table,
The log output means causes the database management system specified by the database management system designation information included in the first log output destination information to add log data in the table format to the log table. The information processing system according to claim 2. It further comprises failure detection means for detecting that a failure has occurred in the process of adding log data in the table format to the log table,
The second log output destination information includes file designation information indicating a location and a file name of the log file,
The log output destination determination unit determines to switch the log output destination from the log table to the log file in response to detection of the occurrence of a failure by the failure detection unit, and usable log output destination information Switch from the first log output destination information to the second log output destination information,
When the log output destination determination unit determines that the log output destination is to be switched from the log table to the log file, the file generation unit stores the first disk drive in the currently used disk drive indicated by the detection target designation information. The information processing system according to claim 3, wherein a new log file specified by the file specification information included in the log output destination information is generated. The first log output destination information includes a generation condition for generating a new log table,
The second log output destination information includes file designation information indicating a location and a file name of the log file and a generation condition for generating a new log file,
The information processing system includes a table / file generation determination unit that determines whether a generation condition included in log output destination information in a usable state among the first and second log output destination information is satisfied. In addition,
The table creation means is included in the first log output destination information when the table / file generation determination means determines that the generation condition included in the first log output destination information is satisfied. The database management system designated by the database management system designation information is configured to generate a new log table in the currently used disk drive indicated by the detection target designation information,
The file generation unit is currently used as indicated by the detection target designation information when the table / file generation determination unit determines that the generation condition included in the second log output destination information is satisfied. 4. The information processing system according to claim 3, wherein a new log file is generated on a disk drive based on file designation information included in the second log output destination information. In a log data management method applied in an information processing system for managing log data,
Disk switching information stored in advance in the disk switching information storage means, detection target designation information for designating a disk drive used for storing log data as a target for monitoring free capacity, and the free capacity of the disk drive Included in the disk switching information based on the disk switching information including reference free capacity information indicating the lower limit value of the disk and switching destination designation information for designating the disk drive used instead of the disk drive designated by the detection target designation information. Monitoring the free capacity of the disk drive designated by the detection target designation information, and detecting that the free capacity falls below a threshold indicated by the reference free capacity information;
When it is detected that the free space of the disk drive specified by the detection target specification information is below the threshold indicated by the reference free space information, the detection target specification is set as a disk drive used to store log data. Switching from the currently used disk drive indicated by the information to the disk drive indicated by the switching destination designation information;
Collecting log data;
Storing the collected log data in a disk drive that is currently used to store the log data. A program for managing log data,
On the computer,
Disk switching information stored in advance in the disk switching information storage means, detection target designation information for designating a disk drive used for storing log data as a target for monitoring the free capacity, the free capacity of the disk drive Included in the disk switching information based on the disk switching information including reference free capacity information indicating the lower limit value of the disk and switching destination designation information for designating the disk drive used instead of the disk drive designated by the detection target designation information. Monitoring the free capacity of the disk drive designated by the detection target designation information, and detecting that the free capacity falls below a threshold indicated by the reference free capacity information;
When it is detected that the free space of the disk drive specified by the detection target specification information is below the threshold value indicated by the reference free space information, the detection target specification is set as a disk drive used for storing log data. Switching from the currently used disk drive indicated by the information to the disk drive indicated by the switching destination designation information;
Collecting log data;
A program for executing the step of storing the collected log data in a disk drive currently used to store the log data.

Images