Operation management devices, systems, methods, and programs

Abstract

An operation management device (1) is provided with: an extraction unit (11) that, on the basis of format information of a collection file collected from a component of an information system and on the basis of definition information of the delimiter between items defined by the component, extracts data for each item from the collection file; a storage unit (12) that associates and stores, in a collected data table, the extracted data and the items; and a comparison unit (13) that compares the data associated with an item in the collected data table with the data associated with the same corresponding item in an expected value table storing an expected value of each item in the collection file, and outputs the comparison result.

Description

Technical Field

[0001] The present invention relates to an operation management device, a system, a method, and a program.

Background Art

[0002] In recent years, with the large-scale expansion and complexity of information systems, the types of data to be collected from information systems have diversified. Here, information systems include various components such as hardware such as computers (servers), communication devices (network devices), and storage devices, and software such as an OS (Operating System), middleware, or applications. Then, an operator of an information system collects the network, hardware, and software setting contents of each component as files, analyzes the collected files, and performs setting confirmation, failure monitoring, etc.

[0003] Patent Document 1 discloses a technique related to a management system for environment definition information in a large-scale computing system. The management system stores a master file of system setting files for distribution and application to each computer in a large-scale computing system in a storage unit. Further, the management system generates form data in a predetermined unified format based on given environment definition parameter values and stores it in the storage unit. Then, the management system collects the environment definition files applied to each computer and checks the syntax of the files, the propriety of the setting parameter values, and the differences from the master file.

[0004] Patent Document 2 discloses a technique related to a master file difference automatic output device. The device refers to a master configuration comparison table file in which the correspondence relationship of items between old and new master files is defined in advance, and extracts the difference at the record unit between the old master and the new master. Then, the device uses the record unit difference file to compare the item values for each item in each record, and displays only the items whose item values have been updated.

Prior Art Documents

[0005] [Patent Document 1] Japanese Patent Publication No. 2004-046445 [Patent Document 2] Japanese Patent Publication No. 2014-099004 [Overview of the Initiative] [Problems that the invention aims to solve]

[0006] The technologies described in Patent Documents 1 and 2 analyze each file to be compared using their respective analysis logic and perform file-based difference comparisons. However, information systems have a wide variety of configuration files for each component, and it is necessary to consider not only differences in file formats but also differences in description rules for each component. As a result, various analysis processing modules are required, and in particular, there is a problem that the implementation of the item value extraction process becomes complicated.

[0007] The purpose of this disclosure is to provide an operational management device, system, method, and program for efficiently extracting various settings of an information system and supporting the verification of the validity of those settings, in light of the aforementioned issues. [Means for solving the problem]

[0008] The operation management device relating to the first aspect of this disclosure is An extraction means for extracting data item by item from a collection file based on the format information of the collection file collected from the components of the information system and the definition information of the delimiter character between items specified in the components, A storage means for associating the extracted data with the items and storing them in a collected data table, A comparison means that compares an expected value table storing the expected value of each item in the collection file with data associated with common items in the collection data table, and outputs the comparison result. It is equipped with.

[0009] The operational management system relating to the second aspect of this disclosure is: A collection device that collects files from the components of an information system, The operation management device connected to the aforementioned collection device, Equipped with, The aforementioned operation management device is An extraction means for extracting data item by item from a collection file collected by the collection device, based on the format information of the collection file and the definition information of delimiters between items defined in the components, A storage means for associating the extracted data with the items and storing them in a collected data table, A comparison means that compares an expected value table storing the expected value of each item in the collection file with data associated with common items in the collection data table, and outputs the comparison result. It is equipped with.

[0010] The operational management method relating to the third aspect of this disclosure is: Computers Based on the format information of the collected files gathered from the components of the information system and the definition information of the delimiters between items specified in those components, data is extracted from the collected files item by item. The extracted data and the items are associated and stored in the collected data table. The expected value table, which stores the expected value of each item in the collection file, and the data associated with common items in the collection data table are compared. Output the comparison results.

[0011] The operational management program relating to the fourth aspect of this disclosure is: An extraction process that extracts data item by item from a collection file based on the format information of the collection file collected from the components of the information system and the definition information of the delimiter character between items specified in the components, A storage process that associates the extracted data with the items and stores them in a collected data table, A comparison process that compares data associated with common items in an expected value table storing the expected values of each item in the collection file and the collection data table, and outputs the comparison result; causing a computer to execute the above.

Effect of the Invention

[0012] According to the present disclosure, it is possible to provide an operation management device, a system, a method, and a program for efficiently extracting various setting values of an information system and supporting verification of the validity of the setting values.

Brief Description of the Drawings

