WO2011125138A1 - Performance monitoring device, method, and program - Google Patents

Abstract

Disclosed is a performance monitoring device for imparting a configuration number to each system configuration of an information processing system, and storing system configuration information and a baseline associated with the configuration number. The disclosed performance monitoring device detects a system configuration modification of the information processing system, and if the system configuration information of the information processing system after configuration modification has been stored, acquires a baseline associated with the configuration number attached to the system configuration after system configuration modification, and substitutes the baseline currently used in performance monitoring with the acquired baseline.

Description

Performance monitoring device, method and program Capture by reference

This application claims the priority of Japanese Patent Application No. 2010-087908 filed on April 6, 2010, and is incorporated into the present application by referring to its contents.

The present invention relates to a performance monitoring apparatus, a performance monitoring method, and a monitoring program for monitoring the processing performance of an information processing system.

The present invention relates to baseline monitoring of an information processing system. Baseline monitoring is a process of accumulating measurement results of information processing system performance as a history, and creating a normal baseline (hereinafter referred to as a baseline) for the processing performance of the information processing system based on the history. However, this is a monitoring method that compares the measurement results of the processing performance of the information processing system with the baseline, and determines that the processing performance of the information processing system is abnormal if the measured value deviates significantly from the baseline. .

There is prior art about baseline monitoring technology. For example, Patent Document 1 (Japanese Patent Application Laid-Open No. 2004-164737) discloses an invention relating to a method for providing a mechanism for performing baseline processing and automatic threshold processing.
The baseline creation processing and the baseline-based monitoring processing method of Patent Document 1 collect performance information (data values) over a predetermined interval, aggregate performance information into one data point, and aggregate Updating the baseline object based on the collected data points, predicting the next data value based on the aggregated data points, comparing the predicted data value with the actual collected data value, It is described that a threshold violation event is generated when there is a difference between the predicted data value and the actually collected data value.

Patent Document 2 (Japanese Unexamined Patent Application Publication No. 2009-193238) discloses an invention relating to a method for predicting a future load from a history of differences between measured values and baselines.
In the load prediction method of Patent Document 2, a storage unit is provided for accumulating the difference and deviation between the past measured value of the system load and the baseline, and the future value of the system load is determined based on the accumulated difference and deviation. The prediction is described.

Japanese Patent Laid-Open No. 2004-164637 JP 2009-193238 A

In previous information processing systems, system configuration changes were rarely made. However, with the maturation of virtualization technology that runs multiple virtual computers (virtual computers) on the (physical) computers that make up an information processing system, system configuration changes have become much easier than before. Yes. In other words, change of physical computer resources (CPU and memory allocation) allocated to the virtual machine, addition / reduction of virtual machines to the information processing system, change of the physical machine on which the virtual machine operates (migration of virtual machines) Thus, the configuration change of the information processing system can be performed relatively easily.

Furthermore, in a virtual environment, multiple information processing systems share the same computing resource. For example, in the case where virtual computers belonging to different information processing systems operate on the same physical computer, a plurality of information processing systems share the physical computer. If the system configuration of one information processing system is changed, not only will the baseline for that information processing system change, but the baseline of the other information processing system will also change via the shared physical computer. there's a possibility that.

Since the baseline monitoring technology automatically generates a monitoring threshold that changes in time series from the history of measured performance information, it is not necessary to set monitoring thresholds for a large number of monitoring items. On the other hand, since the baseline is created from the history of performance information, the dependency on the system configuration of the measurement target information processing system is strong. For this reason, usually, when the system configuration of the information processing system is changed, it is necessary to accumulate performance information under the system configuration after the configuration change and re-create the baseline over a period of several days.

None of the above prior art documents consider the handling of the baseline due to the system change of the information processing system.

Therefore, in an environment where the configuration of the information processing system can be easily changed, it is necessary to reduce the chances of re-creating the baseline accompanying the system configuration change.

In order to solve the above problems, in the present invention, a baseline is stored for each version of the system configuration of the information processing system, and when the system configuration is changed, it is determined whether or not it is the same as the previous system configuration. If so, reuse the previously created baseline. Also, by storing the configuration version of another information processing system that shares computing resources with the information processing system as version information of the system configuration, it is the same, including the configuration of the related system, when the configuration is changed. You can determine whether or not you want to reuse a previously created baseline.

Specific embodiments of the present invention are the following performance monitoring apparatus, performance monitoring method, and performance monitoring program. The performance monitoring device corresponds to the configuration storage unit that stores the system configuration information of the information processing system, the configuration information management unit that assigns a unique configuration number to each different system configuration of the information processing system, and the configuration number and the baseline. And a baseline storage unit for storing the baseline. The performance monitoring device monitors the performance of the information processing system based on the baseline created from the performance information history measured from the information processing system. The configuration information management unit changes the system configuration of the information processing system. Detects and queries whether the system configuration information of the information processing system after the configuration change exists in the configuration storage unit, and queries the presence or absence of the system configuration information after the configuration change of the information processing system by the configuration information management unit If the result is yes, the first baseline associated with the configuration number assigned to the system configuration after the system configuration change is obtained from the baseline storage unit and used for current performance monitoring. The existing second baseline is replaced with the first baseline.

According to another aspect of the present invention, a performance monitoring apparatus includes a configuration storage unit that stores system configuration information of a first information processing system, and a unique first information for each different system configuration of the first information processing system. A second information processing system that is assigned a configuration number and is uniquely assigned to each different system configuration of the second information processing system with respect to the second information processing system that shares computing resources with the first information processing system. A configuration information management unit that stores the configuration numbers in association with each other, and a baseline storage unit that stores the first configuration number, the second configuration number, and the baseline in association with each other. The performance monitoring device monitors the performance of the first information processing system based on a baseline created from the performance information history measured from the first information processing system. , Detecting the system configuration change of the first information processing system, inquiring whether the system configuration information of the first information processing system after the configuration change exists in the configuration storage unit, and by the configuration information management unit, If the result of the inquiry about the presence or absence of the system configuration information after the configuration change of the first information processing system is present, the system information from the baseline storage unit is changed to the system configuration after the system configuration change of the first information processing system. The first baseline associated with the assigned configuration number is acquired, and the second baseline currently used for performance monitoring of the first information processing system is used as the first baseline. Replace the line.

According to still another aspect of the present invention, in the other correspondence, the performance monitoring apparatus further includes a second configuration number of the second information processing system associated with the first configuration number. Inquire whether the third configuration number assigned to the current system configuration of the information processing system 2 is the same, and if the second configuration number does not match the third configuration number, A third baseline is newly created from the performance information history of the second information processing system after changing the system configuration of the information processing system, and the first configuration number, the third configuration number, and the created third A baseline is associated and stored in the baseline storage unit, and a third baseline corresponding to the first configuration number and the third configuration number is acquired from the baseline storage unit from the baseline storage unit, Currently the second information processing system The fourth baseline is used to performance monitoring, replaced with a third baseline.

According to the present invention, it is possible to reduce the number of times the baseline is recreated in an environment in which the system configuration can be easily changed and the computing resources are virtualized.

