JP2020177281A - Information management device and information management program - Google Patents

Abstract

To provide an information management device and an information management program which reduce labor for an estimate of a disk size used for storing a log.SOLUTION: A log information collection unit 11 collects configuration information, information on a collection setting, and a size of a storage area in which an operation history is stored of a management object device from which the operation history is acquired according to the collection setting. A support information collection unit 12 collects failure handling information representing a state of failure handling performed when failure occurs in the management object device. A recommended value determination unit 17 acquires configuration information on a new apparatus and calculates a recommended value of a storage capacity for storing an operation history of the new apparatus on the basis of the configuration information, the information on the collection setting, and the size of the storage area in which the operation history is stored collected by the log information collection unit 11 and the failure handling information collected by the support information collection unit 12. A notification unit 18 gives notification of the recommended value determined by the recommended value determination unit 17.SELECTED DRAWING: Figure 2

Description

The present invention relates to an information management device and an information management program.

In recent years, it is common to monitor and manage devices in an on-premises environment with management software. Many management software has a log management function as one of its functions. The log management function is a function that periodically collects logs of hardware and software of managed devices, saves and displays the collected logs, and provides logs as investigation materials in the event of a failure. The logs collected by the management software may be sent to the integrated management server that collectively manages the logs of each company via the Internet and accumulated.

Since the disk size used for storing the log of the management software differs depending on the type of managed device, the number of devices, the device configuration, the device setting, and the log collection setting, it is difficult to calculate an appropriate size. In general, the disk size used to store logs is often determined by the administrator. For example, the administrator determines the log collection settings such as the log collection cycle based on past experience based on the log size for each managed model described in the manual of the managed device or management software, and the determined log collection. Estimate the log storage disk size according to the settings.

Conventionally, there are roughly two types of methods for estimating the log storage disk size. One is to obtain a guideline for the log size by referring to the manuals of the managed devices and log management software, multiply the obtained guideline by the number of devices to calculate the total log size, and calculate the total log size. This is a method of estimating by adding the size of the buffer to.

The other method is to estimate the disk size used for log storage from past crisis management experience. This method is premised on sharing know-how regarding log storage. In this regard, know-how can be shared by searching past records or asking another manager of the same company within a large company such as a company with a large number of management units or a company with a large total number of managers. To.

As such a log storage technique, there is a conventional technique for automatically generating and presenting a log database setting change proposal based on log database data usage information. Further, there is a conventional technique for deciding a log to be stored among the logs output for each event based on a keyword when a failure occurs and storing operation history information used for failure analysis.

Japanese Unexamined Patent Publication No. 2014-106655 JP-A-2017-27169

However, the method of estimating the disk size used for log storage with reference to the manual may take time to check the log size for each managed device when there are many types of devices. Also, how much buffer is provided depends on experience. In some cases, the manual does not provide a guideline for log size. Furthermore, the size of the output log may change depending on the device configuration and the log collection settings such as the log collection interval and the number of generations to be retained. In addition, even if you try to obtain reference information from other users or the Internet, it may be difficult for a suitable user to find it, or it may be difficult to find information suitable for your environment from the Internet. For the above reasons, it is difficult to accurately estimate the log storage disk size using this method.

In addition, unlike large-scale companies, the method of estimating the log storage disk size based on past crisis management experience is sufficient for small and medium-sized companies to accumulate equipment management information because the number of administrators and the number of managed units are small. It is difficult to share know-how. Therefore, even if this method is used, it is difficult to accurately estimate the log storage disk size depending on the operating environment.

Further, although it is possible to improve the log collection method by using the conventional technique for automatically generating a setting change proposal based on the usage information, it is difficult to estimate an appropriate log size. Furthermore, even if a conventional technique for determining a log to be stored based on a keyword occurs when a failure occurs, it is difficult to estimate an appropriate log size in periodic log collection.

The technique of disclosure is made in view of the above, and an object of the present invention is to provide an information management device and an information management program that easily present appropriate recommended values for estimating a disk size for log storage. ..

In one aspect of the information management device and the information management program disclosed in the present application, the information collecting unit stores the configuration information of the managed device for which the operation history is acquired according to the collection setting, the information of the collection setting, and the operation history. Collect the size of the area. The failure response information collection unit collects failure response information indicating the status of the failure response implemented when a failure occurs in the managed device. The recommended value determination unit acquires the configuration information of the new device, and is collected by the configuration information collected by the information collection unit, the size of the storage area for storing the collection setting information and the operation history, and the failure response information collection unit. Based on the failure response information, the recommended value of the storage capacity for storing the operation history of the new device is calculated. The notification unit notifies the recommended value determined by the recommended value determination unit.

In one aspect, the present invention can readily provide appropriate recommendations for estimating log storage disk size.

FIG. 1 is a system configuration diagram showing an example of an information management system. FIG. 2 is a block diagram of the integrated management server. FIG. 3 is a diagram showing an example of a log information table. FIG. 4 is a diagram showing an example of a support information table. FIG. 5 is a diagram showing an example of a failure information table. FIG. 6 is a diagram showing an example of a collection setting information table. FIG. 7 is a sequence diagram of log collection processing during normal operation. FIG. 8 is a sequence diagram of information storage processing in the integrated management server during normal operation. FIG. 9 is a sequence diagram of information storage processing in the integrated management server when a failure occurs. FIG. 10 is a sequence diagram of the process of providing support information by the support department. FIG. 11 is a sequence diagram of determination of recommended settings and transmission processing by the integrated management server. FIG. 12 is a flowchart of information storage processing by the integrated management server. FIG. 13 is a flowchart of the support information collection process by the integrated management server. FIG. 14 is a flowchart of notification processing of recommended settings by the integrated management server according to the first embodiment. FIG. 15 is a flowchart of notification processing of recommended settings by the integrated management server according to the second embodiment. FIG. 16 is a hardware configuration diagram of the integrated management server.

Hereinafter, examples of the information management device and the information management program disclosed in the present application will be described in detail with reference to the drawings. The information management device and information management program disclosed in the present application are not limited by the following examples.

FIG. 1 is a system configuration diagram showing an example of an information management system. The information processing system 100 includes a plurality of companies 201 to 203, an integrated management server 1 arranged on a portal site, a support department terminal 30, and a user terminal 40.

Company 201 has a server group 211 and a server group 212. Then, the server group 211 is managed by the management software 221. The management software 221 collects the logs of the server group 211 periodically or when a failure occurs according to the log collection setting, and stores them in the storage device 231. Further, the server group 212 is managed by the management software 222. The management software 222 collects the log, which is the operation history of the server group 212, periodically or when a failure occurs according to the log collection setting, and stores it in the storage device 232. Then, the logs held in the storage devices 231 and 232 are sent to the integrated management server 1 via the Internet on a regular basis or when a failure occurs. Similarly, company 202 has a group of servers 213. The server group 213 is managed by the management software 223. The management software 223 collects the log of the server group 213 periodically or when a failure occurs according to the log collection setting and stores it in the storage device 233. Then, the log held in the storage device 233 is sent to the integrated management server 1 via the Internet at regular intervals or when a failure occurs. Company 203 has a server group 214. The server group 214 is managed by the management software 224. The management software 224 collects the log of the server group 214 periodically or when a failure occurs according to the log collection setting and stores it in the storage device 234. Then, the log held in the storage device 234 is sent to the integrated management server 1 via the Internet at regular intervals or when a failure occurs.

The support department terminal 30 is a computer owned by an organization to which a worker who solves a problem belongs when a failure occurs in the server groups 211 to 214. The support department terminal 30 is operated by the worker and transmits support information representing the contents of the work performed by the worker to the integrated management server 1.