[0013] [Figure 1] It is a block diagram showing the configuration of the operation management device according to Embodiment 1. [Figure 2] It is a flowchart showing the flow of the operation management method according to Embodiment 1. [Figure 3] It is a block diagram showing the overall configuration including the operation management system according to Embodiment 2 and the information system to be managed. [Figure 4] It is a diagram for explaining an example of the collection file (CSV) according to Embodiment 2. [Figure 5] It is a diagram for explaining an example of the collection file (XML) according to Embodiment 2. [Figure 6] It is a block diagram showing the configuration of the operation management device according to Embodiment 2. [Figure 7] It is a diagram for explaining an example of the collection file definition information according to Embodiment 2. [Figure 8] It is a diagram for explaining an example of the delimiter definition information according to Embodiment 2. [Figure 9] It is a diagram for explaining an example of the expected value table according to Embodiment 2. [Figure 10] It is a diagram for explaining an example of the collection data table according to Embodiment 2. [Figure 11] It is a flowchart showing the flow of the expected value registration process according to Embodiment 2. [Figure 12] This flowchart shows the flow of the data collection registration process according to this second embodiment. [Figure 13] This flowchart shows the flow of the comparison process according to this second embodiment. [Figure 14] This figure shows an example of the comparison result information for all items according to this second embodiment. [Figure 15] This is a block diagram showing the configuration of the operation management device according to this third embodiment. [Figure 16] This figure shows an example of comparison definition information according to this third embodiment. [Figure 17] This flowchart shows the flow of the comparison process according to this third embodiment. [Figure 18] This figure shows an example of comparison result information for specified items according to this third embodiment. [Figure 19] This is a block diagram showing the configuration of the operation management device according to this fourth embodiment. [Figure 20] This flowchart shows the flow of the comparison process according to this embodiment 4. [Modes for carrying out the invention]

[0014] Embodiments of the present disclosure will be described in detail below with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and redundant explanations will be omitted where necessary for clarity.

[0015] <Embodiment 1> Figure 1 is a block diagram showing the configuration of the operation management device 1 according to this embodiment 1. The operation management device 1 is an information processing device for managing the operation of an information system. In particular, the operation management device 1 compares the setting value of each setting item included in the collection file collected from the components of the information system with the expected value of that setting item. Here, the components refer to the hardware and software that make up the information system. Hardware includes, for example, computers (servers), communication equipment (network equipment), storage devices, etc. Software includes operating systems, middleware, or applications, etc. However, the components of the information system are not limited to these.

[0016] The operation management device 1 comprises an extraction unit 11, a storage unit 12, and a comparison unit 13. The extraction unit 11 extracts data item by item from the collected file based on the format information of the collected file collected from the components of the information system and the definition information of the delimiter characters between items specified in the components. Here, the format information is information that defines the format of the file. For example, in the case of an XML (Extensible Markup Language) file, the format information is the XML schema or DTD (Document Type Definition), and in the case of a CSV (Comma-Separated Values) file, it is the case that newline characters are used to represent records and commas are used to separate the data.

[0017] The storage unit 12 associates the extracted data with the corresponding items and stores them in the collected data table. The comparison unit 13 compares the data associated with common items in the expected value table and the collected data table and outputs the comparison results.

[0018] Here, the expected value table is a table that stores the expected value of each item in the collection file. Furthermore, the format information, the definition information of the delimiter between items, the expected value table, and the collection data table are all stored in the internal storage device of the operation management device 1, or in an external storage device connected to the operation management device 1.

[0019] Figure 2 is a flowchart showing the flow of the operation management method according to this embodiment 1. First, the extraction unit 11 extracts data from the collection file item by item based on the format information of the collection file and the definition information of the delimiter between items (S11). Here, the collection file is assumed to have been collected in advance from the components of the information system by the operation management device 1 or another computer. The delimiter between items is assumed to be a character defined in the components. For example, if the collection file is a CSV file, the delimiter between items is a character other than a newline character and a comma. On the other hand, if the collection file is an XML file, the delimiter between items may include a comma.

[0020] Next, the storage unit 12 associates the extracted data with the corresponding items and stores them in the collected data table (S12). Then, the comparison unit 13 compares the data associated with common items in the expected value table and the collected data table (S13). After that, the comparison unit 13 outputs the comparison results (S14).

[0021] Thus, the operation management device 1 according to this embodiment not only analyzes the collected files according to the file format, but also analyzes them using delimiters between items defined in the components. Therefore, it can appropriately extract data for each item from collected files of various formats. Furthermore, since both the expected value table and the collected data table associate items with data (expected values ​​or collected data), comparison between the tables is easy. Therefore, it can efficiently extract various setting values ​​of the information system and support the verification of the validity of the setting values.

[0022] The operation management device 1 includes a processor, memory, and storage device (not shown in the diagram). The storage device stores a computer program that implements the operation management method according to this embodiment. The processor then loads the computer program from the storage device into the memory and executes the computer program. In this way, the processor realizes the functions of the extraction unit 11, the storage unit 12, and the comparison unit 13.

[0023] Alternatively, each component of the operation management device 1 may be implemented with dedicated hardware. Furthermore, some or all of the components of each device may be implemented by general-purpose or dedicated circuits, processors, etc., or combinations thereof. These may be composed of a single chip or multiple chips connected via a bus. Some or all of the components of each device may be implemented by a combination of the aforementioned circuits, etc., and programs. Additionally, a CPU (Central Processing Unit), GPU (Graphics Processing Unit), FPGA (Field-Programmable Gate Array), quantum processor (quantum computer control chip), etc., can be used as the processor.

[0024] <Embodiment 2> This second embodiment is a specific example of the first embodiment described above. Figure 3 is a block diagram showing the overall configuration including the operation management system 200 and the managed information system 100 according to this second embodiment. The information system 100 and the operation management system 200 are connected via a network N. Network N is a communication network including a wireless communication network, a mobile phone network, etc. Network N may also include the Internet. Furthermore, the communication network is not limited by the type of communication protocol.

[0025] The information system 100 includes multiple components. For example, the information system 100 comprises a network device 101, servers 111, 112, ... 11n (where n is a natural number greater than or equal to 1), and storage devices 121, ... 12m (where m is a natural number greater than or equal to 1). In this example, the network device 101 is connected to the network N and each of the servers 111 to 11n, and each of the servers 111 to 11n is connected to each of the storage devices 121 to 12m. However, the hardware configuration and connection relationships of the information system 100 are not limited to these.