1 is an overall system configuration diagram of Embodiment 1. FIG. It is a hardware block diagram of a monitoring computer. It is a hardware block diagram of a physical computer. It is a relationship diagram between the physical computer and its peripheral hardware It is a functional block diagram of the performance monitoring program in Example 1. FIG. 3 is a configuration diagram of a baseline management table according to the first embodiment. It is a block diagram of a structure information table. It is a block diagram of a component related table. It is a block diagram of a baseline data table. It is a block diagram of a performance information table. It is a schematic flowchart of a baseline management. 3 is a baseline change process distribution flowchart according to the first embodiment. 4 is a flowchart of a baseline re-creation process in the first embodiment. 6 is an example of a display screen when the system configuration is changed in the first embodiment. It is a block diagram of a consent table. FIG. 10 is a configuration diagram of a baseline management table of Example 2. 10 is a flowchart of distributing a base line change process according to the second embodiment. FIG. 10 is a functional block diagram of a performance monitoring program according to a third embodiment. It is a block diagram of a baseline comparison history table. FIG. 10 is a baseline change process distribution flowchart in Embodiment 3. FIG. 10 is a flowchart of a baseline re-creation process in the third embodiment. FIG. 10 is a function lock diagram of a performance monitoring program according to a fourth embodiment. 12 is a flowchart of performance failure cause analysis processing in the fourth embodiment. FIG. 10 is a functional block diagram of a performance monitoring program according to a fifth embodiment. 10 is a flowchart of a system configuration history search process in Embodiment 5. FIG. 10 is a flowchart for distributing a base line change process according to a sixth embodiment.

In one embodiment of the present invention, the performance monitoring apparatus assigns a configuration number to each system configuration of the information processing system, and stores system configuration information and a baseline associated with the configuration number. The performance monitoring device detects the system configuration change of the information processing system, and when the system configuration information of the information processing system after the configuration change is stored, the configuration number assigned to the system configuration after the system configuration change The baseline associated with is acquired, and the baseline currently used for performance monitoring is replaced with the acquired baseline. According to such an embodiment, it is possible to reduce the number of times the baseline is recreated in an environment where the configuration of the system is easy and the computing resources are virtualized. Hereinafter, the embodiment will be specifically described.

(System configuration)
FIG. 1 shows an overall system configuration including a response time monitoring device that monitors the response time of the information processing system. The whole system has no positive meaning and is a name for distinguishing it from the information processing system. The response time monitoring device corresponds to the monitoring computer 200 of FIG. The monitoring computer 200 is connected to the physical computer 202 and the measurement computer 201. On the physical computer 202, at least one virtual computer 203 operates. The information processing system 204 is configured by one or more physical computers 203 or virtual computers 203 (the figure shows a state in which the information processing system 204 is configured by the virtual computers 203).

At least one information processing system is configured on such a computer system. An information processing system is a unit of system configuration. For example, from an application point of view, one information processing system is a sales management system, and the other information processing system is an inventory management system. In another example, one information processing system is a sales management and inventory management system, and the other information processing system is a settlement management system. As described above, the information processing system is a structural unit of the system realized on the computer system, and the viewpoint is not limited to the application. Hereinafter, the information processing system 204 is simply referred to as a system 204.

The measurement computer 201 is connected to the physical computer 202. The measurement computer 201 periodically sends a request to the system 204, receives a response from the system 204, and measures the response time (the time from the request transmission time to the response reception time). The response time measurement method of the measurement computer 201 may be another method. For example, a response time may be measured by capturing a packet transmitted and received by a computer constituting the system 204 from a mirror port of an IP switch connected to the physical computer 202.

The measurement computer 201 and the monitoring computer 200 are connected via a network, and the response time measured by the measurement computer 201 is sent to the management computer 200 as needed. The management computer 200 performs baseline monitoring of the response time for each system 204 that has collected the response time. Baseline monitoring creates a normal response time range (for example, using the average response time and its deviation) based on the collected response time history, and sets the response time that deviates from that range. This is a monitoring method that notifies the system administrator of abnormal values as measured values.

(Hardware configuration)
FIG. 2 shows a hardware configuration of the monitoring computer 200. The monitoring computer 200 includes a CPU 300, a memory 301, a display 302, and a hard disk 303 that is a storage device. The hard disk 303 stores an operating system 304 for operating the monitoring computer 200 and a performance monitoring program 305. The performance monitoring program 305 is read into the memory 301 and operates on the CPU 300.

FIG. 3 shows the hardware configuration of the physical computer 202. Similar to the monitoring computer 200, the physical computer 202 includes a CPU 307, a memory 308, a display 309, and a hard disk 310. In the physical computer 202, the hypervisor 306 operates, and the virtual computer 203 operates under the control of the hypervisor 306.

FIG. 4 shows a relationship diagram between the physical computer 202 and its peripheral hardware. The virtual computer 203 operating on the physical computer 202 is connected to the virtual switch 400 (operating as software) in the physical computer 202. The virtual switch 400 is connected to a communication card (NIC: Network Interface Card) 401 connected to the physical computer 202. The NIC 401 is connected to the physical switch 402. The physical switch 402 is connected to other physical switches 402. The physical computer 202 is connected to an HBA (Host Bus Adaptor) 403 for connection to the storage device 405. The HBA 403 is connected to the storage apparatus 405 via a SAN (Storage Area Network) switch 404.

(Configuration of performance monitoring program)
As described above, the performance monitoring program 305 monitors the presence or absence of an abnormality in the response time of the system 204 using the baseline created based on the response time history of the system 204. Since the response time baseline differs for each configuration of the system 204, the performance monitoring program 305 stores the baseline data for each system configuration of the system 204. When the system configuration of the system 204 is changed, the performance monitoring program 305 extracts baseline data corresponding to the changed system configuration and performs baseline monitoring. If there is no baseline corresponding to the system configuration after the change, a new baseline corresponding to the system configuration after the change is created.

FIG. 5 shows a functional block diagram of the performance monitoring program 305. The baseline management unit 500 manages baseline data for each system configuration of the system 204. The baseline management unit 500 includes a baseline creation unit 505 and a configuration comparison unit 506. When the configuration of the system 204 is changed, the configuration comparison unit 506 matches or nearly matches the system configuration after the change (does not require a baseline change and can be considered to match). Find out if there is. In other words, it is checked whether the system configuration has been restored to the system configuration that has been operated in the past. In this specification, the term “match” is used, including the case where the values almost match. The baseline creation unit 505 creates a baseline for a new system configuration that has not existed before. The baseline storage unit 501 stores data related to the baseline. The configuration management unit 503 collects hardware / software configuration information constituting the performance monitoring target system 204 and provides the collected configuration information to the baseline creation unit 505. The configuration management unit 503 instructs and controls the configuration change of the system 204 to be monitored. The configuration change of the system 204 is, for example, addition or reduction of the virtual machine 203, movement of the virtual machine 203 between the physical machines 202, change of assignment of calculation resources such as a CPU to the virtual machine 203, weight of the load balancer For example, change, increase / decrease of volume allocation of the storage apparatus 405 to the virtual machine 203, change of volume arrangement, change of software parameters, and the like. As an example of the above-mentioned almost identical system configuration (which can be regarded as identical), there is a volume arrangement change in one storage apparatus 405. This is because the same storage device 405 has almost the same access performance to the volume.

The performance monitoring unit 504 measures the performance of the monitoring target system 204, stores the measured performance information, and provides the performance information to the baseline management unit 500. In addition, the performance monitoring unit 504 performs baseline monitoring on the monitoring target system 204 using the baseline acquired from the baseline management unit 500. In the system configuration diagram of FIG. 1, the performance monitoring unit 504 operates on the measurement computer 201. However, some of the functions of the performance monitoring unit 504 may operate on the monitoring computer 200, for example, functions such as storage and provision of performance information. In this embodiment, the performance monitoring unit 504 measures the response time as the performance of the monitored system 204. However, the performance monitoring unit 504 is not limited to the response time, and the CPU usage rate, memory usage, disk I / O amount, etc. Hardware performance may be measured, or software performance such as database applications may be measured.
The display / input unit 502 displays information for the administrator and receives input from the administrator.

