JP2009193153A - Management system, method for storing history information, and data structure of history information database - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently manage histories of changing configuration and collecting monitoring information related to a target system, by a database with a star schema structure. <P>SOLUTION: In this management system 100, a configuration information DB 3 stores configuration information related to a plurality of managed servers of the target system. A history information DB 4 having the star schema structure includes: a history fact table storing history information including the monitoring information related to each of the plurality of managed servers in association with a server ID associated to the managed server; and a server dimension table storing an attribute of the managed server in association with the server ID. A dimension table data addition part 11 adds a new record including an attribute value of the reconfigured managed server concerning the configuration change to the server dimension table in response to the configuration change of the terminal system. A history data addition part 21 stores the monitoring information collected from the target system in the history fact table. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a management system for performing asset management, status monitoring, provisioning, and the like of a target system including a plurality of managed elements, and more particularly, to a management system that stores a configuration change history and monitoring information collection history of the target system. .

  For example, in a management system that manages a target system such as a computer system including a plurality of computer terminals, a configuration information database (hereinafter referred to as a configuration information DB) is used for recording configuration information for asset management, status monitoring, provisioning, and the like. Is used). Here, the term “configuration information” in this specification means information related to the configuration of a plurality of managed elements (for example, computer terminals) that the target system (for example, a computer system) currently has. For example, when the target system is a computer system and the managed element is a computer terminal, the configuration information includes a computer name, an IP (Internet Protocol) address, an installed OS (Operating System) type, and installation of predetermined software. Presence / absence, version information of installed software, etc. are included.

  In Patent Document 1, as a conventional technique, a configuration information DB (“Configuration Management Database” in Patent Document 1) that records configuration information of the current target system (“Facility” in Patent Document 1), and configuration information A management system is described in which a history information DB (in Patent Document 1, “configuration history management database”) for managing a change history is provided independently. Thus, since the management system that stores only the current configuration information in the configuration information DB only needs to have records corresponding to the management target equipment, the data amount of the recorded data is small and the searchability is excellent. There is an advantage.

  Also, in Patent Document 2, as in the above-described prior art of Patent Document 1, a configuration information DB (“Configuration Information Database” in Patent Document 2) that records the current configuration information of the target system, and configuration information A management system (a “configuration information management server” in Patent Document 2) that separately and independently provides a history information DB (in Patent Document 2, “configuration change history database”) that records a change history is disclosed.

By the way, “star schema” is known as a database structure suitable for a data warehouse. For example, Patent Document 3 discloses a technique for speeding up a search when a star schema is used on a relational database regarding a database constituting a data warehouse system.
JP 2004-258733 A JP 2005-250788 A Japanese Patent Laid-Open No. 2001-265783

  The main purpose of the configuration information DB described above is to record and hold the current state of the target system. Therefore, the database structure of the configuration information DB is generally a structure that can immediately follow the configuration change of the target system and reflect the latest state. However, such a database structure is a structure in which it is difficult to keep the past state of the target system. Therefore, as disclosed in Patent Documents 1 and 2, a configuration information DB that records configuration information that requires immediate updating, and a history that records a history of configuration changes of a target system that tends to have a large amount of data. A configuration in which the information DB is provided separately is one of the appropriate configurations of the management system.

  However, Patent Documents 1 and 2 described above only disclose that the history information DB for recording the history of the configuration change is provided independently of the configuration information DB for holding the configuration information of the target system. There is no disclosure of a configuration that holds a collection history of monitoring information related to the target system in addition to the configuration change history in the history information DB. Here, the monitoring information related to the target system is performance information, failure occurrence information, and the like of the target system, and is collected by periodic polling by the management system or voluntary notification from the target system. For example, the performance information when the target system is a computer system including a plurality of computer terminals is a load status of a CP (Central Processing Unit), a type of software used, and the like.

  The present invention has been made based on the above-described knowledge, and provides a management system capable of efficiently managing the configuration change history and monitoring information collection history of the target system with a history information database having a star schema structure. For the purpose.

  The management system according to the first aspect of the present invention includes a configuration information database, a history information database, a configuration management means, a dimension table / data addition means, a monitoring information collection means, and a history data addition means.

  Here, the configuration information database stores configuration information related to a plurality of managed elements of the target system. The history information database is a database having a star schema structure, and stores history information including monitoring information relating to each of the plurality of managed elements in association with a dimension key value associated with the managed element. A managed element dimension table for storing attributes of the managed elements in association with the table and the dimension key;

  The configuration management means generates the configuration information corresponding to the target system after the configuration change and stores it in the configuration information database in response to the configuration change of the target system. The dimension table / data adding means adds a new record including an attribute value after the configuration change of the managed element related to the configuration change to the managed element dimension table in response to the configuration change of the target system. .

  Further, the monitoring information collecting means collects monitoring information related to the target system. The history data adding means stores the collected monitoring information as the history information in the history fact table.

  According to the first aspect of the present invention, the collection history of monitoring information can be accumulated by storing the monitoring information in the history fact table. In addition, according to the first aspect of the present invention, every time a configuration change of the target system occurs, an attribute after the configuration change of the managed element having the configuration change is additionally recorded in the managed element dimension table. For this reason, the configuration content of the past managed element is stored as a history in the managed element dimension table. That is, in the first aspect of the present invention, the configuration change history of the target system can be recorded by the managed element dimension table.

  According to the first aspect of the present invention, it is possible to efficiently manage the collection history of monitoring information related to the target system and the history of configuration change with a database having a star schema structure.

  Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings. In the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted as necessary for the sake of clarity.