[0026] Furthermore, each of the NW device 101, servers 111-11n, and storage devices 121-12m may be configured to output configuration values ​​in hardware, firmware, OS, middleware, applications, etc., as configuration files via a predetermined command. Alternatively, each of the NW device 101, servers 111-11n, and storage devices 121-12m may be configured to output software logs, etc., as log files via a predetermined command. Alternatively, each of the NW device 101, servers 111-11n, and storage devices 121-12m may output configuration files or log files to internal storage or external storage devices. A configuration file or log file is a file in which built values ​​(attribute values, parameter values) are recorded for each of multiple items (or attributes), and is an example of a collected file.

[0027] Figure 4 illustrates an example of a collection file 3a (CSV) according to this second embodiment. The collection file 3a is a CSV file in which each data record is separated by a newline character, and each item value within the data record is separated by a comma character ",". Furthermore, the components of the collection file 3a are defined to have a unique specification, where the string between commas contains multiple item values, and the items are separated by a semicolon character ";". For example, the first record in the collection file 3a is the string "R1,aa1;aa2,bbb,ccc", and the comma and semicolon characters indicate that it contains five item values: "R1", "aa1", "aa2", "bbb", and "ccc".

[0028] Figure 5 illustrates an example of a collection file 3b (XML) according to this second embodiment. The collection file 3b is an XML file in which each data record and its item names and item values ​​are described according to format information such as XML tag definitions. In this case, the format information corresponding to the collection file 3b will define, for example, that it is in XML format. The format information may also define that the element of the data record is "record", its child elements are "element1", "element2", and the child elements of "element1" are multiple "element11". Furthermore, the collection file 3b is assumed to have a unique specification in which the components of the collection source are defined to separate the element values ​​within "element2" with the delimiter character "$". For example, the first record of the collection file 3b will contain the item values ​​"R1", "ccc", "d1", "x1", "d2", "x2", "e11", and "e1y".

[0029] Returning to Figure 3, let's continue the explanation. The operation management system 200 comprises a collection device 201, an operation management device 202, and a management terminal 203. Here, we show that the collection device 201 and the operation management device 202 are connected, and the operation management device 202 and the management terminal 203 are connected. Note that some or all of the collection device 201, the operation management device 202, and the management terminal 203 may be composed of the same hardware. Alternatively, the collection device 201 and the operation management device 202 may be redundantly configured using multiple computers. Also, there may be multiple management terminals 203.

[0030] The data collection device 201 collects configuration files or log files from each component of the information system 100 via the network N at predetermined timings and stores them internally. Alternatively, the data collection device 201 may transmit the collected files to the operation management device 202.

[0031] The operation management device 202 is an example of the operation management device 1 described above. Based on format information and delimiter definition information, the operation management device 202 registers the expected values ​​for each item in various collection files into an expected value table. The operation management device 202 also registers the data for each item from various collection files into a collected data table based on format information and delimiter definition information. Then, for a specific collection file, the operation management device 202 compares the data associated with common items in the expected value table and the collected data table and outputs the comparison result. Note that the operation management device 202 may be redundantly implemented on multiple computers, and each functional block may be implemented on multiple computers.

[0032] Figure 6 is a block diagram showing the configuration of the 202 operation management device according to this second embodiment. The operation management device 202 comprises a storage unit 210, a memory 220, a communication unit 230, and a control unit 240. The storage unit 210 is an example of a storage device such as a hard disk or flash memory. The storage unit 210 stores the operation management program 211, collection file definition information 212, format information 213, delimiter definition information 214, expected value table 215, and collection data table 216. Note that some or all of the collection file definition information 212, format information 213, delimiter definition information 214, expected value table 215, and collection data table 216 may be stored in an external storage device connected to the operation management device 202. The operation management program 211 is a computer program on which the operation management processing according to this second embodiment is implemented.

[0033] The file collection definition information 212 defines the files to be collected by the collection device 201. The file collection definition information 212 defines the components of the source of the files to be collected, the path (directory name) where the files are saved, the file name, etc.

[0034] Figure 7 illustrates an example of the collected file definition information 212 according to this second embodiment. The collected file definition information 212 is information that associates the file ID, host name, path, and file name.

[0035] Returning to Figure 6, we continue the explanation. Format information 213 is information that defines the format corresponding to the file format of the collected file. Format information 213 may be defined for each file ID in the collected file definition information 212. For example, format information 213 may include definition information for CSV format, XML format, etc. In the case of XML format, various tags may be defined for each collected file.

[0036] Delimiter definition information 214 defines the delimiter characters between items specified for each component of the information system. In other words, delimiter definition information 214 defines the way items are written, as uniquely defined by each component, in addition to the definitions in the format information 213 described above. In the following, the delimiter characters may be referred to as delimiters or delimiter characters.

[0037] Figure 8 illustrates an example of delimiter definition information 214 according to this second embodiment. Delimiter definition information 214 is information that associates No., file ID, item information, and delimiter. Here, item information is, for example, the order (position information) of elements within a record in the case of CSV format, and the element name (tag name) in the case of XML format. For example, file ID "f1" is a CSV file according to format information 213, so records and items are usually separated by newline characters and comma characters. In addition to this, No. "1" of delimiter definition information 214 indicates that the delimiter ";" is used as the separator between items in file ID "f1" and item information "2". In the collected file 3a in Figure 4 described above, the second element "aa1;aa2" when separated by a comma means that the two item values ​​"aa1" and "aa2" are set with the delimiter ";".