The baseline storage unit 501 holds a baseline management table 600, a configuration information table 700, a component related table 800, and a baseline data table 1000.

FIG. 6 shows the configuration of the baseline management table 600. The baseline management table 600 manages baseline data of “for each configuration” of the system 204. The baseline management table 600 stores the following data.
The system name 601 stores the name of the system 204. The configuration number 602 stores a number uniquely assigned to each configuration of the system 204. The configuration number 602 may be assigned a unique number for each system 204, or may be assigned a unique number as a whole rather than for each system. The previous configuration number 603 stores the configuration number 602 of the system 204 before the configuration of the system 204 is changed. A plurality of configuration numbers may be stored in the previous configuration number 603. For example, there are cases where the configuration is changed from configuration number 2 to configuration number 3 and when the configuration is changed from configuration number 4 to configuration number 3. The current flag 604 stores whether or not the current configuration is used. In FIG. 6, “Y” is stored in the current configuration, and “N” is stored in the other configuration (a configuration that has been taken before). The usage time 65 stores the time (time zone) when the configuration was taken. Similar to the previous configuration number 603, the usage time 605 may store a plurality of times. Each of the plurality of times is stored in correspondence with each of the previous configuration numbers. Baseline number 606 stores a unique number to the baseline data in the configuration. This number matches the baseline number 1001 stored in the baseline data table 1000, which will be described later, and the baseline data is acquired from the baseline data table 1000 using the baseline number 606 as a key.

The configuration information table 700 and the component related table 800 store what the configuration the system has taken before. In other words, it is a snapshot of configuration information. The baseline management unit 500 acquires the configuration information collected by the configuration management unit 503 and stores the data in these tables.

FIG. 7 shows the configuration of the configuration information table 700. The configuration information table stores information on various elements (computers, network devices, operation programs, etc.) constituting the system 204. In this embodiment, line data is created in the configuration information table 700 for each component. The system name 701 stores the system name of the system 204. The configuration number 702 stores the configuration number of the system 204 (the number common to the configuration number 602 and the previous configuration number 603 in the baseline management data 600). In the component 703, the name of the component (or a number uniquely assigned to the component) is stored. Property name 704 and property value 704 store the attribute name and value of the component.

FIG. 8 shows the configuration of the component related table 800. The component relationship table 800 stores connections (relationships) between components. In this embodiment, it is assumed that row data is created in the component relationship table 800 for each relationship between components. The system name 801 and the configuration number 802 are the same as the system name 701 and the configuration number 702 in the component table 700. The association source component 803 and the association destination component 804 store the names of the two related components. The relation source and the relation destination do not indicate the direction of the relation but are names for identifying two related components. When a plurality of systems share one component, for example, when virtual computers 203 belonging to different systems 204 are operating on the same physical computer 202 (status of the central physical computer 202 in FIG. 1) The relationship between the shared physical computer 202 and the virtual computer 203 is stored in the component relationship table as belonging to each system 204.

FIG. 9 shows the configuration of the baseline data table 1000. The baseline data table 1000 holds the following data. Baseline number 1001 is a number uniquely assigned to baseline data in a configuration of system 204. The service name 1002 stores the URL of the service whose response time is measured. The time zone section 1003 stores a time zone to which the baseline data is applied. Baseline data 1004 stores baseline data (average value of response time, deviation, etc.).

In this embodiment, the baseline data table 1000 is described as a response time baseline. However, it is possible for those skilled in the art to use this for other measurement items such as CPU usage rate and memory usage. Easy.

FIG. 10 shows the configuration of the performance information table 900 held by the performance monitoring unit 504. The performance information table 900 stores performance information collected from the monitored system 204. The performance information table 900 stores the monitored system name 901, the acquisition date and time 902 when the response time was acquired, the service name 903 that acquired (measured) the response time, and the acquired data (acquired data 904). These measurement data are the original data for creating the baseline.

(Baseline management procedure)
In the following, an overall outline flowchart of the baseline management procedure when the configuration of the system 204 to be monitored is changed in this embodiment is shown in FIG. It is assumed that the system configuration has been changed before the processing of this flowchart. That is, it is assumed that the configuration management unit 503 has changed the system configuration of the monitoring target system 204 (increase / decrease or move the virtual machine 203) in response to a request to change the system configuration.

In the first to third embodiments, the processing procedure of this outline flowchart is common. However, the details of the processing of S101 to S103 in the flowchart are different in each embodiment. Details of these steps will be described in detail in the description of each embodiment.

First, in S100, the baseline management unit 500 acquires system configuration information after the configuration change. The configuration management unit 503 collects configuration information. The collected configuration information may be temporarily stored in the storage device of the configuration management unit 503 or directly passed to the baseline management unit 500.

In S101, a system that requires a baseline change process is identified, and for each system 204, it is determined whether to perform a baseline reuse (S102) process or a baseline recreation (S103) process. Thereafter, the base line reuse (S102) process or the base line recreation (S103) process is performed for each of the systems specified from step S101. Details of the bags S101 to S103 in the first embodiment will be described below.

(S101: Baseline change process distribution)
FIG. 12 shows a detailed flowchart of S101 in the first embodiment. In this flowchart, the system configuration after the change of the system 204 (hereinafter referred to as the changed system) is compared with the system configuration after the change (hereinafter referred to as the current system configuration) and the previous system configuration of the system 204. If the system configuration matches the previous system configuration, the baseline data is reused. If the system configuration does not match, the baseline is recreated in the system configuration after the change.

First, in S1200, various tables stored in the baseline storage unit 501 are read and compared with the current system configuration and the previous system configuration. First, referring to the configuration information table 700 and the component-related table 800 from the system name of the changed system and the previously acquired configuration number, the system configuration after the system configuration change collected in S100 and the configuration taken before And compare. In this embodiment, any comparison method may be used. For example, for each entry in the configuration information table 700 where the system name 701 and the configuration number 702 match, the determination as to whether or not the configuration element 703, property name 704, and property value 705 match is repeated. Further, the matching determination process is repeated in the same manner for the related source component 803 and the related destination component 804 in the component related table 800. If a pair (system name, configuration number) that matches all entries is found, it is determined that there is a previous system configuration that matches the current system configuration, and the process advances to step S1202. If not, the process proceeds to S103. At this time, the pair of (system name, configuration number) is stored and used in the processing after S1202.

It should be noted that some exceptions may be made in comparing the configuration information. For example, in the case of a system change where the baseline is unlikely to change, such as movement of the virtual machine 203 between physical machines 202 of the same specification, the stored contents of the component related table 800 do not match the current contents. However, an exception may be made such that the system configurations are considered to be the same. Further, such exceptions may be ruled and held by each component 506. In this way, in the case where the system configurations are considered to be the same, it is not necessary to switch the baseline data used for performance monitoring, so only the contents of the component relation table 800 are updated, and the processing of this flowchart ends.

In S1202, the administrator is notified that the baseline data is to be switched along with the configuration change. The baseline management unit 500 passes the baseline data used before the change and the baseline data to be switched to the display / input unit 502, and the display / input unit 502 displays the received data on a display device such as a display. To do. As a notification method other than displaying on the display, a mail or a notification event may be issued.

