JP5375281B2 - Failure analysis information collection device, failure analysis information collection method, failure analysis information collection program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To quickly sample information necessary for the analysis of an obstacle generated in a computer system. <P>SOLUTION: An obstacle analysis information gathering device includes: an acceptance part 11 for accepting an input parameter indicating information related with an obstacle form an external terminal; a difference management DB121 for storing system difference information indicating the difference of unique file system setting; a parameter analyzing part 12 for converting an input parameter 21 into a conversion parameter 22 based on the system difference information of the difference management DB 121; an information gathering script generation part 13 for generating information gathering script 131 indicating the acquisition procedure of information for performing obstacle analysis based on the conversion parameter 22; and a script execution means for sampling the obstacle analysis information by executing the information gathering script. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to a technique for collecting information related to a failure in a computer system.

  When a failure occurs in a computer system, the necessary information is collected as quickly as possible, the failure is analyzed, and information such as log files and system configuration files necessary for proper system recovery It is required to quickly collect and analyze the failure based on this information.

  For example, for a known or similar failure in a specific computer system, a method of automatically collecting information necessary for failure analysis set in advance according to the content of the failure that has occurred (Patent Document 1, Patent Document) 2).

  On the other hand, when a new failure occurs in a specific computer system, the necessary information collected differs depending on the system operation status, the failure status, and the like. For this reason, it is difficult to automatically collect information necessary for failure analysis.

On the other hand, a related technique for efficiently collecting information in response to a new failure occurring in a computer system is disclosed (Patent Document 3).
In this related technology, information is automatically collected for known failures, and information to be collected by the operator for new failures is automatically entered by inputting a parameter sheet (information collection script). Generate. In addition, by registering the generated information collection script in the database (DB), the next time the same failure occurs, the registered information collection script will be executed. Collects automatically.

Here, for example, a new failure occurs in a certain product (here, a computer system), and the department (survey analysis department) collects information for failure investigation (mainly logs). Consider a case where an operation administrator (operation management server) is requested for a file or a setting file.
The survey analysis department may be a server computer set in advance.

At this time, the information transmitted to the operation management server from the investigation and analysis department that performs failure investigation and analysis includes information such as the log file stored in the investigation target product, the log output destination file (log output destination), and the configuration file This is the default path that indicates the stored location.
However, the information indicating the log output destination and the storage location of the setting file of the computer system often differ depending on the computer system.
Depending on the computer system, the log file storage location is rotated at a fixed timing. The interval at which rotation is performed varies depending on the computer system.

  For this reason, the operation administrator side (operation management server) cannot input the parameter sheet on the survey analysis department side, and based on the information notified from the survey analysis department, for example, manual input, etc. Was done.

  However, in this case, it is necessary to input the information communicated on the operation manager side after re-reading the information in accordance with the file storage method and the hierarchical structure in the actual computer system. There are inconveniences such as reading errors or misreading during input.

  As a related technique for this, a LAN automatic test apparatus is disclosed that mechanizes items relating to simple work for confirmation tests of a distributed system and automatically performs tests (Patent Document 4).

JP 2003-345628 A JP 2003-195687 A JP 2003-171061 A JP 04-264628 A

However, in the related techniques disclosed in Patent Documents 1 to 4, for example, when a new failure occurs in a specific computer system, information for performing failure analysis related to this failure is collected. Therefore, it is necessary to consider the settings specific to each computer system, and it is necessary to rewrite log rotation and the like based on the judgment of the operation operator.
For this reason, as described above, it takes a long time to collect information related to failure analysis, or an artificial information collection error due to an input error occurs. Inconvenience that cannot be collected quickly can occur.

[Object of invention]
The present invention provides a failure analysis information collection device, a failure analysis information collection method, and a failure analysis information collection program for quickly collecting information necessary for analysis of a failure that has occurred in a computer system, improving the disadvantages of the related technology. The purpose is to do.