[0038] Furthermore, the delimiter definition information 214 may define multiple delimiters for a particular component. For example, since file ID "f2" is an XML file according to format information 213, the records and the values ​​of each item are usually described based on the tag definitions. In addition to this, delimiter definition information 214 No. "2" indicates that the delimiter "=" is used as the delimiter between items in file ID "f2" and item information "element11". Then, delimiter definition information 214 No. "3" indicates that the delimiter "$" is used as the delimiter between items in file ID "f2" and item information "element2". In the collected file 3b in Figure 5 described above, this means that in "element11" of record R1, the delimiter "=" is used to set two item values ​​"d1" and "x1", and "d2" and "x2". Furthermore, in collected file 3b, the "element2" of record R1 has two item values, "e11" and "e1y," set with the delimiter "$". In other words, in a single collected file 3b, two types of delimiters are defined in addition to the usual XML tag definitions. Note that three or more delimiters may be defined for a specific component. This allows for flexible handling of a wide variety of item definitions, not only for general file format definitions (format information), but also for files with the same extension or file format. For example, format information 213 can define general format information common to multiple collected files. If some of the collected files have a unique specification, the item definitions for the differences from format information 213 can be defined in delimiter definition information 214. This prevents duplicate definitions, eliminates the need to modify the data extraction process for each type of collected file, and reduces maintenance costs.

[0039] From the above, it can be said that the item information of the collected files (item name, order of items, position of elements) is defined across both the format information 213 and the delimiter definition information 214. However, the delimiter definition information 214 does not have to be defined for all collected files defined in the collected file definition information 212. In other words, some collected files may not be defined in the delimiter definition information 214, but their item information may be defined by the format information 213.

[0040] Returning to Figure 6, we continue the explanation. The expected value table 215 is a table that stores expected values ​​to be compared with the data for each item in the collection file. Figure 9 is a diagram illustrating an example of the expected value table 215 according to this second embodiment. Figure 9 is an example in which the data 2152 for each item 2151 in each collection file defined in the collection file definition information 212 is stored as expected values. Item 2151 is a pair of record number and element number.

[0041] Returning to Figure 6, we continue the explanation. The collected data table 216 is a table that stores the data (collected data) in each collection file defined in the collection file definition information 212, with each item associated with the data. Figure 10 is a diagram illustrating an example of the collected data table 216 according to this second embodiment. Figure 10 is an example in which data 2162 for each item 2161 extracted from the collection files 3a and 3b based on the format information 213 and delimiter definition information 214 is stored. Item 2161 is a pair of record number and element number. Note that the data "e1y" in data 2163 is different from the data "e12" in the corresponding item (record number "1", element number "8") in the expected value table 215.

[0042] Note that in Figures 9 and 10, the data structures (attribute names and attribute order) of the expected value table 215 and the collected data table 216 are shown to be identical, but this is not necessarily required. The expected value table 215 and the collected data table 216 only need to have the target collection file, item (or item name, item information), and item value as attributes.

[0043] Furthermore, while the examples in Figures 9 and 10 included element names (R1, ccc, d1, d2, etc.) as items in the XML file, this is not limited to this. For example, R1 and R2 in the collection file 3b may be used as record names and record number values. Alternatively, the name attributes "d1" and "d2" of "element1" in the collection file 3b may be used as item names and element number values. In other words, the expected value table 215 and the collected data table 216 may be stored as record number "R1", element number "d1", and data "x1".

[0044] Returning to Figure 6, we continue the explanation. Memory 220 is a volatile storage device such as RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 240 is operating. The communication unit 230 is a communication interface between the inside of the operation management device 202 and the outside.

[0045] The control unit 240 is a processor, or control device, that controls each component of the operation management device 202. The control unit 240 loads the operation management program 211 from the storage unit 210 into the memory 220 and executes the operation management program 211. In this way, the control unit 240 realizes the functions of the registration unit 241, extraction unit 242, storage unit 243, comparison unit 244, and output unit 245.

[0046] The registration unit 241 acquires the collection file from the collection device 201 based on the collection file definition information 212, and uses the extraction unit 242 and storage unit 243 (described later) to register the data for each item extracted from the collection file into the expected value table 215 or the collection data table 216. In other words, the registration unit 241, extraction unit 242, and storage unit 243 perform the expected value registration process and the collection data registration process.

[0047] The extraction unit 242 is an example of the extraction unit 11 described above. Based on the format information 213 and delimiter definition information 214 of the collection file to be processed, the extraction unit 242 extracts data item by item from the collection file collected by the collection device 201. Specifically, the extraction unit 242 extracts record data, which is a string of records, from the collection file according to the format information 213, divides the record data using the delimiter defined in the delimiter definition information 214, and extracts the divided strings as data for each item.

[0048] The storage unit 243 is an example of the storage unit 12 described above. The storage unit 243 associates the data extracted by the extraction unit 242 with the corresponding items and stores them in the collected data table 216. Furthermore, when the storage unit 243 obtains the expected value for each item in the collected file, it associates the expected value with the corresponding item and stores it in the expected value table 215.

[0049] The comparison unit 244 compares the data in the collection files to be compared that are associated with common items in the expected value table 215 and the collected data table 216.

[0050] The output unit 245 outputs the comparison result from the comparison unit 244. For example, the output unit 245 outputs the comparison result to the management terminal 203. Note that the comparison unit 244 and the output unit 245 are examples of the comparison unit 13 described above.