FIG. 14A shows an example of a screen displayed on the display for the administrator. The baseline comparison screen 1400 displays a baseline comparison graph 1401, a baseline graph description 1402, a consent button 1403, and a non-approval button 1404. The baseline comparison graph 1401 displays the baseline data used in the previous configuration and the baseline data to be switched after the configuration change. In the baseline graph description 1402, an explanation message for each graph is displayed. For the baseline to be switched, the date and time of creation are also displayed, and the material used by the administrator to determine whether or not to switch (for example, the base created one month ago, even if the configuration is the same) Lines should not be used, but should be recreated). The administrator presses the accept button 1403 when accepting the switching of the baseline data, and presses the non-accept button 1404 when not accepting the change. The display / input unit 502 receives the approval / non-acceptance decision of the manager and sends it to the baseline management unit 500. The baseline management unit 500 proceeds to S102 in the case of consent, and proceeds to S103 in the case of non-consent.

For S1202 and S1203, the step of obtaining consent from the administrator may be skipped under the following conditions.
Condition 1:
If the elapsed time from the creation / update date / time of the baseline data to be switched is less than or equal to a predefined threshold,
Condition 2:
When the baseline management unit 500 refers to the configuration number 602, the previous configuration number 603, and the usage time 605 in the baseline management table 600 and detects periodicity in the change transition of the system configuration,
Condition 3:
When the administrator's approval / disapproval decision history is recorded in the approval table 1500 shown in FIG. 14B and the same configuration change has been previously approved is recorded in the history.
The approval table 1500 is an administrator for data necessary for the above determination, that is, system name 1501, configuration numbers before and after system configuration (previous configuration number 1502, rear configuration number 1503), and baseline switching due to the configuration change. Holds an acceptance flag 1504 indicating whether or not. At the same time, the time of acceptance may be recorded as a list.

(S102: Baseline reuse)
In this step, the baseline management table 600 is referenced using the (system name, configuration number) pair acquired in step S1201 as a key, and the baseline number 606 of the entry previously created in the configuration is acquired. With reference to the baseline number as a key, the baseline data table 1000 is referred to, an entry with the matching baseline number 1001 is obtained, and baseline data 1004 used for monitoring is obtained. The baseline management unit 500 sends the acquired baseline data to the performance monitoring unit 504. The performance monitoring unit 504 replaces the baseline data currently used for baseline monitoring with the baseline data sent from the baseline management unit 500, and continues the baseline monitoring.

(S103: Baseline re-creation)
FIG. 13 shows a detailed flowchart of step S103: baseline re-creation processing in the first embodiment.
In S1300, the administrator is notified that the baseline will be recreated in the system configuration after the change. The notification means may be any means such as display on a GUI screen on the display, mail or event. The contents to be notified are as follows.
(1) Changed system name (2) System configuration before and after the change, and the difference between them (any method can be used, such as showing a topology graph showing the relationship of components on the screen)
(3) Continue monitoring the baseline using the baseline of the previous configuration until performance information samples sufficient for baseline creation are accumulated in the system configuration after the change.

In S1301, a new entry (new configuration entry) for the system configuration after the configuration change is created in the baseline management table 600. A new serial number is stored in the configuration number 602 of the new configuration entry, and the configuration number 602 of the previous configuration entry is stored in the previous configuration number 603. The current flag 604 of the new configuration entry 604 is set to “Y”, and the current time is stored in the usage time 605. In addition, the baseline number of the entry for the immediately previous configuration is temporarily copied to the baseline number 606. The baseline number 606 copied here is overwritten when the baseline for the new configuration is created in S1303.

In S1302, the baseline monitoring is continued using the baseline in the previous configuration provisionally. During this time, the performance monitoring unit 504 continues to monitor the performance of the monitoring target system 204 and accumulates performance information in the performance information table 900. After a system configuration change, after a lapse of a certain time, or when performance information samples necessary for creating a baseline are accumulated in the performance information table 900, the process proceeds to S1303.

While this temporary baseline was used for baseline monitoring, the baseline used was not created with the current system configuration, so an accurate abnormal value could not be determined and was incorrect. A performance failure event may be sent to the administrator. Therefore, in order to alert the administrator who received the event, a flag or message indicating that the monitoring is based on the provisional baseline may be added to the performance failure event transmitted during this period.

S1303 is a baseline creation process that is normally performed. That is, the baseline creation unit 505 refers to the performance information table 900, fetches performance information after the usage time 605 of the baseline management table 600, and performs statistical processing (average, deviation calculation, etc.) on these data. The baseline data calculated as a result is stored in the baseline data table 1000. Also, the baseline number 1001 assigned at the time of registration of the baseline data is acquired, and the baseline number 606 of the temporary baseline stored in the baseline management table 600 is overwritten with the new baseline number.

According to the present embodiment, it is possible to reduce the opportunity to re-create the baseline along with the system configuration change.

In the second embodiment, unlike the first embodiment, the influence of the plurality of systems 204 that interfere with each other by sharing calculation resources such as computers and network devices is taken into consideration. That is, among the multiple systems 204 that share computing resources, taking into account that the sharing relationship of the computing resources to be shared changes by changing the configuration of one system, and for the system whose configuration has been changed as necessary. Recreate baselines for other systems as well as baselines.

(System configuration)
The overall system configuration is the same as in the first embodiment. However, in the second embodiment, the monitoring computer 200 constantly monitors not only the response performance of the system 204 but also various measurement items of the computing resources (for example, the CPU usage rate of the virtual computer 203 and the disk I / O performance). Suppose you are.

The hardware configuration in the second embodiment is the same as that in the first embodiment. The configuration of the apparatus is the same as that of the first embodiment.

(Configuration of performance monitoring program)
The configuration block diagram of the performance monitoring program 305 in the second embodiment is the same as that in the first embodiment (FIG. 5). However, data (related system name 1401, related system configuration number 1402, shared component 1403) is added to the baseline management table 600 stored in the baseline storage unit 501 as shown in FIG. These data show which other system 204 (and its configuration) and which component (synonymous with computing resource) the system 204 of the entry concerned shares. When the components are shared with a plurality of systems 204, a plurality of these data are created. These data are acquired with reference to the component relation table 800. In other words, the constituent elements constituting the system 204 are fetched from the constituent element relation table 800, and then the procedure of fetching the constituent element relation table 800 in order using these constituent elements as keys is repeated to share the constituent elements. , The system name 801 and its configuration number 802 are acquired.
In the following, the following terms are used with the following meanings. “Change system” is “system whose system configuration has been changed”, and “related system” is “system sharing calculation resources with the change system”.

(Baseline management procedure)
In the following, the procedure of baseline management in the second embodiment will be described with reference to the flowchart of FIG. In this flowchart, since steps other than S1600 have already been described, only S1600 will be described here.

Briefly, S1600 is a step of determining whether or not the configurations are the same, including the configurations of related systems that share computing resources, when the configuration changes to the system 204 and returns to the previous configuration. It is. In this step, first, the configuration comparison unit 506 stores the related system name 1401, the configuration entry of the system configuration after the configuration change (which has been acquired in step S101) stored in the baseline management table 600. The related system configuration number 1402 is acquired. Next, using these two data as keys, the baseline management table 600 is referenced again, the system name 601 matches the related system name 1401 acquired first, and the configuration number 602 is the related system configuration number acquired first. An entry matching 1402 is obtained. Next, the current flag 604 of the same entry is referred to, and it is checked whether or not the content of the current flag 604 is “Y”. “Y” indicates that the configuration of the related system matches the current configuration. If the current flag 604 is “N”, the current configuration is different from the previous configuration. Therefore, it is determined that the previously created baseline data needs to be recreated, and the baseline is recreated S103. Proceed to If all the current flags 604 of the related system are “Y”, the process proceeds to S104, which is a baseline reuse process, without recreating the baseline.