In order to achieve the above object, a failure analysis information collection device according to the present invention is a failure analysis information collection device including an input parameter receiving unit that receives an input parameter indicating information related to a failure from an external terminal. A difference management unit for holding system difference information indicating a difference in file system settings unique to each of the analysis information collection device and the external terminal, and a file name of the information indicated in the input parameter and a file indicating a file storage location address, and if the source and movement information indicating the movement destination of the file contains a parameter interpretation unit to convert these information based on the system differential information of the differential management unit, wherein the converted input Information for generating an information collection script indicating an information acquisition procedure for performing the failure analysis based on the parameters And preparative script generating section, Rutotomoni a script execution unit for executing said generated information extraction script for collecting information for the failure analysis, the parameter interpretation unit, a row of the input parameters Rotation The log rotation check function for including the storage location of the log file in the converted input parameter based on the log rotation rule included in the system difference information. Yes.

Also, the failure analysis information collection method according to the present invention is a failure analysis information collection device including the input parameter receiving unit that receives an input parameter indicating information related to a failure from an external terminal, and performs the analysis of the failure The failure analysis information collecting method for collecting the failure analysis information of the failure analysis information, and storing system difference information indicating differences in file system settings specific to each of the failure analysis information collection device and the operation terminal and indicated in the input parameter file name information, file address indicating the storage location of the file, and if the source and movement information indicating the movement destination of the file contains, these are based on the system differential information of the differential management unit It converts the information, information indicating the acquisition procedure information for performing the failure analysis based on the converted input parameters Generates a preparative script, while collecting information for the fault analysis by running the generated information collection script, processing for converting the movement information of the input parameters, the input parameters is carried out with rotation The storage location of the log file is included in the converted input parameter based on the log rotation rule included in the system difference information .

The failure analysis information collection program according to the present invention is a failure analysis information collection device including the input parameter reception unit that receives an input parameter indicating information related to a failure from an external terminal, and collects information related to the failure A failure analysis information collection program for performing information on the information indicated in the input parameter based on system difference information indicating a difference in file system settings specific to each of the failure analysis information collection device and the operation terminal. When the file name, the file address indicating the file storage location, and the movement information indicating the movement source and the movement destination of the file are included, a parameter conversion function for converting these information respectively, and the converted input parameter Information collection script showing information acquisition procedure for failure analysis based on A script generating function of generating a fault analysis information acquisition processing function for performing a process of collecting information for performing the failure analysis by running the generated information collection script, with those causing a computer to execute the The parameter conversion function converts the storage location of the log file based on a log rotation rule included in the system difference information when the input parameter relates to a log file being rotated. It includes a log rotation check function included in the input parameters .

  Since the present invention is configured and functions as described above, according to this, the input parameter is converted based on the system difference information indicating the difference of the file system setting specific to each of the failure analysis information collection device and the external terminal. In addition, the information collecting script is generated based on the converted input parameter, and the information collecting script is executed to collect the information related to the failure, thereby analyzing the failure occurring in the computer system. A failure analysis information collection device, a failure analysis information collection method, and a failure analysis information collection program that can quickly collect necessary information can be provided.