The user terminal 40 is a computer operated by a user who intends to newly construct an information processing system or a user who intends to update the information processing system. The user inputs the configuration information of the information processing system for which the log storage disk size is to be determined by using the input screen displayed on the user terminal 40. This configuration information includes the hardware type, the installed OS, and the number of them. The user terminal 40 transmits the configuration information input by the user using the input screen to the integrated management server 1 together with a request for acquiring a recommended value of the log storage disk size. After that, the user terminal 40 receives the recommended value of the log storage disk size from the integrated management server 1. Then, the user terminal 40 notifies the user by displaying a recommended value of the log storage disk size on the display screen.

The integrated management server 1 has a database 10. The integrated management server 1 acquires the logs of the server groups 211 to 214 of each company 201 to 203 and holds them in the database 10. Further, the integrated management server 1 acquires support information from the support department terminal 30 owned by the support department and stores it in the database 10. Then, the integrated management server 1 acquires information for determining the log collection setting for each hardware type and installed OS (Operating System) by using the logs and support information of the server groups 211 to 214.

The integrated management server 1 acquires the configuration information of the information processing system input by the user who plans to newly introduce or update the information processing system using the user terminal 40 via the Internet. Then, the integrated management server 1 obtains recommended settings including information on the log collection interval, the number of generations, and the recommended value of the log storage disk size for each device from the input configuration information. Then, the integrated management server 1 transmits the requested recommended setting to the user terminal 40 via the Internet, and notifies the user who plans to newly introduce or update the information processing system. Therefore, the function of determining the recommended setting of the log collection setting and the notification function of the integrated management server 1 will be described in detail below.

FIG. 2 is a block diagram of the integrated management server. The integrated management server 1 includes a database 10, a log information collection unit 11, a support information collection unit 12, a log setting information calculation unit 13, a recording unit 14, a new configuration acquisition unit 15, a search processing unit 16, a recommended value determination unit 17, and a notification. It has a part 18.

Here, the individual management device 20 in FIG. 2 is a device in which the information processing devices operating in the management software 221 to 224 in FIG. 1 are represented without distinction. Hereinafter, each information processing device under the control of the individual management device 20 is referred to as a management target device 210. The individual management device 20 periodically transmits the logs collected in a predetermined log collection cycle to the integrated management server 1. Further, when a failure occurs, the individual management device 20 transmits a log at the time of failure to the integrated management server 1.

The log information collecting unit 11 periodically receives the monitoring data indicating the monitoring state, the configuration information indicating the system configuration of the managed device 210, and the log together with the identification information of the managed device 210 from the individual management device 20. Here, the identification information of the managed device 210 is information indicating which managed device 210 is located in any of the companies 201 to 203. This identification information is assigned according to, for example, the hardware type of the managed device 210 and the set of the installed OS.

The monitoring data includes the log collection setting and the collected log size for each managed device 210. The log collection settings include the log collection cycle and the number of generations in which the logs are saved. The number of generations refers to the maximum number of accumulated logs when one log collection is regarded as one generation. This collected log size corresponds to an example of "storage capacity for storing operation history".

In addition, the configuration information includes the hardware type, installed OS, number of units, and the like of each managed device 210. The number of managed devices 210 is, for example, the number of managed devices 210 having the same hardware type and installed OS among the managed devices 210 included in the server group 211 in the case of configuration information transmitted by the management software 221. is there.

Further, when a failure occurs in the managed device 210, the log information collecting unit 11 receives the configuration information and the log from the individual management device 20 together with the identification information of the managed device 210. In this case, the log information collecting unit 11 does not have to acquire the monitoring data representing the monitoring state.

Then, the log information collecting unit 11 associates the acquired log with the identification information and stores it in the database 10. Here, when the log information collection unit 11 holds logs exceeding the number of generations specified in the log collection setting at this time, the log information collection unit 11 may perform generation management for deleting the oldest log among the accumulated logs. ..

Further, the log information collecting unit 11 registers information such as acquired configuration information and monitoring data in the log information table 101 of the database 10. This log information collecting unit 11 corresponds to an example of the "information collecting unit".

FIG. 3 is a diagram showing an example of a log information table. In the log information table 101 according to this embodiment, as shown in FIG. 3, information is registered for each set of hardware type and installed OS. Then, in the log information table 101, a log flag, a log collection setting, a device configuration, and a log size are registered for each set of hardware type and installed OS.

The log flag in the log information table 101 is a flag for distinguishing whether it is a log at the time of normal collection or a log at the time of failure. Here, the initial value of the log flag is a value representing a normal value, and the log information collecting unit 11 sets a flag representing a failure in the case of log collection at the time of a failure. In addition, the log collection cycle and the number of generations in which the log is saved are registered in the log collection setting. In addition, the type of installed OS, the type of hardware, the number of units, and the like are registered in the device configuration.

The explanation will be continued by returning to FIG. The support information collection unit 12 required from the support department terminal 30 to identify the managed device 210 to be supported, as well as the "use log period" which is the log period used for investigating the cause in troubleshooting and the resolution of the failure. Receive input of support information including "time to resolve" which is the time. This support information is an example of "fault response information". Then, the support information collecting unit 12 registers the acquired support information in the support information table 102 of the database 10.

FIG. 4 is a diagram showing an example of a support information table. In the support information table 102 according to this embodiment, as shown in FIG. 4, the usage log period and the time until resolution are registered in correspondence with the identification information of the managed device 210 to be supported.

Next, the support information collecting unit 12 acquires the server type and the installed OS of the managed device 210 having the acquired identification information from the log information table 101. Next, the support information collecting unit 12 acquires the total number of managed devices 210 corresponding to the server type and the set of installed OS from the log information table 101. Next, the support information collecting unit 12 determines whether or not the managed device 210 corresponding to the server type and the set of installed OS is registered in the failure information table 103 shown in FIG. FIG. 5 is a diagram showing an example of a failure information table.

If the managed device 210 corresponding to the server type and the set of installed OS is registered in the failure information table 103, the support information collecting unit 12 indicates the number of failures of the managed device 210 as failure information shown in FIG. Obtained from Table 103. Then, the support information collecting unit 12 adds 1 to the acquired number of failures and divides the addition result by the total number of managed devices 210 corresponding to the server type and the set of installed OS to calculate the failure rate. After that, the support information collecting unit 12 registers and updates the failure rate in the failure information table 103.

If the managed device 210 corresponding to the server type and the set of installed OS is not registered in the failure information table 103, the support information collecting unit 12 uses the result of adding 1 to 0 as the number of failures so far. To calculate the failure rate. This support information collection unit 12 corresponds to an example of the “fault response information collection unit”.

The explanation will be continued by returning to FIG. The log setting information calculation unit 13 acquires the identification information of each supported device 210 registered in the support information table 102. Then, the log setting information calculation unit 13 acquires the server type and the installed OS of the management target device 210 having the acquired identification information from the log information table 101. Then, the log setting information calculation unit 13 outputs the information of the server type and the installed OS of the managed device 210 to be supported to the recording unit 14.

Further, the log setting information calculation unit 13 stores each time range in which the time is divided into predetermined divisions as a time range until resolution in advance. For example, the time range for resolution is divided into 3 hours, 6 hours, 12 hours, 1 day, 3 days, 1 week, and the like. The log setting information calculation unit 13 acquires the time until resolution from the support information table 102 for each managed device 210 to be supported. Then, the log setting information calculation unit 13 specifies which time range the acquired time until the resolution corresponds to. After that, the log setting information calculation unit 13 outputs the specified time range to the recording unit 14.

Further, the log setting information calculation unit 13 acquires the usage log period from the support information table 102. Further, the log setting information calculation unit 13 acquires the log collection setting from the log information table 101. Then, the log setting information calculation unit 13 calculates the generation that covers the acquired usage log period. For example, if the usage log period is 7 days worth of logs and the cycle is twice a day, it is calculated that the generation used for investigating the cause is 14 generations. After that, the log setting information calculation unit 13 outputs the cycle acquired from the log information table 101 and the calculated number of generations to the recording unit 14 as the log collection setting.