<Embodiment 1 of the Invention>
The management system 100 according to the present embodiment is a management system that manages the current configuration of a computer system (not shown) having a plurality of servers as managed elements, and collects configuration change history and monitoring information. FIG. 1 is a block diagram showing the overall configuration of the management system 100.

  In FIG. 1, a configuration management component 1 performs configuration management of a plurality of servers (hereinafter referred to as managed servers) included in a computer system that is a target system. The configuration management component 1 includes a system configuration management unit 10 and a dimension table / data addition unit 11.

  The system configuration management unit 10 acquires configuration information of a plurality of managed servers, and updates the configuration information DB 3 so that the configuration information DB 3 reflects the current configuration of the plurality of managed servers. Specifically, the system configuration management unit 10 displays the configuration information held in the configuration information DB 3 in response to a configuration change such as a configuration change of a managed server, a new managed server addition, or a deletion of a managed server. Update. Here, the configuration information of the managed server includes, for example, a server name, an installed OS name, an IP address, an installation location, and the like.

  The dimension table / data adding unit 11 acquires the configuration change contents of the managed server collected by the system configuration management unit 10 and stores the configuration change history of the managed server in the history information DB 4 having a star schema structure. More specifically, the dimension table / data adding unit 11 newly adds a record indicating the configuration information of the server related to the configuration change to the server dimension table 42 included in the history information DB 4 having the star schema structure. Thus, the configuration change history of the managed server is saved. Details of the procedure for storing the configuration change history of the managed server in the server dimension table 42 will be described later.

  The system monitoring component 2 monitors the status of a plurality of managed servers included in the computer system that is the target system. The system monitoring component 2 includes a monitoring information acquisition unit 20 and a history data addition unit 21.

  The monitoring information acquisition unit 20 acquires monitoring information indicating the current state of a plurality of managed servers. Here, the monitored information of the managed server includes, for example, the CPU load status and various statistical information (the number of occurrences of failure events, the number of occurrences of system configuration changes, the number of software distributions, the number of backup / restore executions, etc.).

  The history data adding unit 21 stores the monitoring information acquired by the monitoring information acquiring unit 20 in the history information DB 4 as history information. More specifically, the history data adding unit 21 records monitoring information in the history fact table 40 included in the history information DB 4 having a star schema structure. Details of the procedure for recording the monitoring information of the managed server in the history fact table 40 will be described later.

  The configuration information DB 3 is a database that stores the current configuration information of the target system. An example of the data structure of the configuration information DB 3 is shown in FIG. FIG. 2 shows the data structure of the server configuration management table 30 included in the configuration information DB 3. The server configuration management table 30 includes records corresponding to managed elements included in the target system, that is, managed servers. Further, the attribute of each record in the example of FIG. 2 includes a server ID 310 for the configuration information DB, a server name 311, a group name 312, an OS name 313, an IP address 314, and a corresponding server ID 315 in the history information DB. .

  The server ID 310 for the configuration information DB is an identification code for identifying each of the plurality of managed servers, and is a main key attribute of the configuration information DB 3. The server name 311, the group name 312, the OS name 313, and the IP address 314 are the computer name assigned to the managed server, the name of the group to which the managed server belongs, the OS type installed on the managed server, and the Indicates the IP address assigned to the management server.

  On the other hand, the corresponding server ID 315 is a server ID assigned to the managed server in the server dimension table 42 included in the history information DB 4. That is, the configuration information DB 3 in FIG. 3 specifies the server ID 420 given to each managed server that the target system currently has in the history information DB 4 by referring to the corresponding server ID 315 in the configuration information DB 3. It is configured to be able to. Although details will be described later, a new record including a new server ID different from that before the configuration change is added to the server dimension table 42 every time a configuration change of the managed server occurs. Therefore, the corresponding server ID 315 in the server configuration management table 30 is rewritten with a new server ID in response to the addition of a new record to the server dimension table 42 with the occurrence of a configuration change of the managed server.

  It should be noted that the attributes of the managed server held in the configuration information DB 3 shown in FIG. 2 are merely examples, and it is needless to say that the attributes are not limited to those shown in FIG.

  The history information DB 4 is a database that holds a history of monitoring information and a history of configuration changes of managed servers. As described above, the history information DB 4 has a star schema structure. An example of the data structure of the history information DB 4 is shown in FIG. The history information DB 4 in FIG. 3 has two dimension tables, that is, a time dimension table 41 and a server dimension table 42, with a history fact table 40 in which monitoring information to be analyzed is sequentially stored.

  The history fact table 40 stores the monitoring information 402 collected by the system monitoring component 2 in association with the time ID 400 and the server ID 401. Here, the time ID 400 is a dimension key that associates the history fact table 40 with the time dimension table 41. Similarly, the server ID 401 is a dimension key that associates the history fact table 40 with the server dimension table 42.

  The time dimension table 41 defines an attribute of collection time, which is one of the dimensions (dimensions) of monitoring information stored in the history fact table 40. In the example of FIG. 3, the time dimension table 41 has five attributes of year 411, month 412, day 413, hour 414, and minute 415 in association with the dimension key, that is, the time ID 410 that is the primary key of the time dimension table 41. To do.

  The server dimension table 42 defines the attribute of the managed server that is one of the dimensions (dimensions) of the monitoring information stored in the history fact table 40. In the example of FIG. 3, the server dimension table 42 is associated with a server ID 420 that is a dimension key, that is, a primary key of the server dimension table 42, and includes four attributes of a server name 421, a group name 422, an OS name 423, and an IP address 424. Hold.

  Finally, the report creation unit 5 in FIG. 1 searches the history information DB 4 for data based on the data search condition and data aggregation condition requested by the user, and provides the obtained search result to the user.

  Next, the update process of the server dimension table 42 executed by the dimension table / data adding unit 11 in response to the occurrence of a configuration change of the managed server will be described in detail. FIG. 4 is a flowchart showing an example of the update procedure of the server dimension table 42.

  In step S <b> 11, the dimension table / data addition unit 11 acquires the contents of the configuration change of the managed server from the system configuration management unit 10.

  In step S <b> 12, the dimension table / data adding unit 11 adds server information regarding the managed server whose configuration has been changed to the server dimension table 42 as a new record.

  In step S <b> 13, the dimension table / data addition unit 11 acquires a new server ID 420 value assigned to the new record added to the server dimension table 42.

  In step S14, the dimension table / data adding unit 11 records the value of the server ID 420 in the history information DB 4 acquired in step S13 as the corresponding server ID 315 in the configuration information DB 3.

  Here, a specific example of the update of the server dimension table 42 executed by the processing procedure shown in FIG. 4 will be described with reference to FIGS. 5A and 5B. FIG. 5A shows a specific example of the state of the managed server 61 before the configuration change and the corresponding configuration information DB 3 and server dimension table 42. In the example of FIG. 5A, “A0001” is assigned as the server ID 310 on the configuration information DB 3 for the managed server 61. Further, “B1001” is assigned as the server ID 420 on the server dimension table 42 for the managed server 61. Further, the value “B1001” of the server ID 420 assigned to the managed server 61 is recorded as the corresponding server ID 315 on the configuration information DB 3.

  On the other hand, FIG. 5B shows a specific example of the state of the managed server 61 after the configuration change and the corresponding configuration information DB 3 and server dimension table 42. Specifically, the OS name has been changed from “CCC” to “DDD” as the installed OS of the managed server 61 is changed.

  The hatched cells in FIG. 5B indicate the update locations of the configuration information DB 3 and the server dimension table 42 that accompany the configuration change of the managed server 61. In response to the configuration change of the managed server 61, the OS name 313 on the configuration information DB 3 shown in FIG. 5B is updated by the system configuration management unit 10. In accordance with this, a new record 62 corresponding to the new configuration of the managed server 61 whose configuration has been changed is added to the server dimension table 42 by the dimension table / data adding unit 11. Further, the value of the corresponding server ID 315 of the record corresponding to the managed server 61 on the configuration information DB 3 is determined by the value “B1201” of the server ID 420 assigned to the managed server 61 in the new record 62 of the server dimension table 42. Updated.

  Subsequently, the update process of the history fact table 40 executed by the system monitoring component 2 that collects monitoring information will be described in detail below. FIG. 6 is a flowchart showing an example of a procedure for updating the history fact table 40.

  In step S21, the monitoring information collecting unit 20 collects monitoring information from the managed server in the target system. As described above, the monitoring information is performance information such as CPU load information of the managed server and failure information. Here, the collected monitoring information is used as history information stored in the history information DB 4.

  In step S22, the history data adding unit 21 acquires the current time. The current time acquired here is recorded in the history information DB 4 as the monitoring information acquisition time acquired in step S21. The monitoring information acquisition time may be notified to the system monitoring component 2 by the managed server 61 together with the monitoring information.

  In step S23, the history data adding unit 21 reads the value of the corresponding server ID 315 in the configuration information DB3. This value is used as the value of the server ID 401 that is a dimension key when adding history information to the history fact table 40.

  In step S24, the history data adding unit 21 adds the current time acquired in step S22 to the time dimension table 41 as a new record. Here, the value of the time ID 410 of the added new record is used as the value of the time ID 400 which is a dimension key when adding history information to the history fact table 40.

  Finally, in step S25, the history data adding unit 21 uses the value of the corresponding server ID 315 acquired in step S23 and the value of the time ID 410 generated in step S24 to newly monitor the monitoring information collected in step S21. The record is added to the history fact table 40 as a record.

  As described above, the management system 100 according to the present embodiment employs a star schema for the history information DB 4, and thus can enjoy the advantages of the star schema. That is, since the history information DB 4 has a simple structure centered on a fact table, a data-intensive query that spans a plurality of tables can be processed at high speed.

  In addition, the management system 100 can accumulate the monitoring information collection history by storing the monitoring information in the history fact table 40. In addition, each time a configuration change of a plurality of managed servers included in the target system occurs, the management system 100 creates a new record in the server dimension table 42 of the attribute after the configuration change related to the managed server having the configuration change. Record additional. For this reason, the configuration contents of the past managed server are stored in the server dimension table 42 as a history. That is, the management system 100 can record the configuration change history of the target system using the server dimension table 42.

  With this configuration, the search for the configuration change history of the managed server can be processed by scanning in the server dimension table 42. That is, it is not necessary to operate the history fact table 40 with a huge amount of data, and the configuration change history of the managed server can be searched at high speed.

  In addition, the management system 100 according to the present embodiment holds the corresponding server ID 315 in the configuration information DB 3 and adds data to the history fact table 40 using the value of the corresponding server ID 315 in the configuration information DB 3. It was. Since the server configuration management table 30 held in the configuration information DB 3 only holds the current state of the managed server, the data amount is relatively small compared to the server dimension table 42, and high-speed search is possible. Therefore, the management system 100 that holds the corresponding server ID 315 in the configuration information DB 3 can acquire the server ID 401, which is one of the dimension keys necessary for adding data to the history fact table 40, at high speed.

  FIG. 3 shows a configuration in which the history information DB 4 has one fact table (history fact table 40) and two dimension tables (time dimension table 41 and server dimension table 42). Of course, this is only an example. For example, the history information DB 4 may include a plurality of fact tables each storing different facts (that is, history information). The history information DB 4 may have an additional dimension table that defines other attributes related to the configuration of the managed server. At this time, the above-described method of storing the history information of the configuration change by adding the record related to the managed server updated to the server dimension table 42 may be applied to the additional dimension table.