Subsequently, a different part of S103 which is the baseline re-creation processing will be described between the first embodiment and the second embodiment.
In the second embodiment, compared to the first embodiment, a related system name 1401, a related system configuration number 1402, and a shared component 1403 are added to the baseline management table 600. Therefore, S1301 for creating an entry in the baseline management table 600 is as follows. That is, the baseline creation unit 505 refers to the component relation table 800 for each of the change system and the related system using the system name and the configuration number as a key, and the component relation table 800 for each of the change system and the related system. , And by referring to the related source component 803 or the related destination component 804, the common component between the change system and the related system is specified. When creating an entry for the changed system, an entry is created with the identified component as the shared component 1403, the related system as the related system name 1401, and the configuration number as the related system configuration number 1402. Conversely, when creating an entry for a related system, an entry is created with the identified component as the shared component 1403, the changed system as the related system name 1401, and the configuration number as the related system configuration number 1402.

According to this embodiment, when a plurality of information processing systems share a computing resource, it is possible to correctly re-create a baseline for the information processing system that has changed the system configuration and another information processing system that shares the computing resource.

In the third embodiment, the configuration change of a system 204 and the performance impact of the change on a system 204 (related system) that shares computing resources with the system 204 that has undergone the configuration change are expressed as baselines before and after the system configuration change. An appropriate baseline is created in the environment after the system configuration change while evaluating by comparing the amount of change. That is, in the third embodiment, based on the second embodiment, the baseline management unit 500 has a function of comparing and evaluating the baseline.

The overall system configuration, hardware configuration, and device configuration in the third embodiment are the same as those in the second embodiment.

FIG. 17 shows a block diagram of the performance monitoring program configuration in the third embodiment. As can be seen from the figure, the second embodiment is the same as the second embodiment except that a baseline comparison unit 507 is added to the baseline management unit 500. In addition, with the addition of the baseline comparison unit 507, a baseline comparison history table 1800 is added to the baseline storage unit 501, which stores the results of comparative evaluation of the baselines.

FIG. 18 shows the configuration of the baseline comparison history table 1800. The baseline comparison history table 1800 includes a history number 1801, which is a serial number of the comparison history, a system name 1802, a configuration number 1803 of the system 204 for comparing the baselines, and a change content 1804 for storing the factors for the baseline comparison processing. Cause history number 1805 indicating the original cause of the change contents (history number 1801 of another entry in the baseline comparison history table 1800), compared baseline number 1806, measured item 1807 compared, evaluation formula 1808 used for comparison, evaluation It has a divergence degree 1809 as a result.

(Baseline management procedure)
Of the flowchart of the baseline management procedure according to the third embodiment, FIG. 19 shows a flowchart of S101 which is a baseline change distribution process. This flowchart is the same as the flowchart of FIG. 16 of S101 in the second embodiment (FIG. 16), except that the process proceeds to S1901 when the related system configuration does not match the current configuration in S1600.

In the processing flow shown in Example 2, if the configuration of the related system is different even at one place, the baseline was recreated. However, if it can be determined that the difference in the system configuration has little effect on the baseline, there is little possibility of inconvenience even if the previous baseline is reused. S1901 determines the degree of this effect. That is, the configuration information obtained by referring to the configuration information table 700 from the configuration number 1401 (configuration number 1) of the related system stored in the baseline management table 600 and the current configuration number 602 (configuration of the related system) Similarly, for the number 2), the configuration information obtained by referring to the configuration information table 700 is compared, and the common components are identified. Next, the baseline stored in the configuration number 1 of the component (which can be obtained by referring to the entry of the baseline data table 1000 specified by the baseline number 606 of the baseline management table 600), The baselines stored in the configuration number 2 are compared, and if the degree of divergence is small, it is determined that the influence due to the difference in the configuration of the related systems is small, and the process proceeds to S104 which is a baseline reuse process. If the degree of divergence is large, the process proceeds to S103, which is a baseline re-creation process. The calculation of the baseline divergence may be, for example, a cumulative value of baseline values for each time or a cumulative value of baseline deviations.

Next, in the flowchart of the baseline management procedure in the third embodiment, S103, which is a baseline re-creation process, will be described. FIG. 20 shows a flowchart of S103 in the third embodiment.
This flowchart is the same as the baseline re-creation processing (FIG. 13) of the second embodiment but the processing from S1300 to S1303, but is different in that S2001 to S2003 are added thereafter. Hereinafter, the differences S2001 to S2003 will be described.

In S2001, for the related system of the system 204 whose system configuration has been changed, the baseline created before the system configuration change of the system 204 is compared with the baseline created after the system configuration change (created in step S1303). The degree of divergence is calculated, and the degree of change that the system configuration change gives to the baseline of the related system is calculated. If the calculated baseline divergence is greater than or equal to a predetermined threshold, the process advances to step S2003. On the other hand, if the calculated baseline divergence is less than or equal to a predetermined threshold, it can be determined that the change in the system configuration has little effect on the baseline of the related system, and thus the process ends. The result of this comparison processing is stored in the baseline comparison history table 1800. The result entry of the baseline comparison history for the changed system is stored in the baseline comparison history table 1800 prior to the related system. The change contents 1804 of the result entry of the baseline comparison history for the changed system store the configuration change of the system and the configuration numbers before and after the change. The cause history number 1805 may have no data. On the other hand, in the change entry 1804 of the result of the baseline comparison history for the related system, the fact that the comparison is a baseline comparison due to the configuration change of the related system of the same system is stored. The history number 1801 of the entry is stored.

According to this embodiment, when a plurality of information processing systems share computing resources, the validity of reusing a previously created baseline is determined and then the baseline is recreated. You can recreate the line.

In the fourth embodiment, a procedure for tracking a system configuration change causing a performance failure using the record of the baseline change amount accompanying the system configuration change shown in the third embodiment will be described.

The overall system configuration, hardware configuration, and device configuration in the fourth embodiment are the same as those in the third embodiment.

(Configuration of performance monitoring program)
FIG. 21 shows a functional block diagram of the performance monitoring program in the fourth embodiment. As shown in the figure, the difference from the block diagram of the third embodiment (FIG. 17) is that a cause analysis unit 508 is added.

(Cause analysis procedure)
FIG. 22 shows the cause analysis procedure of the performance failure by the cause analysis unit 508.
First, in S2200, the cause analysis unit 508 refers to the baseline management table 600, acquires an entry for the current configuration of the system in which the performance failure has occurred (an entry whose current flag 604 is “Y”), and The related system name 1401 and the related system configuration number 1402 are acquired.

Next, in S2201, the baseline comparison history table 1800 is referred to, and the system name 1802 and the configuration number 1803 are subtracted from the related system name and the related system configuration number acquired in the previous step, respectively, and the existence of the corresponding entry is checked. If there is no corresponding entry, it is determined that there is no system configuration change that is considered to be the cause, and the analysis process is terminated. If there is a corresponding entry, the process proceeds to step S2202.

In S2202, the entry change content 1804 acquired in the previous step is referred to, and it is checked whether or not the content is “configuration change”. If it is a configuration change, it is notified that a performance failure has occurred due to the configuration change according to the change contents 1804 of the entry (S2203). Also, in this step, a baseline deviation degree, which will be described later in S2204, may be examined. That is, referring to the entry divergence degree 1809, if the value exceeds a given threshold value, the process may proceed to S2203.