The recording unit 14 registers the hardware type and the installed OS for each managed device 210 input from the log setting information calculation unit 13, and creates the collection setting information table 104 shown in FIG. FIG. 6 is a diagram showing an example of a collection setting information table. The recording unit 14 registers the time range until the resolution of the managed device 210 to be supported, which is input from the log setting information calculation unit 13, in the created collection setting information table 104. Further, the recording unit 14 registers the cycle and the number of generations input from the log setting information calculation unit 13 in the collection setting information table 104.

The new configuration acquisition unit 15 receives input of configuration information of the information processing system to be newly introduced or updated from the user terminal 40. Here, the configuration information includes the hardware type, the installed OS, and the number of units. Further, when there is a search condition, the new configuration acquisition unit 15 also receives the input of the search condition from the user terminal 40. The search condition is, for example, an allowable time until resolution. Here, if the search condition is not input, the condition that takes the shortest time to resolve is determined as the specified search condition. Then, the new configuration acquisition unit 15 outputs the acquired configuration information and search conditions to the search processing unit 16.

The search processing unit 16 receives input of search conditions and configuration information from the new configuration acquisition unit 15. Then, the search processing unit 16 acquires the hardware type, the installed OS, and the number of units from the acquired configuration information. Next, the search processing unit 16 acquires the failure rate of the designated hardware type and the set of installed OS from the failure information table 103. Then, the search processing unit 16 outputs the acquired failure rate to the recommended value determination unit 17.

In addition, the search processing unit 16 extracts entries in the log information table 101 having a device configuration corresponding to the specified hardware type and set of installed OS. Then, the search processing unit 16 acquires the log size at the time of normal and at the time of failure in the specified entry. After that, the search processing unit 16 outputs the log size at the time of normal and at the time of failure to the recommended value determination unit 17. Here, when a plurality of entries are extracted, the search processing unit 16 outputs all the acquired log sizes to the recommended value determination unit 17.

Further, the search processing unit 16 confirms the search conditions. When the search condition has the shortest time to resolve, the search processing unit 16 executes the following processing. The search processing unit 16 acquires the log collection setting from the collection setting information table 104, which is the set of the specified hardware type and the installed OS and has the shortest time range until the resolution. Here, when there are a plurality of log collection settings that have the shortest time range until resolution, the search processing unit 16 acquires the most log collection settings among them. In this case, the search processing unit 16 may use a standard deviation or the like to remove the log collection setting in a peculiar case. After that, the search processing unit 16 outputs the acquired log collection setting to the recommended value determination unit 17.

On the other hand, when the search condition includes a plurality of time ranges, the search processing unit 16 executes the following processing. The search processing unit 16 selects one time range from the designated time range. Then, the search processing unit 16 acquires the log collection setting from the collection setting information table 104, which is a set of the specified hardware type and the installed OS and the time until the resolution falls within the selected time range. Here, when there are a plurality of log collection settings that fall within the specified time range, the search processing unit 16 acquires the most log collection settings among them. In this case, the search processing unit 16 may use a standard deviation or the like to remove the log collection setting in a peculiar case. The search processing unit 16 acquires the log collection setting for all of the designated time range. After that, the search processing unit 16 outputs the acquired log collection setting to the recommended value determination unit 17.

The recommended value determination unit 17 receives input from the search processing unit 16 of the specified hardware type, the failure rate of the set of installed OS, the log size at the time of normal and failure, and the information of the log collection setting. Here, when there are a plurality of log sizes in both the normal time and the failure time, the recommended value determination unit 17 obtains the average log size for each of the normal time and the failure time, and obtains the obtained value for the normal time and the failure time log. The size. Next, the recommended value determination unit 17 determines whether or not the acquired failure rate is equal to or higher than a predetermined reference value. Further, the recommended value determination unit 17 acquires the number of managed devices 210 corresponding to the designated hardware type and the set of installed OS from the search processing unit 16.

When the failure rate is equal to or less than the reference value, the recommended value determination unit 17 calculates the log storage disk size per unit by multiplying the multiplication result by multiplying the period by the number of generations by the normal log size. Further, the recommended value determination unit 17 multiplies the log storage disk size per unit by the number of units, and the recommended value of the log storage disk size corresponding to the selected hardware type and the set of installed OS in the specified configuration. Is calculated. Then, the recommended value determination unit 17 holds the information of the log collection setting according to the recommended value of the obtained log storage disk size.

Here, when a plurality of time ranges are specified, the recommended value of the log storage disk size for the number of time ranges is calculated. In that case, the recommended value determination unit 17 selects the recommended value of the minimum log storage disk size. Then, the recommended value determination unit 17 holds a guideline for the time until the problem is solved, in addition to the information of the log collection setting according to the recommended value of the obtained log storage disk size.

On the other hand, when the failure rate is equal to or less than the reference value, the recommended value determination unit 17 multiplies the multiplication result by multiplying the period by the number of generations by the normal log size, and adds the failure log size to the multiplication result to 1 Calculate the log storage disk size per unit. Further, the recommended value determination unit 17 multiplies the log storage disk size per unit by the number of units to determine the recommended value of the log storage disk size corresponding to the hardware type and the set of installed OS in the specified configuration. calculate. Then, the recommended value determination unit 17 holds the information of the log collection setting according to the recommended value of the obtained log storage disk size.

In this case as well, if a plurality of time ranges are specified, the recommended value of the log storage disk size for the number of time ranges is calculated. In that case, the recommended value determination unit 17 selects the recommended value of the minimum log storage disk size. Then, the recommended value determination unit 17 holds a guideline for the time until the problem is solved, in addition to the information of the log collection setting according to the recommended value of the obtained log storage disk size.

The recommended value determination unit 17 calculates the recommended value of the log storage disk size for all the hardware types and the sets of installed OS included in the configuration information input from the user terminal 40. After that, the recommended value determination unit 17 outputs the recommended setting including the recommended value of the log storage disk size for each set of the hardware type and the installed OS and the information of the log collection setting to the notification unit 18. In addition, when there are a plurality of specified time ranges, the recommended value determination unit 17 includes the guideline of the time until the problem is solved for each set of the hardware type and the installed OS in the recommended setting, and sends the recommended value determination unit 17. Output. The recommended value of the log storage disk size calculated by the recommended value determination unit 17 corresponds to an example of the "recommended value of the storage capacity for storing the operation history".

The notification unit 18 receives input from the recommended value determination unit 17 of the recommended setting including the recommended value of the log storage disk size and the information of the log collection setting for each set of the hardware type and the installed OS. Then, the notification unit 18 transmits the recommended setting including the recommended value of the log storage disk size and the log collection setting for each set of the hardware type and the installed OS to the user terminal 40, and the information specified by the user. Notify the user of the recommended settings of the processing system.

When there are a plurality of designated time ranges, the notification unit 18 receives input from the recommended value determination unit 17 including a guideline for the time until the problem is solved for each set of the hardware type and the installed OS. In this case, the notification unit 18 sends the recommended setting including the recommended value of the log storage disk size and the log collection setting as well as the guideline of the time until the problem is solved to the user terminal 40 to notify the user.

Next, the flow of processing from log collection at the time of normal and failure to notification of the recommended value of the log storage disk size will be described. First, the flow of log collection in the normal state will be described with reference to FIG. 7. FIG. 7 is a sequence diagram of log collection processing during normal operation.

In the individual management device 20, any of the management software 221 to 224 is set up (step S101). Next, the management target device 210 is registered with respect to the individual management device 20 in which the management software is set up (step S102). For example, in FIG. 1, the management target device 210 of the management software 221 is each server included in the server group 211.