[0051] Returning to Figure 3, let's continue the explanation. The management terminal 203 is a terminal device operated by the administrator of the operation management system 200, such as a personal computer. The management terminal 203 is connected to the operation management device 202 via a network or the like, and accesses the operation management device 202 to input information, etc., in response to the administrator's operations. The management terminal 203 may also be connected to the collection device 201 and network N.

[0052] Figure 11 is a flowchart showing the flow of the expected value registration process according to this second embodiment. Here, a master file is used in which expected values ​​are set for each item in a file of the same format as the collection file. For example, the collection file collected during the initial setup when building the environment of the components within the information system 100 may be used as the master file. Alternatively, instead of a master file, the administrator may input the expected values ​​for each item via the management terminal 203 and register them in the expected value table 215 of the operation management device 202.

[0053] First, the management terminal 203 sends an expected value registration request, including the master file, to the operation management device 202 in response to the administrator's operation. At this time, the management terminal 203 may also include the file ID of the collected file definition information 212 in the expected value registration request. In response, the registration unit 241 of the operation management device 202 obtains the master file from the management terminal 203 (S201).

[0054] Next, the extraction unit 242 identifies the file ID included in the expected value registration request and, by referring to the collected file definition information 212, identifies the type of master file obtained in step S201. Then, the extraction unit 242 extracts record data on a record-by-record basis from the master file according to the format information 213 (S202). Specifically, the extraction unit 242 analyzes the master file according to the format corresponding to the identified file ID in the format information 213 and extracts the record data.

[0055] Then, the extraction unit 242 divides the record data using the delimiter defined in the delimiter definition information 214, and extracts the divided strings as data (expected values) for each item (S203).

[0056] Subsequently, the storage unit 243 associates the expected value with the item and stores it in the expected value table 215 (S204). As a result, the expected value is stored in association with the item, for example, as shown in Figure 9 above.

[0057] Figure 12 is a flowchart illustrating the flow of the data collection registration process according to this second embodiment. As a prerequisite, the collection device 201 has already collected each collection file defined in the collection file definition information 212 from each component of the information system 100 via the network N. Then, the registration unit 241 of the operation management device 202 acquires the collection files from the collection device 201 (S211). Note that the collection files may include a file ID. Alternatively, the registration unit 241 may acquire the collection files by specifying a set of file ID, host name, path, and file name to the collection device 201.

[0058] Next, the extraction unit 242 extracts record data on a record-by-record basis from the collection file according to the format information 213, similar to step S202 described above (S212). Then, the extraction unit 242 divides the record data using the delimiter defined in the delimiter definition information 214, similar to step S203 described above, and extracts the divided strings as data for each item (S213).

[0059] Subsequently, the storage unit 243 associates the extracted data with the corresponding items and stores them in the collected data table 216 (S214). As a result, the collected data is stored in association with the items, for example, as shown in Figure 10 above.

[0060] Figure 13 is a flowchart showing the flow of the comparison process according to this embodiment 2. The operation management device 202 executes the comparison process following Figure 12, or at any arbitrary timing. For example, the management terminal 203 receives the specification of the file ID of the file to be compared by the administrator and sends the file ID to the operation management device 202. Alternatively, the management terminal 203 receives the specification of the hostname, path, and filename of the file to be compared by the administrator and sends these to the operation management device 202. In response to these, the comparison unit 244 of the operation management device 202 receives the specification of the file to be compared (S221). Specifically, the comparison unit 244 refers to the collected file definition information 212 and identifies the file to be compared from the specified file ID. For example, if "f2" is specified as the file ID, the comparison unit 244 identifies the hostname "Server A", path " / etc", and filename "def.xml".

[0061] Next, the comparison unit 244 retrieves data from the expected value table 215 and the collected data table 216 (S222). For example, the comparison unit 244 reads the hostname "Server A", path " / etc", and filename "def.xml" entries and data from the expected value table 215 and the collected data table 216.

[0062] The comparison unit 244 then compares the acquired data item by item (S223). For example, the comparison unit 244 compares the expected value "R1" for No. "101" in the expected value table 215 with the expected value "R1" for No. "101" in the collected data table 216. The comparison unit 244 also compares the expected value "e12" for No. "108" in the expected value table 215 with the expected value "e1y" for No. "108" in the collected data table 216.

[0063] Then, the comparison unit 244 generates the comparison result (S224). Specifically, if the data matches in the comparison in step S223, the comparison unit 244 sets the comparison result to "○", and if the data does not match, it sets the comparison result to "×". Then, the comparison unit 244 generates screen display data including the comparison result.

[0064] Subsequently, the output unit 245 outputs the comparison results to the management terminal 203 (S225). Specifically, the output unit 245 sends the generated screen display data to the management terminal 203. In response, the management terminal 203 displays the received screen display data on its screen.

[0065] Figure 14 shows an example of the comparison result information 4 for all items according to this embodiment 2. The comparison result information 4 includes the comparison target file information 40, items 41, master data 42, comparison result 43, and collected data 44. The comparison target file information 40 displays information about the comparison target file specified and identified in step S221. Item 41 is a pair of record number and element number. Here, it is shown that items from No. "101" onwards from the expected value table 215 in Figure 9 and the collected data table 216 in Figure 10 are displayed. The master data 42 is the expected value obtained from the expected value table 215 in step S222, and the collected data 44 is the data value obtained from the collected data table 216 in step S222. The comparison result 43 is the comparison result for each item generated in step S224. In this example, the comparison result 45 shows that the expected value and the collected data do not match.