<Other embodiments>
In order to record the occurrence time of the configuration change of the managed server, for example, the occurrence time 425 of the configuration change may be provided as an attribute of the server dimension table 42 as shown in FIG. In addition, the occurrence time of the configuration change may be recorded in the server dimension table 42 as a hierarchical structure with other dimension tables. For example, the time ID may be held as an attribute of the server dimension table 42 and the configuration change occurrence time may be acquired by referring to the time dimension table 41. In addition, when the status of the configuration change of the managed server is to be analyzed, the configuration change occurrence event may be recorded in the history fact table 40 as history information. With such a configuration, the relationship between the past configuration information of the managed server and the monitoring information such as the past performance information and failure information statistically recorded can be analyzed retrospectively.

  Note that the management system 100 described above is described as a target system that is a computer system including a plurality of managed servers. However, the target system is not limited to a computer system. Another example of the target system is a network including a plurality of communication devices such as a LAN switch and a router. The present invention can also be applied to a management system used by a telecom operator or the like for monitoring and controlling a plurality of communication devices and communication lines set in them.

  Furthermore, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the gist of the present invention described above.

It is a block diagram of the management system concerning Embodiment 1 of invention. It is a figure which shows an example of the data structure of structure information DB which the management system concerning Embodiment 1 of invention has. It is a figure which shows an example of the data structure of history information DB which the management system concerning Embodiment 1 of invention has. It is a flowchart which shows the update procedure of the server dimension table in the management system concerning Embodiment 1 of invention. It is a figure for demonstrating the update process of structure information DB and log | history information DB performed at the time of the structure change of a target system. It is a figure for demonstrating the update process of structure information DB and log | history information DB performed at the time of the structure change of a target system. It is a flowchart which shows the update procedure of the history fact table in the management system concerning Embodiment 1 of invention. It is a figure which shows the other example of the data structure of structure information DB which the management system concerning Embodiment 1 of invention has.