Next, the individual management device 20 implements the monitoring setting for the registered managed device 210 including the log collection setting (step S103).

After that, the individual management device 20 executes the monitoring process according to the monitoring settings (step S104). Here, the monitoring process will be described in detail.

The individual management device 20 collects log collection settings, monitoring data including the collected log size for each managed device 210, information on the hardware type and installed OS of each managed device 210, and configuration information including the number of units. (Step S141). The management target device 210 provides the monitoring data and the configuration information to the individual management device 20 in response to the collection process of the configuration information of the individual management device 20 (step S105). The individual management device 20 accumulates monitoring data and configuration information (step S142).

Further, the individual management device 20 collects logs for each managed device 210 (step S143). The management target device 210 provides the log for each management target device 210 to the individual management device 20 in response to the log collection process of the individual management device 20 (step S106). After that, the individual management device 20 accumulates the log for each managed device 210 (step S144).

After that, the individual management device 20 performs a generation management process of discarding the oldest generation log and holding the latest log when the number of generations has reached the upper limit (step S145).

Next, with reference to FIG. 8, the flow of information storage processing in the integrated management server 1 at the normal time will be described. FIG. 8 is a sequence diagram of information storage processing in the integrated management server during normal operation.

The individual management device 20 confirms the accumulated monitoring data and the log (step S201).

Next, the individual management device 20 extracts untransmitted information from the accumulated monitoring data and the log (step S202).

Next, the individual management device 20 generates normal monitoring information including configuration information, monitoring data, and logs (step S203).

Next, the individual management device 20 transmits the normal monitoring information to the integrated management server 1 (step S204). The integrated management server 1 normally receives the monitoring information from the individual management device 20 (step S205).

After that, the integrated management server 1 generates a reception response of the normal monitoring information and transmits it to the individual management device 20 (step S206). The individual management device 20 receives the reception response from the integrated management server 1 (step S207).

Next, the integrated management server 1 acquires the log size for each monitored device from the normal monitoring information (step S208).

After that, the integrated management server 1 registers and saves the log collection setting, the device configuration, and the log size in the log information table 101 of the database 10 in association with the identification information of the managed device 210 (step S209).

Next, with reference to FIG. 9, the flow of information storage processing in the integrated management server 1 when a failure occurs will be described. FIG. 9 is a sequence diagram of information storage processing in the integrated management server when a failure occurs.

A failure occurs in the managed device 210 (step S301).

The management target device 210 notifies the individual management device 20 of the occurrence of a failure (step S302). The individual management device 20 receives the notification of the occurrence of the failure from the managed device 210 (step S303).

Upon receiving the notification of the occurrence of the failure, the individual management device 20 detects the occurrence of the failure in the managed device 210 (step S304).

Next, the individual management device 20 collects the configuration information and the log (step S305). The management target device 210 receives the transmission request from the individual management device 20 and provides the configuration information and the log to the individual management device 20 (step S306).

Then, the individual management device 20 saves the configuration information and the log received from the management target device 210 (step S307).

Next, the individual management device 20 acquires monitoring data including the log collection setting and the log size that have already been acquired at normal times (step S308).

Next, the individual management device 20 generates failure information including configuration information, monitoring data, and a log (step S309).

Next, the individual management device 20 transmits the failure information to the integrated management server 1 (step S310). The integrated management server 1 receives the failure information from the individual management device 20 (step S311).

After that, the integrated management server 1 generates a reception completion response of the failure information and transmits it to the individual management device 20 (step S312). The individual management device 20 receives the reception completion response from the integrated management server 1 (step S313).

Next, the integrated management server 1 acquires the log size from the received failure information (step S314).

After that, the integrated management server 1 sets the log flag as a failure in association with the identification information of the managed device 210, and registers and saves the log collection setting, the device configuration, and the log size in the log information table 101 of the database 10. (Step S315).

Next, the integrated management server 1 notifies the support department terminal 30 of the support department 300 of the failure notification of the managed device 210 (step S316). Here, the support department 300 is an organization in which the support department terminal 30 is arranged, and the actual operation is mainly performed by a worker belonging to the support department terminal 30 or the support department 300. The support department terminal 30 of the support department 300 receives the failure notification and receives the support request (step S317).

After that, the support department terminal 30 of the support department 300 generates a failure notification reception completion response and transmits it to the integrated management server 1 (step S318). The integrated management server 1 receives the reception completion response from the support department terminal 30 of the support department 300 (step S319).

After that, the worker of the support department 300 performs the support work for the managed device 210 in which the failure has occurred according to the support request (step S320).

Next, the flow of providing support information by the support department 300 will be described with reference to FIG. FIG. 10 is a sequence diagram of the process of providing support information by the support department.

The worker of the support department 300 collects the survey data for the integrated management server 1 using the support department terminal 30 (step S401). In response to the request from the support department terminal 30, the integrated management server 1 transmits the log and configuration information of the managed device 210 in which the failure has occurred to the support department terminal 30 of the support department 300 (step S402).

The worker of the support department 300 investigates the failure by using the log and the configuration information of the managed device 210 in which the failure has occurred (step S403).

In the investigation, the worker of the support department 300 determines whether or not the log is insufficient (step S404). If the cause can be investigated from the acquired log (step S404: negation), the process proceeds to step S411.

On the other hand, when the acquired log is insufficient for investigating the cause (step S404: affirmative), the worker of the support department 300 uses the support department terminal 30 to use the log before the acquired log. The managed device 210 is requested to reacquire the log in order to acquire the log (step S405).

The managed device 210 receives the request for reacquisition of the log from the support department terminal 30 (step S406).

Next, the managed device 210 reacquires the log before the log already held by the worker in the support department 300 (step S407).

Next, the managed device 210 provides the reacquired log to the support department terminal 30 of the support department 300 (step S408). The support department terminal 30 of the support department 300 receives the re-acquired log before the acquired log from the managed device 210 (step S409).

Then, the worker of the support department 300 re-investigates the failure that occurred in the managed device 210 by using the log before the acquired log in addition to the acquired log (step S410).

After that, the worker of the support department 300 determines the cause of the failure (step S411).

Next, the worker of the support department 300 carries out the work of dealing with the failure according to the found cause (step S412). As a result, the managed device 210 in which the failure has occurred is repaired and the failure is resolved. After that, the worker of the support department 300 completes the work of dealing with the failure (step S413).

After that, the worker of the support department 300 inputs the support information to the integrated management server 1 using the support department terminal 30 (step S414). The integrated management server 1 receives the support information from the support department terminal 30 of the support department 300 (step S415).

After that, the integrated management server 1 calculates the number of log generations used in the survey (step S416).

Then, the integrated management server 1 displays the collection setting information table 104 in which the time until resolution, the cycle, and the calculated number of generations are registered in association with the hardware type and the installed OS of the managed device 210 to be supported. Create (step S417).

Next, with reference to FIG. 11, the flow of determination of recommended settings and transmission processing by the integrated management server 1 will be described. FIG. 11 is a sequence diagram of determination of recommended settings and transmission processing by the integrated management server. Here, the case where the condition with the shortest resolution time, which is the specified condition, is set as the search condition will be described.

The user inputs information on the device configuration of the information processing system to be newly introduced or updated using the user terminal 40 to the integrated management server 1 (step S501). The integrated management server 1 receives the device configuration information (step S502).

Next, the integrated management server 1 acquires the log collection setting when the time range until resolution is the shortest for each hardware type and the combination of the installed OS from the collection setting information table 104 (step S503).

Next, the integrated management server 1 calculates the log storage disk size for each hardware type and combination of installed OSs using the acquired log collection settings and the normal log size (step S504).