[0066] Thus, in this embodiment, by analyzing the collected files using delimiter definition information 214 in addition to format information 213, data can be appropriately extracted using the same extraction process even with a wide variety of file formats, especially those with item settings specific to the constituent elements. For example, even with multiple XML files sharing the same XML schema, which is an example of format information 213, one application server may interpret item values ​​by separating them using its own delimiter within the element values ​​of defined tags. On the other hand, even with configuration files of the same XML schema, a DB server may interpret item values ​​by separating them using different delimiters for element values ​​of different tags. In such cases, it was usually necessary to define separate format information or customize the extraction processing module individually. In contrast, with this embodiment, parts of the item definition common to multiple collected files are defined in format information 213, and unique parts are defined in delimiter definition information 214, allowing for flexible handling of a wide variety of file formats. Furthermore, since partial format differences can be defined in delimiter definition information 214 and handled by the same extraction processing module, the amount of definition required is reduced, and the complexity of modifying the extraction processing module is lessened.

[0067] Furthermore, by unifying the data structure between the expected value table 215 and the collected data table 216, comparison processing can be simplified, improving processing efficiency. In addition, visualizing the comparison results allows administrators to easily see the results.

[0068] <Embodiment 3> This third embodiment is a modification of the second embodiment described above. In this third embodiment, the comparison process is made more efficient and the confirmation of the comparison results is made easier by narrowing down the items to be compared. The overall configuration of this embodiment, including the operation management system and the information system to be managed, is the same as in Figure 3 described above, and explanations that overlap with the second embodiment, including other details, will be omitted as appropriate.

[0069] Figure 15 is a block diagram showing the configuration of the operation management device 202a according to this third embodiment. Compared to Figure 6 described above, the operation management device 202a has the operation management program 211a and comparison unit 244a replaced, and comparison definition information 217 added. The other configurations are the same as those of the operation management device 202 described above.

[0070] The operation management program 211a is a computer program that implements the operation management processing and the like according to this embodiment 3. The comparison definition information 217 is information that defines the items to be compared for each file. In other words, the comparison definition information 217 is used to narrow down the items to be compared.

[0071] Figure 16 shows an example of comparison definition information 217 according to this third embodiment. Comparison definition information 217 is information that associates No., definition name, path, file name, record number, and element number. The record number and element number are item 2171. Here, "Definition A" shows that record number "1" and element number "4" of "abc.csv" are used as the comparison target, and other items in the same file are excluded from the comparison. Similarly, "Definition B" shows that record number "1" and element number "8" of "def.xml" are used as the comparison target, and other items in the same file are excluded from the comparison. Note that Figure 16 is for illustrative purposes only.

[0072] Returning to Figure 15, the explanation continues. The comparison unit 244a compares the data associated with the specified items in the collection file in the expected value table 215 and the collected data table 216, and obtains the comparison result.

[0073] Figure 17 is a flowchart showing the flow of the comparison process according to this embodiment 3. Compared to Figure 13 described above, Figure 17 has S221a added after step S221, and step S222 is replaced by S222a. The following will mainly explain the differences from Figure 13.

[0074] After step S221, the comparison unit 244a identifies the items to be compared from the comparison definition information 217 (S221a). For example, if "f2" is specified as the file ID, the comparison unit 244a identifies the record number "1" and element number "8" of "def.xml" in "Definition B" from the comparison definition information 217 as the items to be compared.

[0075] Then, the comparison unit 244a retrieves data for the items in the specified records among the specified comparison target files from the expected value table 215 and the collected data table 216 (S222a). For example, the comparison unit 244a retrieves the expected value "e12" from the expected value table 215 and the collected data "e1y" from the collected data table 216.

[0076] Then, the comparison unit 244a compares the acquired data item by item (S223). For example, the comparison unit 244a determines whether the expected value "e12" and the collected data "e1y" match. Then, the comparison unit 244a generates the comparison result (S224). Here, The comparison unit 244a sets the comparison result to "×". Then, the comparison unit 244a generates screen display data that includes the expected value "e12", the collected data "e1y", and the comparison result "×".

[0077] Subsequently, the output unit 245 outputs the comparison results to the management terminal 203 (S225). Figure 18 shows an example of comparison result information 4a for a specified item according to this embodiment 3. The comparison result information 4a includes comparison target definition information 40a, item 41, master data 42, comparison result 43, and collected data 44. The comparison target definition information 40a displays information about the comparison target file identified in step S221a and its definition. The collected data 44 from item 41 shows that it has been narrowed down to the comparison result 45 compared to Figure 14 described above.

[0078] In the above-described embodiment 2, the comparison results between expected values ​​and collected data were displayed for all items in the comparison file. However, administrators often identify the most important items to compare through daily monitoring. Furthermore, the comparison results for all items are voluminous, and there is a risk of overlooking the comparison results for highly important items. Therefore, in this embodiment, the comparison target items are narrowed down during the comparison process by pre-setting the comparison definition information 217. This makes the comparison process more efficient, facilitates administrators to check the comparison results, and in particular, enables efficient detection of discrepancies in highly important items.

[0079] Furthermore, the operation management device 202 may, during the comparison process, accept a selection from the management terminal 203 to compare all items or only the items set in the comparison definition information 217, and execute the comparison process according to the selection. In addition, the comparison definition information 217 may contain multiple types of definition information for the same collection file. This makes it easy to switch the items to be compared depending on the situation.