It is a schematic block diagram which shows one Embodiment of the failure analysis information collection device by this invention. It is explanatory drawing which shows an example of the input parameter in the failure analysis information collection device disclosed in FIG. It is explanatory drawing which shows an example of the system specific name management table in the failure analysis information collection device disclosed in FIG. It is explanatory drawing which shows an example of the rotation log management table in the failure analysis information collection device disclosed in FIG. It is explanatory drawing which shows an example of the conversion parameter in the failure analysis information collection device disclosed in FIG. It is a flowchart which shows the operation | movement process step of the input parameter reception part 11 in the failure analysis information collection device disclosed in FIG. It is a flowchart which shows the operation | movement process step of the parameter interpretation part 12 in the failure analysis information collection device disclosed in FIG. It is a flowchart which shows the operation | movement process step of the system specific check by the parameter interpretation part 12 in the failure analysis information collection device disclosed in FIG. 6 is a flowchart showing operation processing steps of log rotation check by a parameter interpretation unit 12 in the failure analysis information collection device disclosed in FIG. 1. It is a flowchart which shows the operation | movement process step of the script production | generation part 13 in the failure analysis information collection device disclosed in FIG. It is a flowchart which shows the operation processing step of the command execution script production | generation by the script production | generation part 13 in the failure analysis information collection apparatus disclosed in FIG. It is a flowchart which shows the operation processing step of log file collection script generation by the script generation part 13 in the failure analysis information collection device disclosed in FIG. It is a flowchart which shows the operation | movement process step of the certification | authentication file collection | recovery script generation by the script production | generation part 13 in the failure analysis information collection apparatus disclosed in FIG. It is a flowchart which shows the operation | movement process step of the system specific check by the script production | generation part 13 in the failure analysis information collection device disclosed in FIG. It is a flowchart which shows the operation | movement process step of the script execution part 14 in the failure analysis information collection device disclosed in FIG. 7 is a flowchart illustrating an example of transition of an acquisition target file list when a rotation log collection algorithm is applied in the failure analysis information collection apparatus disclosed in FIG. 1.

[Embodiment]
Next, the basic configuration content of the embodiment of the present invention will be described.

The configuration of the embodiment of the present invention will be described in detail with reference to the drawings.
As shown in FIG. 1, the failure analysis information collection device 1 of the present embodiment is configured to be connected to an operation terminal (external terminal) 2 for inputting input parameters.

As shown in FIG. 1, the failure analysis information collecting apparatus 1 includes an input parameter receiving unit 11, a parameter interpretation unit 12, a difference management DB 121, a script generation unit 13, and a script execution unit 14.
Here, the failure analysis information collecting device is a computer having a CPU, a memory, and an HDD, and the input parameter receiving unit 11, the parameter interpreting unit are controlled by the CPU controlling the execution of the program read into the memory. 12, the operation processing of the difference management DB 121, the script generation unit 13, and the script execution unit 14 is realized.

Here, the failure analysis information collecting apparatus 1 has a file structure composed of hierarchical directories and files, like a computer system such as a UNIX system (UNIX is a registered trademark). A file can be uniquely identified by specifying an absolute path (storage directory + file name).
The file name of a certain file stored in the failure analysis information collecting apparatus 1 which is a computer system in this embodiment is “syslog.log”, and the storage directory of this file is “/ var / adm / syslog /”. The absolute path of this file is "/var/adm/syslog/syslog.log".
Each file holds the last update date as a value, and the system can refer to it at any time.

The operation terminal 2 has a function of creating an input parameter 21 based on a predetermined format and sending it to the failure analysis information collection device 1.
The input parameter reception unit 11 has a function of receiving an input parameter 21 having a predetermined format from the operation terminal 2 and passing it to the parameter interpretation unit 12.

  The parameter interpretation unit 12 receives the input parameter 21 from the input parameter reception unit 11, makes an inquiry to the difference management DB 121, and converts the storage location of the information to be collected as necessary into a system-specific value. Is generated.

  The script generation unit 13 receives the conversion parameter 22 from the parameter interpretation unit 12, and generates an information collection script 131 based on the received parameter.

  The script execution unit 14 executes the information collection script 131 and collects necessary information.

  As shown in FIG. 2, the input parameter 21 includes a type 211, a default name 212, an option A213, and an option B214.