Next, the integrated management server 1 acquires the failure rate for each hardware type and combination of installed OSs from the failure information table 103 (step S505).

Next, the integrated management server 1 acquires the log size at the time of failure from the log information table 101 for the combination whose failure rate is equal to or higher than the reference value (step S506).

Next, the integrated management server 1 determines the log size at the time of failure as the log increment for the combination having the failure rate equal to or higher than the reference value, and the log increment as 0 for the combination having the failure rate less than the reference value (step S507). ..

Next, the integrated management server 1 adds the log increment to the log storage disk size for each hardware type and set of installed OS (step S508). Then, the integrated management server 1 sets the log storage disk size at this point as a recommended value for each hardware type and combination of installed OSs.

After that, the integrated management server 1 transmits the recommended settings including the recommended value of the log storage disk size and the log collection setting to the user terminal 40 for each hardware type and the set of the installed OS (step S509).

The user terminal 40 receives the recommended value of the log storage disk size and the recommended setting including the log collection setting from the integrated management server 1 (step S510). The user confirms the recommended value of the log storage disk size provided by the integrated management server 1 and the recommended settings including the log collection setting by using the user terminal 40, and sets the disk size for log storage in the information processing system. decide.

Further, details of each process by the integrated management server 1 will be described. First, with reference to FIG. 12, the details of the information storage process by the integrated management server 1 will be described. FIG. 12 is a flowchart of information storage processing by the integrated management server.

The log information collecting unit 11 receives various information from the individual management device 20 together with the identification information of the management target device 210 at regular intervals and when a failure occurs (step S601).

Next, the log information collecting unit 11 searches the log information table 101 using the identification information, and determines whether or not it is the managed device 210 registered in the database 10 (step S602).

In the case of the registered managed device 210 (step S602: affirmative), the log information collecting unit 11 determines whether or not the acquired information is information at the time of failure (step S603). If the acquired information is normal information (step S603: negative), the log information collecting unit 11 proceeds to step S605.

On the other hand, when the acquired information is information at the time of failure (step S603: affirmative), the log information collecting unit 11 sets a flag indicating the failure as the log flag of the log information table 101 (step S604).

Next, the log information collecting unit 11 determines whether or not the configuration information has been updated (step S605). When there is an update in the configuration information (step S605: affirmative), the log information collection unit 11 updates the device configuration, log collection setting, and log size information in the log information table 101 (step S606).

On the other hand, when the configuration information is not updated (step S605: negative), the log information collecting unit 11 updates the log collection setting and log size information in the log information table 101 (step S607).

On the other hand, in the case of the unregistered managed device 210 (step S602: negative), the log information collecting unit 11 newly registers the managed device 210 in the log information table 101 (step S608).

Next, the log information collecting unit 11 determines whether or not the acquired information is information at the time of failure (step S609). If the acquired information is normal information (step S609: negative), the log information collecting unit 11 proceeds to step S611.

On the other hand, when the acquired information is information at the time of failure (step S609: affirmative), the log information collecting unit 11 sets a flag indicating the failure as the log flag of the log information table 101 (step S610).

After that, the log information collection unit 11 registers the device configuration, the log collection setting, and the log size information in correspondence with the newly registered identification information of the managed device 210 in the log information table 101 (step S611).

Next, the flow of collecting support information by the integrated management server 1 will be described with reference to FIG. FIG. 13 is a flowchart of the support information collection process by the integrated management server.

The support information collecting unit 12 receives the support information input from the support department terminal 30 (step S621). This support information includes user information representing a company name and device information representing a managed device 210.

Next, the support information collecting unit 12 searches for the company name included in the identification information of the log information table 101, and determines whether or not the user information specified in the support information exists in the database 10 (step). S622). If there is no user information in the database 10 (step S622: denial), the support information collection unit 12 records the absence of the corresponding user information in the database 10 (step S623), and ends the support information collection process.

On the other hand, when there is user information in the database 10 (step S622: affirmative), the support information collecting unit 12 performs the following processing. The support information collecting unit 12 searches the server information in the identification information of the log information table 101, and determines whether or not the supported device is registered or exists in the database 10 (step S624). If the device to be supported is not registered in the database 10 (step S624: negative), the support information collection unit 12 records the absence of the device in the database 10 (step S625), and ends the support information collection process.

On the other hand, when the supported device is registered in the database 10 (step S624: affirmative), the support information collecting unit 12 continues until the usage log period and the solution used for investigating the cause of the supported managed device 210. The time of is registered in the support information table 102. The log setting information calculation unit 13 acquires the same managed device 210 as the hardware type of the supported managed device 210 and the installed OS from the log information table 101. Further, the log setting information calculation unit 13 acquires the hardware type of the managed device 210 to be supported and the number of failures of the managed device 210 which is the same as the installed OS from the failure information table 103 (step S626).

Next, the log setting information calculation unit 13 calculates the failure rate of the managed device 210 which is the same as the hardware type and the installed OS of the managed device 210 to be supported, and calculates the calculated failure rate and the number of failures in the failure information table 103. The database 10 is updated by registering in (step S627).

Next, the log setting information calculation unit 13 acquires the log setting information of the managed device 210 to be supported from the log information table 101 (step S628).

Next, the log setting information calculation unit 13 specifies the time range of the time until resolution (step S629).

Further, the log setting information calculation unit 13 acquires the usage log period from the support information table 102. Then, the log setting information calculation unit 13 calculates the number of log generations used to solve the problem by using the usage log period and the log collection cycle (step S630).

After that, the log setting information calculation unit 13 outputs the time range of the time until resolution, the log collection cycle, and the number of generations to the recording unit 14, together with the hardware type and the installed OS of the managed device 210 to be supported. The recording unit 14 registers the time range of the time until resolution, the log collection cycle, and the number of generations in the collection setting information table 104 according to the hardware type and the installed OS input from the log setting information calculation unit 13. (Step S631).

Next, with reference to FIG. 14, a flow of notification processing of recommended settings by the integrated management server 1 according to this embodiment will be described. FIG. 14 is a flowchart of notification processing of recommended settings by the integrated management server according to the first embodiment.

The new configuration acquisition unit 15 receives the acquisition request of the recommended setting including the search condition if there is the configuration information and the search condition of the information processing system to be introduced (step S701). Then, the new configuration acquisition unit 15 outputs the acquisition request of the recommended setting to the search processing unit 16.

The search processing unit 16 receives an input of an acquisition request for recommended settings from the new configuration acquisition unit 15. Then, the search processing unit 16 determines whether or not there is a search condition specified in the acquisition request of the recommended setting (step S702). If there is a search condition (step S702: affirmative), the search processing unit 16 proceeds to step S704.

When there is no search condition (step S702: negative), the search processing unit 16 sets a specified condition as a search condition (step S703). The specified condition is, for example, a condition such as the shortest resolution time.

Next, the search processing unit 16 selects one from the set of the hardware type and the installed OS specified in the configuration information (step S704). In the following, the search processing unit 16 performs processing on the selected hardware type and set of installed OS.

The search processing unit 16 determines whether or not the time range specified in the search condition is one (step S705).

When there is one time range (step S705: affirmative), the search processing unit 16 searches the collection setting information table 104 and acquires the maximum number of log collection cycles and the number of log generations in the specified time range (step S706). ).

Next, the search processing unit 16 extracts the managed device 210 whose configuration information is the selected hardware type and the set of the installed OS from the log information table 101, and determines the normal log size of the extracted managed device 210. Obtained from log information table 101. After that, the search processing unit 16 calculates the average log size of the acquired log size. Further, the search processing unit 16 acquires the log size at the time of failure of the selected hardware type and the set of installed OS, and calculates the average log size at the time of failure (step S707). Further, the search processing unit 16 acquires the failure rate of the selected hardware type and the set of the installed OS from the failure information table 103. After that, the search processing unit 16 outputs to the recommended value determination unit 17 the average log size at the time of normal and failure, the failure rate, and the number of units included in the new information system of the selected hardware type and the set of installed OS. To do.