If it is determined in step S2202 that the entry change content 1804 is not “configuration change”, the process advances to step S2204. Supplementally, this case corresponds to a case where the baseline has changed due to a configuration change of another system (for example, a system sharing resources).

In S2204, the amount of change (degree of divergence) of the baseline of the entry is checked. The divergence degree 1809 of the entry is referred to, and if the value exceeds a given threshold value, the process proceeds to step S2205. Supplementally, this case corresponds to a case where a large change has occurred in the baseline due to a configuration change of another system (for example, a system sharing resources). If the threshold value is not exceeded in the previous divergence comparison, the analysis process is terminated with no system configuration change considered as the cause of the performance failure.

In S2205, the cause history number 1805 of the same entry is referenced, and then the baseline comparison history table 1800 is referenced to search for and obtain an entry where the cause history number 1805 matches the history number 1801. The processing from S2202 is repeated again on the acquired entry.

According to the present embodiment, it is possible to track the system configuration change that causes the performance failure by using the record of the baseline change amount accompanying the system configuration change.

Example 5 shows an example in which a configuration that satisfies a specified service level is searched from a past configuration history based on the baseline management data shown in Example 3.

The overall system configuration, hardware configuration, and device configuration in the fifth embodiment are the same as those in the third embodiment.

(Configuration of performance monitoring program)
FIG. 23 shows a block configuration of the performance monitoring program in the fifth embodiment. As shown in the figure, the difference from the block diagram (FIG. 17) shown in the third embodiment is that a configuration history search unit 509 is added.

(Configuration history search procedure)
FIG. 24 shows a flowchart of the procedure for searching the configuration history analysis unit 509 for a configuration satisfying the specified service level from the past history.
First, in S2400, the configuration history analysis unit 509 receives the input service level (for a certain system) from the display / input unit 502. The service level is a numerical performance requirement such as response time and throughput that the system 204 should satisfy. In the following, the system 204 that is the service level designation target is simply referred to as a target system.

Next, in S2401, the configuration history analysis unit 509 refers to the baseline management table 600 and searches for an entry in which the system name 601 matches the specified system name. Next, the baseline number 606 is referenced, and the baseline data table 1000 is referenced based on the baseline number 606 to obtain a list of baseline data in the configuration of the system. Next, the service level specified in S2400 is compared with the acquired baseline data. For example, when the throughput of the number of requests to be processed by the system 204 is designated as the service level, the configuration history analysis unit 509 compares the request throughput baseline data with the service level to determine whether the requirement can be satisfied. Determine. If there is no baseline data satisfying the service level as a result of the determination, the process is terminated assuming that there is no configuration satisfying the service level in the history. If there is a system configuration satisfying the service level, the process advances to step S2403.

In step S2403, when there is a configuration satisfying the specified service level in the history, it is determined whether or not the configuration of the related system that shares resources with the system is the same as the current configuration in the history. . Specifically, the related system name 1401 and the related system configuration number 1402 of the entry (hereinafter simply referred to as entry 1) of the baseline management table 600 acquired in S2401 are referred to. Next, using them as a key, the baseline management table 600 is referenced again to obtain an entry of the relevant system, and it is checked whether or not the current flag 604 of the entry is “Y”. If the current flag 604 of all related systems is “Y”, the configuration of the related system is not different from the current configuration, that is, the specified service level can be satisfied with the configuration of the entry 1 described above. , Entry 1 is used as a search result, and the process ends. If all of the related system current flags 604 are not “Y”, that is, if there is an entry of “N”, the processing from the next S2404 is advanced on the corresponding related system entry.

In S2404, the degree of influence due to the fact that the configuration of the related system remaining in the history is different from the current configuration is evaluated. That is, in each configuration of the related system, the baselines of resources shared between the target system and the related system are compared, and the degree of divergence is evaluated. This evaluation process is the same as S1901 in FIG. Finally, the process ends with the pair of the deviation degree evaluated here and the data of entry 1 as a search result. In S2400, the administrator or the program who has designated the service level can determine whether or not to change the configuration of the target system remaining as a history in entry 1, with reference to the divergence as the search result.

According to this embodiment, a configuration that satisfies a specified service level can be searched and acquired from a past configuration history.

In Example 1, it was determined whether or not to reuse the previous baseline depending on whether or not the system configuration after the configuration change matches the previous system configuration. In the sixth embodiment, when the previous system configuration does not completely match, the “difference amount” between the system configuration after the configuration change and the previous system configuration is calculated, and the difference amount is the largest among the previous system configurations. Reuse baselines in small system configurations.

FIG. 25 shows a baseline selection processing flow in this embodiment. This processing flow is a detailed version of S101 in the schematic flowchart of baseline management shown in FIG. In other words, the system configuration closest to the system configuration after the configuration change is selected from the previous system configurations by the baseline selection processing of FIG. 25, and the baseline of the system configuration is reused in S102.

The baseline selection processing flow in FIG. 25 will be described.
In this processing flow, a system that reuses the baseline based on the virtual machine resource amount for each of the system configuration after the configuration change (hereinafter referred to as the current system configuration) and the previous system configuration (hereinafter referred to as the previous system configuration). select. In other words, it is based on the idea that if the difference in resource amount is small, the baseline will be close.

First, in S2500, the configuration comparison unit 506 refers to the baseline management table 600 and the configuration information table 700, and acquires information regarding the current system configuration, the virtual computer in the previous system configuration, and its resource amount. Next, the configuration comparison unit 506 checks, for each virtual computer of the current system configuration, whether the same virtual computer exists in the previous system configuration, and if it exists, the resource amount is equivalent (difference survey). ). If there is only one previous system configuration in which the difference investigation results are all the same, the process advances to S2501. If there are a plurality of previous system configurations in which the results of the difference investigation are all the same, the process proceeds to S2502. (Supplementary explanation, even if the resource amount of the virtual machine is the same, the physical machine on which the virtual machine operates may be different. Therefore, there may be multiple previous system configurations that have the same difference survey results). If there is no previous system configuration in which the results of the difference investigation are all the same, the process proceeds to S2503.

In S2501, the configuration comparison unit 506 selects a previous system configuration in which the difference investigation results are all the same in S2500 as a system for reusing the baseline, and proceeds to S102 (FIG. 11).

In S2502, the configuration comparison unit 506 selects the configuration closest to the current system configuration from the plurality of previous system configurations specified in S2500. That is, the correspondence relationship between the virtual computer and the physical computer in the current system configuration and the correspondence relationship between the virtual computer and the physical computer in the previous system configuration are compared, and the number of correspondence differences is calculated, and the number is minimized. Select the previous system configuration that is. For example, assume that virtual computer A is associated with physical computer A in the current system configuration. On the other hand, assume that virtual computer A is associated with physical computer B in the previous system configuration. For the other virtual machines in the current system configuration, there is no difference in the associated physical machines. In this case, the number of correspondence differences is “1”. The configuration comparison unit 506 selects a previous system configuration with the smallest number of calculated differences in correspondence among a plurality of previous system configurations as a target system configuration for reusing the baseline. When there are a plurality of previous system configurations having the smallest number of correspondence differences, the most recent system (see the usage time 605 of the baseline management table 600) is selected.