Here, “command execution”, “log file”, or “setting file” is designated as the type 211.
The information to be collected is roughly divided into command execution results and log files.
Since the values input to the default name 212, option A213, and option B214 differ depending on the type, each type will be described below.

  When the type 211 is “command execution”, the default command 212 describes the corresponding command name, the option A 213 describes the command option, and the option B 214 describes the output destination file name. The option A213 may be blank, but the output destination file name of the option B214 is an essential item. For example, to output the command execution result of “ls_l” with the file name “ls.log”, type 211 = “command execution”, default name 212 = “ls”, option A213 = “-l”, option B214 = “ls.log”.

When the type 211 is “log file”, the default name 212 describes the corresponding file name, the option A213 describes the log acquisition start time, and the option B214 describes the log acquisition end time.
Here, it is assumed that the log file is constantly updated and is rotated according to time, file size, and the like.
For example, since the failure occurrence time is “2008/11/7 20:15”, and it is desired to obtain a log of 10 minutes before and after the failure occurrence, the option A213 contains “2008/11/7 20:05” B214 describes “2008/11/7 20:25”.

  One or both of option A 213 and option B 214 may be blank. When blank, there is no start time and no end time. For example, if both are blank, it means that the latest log file and all rotated log files are acquired.

  When the type 211 is “setting file”, the default name 212 is the corresponding file name, and the options A213 and B214 are blank.

  The difference management DB 121 includes two systems, a system unique name management table 122 and a log rotation rule management table 123, as shown in FIGS.

  The system unique name management table 122 is a correspondence table of default names 1221 and system unique names 1222. The system unique name 1222 is an absolute path (unique value in the system) of a command or file.

  The parameter interpretation unit 12 refers to the default name 212 of the input parameter and the default name 1221 of the system unique name management table, and if there is a match, the system unique name 1222 is found, and if there is no match, the default name 212 of the input parameter. The conversion parameter 22 is output using as a value. Further, the default name 1221 and the system unique name 1222 may have an N: 1 relationship.

For example, if `` syslog '' is an abbreviation, it officially means `` /var/adm/syslog/syslog.log '' and the system specific name is `` /var2/adm/syslog/syslog.log '' In the system unique name management table 122,
"Syslog"->"/var2/adm/syslog/syslog.log"
And `` /var/adm/syslog/syslog.log '' → `` /var2/adm/syslog/syslog.log ''
These two lines are registered, and the value after conversion is determined to be one regardless of the input parameter. By allowing input by abbreviations, it is possible to reduce the load related to input of operator input parameters.

The rotation log management table 123 is a correspondence table of log file names 1231 and rotation log storage locations 1232. The log file name 1231 is an absolute path (a unique value in the system).
The rotation log storage location 1232 is one for each log file, and when a certain log file is rotated a plurality of times, it is stored with different file names in the same directory.

Further, it is assumed that no files other than the rotation log of the corresponding log file are stored in the corresponding directory.
Further, when the type is “log file”, the rotation log management table 123 is referred to, and the rotation log storage location 1232 of the corresponding log file 1231 is added to the conversion parameter 1222.

  Referring to FIG. 5, the conversion parameter 22 includes a type 221, a system unique name 222, an option A 223, an option B 224, and a rotation log storage location 225.

  The value of the input parameter 21 is entered as it is in the type 221, option A223, and option B224.

  The system unique name 222 is a value converted by the parameter interpretation unit 12 with reference to the system unique name management table 122.

  A value added by the parameter interpretation unit 12 with reference to the rotation log management table 123 is entered in the rotation log storage location 225. For this reason, it is blank when the type 221 is “command execution” or “setting file”.

  The information collection script 131 is a script created by the script generation unit 13 based on the conversion parameter 22. Necessary information is collected when the script execution unit 14 executes this script.

  With this configuration, in this embodiment, even when the rotation interval of the log, the storage location of the rotated log file, the system setting file, and the like differ from system to system, for example, the computer system It is possible to efficiently collect failure analysis information related to a failure.

  In this embodiment, when inputting the log name and command name necessary for the parameter sheet, failure analysis is performed without considering system-specific settings such as file storage location and log file rotation destination information. The information necessary for data collection can be efficiently collected using a parameter sheet and an information collection script.