The recommended value determination unit 17 receives input from the search processing unit 16 of the average log size, the failure rate, and the number of units at the time of normal and failure. Next, the recommended value determining unit 17 determines whether or not the failure rate is equal to or higher than the reference value (step S708).

When the failure rate is equal to or higher than the reference value (step 708: affirmative), the recommended value determining unit 17 acquires the log size at the time of failure as a log increment (step S709). On the other hand, when the failure rate is less than the reference value (step S708: negative), the recommended value determination unit 17 sets the log increment to 0 (step S710).

After that, the recommended value determining unit 17 calculates the recommended value of the log storage disk size by adding the log increment to the average log size and multiplying the addition result by the number of units (step S711). After that, the recommended value determination unit 17 proceeds to step S721.

On the other hand, when a plurality of time ranges are specified (step S705: negative), the search processing unit 16 selects one time range (step S712).

Next, the search processing unit 16 searches the collection setting information table 104 and acquires the maximum number of log collection cycles and the number of log generations in the selected time range (step S713).

Next, the search processing unit 16 extracts the managed device 210 whose configuration information is the selected hardware type and the set of the installed OS from the log information table 101, and determines the normal log size of the extracted managed device 210. Obtained from log information table 101. After that, the search processing unit 16 calculates the average log size of the acquired log size. Further, the search processing unit 16 acquires the log size at the time of failure of the selected hardware type and the set of installed OS, and calculates the average log size at the time of failure (step S714). Further, the search processing unit 16 acquires the failure rate of the selected hardware type and the set of the installed OS from the failure information table 103. After that, the search processing unit 16 outputs to the recommended value determination unit 17 the average log size at the time of normal and failure, the failure rate, and the number of units included in the new information system of the selected hardware type and the set of installed OS. To do.

The recommended value determination unit 17 receives input from the search processing unit 16 of the average log size, the failure rate, and the number of units at the time of normal and failure. Next, the recommended value determining unit 17 determines whether or not the failure rate is equal to or higher than the reference value (step S715).

When the failure rate is equal to or higher than the reference value (step 715: affirmative), the recommended value determining unit 17 acquires the log size at the time of failure as a log increment (step S716). On the other hand, when the failure rate is less than the reference value (step S715: negative), the recommended value determining unit 17 sets the log increment to 0 (step S717).

After that, the recommended value determination unit 17 calculates the log storage disk size used for solving in the selected time range by adding the log increment to the average log size and multiplying the addition result by the number of units. (Step S718).

Next, the recommended value determination unit 17 determines whether or not the calculation of the log storage disk size has been completed for all the designated time ranges (step S719). If there is a time range in which the log storage disk size has not been calculated (step S719: negation), the process returns to step S712.

On the other hand, when the calculation of the log storage disk size is completed for all the specified time ranges (step S719: affirmative), the recommended value determination unit 17 compares the log storage disk sizes in each time range. .. Then, the recommended value determination unit 17 acquires the log collection cycle, the number of generations, and the time until resolution in the time range in which the log storage disk size is minimized (step S720). After that, the recommended value determination unit 17 proceeds to step S721.

The recommended value determination unit 17 determines whether or not the calculation of the recommended value of the log storage disk size has been completed for all the hardware types and the sets of the installed OS (step S721). If there is a set of hardware type and installed OS for which the recommended value of the log storage disk size has not been calculated (step S721: negative), the process returns to step S704.

On the other hand, when the calculation of the recommended value of the log storage disk size is completed for all the hardware types and the set of the installed OS (step S721: affirmative), the recommended value determination unit 17 notifies the recommended setting. Output to 18. The recommended settings include the recommended value of the log storage disk, the log collection cycle, the number of generations, and the time to resolve. The notification unit 18 transmits the recommended setting acquired from the recommended value determination unit 17 to the user terminal 40 and notifies the user (step S722).

As described above, the integrated management server according to this embodiment acquires log collection settings and configuration information from individual users such as companies. In addition, the integrated management server acquires information on the support provided for the managed device from the support department. Then, the integrated management server saves the log in consideration of the failure rate by using the log collection setting and configuration information of the existing managed device and the support information according to the configuration information specified in the acquisition request of the recommended setting. Calculate the disk size for use and notify the user. As a result, it is possible to provide the user with a recommended value of the log storage disk size according to the environment, and it is possible to reduce the labor of estimating the disk size used for log storage at the time of new construction and environment update. .. In addition, it is possible to provide a mechanism for sharing know-how for estimating the disk size for log storage even for users of small and medium-sized enterprises who have difficulty sharing know-how. Furthermore, by constructing an information processing system using this recommended value, it is possible to accumulate logs for a period considered to be sufficient to solve the failure. Therefore, since the log for investigation has been overwritten when a failure occurs, it is possible to save the trouble of acquiring the log at the time of reproduction, and it is possible to shorten the time until the failure is resolved.

Next, Example 2 will be described. The integrated management server 1 according to this embodiment is also represented by the block diagram of FIG. The integrated management server 1 according to this embodiment is different from the first embodiment in that it notifies the user of the recommended settings in a ranking format in descending order of the number of actual results among the recommended settings that satisfy the time until resolution. Therefore, the determination of the recommended setting and the notification processing by the integrated management server 1 will be mainly described. In the following description, description of the operation of each part similar to that of the first embodiment will be omitted.

In this embodiment, the new configuration acquisition unit 15 of the integrated management server 1 acquires the number of rankings, which is the number of recommended settings to be displayed in the ranking format, from the user terminal 40 as a search condition. Then, the new configuration acquisition unit 15 outputs the search condition and the configuration information including the number of rankings to the search processing unit 16.

The search processing unit 16 receives input of search conditions and configuration information including the number of rankings from the new configuration acquisition unit 15. Next, the search processing unit 16 determines whether or not a time range until resolution is specified.

If the time range is not specified, the search processing unit 16 selects one from the set of the hardware type and the installed OS included in the specified configuration information. Then, the search processing unit 16 sets the number of ranking logs in descending order of the number of log collection settings of the managed device 210 having the hardware type and the set of installed OS selected from the log information table 101. To get.

Next, the search processing unit 16 acquires the log sizes of the managed device 210 having the acquired log collection settings during normal times and failures from the log information table 101, and calculates the average log sizes during normal times and failures. To do. Further, the search processing unit 16 acquires the failure rate of the selected hardware type and the set of the installed OS from the failure information table 103. Then, the search processing unit 16 recommends the log collection setting for each ranking, the log size at the time of normal and failure, the failure rate, the selected hardware type included in the designated information processing system, and the number of sets of installed OS. Output to the value determination unit 17.

On the other hand, when the time range is specified, the search processing unit 16 selects one from the set of the hardware type and the installed OS included in the specified configuration information. Next, the search processing unit 16 determines whether or not there is only one time range designation.

When one time range is specified, the search processing unit 16 is within the specified time range of the log collection settings of the managed device 210 having the hardware type and the set of installed OS selected from the log information table 101. Acquire the log collection setting of the ranking number in descending order of the number set in.

Next, the search processing unit 16 acquires the log size of the managed device 210 having each acquired log collection setting at the time of normal operation and at the time of failure from the log information table 101. Further, the search processing unit 16 acquires the failure rate of the selected hardware type and the set of the installed OS from the failure information table 103. Then, the search processing unit 16 manages the log collection setting for each ranking, the log size at the time of normal and failure, the failure rate, the selected hardware type included in the designated information processing system, and the set of installed OS. The number of target devices 210 is output to the recommended value determination unit 17.