[0080] <Embodiment 4> This fourth embodiment is a modification of the second or third embodiment described above. In the second embodiment described above, an example was shown in which the master file was collected from the same components as the collection file. In contrast, in this fourth embodiment, the collection file of another component with many common settings is used as the expected value. For example, if a second server is built to make the first server redundant, after the first server has already been built in the information system, there are many common settings. In this case, the setting value of the collection file of the first server is used as the expected value of the collection file of the second server. This makes it possible to efficiently check the differences by comparing multiple servers side by side. The overall configuration including the operation management system and the information system to be managed in this embodiment is the same as in Figure 3 described above, and explanations that overlap with the second embodiment, including other details, will be omitted as appropriate.

[0081] Figure 19 is a block diagram showing the configuration of the operation management device 202b according to this embodiment 4. Compared to Figure 6 described above, the operation management device 202b has the operation management program 211b and comparison unit 244b replaced, and the expected value table 215 deleted. The other configurations are the same as those of the operation management device 202 described above.

[0082] The operation management program 211b is a computer program that implements the operation management processing and the like according to this embodiment 4. The collected data table 216 includes a first collected data table and a second collected data table. Here, the first collected data table is a table that stores data extracted from a first collection file collected from a first server, which is a component of the information system. The first collected data table is used as equivalent to the expected value table 215 described above. The second collected data table is a table that stores data extracted from a second collection file collected from a second server, which is a component of the information system.

[0083] The comparison unit 244b compares data associated with common items in the first and second data collection tables.

[0084] Figure 20 is a flowchart showing the flow of the comparison process according to this embodiment 4. Compared to Figure 13 described above, Figure 20 has S221b added after step S221, and step S222 is replaced by S222b. The differences from Figure 13 will be explained below.

[0085] After step S221, the comparison unit 244b accepts the designation of the expected value server and the comparison server (S221b). For example, the comparison unit 244b accepts the designation of the first server as the expected value server and the second server as the comparison server.

[0086] Then, the comparison unit 244b retrieves each data from the data collection table 216 for the files to be compared (S222b). At this time, the comparison unit 244b retrieves the data from the expected value server from the data collection table 216 as the expected value. The comparison unit 244b also retrieves the data from the comparison server from the data collection table 216 as the comparison value.

[0087] Then, the comparison unit 244b compares the acquired data item by item (S223). Specifically, the comparison unit 244b compares the acquired expected value with the comparison value for each item. Subsequently, the operation management device 202b performs steps S224 and S225 in the same manner as shown in Figure 13 above.

[0088] Thus, this embodiment 4 can achieve the same effects as embodiment 2 described above. Furthermore, when there is a lot of commonality in the settings of multiple components, such as when the components are made redundant, it is possible to compare the components side by side and efficiently check for differences. This embodiment 4 is also applicable to embodiment 3 described above.

[0089] <Other Embodiments> In the examples described above, the program includes a set of instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more of the functions described in the embodiments. The program may be stored on a non-temporary computer-readable medium or a physical storage medium. Examples, but not limited to, include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technologies, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disc storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices. The program may be transmitted over a temporary computer-readable medium or a communication medium. Examples, but not limited to, include temporary computer-readable medium or a communication medium that includes electrically, optically, acoustically or otherwise propagating signals.

[0090] This disclosure is not limited to the embodiments described above, and may be modified as appropriate without departing from its spirit. Furthermore, this disclosure may be implemented by combining the respective embodiments as appropriate.

[0091] Some or all of the above embodiments may also be described as follows, but are not limited to the following: (Note A1) An extraction means for extracting data item by item from a collection file based on the format information of the collection file collected from the components of the information system and the definition information of the delimiter character between items specified in the components, A storage means for associating the extracted data with the items and storing them in a collected data table, A comparison means that compares an expected value table storing the expected value of each item in the collection file with data associated with common items in the collection data table, and outputs the comparison result. An operation management device equipped with the following features. (Appendix A2) The extraction means is Record data, which is a string representing each record, is extracted from the collected file according to the format information. The record data is split using the delimiter defined in the definition information, and the resulting split strings are extracted as data for each item. The operation management device described in Appendix A1. (Note A3) The aforementioned comparison means is, In the expected value table and the collected data table, the data corresponding to the specified items in the collected file are compared, and the comparison result is obtained. The operation management device described in Appendix A1 or A2. (Note A4) The aforementioned definition information indicates that multiple delimiters are defined for a particular component. An operation management device as described in any one of the items A1 to A3 in the appendix. (Note A5) The aforementioned expected value table is a first collection data table that stores data extracted from a first collection file collected from a first server, which is one of the components of the information system. The storage means stores the data extracted from the second collection file, which is collected from the second server, among the components of the information system, in the second collection data table. The comparison means compares the data associated with common items in the first and second data collection tables and outputs the comparison result. An operation management device as described in any one of the items A1 to A4 in the appendix. (Note A6) When the storage means obtains the expected value for each item in the collection file, it associates the expected value with the item and stores it in the expected value table. An operation management device as described in any one of the items A1 to A4 in the appendix. (Note B1) A collection device that collects files from the components of an information system, The operation management device connected to the aforementioned collection device, Equipped with, The aforementioned operation management device is An extraction means for extracting data item by item from a collection file collected by the collection device, based on the format information of the collection file and the definition information of delimiters between items defined in the components, A storage means for associating the extracted data with the items and storing them in a collected data table, A comparison means that compares an expected value table storing the expected value of each item in the collection file with data associated with common items in the collection data table, and outputs the comparison result. An operational management system equipped with the following features. (Note B2) The extraction means is Record data, which is a string representing each record, is extracted from the collected file according to the format information. The record data is split using the delimiter defined in the definition information, and the resulting split strings are extracted as data for each item. The operational management system described in Appendix B1. (Note C1) Computers Based on the format information of the collected files gathered from the components of the information system and the definition information of the delimiters between items specified in those components, data is extracted from the collected files item by item. The extracted data and the items are associated and stored in the collected data table. The expected value table, which stores the expected value of each item in the collection file, and the data associated with common items in the collection data table are compared. Output the comparison results. Operation management method. (Note D1) An extraction process that extracts data item by item from a collection file based on the format information of the collection file collected from the components of the information system and the definition information of the delimiter character between items specified in the components, A storage process that associates the extracted data with the items and stores them in a collected data table, A comparison process that compares data associated with common items in an expected value table storing the expected value of each item in the collection file with the collection data table, and outputs the comparison result. A non-temporary, computer-readable medium containing an operational management program that causes a computer to execute a command.