[Description of Operation of Embodiment]
Next, an outline of the operation of this embodiment will be described.
The difference management DB 121 holds system difference information indicating differences in file system settings unique to each of the failure analysis information collection device 1 and the operation terminal 2, and the file name of the information indicated in the input parameter 21 and the storage location of the file Is converted based on the system difference information of the difference management unit (parameter conversion process), and the script generation unit 13 converts the failure based on the conversion parameter 22. An information collection script 131 indicating an acquisition procedure of information for analysis (failure analysis information) is generated (script generation process), and the script execution unit 14 executes the information collection script to collect failure analysis information (failure Analysis information acquisition process).

  Here, with respect to the parameter conversion step, the script generation step, and the failure analysis information acquisition step, the execution contents may be programmed and executed by a computer.

  Next, the operation of this embodiment will be described in detail based on the flowchart of FIG.

First, as shown in FIG. 2, the operation terminal 2 generates an input parameter 21 and inputs the input parameter 21 to the failure analysis information collection device 1.
Here, the operation operator (or the survey analysis department) of the operation terminal 2 may perform input using the operation terminal 2.

  Next, as shown in FIG. 6, the input parameter reception unit 11 receives the input parameter 21 from the operation terminal 2 (step S061), and performs a process of passing it to the parameter interpretation unit 12 (step S062).

Next, the operation of the parameter interpretation unit 12 will be described based on the flowchart of FIG.
The parameter interpretation unit 12 receives the input parameter 21 from the input parameter reception unit 11 (step S071) and performs a syntax check (step S072).
If there is an error (there is an error), an input error is returned to the operation terminal 2 (step S073).
On the other hand, if there is no input error (no error), the input parameter 21 makes an inquiry to the difference management DB 121 (step S074).
Here, the parameter interpretation unit 12 performs a system unique name check and generates a conversion parameter 22 in which a default name is converted into a system unique name (step S075: system unique name check).

Next, the parameter interpretation unit 12 determines the type 211 (step S076), and if the generated conversion parameter 22 is a log file, further performs a log rotation check, and adds the rotation log storage location to the conversion parameter 22 ( Step S077: Log rotation check).
Next, the parameter interpretation unit 12 passes the finally completed conversion parameter 22 to the script generation unit 13 (step S078).

  Here, the system unique name check (S075) will be described with reference to the flowchart of FIG.

The parameter interpretation unit 12 refers to the system unique name management table 122 (S081), and compares and references the default name 212 of the input parameter 21 and the default name 1221 of the system unique name management table 122 (step S082).
As a result of this comparison reference (step S083), when they do not match (NO), the parameter interpretation unit 12 transcribes the default name 2122 of the input parameter 21 to the system unique name 222 of the conversion parameter 22.
On the other hand, if they match as a result of the comparison reference (YES), the parameter interpretation unit 12 transfers the system unique name 122 of the system unique name management table 122 to the system unique name 222 of the conversion parameter 22 (step S085).

  Here, the log rotation check (step S077) by the parameter interpretation unit 12 will be described with reference to the flowchart of FIG.

The parameter interpretation unit 12 refers to the rotation log management table 123 (step S091), and compares the default name 222 of the conversion parameter 22 with the log file name 1231 of the rotation log management table 123 (step S092).
As a result of the comparison (S093), if they do not match (NO), no special action is taken and the rotation log storage location of the conversion parameter 22 is left blank (step S094). The rotation log storage location 1232 of the rotation log management table 123 is transferred to the log storage location 225 (step S095).

  The parameter interpretation unit 12 operates as shown in FIGS. 7 to 9 to convert the input parameter 21 (FIG. 2) into a conversion parameter 22 (FIG. 5), and passes the conversion parameter 22 to the script generation unit 13. .