When a plurality of time ranges are specified, the search processing unit 16 sets the log collection settings of the managed device 210 corresponding to the selected hardware type and the set of the installed OS in the specified plurality of time ranges. Acquire the log collection setting of the ranking number in descending order of the number set in.

Next, the search processing unit 16 acquires the log size of the managed device 210 having each acquired log collection setting at the time of normal operation and at the time of failure from the log information table 101. Further, the search processing unit 16 acquires the failure rate of the selected hardware type and the set of the installed OS from the failure information table 103. Then, the search processing unit 16 outputs the log collection setting for each ranking, the log size at the time of normal and failure, the failure rate, and the number of units to the recommended value determination unit 17.

The recommended value determination unit 17 receives input from the search processing unit 16 of the log collection setting for each ranking, the log size at the time of normal and failure, the failure rate, and the number of units. Then, the recommended value determination unit 17 calculates the average log size of the log size at the time of normal operation and at the time of failure.

Then, if the failure rate is less than the reference value, the recommended value determining unit 17 calculates the recommended value of the log storage disk by multiplying the average log size at the normal time by the number of units. If the failure rate is equal to or higher than the reference value, the recommended value determination unit 17 adds the average log size at the time of failure to the average log size at normal time, and multiplies the addition result by the number of units to save the log. Calculate the recommended value. Then, the recommended value determination unit 17 calculates the recommended value of the log storage disk size for each ranking of all hardware types and sets of installed OSs. After that, the recommended value determination unit 17 outputs the recommended value of the log storage disk size and the log collection setting for each ranking to the notification unit 18.

After that, the recommended value determination unit 17 outputs the recommended value of the log storage disk size and the recommended setting including the log collection setting for each ranking to the notification unit 18.

The notification unit 18 receives the input of the recommended setting from the recommended value determination unit 17. Then, the notification unit 18 assigns a ranking and transmits the recommended setting to the user terminal 40 to notify the user.

Next, with reference to FIG. 15, a flow of notification processing of recommended settings by the integrated management server 1 according to this embodiment will be described. FIG. 15 is a flowchart of notification processing of recommended settings by the integrated management server according to the second embodiment.

The new configuration acquisition unit 15 receives the configuration information of the information processing system to be introduced and the acquisition request of the recommended setting including the search condition if there is a search condition (step S801). Then, the new configuration acquisition unit 15 outputs the acquisition request of the recommended setting to the search processing unit 16.

The search processing unit 16 receives an input of an acquisition request for recommended settings from the new configuration acquisition unit 15. Then, the search processing unit 16 determines whether or not there is a search condition specified in the acquisition request of the recommended setting (step S802). If there is a search condition (step S802: affirmative), the search processing unit 16 proceeds to step S804.

When there is no search condition (step S802: negative), the search processing unit 16 sets a specified condition as a search condition (step S803). The specified condition is, for example, a condition such as the shortest resolution time.

Next, the search processing unit 16 determines whether or not the search condition specifies a time range until resolution (step S804).

When the time range is not specified (step S804: affirmative), the search processing unit 16 selects one from the set of the hardware type and the installed OS included in the specified configuration information (step S805).

Next, the search processing unit 16 collects the ranking number of logs in descending order of the set number of the log collection settings of the managed device 210 having the hardware type and the set of the installed OS selected from the log information table 101. Acquire the setting (step S806). Next, the search processing unit 16 acquires the log size of the managed device 210 having each acquired log collection setting at the time of normal operation and at the time of failure from the log information table 101. Further, the search processing unit 16 acquires the failure rate corresponding to the selected hardware type and the set of the installed OS from the failure information table 103. Then, the search processing unit 16 transmits the log collection setting, the log size at the time of normal and failure, the failure rate, and the number of units to the recommended value determination unit 17.

The recommended value determination unit 17 receives input from the search processing unit 16 of the log collection setting, the log size at the time of normal and failure, the failure rate, and the number of units. Then, the recommended value determination unit 17 calculates the average log size at the time of normal operation and at the time of failure (step S807).

Next, the recommended value determining unit 17 determines whether or not the failure rate is equal to or higher than the reference value (step S808).

When the failure rate is equal to or higher than the reference value (step 808: affirmative), the recommended value determining unit 17 acquires the log size at the time of failure as a log increment (step S809). On the other hand, when the failure rate is less than the reference value (step S808: negative), the recommended value determination unit 17 sets the log increment to 0 (step S810).

After that, the recommended value determining unit 17 calculates the recommended value of the log storage disk size for each ranking order by adding the log increment to the average log size and multiplying the addition result by the number of units (step S811).

The recommended value determination unit 17 determines whether or not the calculation of the recommended values of the log storage disk sizes of all ranks has been completed (step S812). If there is an uncalculated rank of the recommended value of the log storage disk size (step S812: negative), the recommended value determination unit 17 returns to step S811 and calculates the recommended value of the log storage disk size of the remaining ranking. repeat.

On the other hand, when all the calculation of the recommended value of the log storage disk size is completed (step S812: affirmative), the recommended value determining unit 17 acquires the recommended setting for all the hardware types and the set of the installed OS. Determines whether or not is completed (step S813). If there is a set of hardware type and installed OS for which acquisition of recommended settings has not been completed (step S813: negation), the process returns to step S805.

On the other hand, when the acquisition of the recommended settings for all the hardware types and the sets of the installed OS is completed (step S813: affirmative), the recommended value determination unit 17 proceeds to step S831.

On the other hand, when the time range is specified (step S804: negative), the search processing unit 16 selects one from the set of the hardware type and the installed OS included in the specified configuration information (step S814). ..

Next, the search processing unit 16 determines whether or not there is only one time range designation (step S815).

When one time range is specified (step S815: affirmative), the search processing unit 16 extracts the log collection setting of the managed device 210 having the hardware type and the set of installed OS selected from the log information table 101. .. Then, the search processing unit 16 acquires the log collection settings of the ranking number in descending order of the number of the extracted log collection settings that satisfy the designated time range and the set number (step S816). Next, the search processing unit 16 acquires the log size of the managed device 210 having each acquired log collection setting at the time of normal operation and at the time of failure from the log information table 101. Further, the search processing unit 16 acquires the failure rate corresponding to the selected hardware type and the set of the installed OS from the failure information table 103. Then, the search processing unit 16 transmits the log collection setting, the log size at the time of normal and failure, the failure rate, and the number of units to the recommended value determination unit 17.

The recommended value determination unit 17 receives input from the search processing unit 16 of the log collection setting, the log size at the time of normal and failure, the failure rate, and the number of units. Then, the recommended value determination unit 17 calculates the average log size at the time of normal operation and at the time of failure (step S817).

Next, the recommended value determining unit 17 determines whether or not the failure rate is equal to or higher than the reference value (step S818).

When the failure rate is equal to or higher than the reference value (step 818: affirmative), the recommended value determining unit 17 acquires the log size at the time of failure as a log increment (step S819). On the other hand, when the failure rate is less than the reference value (step S818: negative), the recommended value determination unit 17 sets the log increment to 0 (step S820).

After that, the recommended value determination unit 17 calculates the recommended value of the log storage disk size for each ranking by adding the log increment to the average log size and multiplying the addition result by the number of units (step S821). ..

The recommended value determination unit 17 determines whether or not the calculation of the recommended values of the log storage disk sizes of all ranks has been completed (step S822). If there is an uncalculated rank of the recommended value of the log storage disk size (step S822: negative), the recommended value determination unit 17 returns to step S821 and calculates the recommended value of the log storage disk size of the remaining ranking. repeat.

On the other hand, when the calculation of the recommended value of the log storage disk size of all ranks is completed (step S822: affirmative), the recommended value determining unit 17 proceeds to step S830.