[0092] Although the present invention has been described above with reference to embodiments (and examples), the present invention is not limited to the above embodiments (and examples). Various modifications to the structure and details of the present invention can be made, as can be understood by those skilled in the art within the scope of the present invention. [Explanation of Symbols]

[0093] 1 Operation management device 11 Extraction part 12 Storage Unit 13. Comparison Section 100 Information Systems 101 NW equipment 111 Server 112 Servers 11n server 121 Storage devices 12m storage device N Network 200 Operation Management Systems 201 Collection device 202 Operation management equipment 203 Management Terminal 3a Collection files 3b. Collected files 210 Storage section 211 Operations Management Program 212 Collection File Definition Information 213 Format Information 214 Delimiter Definition Information 215 Expected Value Table 2151 items 2152 data 216 Collected Data Table 2161 items 2162 data 2163 Data 220 memory 230 Communications Department 240 Control Unit 241 Registration Department 242 Extraction part 243 Storage Unit 244 Comparison Section 245 Output section 4 Comparison result information 40. Information on files to be compared 41 items 42 Master Data 43 Comparison results 44. Collected Data 202a Operation management device 211a Operation Management Program 217 Comparison definition information 2171 items 244a Comparison section 4a Comparison result information 40a Comparison Target Definition Information 45 Comparison results 202b Operation management device 211b Operation Management Program 244b Comparison section

Claims

1. An extraction means for extracting data item by item from a collection file based on the format information of the collection file collected from the components of the information system and the definition information of the delimiter character between items specified in the components, A storage means for associating the extracted data with the items and storing them in a collected data table, A comparison means that identifies items to be compared from comparison definition information that defines the items to be compared for each file, retrieves data from the expected value table and the collected data table that are common to the identified items in the expected value table and the collected data table that store the expected values ​​of each item in the collected file, compares the retrieved data, and outputs the comparison result. An operation management device equipped with the following features.

2. The extraction means is Record data, which is a string representing each record, is extracted from the collected file according to the format information. The record data is split using the delimiter defined in the definition information, and the resulting split strings are extracted as data for each item. The operation management device according to claim 1.

3. The aforementioned definition information indicates that multiple delimiters are defined for a particular component. The operation management device according to claim 1 or 2.

4. The aforementioned expected value table is a first collection data table that stores data extracted from a first collection file collected from a first server, which is a component of the information system. The storage means stores the data extracted from the second collection file, which is collected from the second server, among the components of the information system, in the second collection data table. The comparison means compares the data associated with common items in the first and second data collection tables and outputs the comparison result. The operation management device according to any one of claims 1 to 3.

5. When the storage means obtains the expected value for each item in the collection file, it associates the expected value with the item and stores it in the expected value table. The operation management device according to any one of claims 1 to 3.

6. A collection device that collects files from the components of an information system, The operation management device connected to the aforementioned collection device, Equipped with, The aforementioned operation management device is An extraction means for extracting data item by item from a collection file collected by the collection device, based on the format information of the collection file and the definition information of delimiters between items defined in the components, A storage means for associating the extracted data with the items and storing them in a collected data table, A comparison means that identifies items to be compared from comparison definition information that defines the items to be compared for each file, retrieves data from the expected value table and the collected data table that are common to the identified items in the expected value table and the collected data table that store the expected values ​​of each item in the collected file, compares the retrieved data, and outputs the comparison result. An operational management system equipped with the following features.

7. The extraction means is Record data, which is a string representing each record, is extracted from the collected file according to the format information. The record data is split using the delimiter defined in the definition information, and the resulting split strings are extracted as data for each item. The operation management system according to claim 6.

8. Computers Based on the format information of the collected files gathered from the components of the information system and the definition information of the delimiters between items specified in those components, data is extracted from the collected files item by item. The extracted data and the items are associated and stored in the collected data table. The items to be compared are identified from the comparison definition information, which defines the items to be compared for each file. Data associated with the identified items among the common items in the expected value table, which stores the expected value of each item in the collected file, and the collected data table are obtained from the expected value table and the collected data table, and the obtained data are compared. Output the comparison results. Operation management method.

9. An extraction process that extracts data item by item from a collection file based on the format information of the collection file collected from the components of the information system and the definition information of the delimiter character between items specified in the components, A storage process that associates the extracted data with the items and stores them in a collected data table, A comparison process that identifies items to be compared from comparison definition information that defines the items to be compared for each file, retrieves data from the expected value table and the collected data table that are common to the identified items and stores the expected value of each item in the collected file, compares the retrieved data, and outputs the comparison result. An operational management program that causes a computer to execute commands.

Images