Next, operation processing steps of the script generation unit 13 will be described based on the flowchart of FIG.
First, the script generation unit 13 receives the conversion parameter 22 from the parameter interpretation unit 21 (step S101), and generates a command execution script (step S102).
Next, the script generation unit 13 generates a log file collection script (step S103) and also generates a setting file collection script (step S104).

  Further, the script generation unit 13 generates a script for archiving and collecting command execution results, log files, and setting files collected by each script (step S105), and finally creates an information collection script 131 that is generated by the script execution unit 14. (Step S106).

  First, command execution script generation (step S102) will be described based on the flowchart shown in FIG. 11, and then log file collection script generation (step S103) will be described based on the flowchart shown in FIG.

Further, the setting file collection script generation (step S104) will be described with reference to the flowchart shown in FIG.
Based on the flowchart shown in FIG. 14, the configuration file collection script generation (step S104) will be described in detail.

First, the operation of the command execution script generation (step S102) by the script generation unit 13 will be described based on the flowchart of FIG.
The script generation unit 13 determines the type 221 (step S111).
At this time, if the type 221 is command execution, the value of the option A 223 is determined (step S112). If the type 221 is not blank, a command execution script is generated using the system unique name 222, option A 223, and option B 224 as parameters. (Step S113).
On the other hand, if it is blank, a command execution script is generated using the system unique name 222 and option B224 as parameters (step S114).

Next, the operation of the log file collection script (step S103) by the script generation unit 13 will be described in detail based on the flowchart of FIG.
First, the script generation unit 13 determines the type 221 (step S121).
At this time, if the type 221 is a log file, a log file collection script is generated based on a preset rotation log collection algorithm (step S122).
The rotation log collection algorithm will be described later with reference to FIG.

Here, the rotation log collection algorithm (of the script generation unit 13) will be described in detail based on the flowchart of FIG.
First, the value of the rotation log storage location 225 is determined.
At this time, if it is blank, the log with the system unique name 222 is added to the collection target log file list (step S132).
If there is a description, all logs that are candidates for acquisition, that is, logs with the system unique name 222 and all files under the rotation log storage location 225 are sorted in ascending order of the last update date and added to the acquisition target log file list (Step S133).

Next, the value of the option A 223 is determined (step S134).
If there is a description, the log file whose last update date and time is earlier than the option A223 is deleted from the acquisition target file list (step S135).
Next, the value of the option B 224 is determined (step S136).

If there is a description, with respect to the log file with the latest update date and time later than the option B224, the log file other than the time closest to the option B224 is deleted from the acquisition target log file list (step S137).
By the operation described above, only the log files including the time of option B 224 to the time of option B 224 are included in the acquisition target file list, and all log files on the list may be acquired (step S138).

  Next, a transition example of the acquisition target file list when the rotate log collection algorithm is applied will be described with reference to FIG.

Option A is 13:30 and Option B is 15:30.
First, it is assumed that the income target log file list becomes L161 by the operation in step S133.
In each log file, a log from the last update date / time of the previous log to its own last update date / time is recorded.

  For example, the log 1 is recorded from 16:00 to 17:00. Next, when the operation in step S135 is performed, the log file whose last update date and time is 13:30 or earlier is deleted from the list. Therefore, the log 5 and the log 6 are deleted, and the acquisition target log file list becomes L162. .

  Next, when the operation in step S137 is performed, out of the log files whose last update date and time is later than 15:30, those other than the log file closest to 15:30 (= log 2) are deleted from the acquisition target log file list. Therefore, log 0 and log 1 are deleted, and log 2, log 3, and log 4 remain in the acquisition target log file list as in L163. Since these logs include logs from 13:00 to 16:00, the condition of logs from 13:30 to 15:30 is satisfied.

  Here, the operation of the setting file collection script (step S104) will be described in detail based on the flowchart of FIG.

  First, the type 221 is determined (step S141). If the type 221 is a command execution file, a setting file collection script is generated using the system unique name 222 as a parameter (step S142).