On the other hand, when a plurality of time ranges are specified (step S815: negative), the search processing unit 16 collects logs of the managed device 210 having the hardware type and the set of installed OS selected from the log information table 101. Extract settings. Then, the search processing unit 16 acquires the log collection settings of the ranking number in descending order of satisfying the plurality of designated time ranges and the set numbers among the extracted log collection settings (step S823). Next, the search processing unit 16 acquires the log size of the managed device 210 having each acquired log collection setting at the time of normal operation and at the time of failure from the log information table 101. Further, the search processing unit 16 acquires the failure rate corresponding to the selected hardware type and the set of the installed OS from the failure information table 103. Then, the search processing unit 16 transmits the log collection setting, the log size at the time of normal and failure, the failure rate, and the number of units to the recommended value determination unit 17.

The recommended value determination unit 17 receives input from the search processing unit 16 of the log collection setting, the log size at the time of normal and failure, the failure rate, and the number of units. Then, the recommended value determination unit 17 calculates the average log size at the time of normal operation and at the time of failure (step S824).

Next, the recommended value determining unit 17 determines whether or not the failure rate is equal to or higher than the reference value (step S825).

When the failure rate is equal to or higher than the reference value (step 825: affirmative), the recommended value determining unit 17 acquires the log size at the time of failure as a log increment (step S826). On the other hand, when the failure rate is less than the reference value (step S825: negative), the recommended value determining unit 17 sets the log increment to 0 (step S827).

After that, the recommended value determination unit 17 calculates the recommended value of the log storage disk size for each ranking by adding the log increment to the average log size and multiplying the addition result by the number of units (step S828). ..

The recommended value determination unit 17 determines whether or not the calculation of the recommended values of the log storage disk sizes of all ranks has been completed (step S829). If there is an uncalculated rank of the recommended value of the log storage disk size (step S829: negative), the recommended value determination unit 17 returns to step S828 and calculates the recommended value of the log storage disk size of the remaining ranking. repeat.

On the other hand, when the calculation of the recommended value of the log storage disk size of all ranks is completed (step S829: affirmative), the recommended value determining unit 17 proceeds to step S830.

The recommended value determination unit 17 determines whether or not the acquisition of the recommended settings for all the hardware types and the sets of installed OSs has been completed (step S830). If there is a set of hardware type and installed OS for which acquisition of recommended settings has not been completed (step S830: negative), the process returns to step S814.

On the other hand, when the acquisition of the recommended settings for all the hardware types and the sets of the installed OS is completed (step S830: affirmative), the recommended value determination unit 17 proceeds to step S831.

The recommended value determination unit 17 outputs to the notification unit 18 the recommended value of the log storage disk size and the recommended setting including the log collection setting for each ranking. The notification unit 18 receives the input of the recommended setting from the recommended value determination unit 17. Then, the notification unit 18 assigns a ranking and transmits the recommended setting to the user terminal 40 to notify the user (step S831).

As described above, the integrated management server according to this embodiment notifies the user of the recommended settings in the ranking format in descending order of the number of achievements. As a result, the user can acquire a plurality of proven recommended settings, and can determine the size of the log storage disk according to the information processing system to be introduced. Therefore, the integrated management server according to this embodiment can easily present an appropriate recommended value for estimating the log storage disk size, and contributes to the construction of an information processing system that better meets the needs of users. can do.

Here, the integrated management server 1 may be configured such that the user selects either the provision of one recommended setting in the first embodiment or the ranking display of the recommended setting in the second embodiment. In that case, when the integrated management server 1 receives the acquisition request of the recommended setting by the user, it also acquires an instruction as to whether or not to display the ranking, and performs any processing according to the instruction.

(Hardware configuration)
Next, the hardware configuration of the integrated management server 1 described above will be described with reference to FIG. FIG. 16 is a hardware configuration diagram of the integrated management server.

As shown in FIG. 16, the integrated management server 1 includes a CPU (Central Processing Unit) 91, a memory 92, a NIC (Network Interface Card) 93, and a disk 94. The CPU 91 is connected to the memory 92, the NIC 93, and the disk 94 via a bus.

The NIC 93 is an interface for the CPU 91 to communicate with an external device. The NIC 93 relays communication between the CPU 91, the individual management device 20, the support department terminal 30, and the user terminal 40. In the NIC 93, for example, when the log information collecting unit 11, the support information collecting unit 12, the new configuration acquisition unit 15, and the notification unit 18 illustrated in FIG. 2 communicate with the support department terminal 30 or the user terminal 40. , Relay communication.

The disk 94 is a secondary storage device. The disk 94 is, for example, a hard disk, an SSD (Solid State Drive), or the like. The disk 94 realizes the function of the database 10 illustrated in FIG. Further, the disk 94 has a log information collection unit 11, a support information collection unit 12, a log setting information calculation unit 13, a recording unit 14, a new configuration acquisition unit 15, a search processing unit 16, and a recommended value determination unit 17 illustrated in FIG. And various programs including a program that realizes the function of the notification unit 18 are stored.

The CPU 91 reads various programs from the disk 94, expands them into the memory 92, and executes them. As a result, the CPU 91 and the memory 92 have the log information collection unit 11, the support information collection unit 12, the log setting information calculation unit 13, the recording unit 14, the new configuration acquisition unit 15, the search processing unit 16, and the recommended values illustrated in FIG. The functions of the determination unit 17 and the notification unit 18 are realized.

1 Integrated management server 10 Database 11 Log information collection unit 12 Support information collection unit 13 Log setting information calculation unit 14 Recording unit 15 New configuration acquisition unit 16 Search processing unit 17 Recommended value determination unit 18 Notification unit 20 Individual management device 30 Support department terminal 40 User terminal 100 Information processing system 210 Managed device

Claims (7)

The configuration information of the managed device whose operation history is acquired according to the collection setting, the information of the collection setting, the information collection unit that collects the storage capacity for storing the operation history, and the information collection unit.
A failure response information collection unit that collects failure response information that represents the status of the failure response that was implemented when a failure occurred in the managed device.
The configuration information collected by the information collecting unit, the storage capacity for storing the collection setting information and the operation history, and the failure collected by the failure handling information collecting unit by acquiring the configuration information of the new device. A recommended value determination unit that calculates the recommended value of the storage capacity for storing the operation history of the new device based on the corresponding information,
A notification unit that notifies the recommended value determined by the recommended value determination unit, and
An information management device characterized by being equipped with. The information management device according to claim 1, wherein the configuration information includes information on the type of hardware of the managed device and the operating system (OS) mounted on the managed device. The information management device according to claim 1 or 2, wherein the collection setting includes a collection cycle of the operation history and the number of generations to be stored. The claim is characterized in that the failure response information includes information on the hardware type and installed OS of the managed device in which a failure has occurred, the period of operation history used for the investigation, and the time spent on the investigation. The information management device according to any one of 1 to 3. Any one of claims 1 to 4, wherein the recommended value determining unit acquires the configuration information of the new device input by using the input screen for inputting the configuration information of the new device. The information management device described in. The recommended value determination unit calculates a plurality of recommended values for the storage capacity and calculates them.
The information management device according to any one of claims 1 to 5, wherein the notification unit ranks and notifies a plurality of the recommended values according to a predetermined standard. The configuration information of the managed device whose operation history is acquired according to the collection setting, the information of the collection setting, and the storage capacity for storing the operation history are collected.
Collects failure response information that represents the status of the failure response that was implemented when a failure occurred in the managed device.
Get the configuration information of the new device
Based on the collected configuration information, the collection setting information, the storage capacity for storing the operation history, and the failure response information, the recommended value of the storage capacity of the new device is calculated.
An information management program characterized in that a computer executes a process of notifying the calculated recommended value.

Images