In S2503, the configuration comparison unit 506 calculates the sum of the differences between the resource amount of the virtual machine with the current system configuration and the resource amount of the virtual computer with the previous system configuration, and sets the previous system configuration with the minimum value as the baseline. Select for reuse. For example, it is assumed that the CPU of the virtual machine A having the current system configuration is 6 GHz. On the other hand, in the previous system configuration, the CPU of the same virtual machine A is assumed to be 8 GHz. In this case, the difference amount of the CPU resource is 2 GHz (calculated as an absolute value). The configuration comparison unit 506 similarly calculates the difference amount for each virtual computer having the current system configuration, and obtains the sum.

The resource difference amount may be a ratio to the previous resource included in the system. For example, it is assumed that the total CPU of virtual machines is 15 GHz in the current system configuration. On the other hand, it is assumed that the CPU total of the virtual computers in the first previous system configuration is 17 GHz, and the CPU total of the virtual computers in the second previous system configuration is 13 GHz. In this case, the resource difference amount is (17−15) /17=0.12 in the first previous system configuration. In the second previous system configuration, | (13-15) | /13=0.15. Therefore, the first previous system configuration with the same simple resource difference amount “2” but a smaller ratio to the resource amount of the entire system is selected.

When there are multiple resources to be compared, such as a CPU or memory, the sum of the resource differences for each resource may be calculated and added after multiplying them by weight, or limited to any one resource You may compare.

In S2504, in S2505, the configuration comparison unit 506 selects the previous system configuration with the smallest sum of resource amount differences as a system for reusing the baseline, and proceeds to S102 (FIG. 11).

S2505 is a process in the case where there are a plurality of previous system configurations with the smallest sum of resource amount differences (obtained by the process in S2503). The configuration comparison unit 506 selects the newest system (see the usage time 605 of the baseline management table 600) among these previous system configurations.

Although the sixth embodiment is described based on the first embodiment, the process of selecting the baseline of the system configuration with the smallest difference amount can also apply the second embodiment to the processing flow (FIG. 16). That is, in the second embodiment, in the baseline reuse processing flow (FIG. 16), the current system configuration is compared with the previous system configuration (S1201 and S1600). You may select as the object of reuse.

According to this embodiment, even when the system configuration after the configuration change does not completely match the previous system configuration, the system configuration with the closest configuration is selected and the baseline is reused. As a result, the number of baseline re-creations can be further reduced.

200: monitoring computer, 201: measurement computer, 202: physical computer, 203: virtual computer, 204: monitoring target system, 300: CPU, 301: memory, 302: display, 303: hard disk, 304: operating system, 305: performance Monitoring program, 306: hypervisor, 307: CPU, 308: memory, 309: display, 310: hard disk, 400: virtual switch, 401: NIC, 402: physical switch, 403: HBA, 404: SAN switch, 405: storage device , 500: Baseline management unit, 501: Baseline storage unit, 502: Display / input unit, 503: Configuration management unit, 504: Performance monitoring unit, 505: Baseline creation unit, 506: Configuration comparison unit, 507: Base Line comparison unit, 508: Cause analysis unit, 09: Configuration history search unit, 600: Baseline management table, 700: Configuration information table, 800: Component related table, 900: Performance information table, 1000: Baseline data table, 1400: Example of baseline change notification, 1500 : Approval table, 1800: Baseline comparison history table.

Claims (19)

1. A performance monitoring device that monitors the performance of an information processing system based on a baseline created from performance information history measured from the information processing system,
   A configuration storage unit for storing system configuration information of the information processing system;
   A configuration information management unit that assigns a unique configuration number to each different system configuration of the information processing system;
   A baseline storage unit that stores the baseline in association with the configuration number and the baseline;
   The configuration information management unit detects a system configuration change of the information processing system, and queries whether the system configuration information of the information processing system after the configuration change exists in the configuration storage unit;
   If the result of the inquiry about the presence or absence of the system configuration information after the configuration change of the information processing system by the configuration information management unit is,
   Obtaining a first baseline associated with a configuration number assigned to the system configuration after the system configuration change from the baseline storage unit;
   A performance monitoring device, wherein a second baseline currently used for performance monitoring is replaced with the first baseline.
2. The performance monitoring device according to claim 1,
   When the inquiry result is none, a third baseline is newly created from the performance information history of the information processing system after the system configuration change, and is given to the system configuration of the information processing system after the system configuration change Corresponding to the configuration number, the created third baseline is stored in the baseline storage unit, and the second baseline currently used for performance monitoring is replaced with the third baseline. A characteristic performance monitoring device.
3. The performance monitoring device according to claim 2,
   In the process of creating the third baseline after changing the system configuration of the information processing system,
   If the performance information measured from the information processing system is compared with the second baseline currently used for monitoring, and it is determined that the performance information indicates an abnormal value, an A performance monitoring apparatus characterized in that information indicating that a new baseline is being created is included in notification information indicating that a value has been detected.
4. The performance monitoring device according to claim 1,
   When there is no inquiry result, the information processing system after the system configuration change is compared with the system configuration information stored in the configuration storage unit, and the difference is calculated.
   Obtaining a third baseline associated with the configuration number assigned to the system configuration information stored in the configuration storage unit with the smallest difference;
   A performance monitoring apparatus, wherein a second baseline currently used for performance monitoring is replaced with the third baseline.
5. A performance monitoring device that monitors the performance of a first information processing system based on a baseline created from a performance information history measured from the first information processing system,
   A configuration storage unit for storing system configuration information of the first information processing system;
   A unique first configuration number is assigned to each different system configuration of the first information processing system, and a second information processing system that shares computing resources with the first information processing system , A configuration information management unit for storing the second configuration number uniquely assigned to each different system configuration of the second information processing system in association with each other;
   A baseline storage unit that stores the first configuration number, the second configuration number, and the baseline in association with each other;
   The configuration information management unit detects a system configuration change of the first information processing system, and determines whether or not system configuration information of the first information processing system after the configuration change exists in the configuration storage unit. Query,
   When the result of inquiring the presence / absence of the system configuration information after the configuration change of the first information processing system by the configuration information management unit is,
   Obtaining a first baseline associated with a configuration number assigned to the system configuration after the system configuration change of the first information processing system from the baseline storage unit;
   A performance monitoring apparatus that replaces a second baseline currently used for performance monitoring of the first information processing system with the first baseline.
6. The performance monitoring device according to claim 5, further comprising:
   The third configuration number associated with the first configuration number is assigned to the current system configuration of the second information processing system. Query whether it matches the configuration number of
   If the second configuration number and the third configuration number do not match,
   A third baseline is newly created from the performance information history of the second information processing system after the system configuration change of the first information processing system, and the first configuration number and the third configuration number are created. And the created third baseline in association with each other and stored in the baseline storage unit,
   Obtaining from the baseline storage unit the third baseline corresponding to the first configuration number and the third configuration number from the baseline storage unit;
   A performance monitoring apparatus, wherein a fourth baseline currently used for performance monitoring of the second information processing system is replaced with the third baseline.
7. The performance monitoring device according to claim 6,
   In the process of creating the third baseline after changing the system configuration of the first information processing system,
   When the performance information measured from the second information processing system is compared with the fourth baseline currently used for monitoring, and it is determined that the performance information indicates an abnormal value, the administrator A performance monitoring apparatus characterized in that information indicating that a new baseline is being created is included in notification information indicating that an abnormal value has been detected.
8. The performance monitoring device according to claim 7, wherein
   Before replacing the fourth baseline currently used for monitoring with the third baseline acquired from the baseline storage device,
   The performance monitoring apparatus, wherein the third baseline and the fourth baseline are displayed together on a management screen.