Explanation of symbols

100 management system 1 configuration management component 10 system configuration management unit 11 dimension table / data addition unit 2 system monitoring component 20 monitoring information collection unit 21 history data addition unit 3 configuration information database (configuration information DB)
30 Server configuration management table 4 History information database (history information DB)
40 History fact table 41 Time dimension table 42 Server dimension table 5 Report creation section

Claims (11)

A configuration information database for storing configuration information on a plurality of managed elements of the target system;
A history fact table that is a database of a star schema structure and stores history information including monitoring information related to each of the plurality of managed elements in association with a dimension key value associated with the managed element, and the dimension key A history information database comprising a managed element dimension table for storing attributes of the managed elements in association with
Configuration management means for generating the configuration information corresponding to the target system after the configuration change and storing it in the configuration information database in response to the occurrence of the configuration change of the target system;
Dimension table data addition means for adding a new record including an attribute value after the configuration change of the managed element according to the configuration change to the managed element dimension table according to the occurrence of the configuration change of the target system;
Monitoring information collecting means for collecting monitoring information on the target system;
History data adding means for storing the collected monitoring information as the history information in the history fact table;
A management system comprising: The configuration information database stores the dimension key value corresponding to each of the managed elements in association with the configuration information,
The history data adding means acquires the dimension key value to be recorded in the history fact table together with the monitoring information from the configuration information database, and stores a record including the acquired dimension key value and the monitoring information in the history fact table. The management system according to claim 1, which is added to the management system.   The management system according to claim 1, wherein the new record added to the managed element dimension table includes time information for specifying a configuration change occurrence time.   The management system according to claim 1, wherein the history data adding unit stores the occurrence of a configuration change in the target system in the history fact table as the history information. A history information storage method for storing a configuration change history and monitoring information collection history of a target system including a plurality of managed elements,
(A) generating a configuration information database that stores configuration information related to a plurality of managed elements of the target system;
A history fact table that is a database of a star schema structure and stores history information including monitoring information related to each of the plurality of managed elements in association with a dimension key value associated with the managed element, and the dimension key (B) generating a history information database comprising a managed element dimension table that stores attributes of the managed elements in association with
(C) generating the configuration information corresponding to the target system after the configuration change and storing it in the configuration information database in response to the occurrence of the configuration change of the target system;
(D) adding a new record including an attribute value after the configuration change of the managed element according to the configuration change to the managed element dimension table according to the occurrence of the configuration change of the target system;
Collecting monitoring information on the target system (e);
Storing the collected monitoring information as the history information in the history fact table;
A history information storage method comprising: The configuration information database further comprises a step (g) of storing the dimension key value corresponding to each of the managed elements in association with the configuration information,
In the step (d), the dimension key value to be recorded in the history fact table together with the monitoring information is acquired from the configuration information database, and a record including the acquired dimension key value and the monitoring information is stored in the history fact table. The method for storing history information according to claim 5, wherein the history information is added to the history information.   The history information storage method according to claim 6 or 7, wherein the new record added to the managed element dimension table includes time information for specifying a configuration change occurrence time.   The history information storage method according to claim 6 or 7, wherein in step (d), occurrence of a configuration change in the target system is stored in the history fact table as the history information. A data structure of a history information database for saving history information for saving a configuration change history and monitoring information collection history of a target system including a plurality of managed elements,
The history information database has a star schema structure and stores history information including the monitoring information related to each of the plurality of managed elements in association with a dimension key value associated with the managed element. And a managed element dimension table for storing attributes of the managed elements in association with the dimension key,
In the managed element dimension table, a new record including a new attribute value after the configuration change of the managed element related to the configuration change is added in response to the configuration change of the target system. The data structure of the history information database.   The data structure according to claim 9, wherein the new record includes time information for specifying an occurrence time of a configuration change.   The data structure according to claim 9 or 10, wherein occurrence of a configuration change in the target system is stored in the history fact table as the history information.

Images