Next, the operation flow of the script execution unit 14 will be described based on the flowchart of FIG.
The information collection script 131 is received from the script generation unit 13 (step S151), and the information collection script 131 is executed to collect necessary logs (step S156).

  As described above, in this embodiment, the operation operator or the research analysis department does not need to consider system-specific information or log rotation, and by inputting specific parameters, for example, failure analysis information, Collection can be performed quickly and accurately.

Further, in the present embodiment, an operation error and a determination error due to rereading are reduced by automatic execution by a script, so that information necessary for personality can be collected.
Furthermore, since it is possible to collect information quickly and accurately, failure analysis and recovery in a computer system can be performed quickly.

  The present invention can be effectively applied to a system that performs failure analysis in a network system such as a local area network or a wide area network in which computer terminals are connected to each other.

1 Failure analysis information collection device 2 Operation terminal (external terminal)
DESCRIPTION OF SYMBOLS 11 Input parameter reception part 121 Difference management database 13 Script generation part 14 Script execution part

Claims (4)

A failure analysis information collection device including an input parameter receiving unit that receives an input parameter indicating information related to a failure from an external terminal,
A difference management unit that holds system difference information indicating a difference in file system settings unique to each of the failure analysis information collection device and the external terminal;
When the input parameter includes a file name of the information, a file address indicating the storage location of the file, and movement information indicating the movement source and destination of the file, it is based on the system difference information of the difference management unit. A parameter interpreter that converts the information ,
An information collection script generating unit that generates an information collection script indicating an acquisition procedure of the information for failure analysis based on the converted input parameter;
Script execution means for collecting the information for failure analysis by executing the generated information collection script;
Provided with a,
When the parameter interpretation unit relates to the log file being rotated, the storage location of the log file based on the log rotation rule included in the system difference information is the converted input. A failure analysis information collection device having a log rotation check function included in a parameter . In the failure analysis information collection device according to claim 1,
When the information content indicated in the input parameter is information to be updated, the parameter interpretation unit stores information before update and information after update of information updated within a preset required time. A failure analysis and sampling device comprising update information storage means for performing In the failure analysis information collecting apparatus including the input parameter receiving unit that receives an input parameter indicating information related to a failure from an external terminal, the failure analysis information collecting method for collecting failure analysis information for the failure analysis,
Holds system difference information indicating differences in file system settings specific to each of the failure analysis information collection device and the operation terminal,
The system difference information of the difference management unit when the file name of the information indicated in the input parameter, the file address indicating the storage location of the file, and the movement information indicating the source and destination of the file are included. convert these information based on the,
Generate an information collection script indicating an acquisition procedure of the information for failure analysis based on the converted input parameter,
Collecting the information for failure analysis by executing the generated information collection script ,
The storage location of the log file based on the log rotation rule included in the system difference information when the process of converting the input parameter movement information relates to a log file in which the input parameter is rotated Is included in the converted input parameter . A failure analysis information collecting apparatus including the input parameter receiving unit that receives an input parameter indicating information relating to a failure from an external terminal, the failure analysis information collecting program for collecting the failure analysis information for failure analysis. And
Based on system difference information indicating a difference in file system settings specific to each of the failure analysis information collection device and the operation terminal, a file name of information indicated in the input parameter, a file address indicating a file storage location, And a parameter conversion function that converts each of the information when the movement information indicating the source and destination of the file is included ,
A script generation function for generating an information collection script indicating an acquisition procedure of the information for failure analysis based on the converted input parameter;
The computer executes the failure analysis information acquisition processing function for executing the generated information collection script and collecting the information for failure analysis , and
When the parameter conversion function is related to a log file in which the input parameter is being rotated, the converted input of the storage location of the log file based on a log rotation rule included in the system difference information Failure analysis information collection program characterized by including a log rotation check function included in parameters .

Images