9. The performance monitoring device according to claim 6,
   Obtaining the first system configuration information of the second information processing system associated with the second configuration number from the configuration information storage unit;
   Obtaining second system configuration information of the second information processing system associated with the third configuration number from the configuration information storage unit;
   Identifying a computing resource that exists in common in the first system configuration information and the second system configuration information;
   Obtaining a baseline of the computing resource associated with the second configuration number from the baseline storage unit;
   Obtaining a baseline of the computational resource associated with the third configuration number from the baseline storage unit;
   A performance monitoring apparatus, characterized in that the degree of divergence between the acquired baselines is calculated, and the baseline is not recreated if the degree of divergence is less than a given threshold.
10. The performance monitoring device according to claim 6,
    When there is no inquiry result, a fifth baseline is newly created from the performance information history of the first information processing system after the system configuration change, and the first information processing system after the system configuration change The created fifth baseline is stored in the baseline storage unit in association with the configuration number assigned to the system configuration, and is used for performance monitoring of the first information processing system. A performance monitoring apparatus, wherein a baseline is replaced with the fifth baseline.
11. The performance monitoring device according to claim 10, wherein
    The fifth baseline;
    Compare with the second baseline currently used for monitoring and calculate the first divergence,
    The first divergence degree, the change in the system configuration of the first information processing system as system configuration change information, the system name of the first information processing system that created the fifth baseline, and A performance monitoring apparatus, wherein the first configuration number associated with a system configuration obtained by changing the configuration of the first information processing system is stored in a baseline change history storage unit in association with the first configuration number.
12. The performance monitoring device according to claim 11,
    When the first divergence degree of the first information processing system exceeds a predetermined threshold, the third base line of the second information processing system and the fourth base currently used for monitoring The second divergence degree is compared with the line, the calculated second divergence degree is associated with the first divergence degree of the first information processing system, and the baseline change is calculated. A performance monitoring apparatus characterized in that it is stored in a history storage unit.
13. The performance monitoring device according to claim 12, wherein
    If the first divergence degree stored in the baseline change history storage unit exceeds a predetermined threshold, the first change degree is stored in the baseline change history storage unit in association with the first divergence degree. If the read second divergence data is below a predetermined threshold value, the system configuration change information corresponding to the first divergence degree is used as a starting point of a baseline change. A performance monitoring device characterized by specifying
14. A configuration storage unit that stores system configuration information of the information processing system; a configuration information management unit that assigns a unique configuration number to each different system configuration of the information processing system; and the configuration number and the baseline are associated with each other A performance monitoring method comprising a baseline storage unit for storing the baseline, wherein the performance monitoring method monitors the performance of the information processing system based on a baseline created from a performance information history measured from the information processing system Because
    The performance monitoring device is:
    The configuration information management unit detects a system configuration change of the information processing system, and queries whether the system configuration information of the information processing system after the configuration change exists in the configuration storage unit,
    If the result of the inquiry about the presence or absence of the system configuration information after the configuration change of the information processing system by the configuration information management unit is,
    Obtaining a first baseline associated with a configuration number assigned to the system configuration after the system configuration change from the baseline storage unit;
    A performance monitoring method, wherein a second baseline currently used for performance monitoring is replaced with the first baseline.
15. A configuration storage unit for storing system configuration information of the first information processing system;
    A unique first configuration number is assigned to each different system configuration of the first information processing system, and a second information processing system that shares computing resources with the first information processing system , A configuration information management unit for storing the second configuration number uniquely assigned to each different system configuration of the second information processing system in association with each other;
    In a performance monitoring apparatus comprising a baseline storage unit that stores the first configuration number, the second configuration number, and the baseline in association with each other, the performance of the first information processing system A performance monitoring method for monitoring based on a baseline created from performance information history measured from one information processing system, wherein the performance monitoring device comprises:
    The configuration information management unit detects a system configuration change of the first information processing system, and determines whether or not system configuration information of the first information processing system after the configuration change exists in the configuration storage unit. Query,
    When the result of inquiring the presence / absence of the system configuration information after the configuration change of the first information processing system by the configuration information management unit is,
    Obtaining a first baseline associated with a configuration number assigned to the system configuration after the system configuration change of the first information processing system from the baseline storage unit;
    A performance monitoring method, wherein a second baseline currently used for performance monitoring of the first information processing system is replaced with the first baseline.
16. 16. The performance monitoring method according to claim 15, wherein the performance monitoring device further includes:
    The third configuration number associated with the first configuration number is assigned to the current system configuration of the second information processing system. Query whether it matches the configuration number of
    If the second configuration number and the third configuration number do not match,
    A third baseline is newly created from the performance information history of the second information processing system after the system configuration change of the first information processing system, and the first configuration number and the third configuration number are created. And the created third baseline in association with each other and stored in the baseline storage unit,
    Obtaining from the baseline storage unit the third baseline corresponding to the first configuration number and the third configuration number from the baseline storage unit;
    A performance monitoring method, wherein a fourth baseline currently used for performance monitoring of the second information processing system is replaced with the third baseline.
17. A configuration storage unit that stores system configuration information of the information processing system; a configuration information management unit that assigns a unique configuration number to each different system configuration of the information processing system; and the configuration number and the baseline are associated with each other A baseline storage unit that stores the baseline, and the performance monitoring device that monitors the performance of the information processing system based on a baseline created from performance information history measured from the information processing system,
    The configuration information management unit detects a system configuration change of the information processing system, and queries whether the system configuration information of the information processing system after the configuration change exists in the configuration storage unit,
    If the result of the inquiry about the presence or absence of the system configuration information after the configuration change of the information processing system by the configuration information management unit is,
    Obtaining a first baseline associated with a configuration number assigned to the system configuration after the system configuration change from the baseline storage unit;
    A performance monitoring program for executing a procedure for replacing a second baseline currently used for performance monitoring with the first baseline.
18. A configuration storage unit for storing system configuration information of the first information processing system;
    A unique first configuration number is assigned to each different system configuration of the first information processing system, and a second information processing system that shares computing resources with the first information processing system , A configuration information management unit for storing the second configuration number uniquely assigned to each different system configuration of the second information processing system in association with each other;
    A baseline storage unit that stores the first configuration number, the second configuration number, and the baseline in association with each other, and the performance of the first information processing system is determined by the first information processing system. In the performance monitoring device that monitors based on the baseline created from the performance information history measured from
    The configuration information management unit detects a system configuration change of the first information processing system,
    Queries whether the system configuration information of the first information processing system after the configuration change exists in the configuration storage unit,
    When the result of inquiring the presence / absence of the system configuration information after the configuration change of the first information processing system by the configuration information management unit is,
    Obtaining a first baseline associated with a configuration number assigned to the system configuration after the system configuration change of the first information processing system from the baseline storage unit;
    A performance monitoring program for executing a procedure for replacing a second baseline currently used for performance monitoring of the first information processing system with the first baseline.
19. The performance monitoring program according to claim 18, further comprising:
    The third configuration number associated with the first configuration number is assigned to the current system configuration of the second information processing system. Query whether it matches the configuration number of
    If the second configuration number and the third configuration number do not match,
    A third baseline is newly created from the performance information history of the second information processing system after the system configuration change of the first information processing system, and the first configuration number and the third configuration number are created. And the created third baseline in association with each other and stored in the baseline storage unit,
    Obtaining from the baseline storage unit the third baseline corresponding to the first configuration number and the third configuration number from the baseline storage unit;
    A performance monitoring program for executing a procedure for replacing a fourth baseline currently used for performance monitoring of the second information processing system with the third baseline.

Images