Computer system and information acquisition method

Abstract

To acquire management information necessary for centrally managing a service provision system built on a plurality of infrastructures.SOLUTION: A computer system is connected to a plurality of infrastructures. A service provision system can be built on the infrastructures, and the service provision system holds service management information on services to be provided. The computer system holds information on the service provision system to be monitored, information on monitoring items, service management information used to generate information corresponding to the monitoring items, and acquisition route management information storing acquisition route data including acquisition routes, identifies an unusable acquisition route to reflect the result in the acquisition route management information when an opportunity to confirm a usable acquisition route is detected, and selects an acquisition route by referring to the acquisition route management information to acquire the service management information when an opportunity to acquire the service management information is detected.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to a technique for unifying the management of service providing systems built on multiple platforms. [Background technology]

[0002] The use of multiple platforms to provide services is becoming more common. When a service provision system is built on multiple platforms, there is a problem that management becomes complicated. For this reason, services that centrally manage service provision systems built on multiple platforms (management services) are emerging.

[0003] The management service acquires management information on the performance etc. of the service providing system from each platform, and centrally manages the multiple service providing systems using the management information. If a failure occurs in a service providing system, the management information cannot be acquired. In response to this, the above-mentioned problem can be addressed by making the service providing system redundant. For example, Patent Document 1 is known as a redundancy technology for a service providing system. If a failure occurs in the communication path for accessing the platform, the management information cannot be acquired. In response to this, the above-mentioned problem can be addressed by making the communication path redundant. For example, Patent Document 2 is known as a redundancy technology for communication paths. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2006-260072 A [Patent Document 2] JP 2013-162308 A Summary of the Invention [Problem to be solved by the invention]

[0005] The reasons why management information cannot be acquired are diverse, and it is difficult to deal with all of them with conventional technology. The present invention utilizes the characteristics of a service provision system built on multiple platforms to provide a technology for acquiring management information required for centrally managing a service provision system built on multiple platforms. [Means for solving the problem]

[0006] A representative example of the invention disclosed in the present application is as follows: That is, a computer system connected to a plurality of platforms, a service providing system that provides a service can be constructed on the platform, the service providing system holds at least one of service management information related to the service provided by the service providing system itself and service management information related to the service provided by another service providing system, and provides one or more APIs, the computer system holds acquisition route management information that stores identification information of the service providing system to be monitored, identification information of monitoring items, identification information of the service management information used to generate information corresponding to the monitoring items, and acquisition route data including an acquisition route of the service management information, the acquisition route being used to generate information corresponding to the monitoring items. The service management information used for generating information corresponding to the monitoring item is defined by a combination of identification information of the service providing system and the API that stores the service management information used for generating information corresponding to the monitoring item, and when the computer system detects an opportunity to check the available acquisition route, it refers to the acquisition route management information to identify the acquisition route that cannot be used and reflects the result in the acquisition route management information, and when the computer system detects an opportunity to acquire the service management information used for generating information corresponding to the monitoring item, it refers to the acquisition route management information to identify the acquisition route that can be used for acquiring the service management information, selects one acquisition route from the identified acquisition routes, and acquires the service management information used for generating information corresponding to the monitoring item via the selected acquisition route. Effect of the Invention

[0007] According to the present invention, it is possible to acquire management information required for centrally managing service provision systems built on multiple platforms. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of a system configuration according to a first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer that configures the management system of the first embodiment. [Diagram 3] FIG. 2 is a diagram illustrating a specific example of a service in the system of the first embodiment. [Figure 4] FIG. 11 illustrates an example of a data structure of template management information according to the first embodiment. [Diagram 5] 13 is a diagram illustrating an example of a data structure of acquired route management information according to the first embodiment; FIG. [Figure 6] 11 is a flowchart illustrating an example of an acquired route data generation process executed by the management system of the first embodiment. [Figure 7] 11 is a flowchart illustrating an example of a service management information acquisition process executed by the management system according to the first embodiment. [Figure 8] 11 is a flowchart illustrating an example of an acquired route confirmation process executed by the management system according to the first embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. However, the present invention should not be interpreted as being limited to the description of the embodiment shown below. It will be easily understood by those skilled in the art that the specific configuration can be changed without departing from the concept or purpose of the present invention.

[0010] In the configurations of the invention described below, the same or similar configurations or functions are given the same reference numerals, and duplicated explanations are omitted.

[0011] In this specification, the terms "first," "second," "third," and the like are used to identify components and do not necessarily limit the number or order. EXAMPLES

[0012] Fig. 1 is a diagram illustrating an example of a system configuration of the first embodiment. Fig. 2 is a diagram illustrating an example of a hardware configuration of a computer that configures the management system of the first embodiment.

[0013] The system includes a management system 100 and a plurality of boards 101. The management system 100 is connected to the plurality of boards 101 via a network 102 such as a wide area network (WAN) and a local area network (LAN).

[0014] The platform 101 provides an environment for constructing a service providing system that provides services. The platform 101 may be either an on-premise platform or a cloud platform. The service providing system may be composed of physical elements such as a computer, or may be composed of virtual elements such as a virtual computer.

[0015] The management system 100 centrally manages a service providing system built on a platform 101. The management system 100 is composed of, for example, a computer 200 shown in FIG. 2. The computer 200 includes a processor 201, a main memory device 202, a secondary memory device 203, and a network interface 204. The processor 201 operates as a functional unit (module) that realizes a specific function by executing processing in accordance with a program stored in the main memory device 202. In the following explanation, when processing is explained with the functional unit as the subject, it indicates that the processor 201 is executing a program that realizes the functional unit.

[0016] The management system 100 has a service monitoring unit 110, a service management information acquisition unit 111, an acquired route selection unit 112, and an acquired route data generation unit 113, and also holds template management information 120, configuration management information 121, and acquired route management information 122.

[0017] The configuration management information 121 is information for managing the configuration of the service providing system built on the platform 101. The acquisition route management information 122 is information for managing the acquisition route of the service management information used for monitoring the operating status and processing performance of the service providing system. The template management information 120 is information for managing templates used for setting the acquisition route management information 122.

[0018] The service monitoring unit 110 monitors the service providing system. For example, the service monitoring unit 110 grasps the state of the service providing system based on the service management information, and monitors performance degradation, occurrence of a failure, drop in service level, implementation of maintenance, and the like. The service management information acquisition unit 111 acquires the service management information from the service providing system. The acquisition route selection unit 112 selects an acquisition route for acquiring the service management information. The acquisition route data generation unit 113 generates acquisition route management information 122 by using a template.

[0019] The management system 100 may be included in any one of the platforms 101 .

[0020] FIG. 3 is a diagram illustrating a specific example of a service in the system according to the first embodiment.

[0021] The platform (1) 101 is, for example, an on-premise platform, and includes a management server 300 and a storage system 310. The management server 300 and the storage system 310 are an example of a service providing system.

[0022] The management server 300 manages the storage system 310 that provides volumes, and holds service management information 301 that stores data related to the performance, etc., of the storage system 310. The management server 300 also provides an API (1) 302 for the management system 100 to access.

[0023] The storage system 310 provides a volume. The storage system 310 holds service management information 311 that stores data related to the performance of the storage system 310. The storage system 310 also provides an API (2) 312 for access by the management system 100, and an API (3) 313 for access by a user who uses the volume.

[0024] The platform (2) 101 is, for example, a cloud-type platform, and includes a software defined storage (SDS) 320 and a log management system 340. The SDS 320 and the log management system 340 are an example of a service providing system.

[0025] The SDS 320 provides a volume. The SDS 320 is composed of a server 330 and a storage volume 331. The server 330 provides an API (4) 332 for access by the management system 100 and the log management system 340. The SDS 320 holds service management information 321 that stores data related to the performance of the SDS 320, etc. The SDS 320 also provides an API (5) 322 for access by the management server 300 and an API (6) 323 for access by the management system 100.

[0026] The log management system 340 manages logs of the operating status, performance, etc. of the SDS 320. The log management system 340 holds service management information 341 that stores data related to the performance, etc. of the SDS 320. In addition, the log management system 340 provides an API (7) 342 for the management system 100 to access.

[0027] The board 101 and the system on the board 101 shown in FIG. 3 are merely an example, and the present invention is not limited to this.

[0028] FIG. 4 is a diagram illustrating an example of the data structure of the template management information 120 according to the first embodiment.

[0029] The template management information 120 stores entries including a target system 401, a monitor item 402, service management information 403, a storage location 404, an acquisition API 405, and a priority 406. One entry corresponds to one template.

[0030] The target system 401 is a field for storing the type of the service providing system to be monitored. The monitoring item 402 is a field for storing the type of the monitoring item of the service providing system to be monitored.

[0031] Service management information 403 is a field that stores the type of service management information used to generate information corresponding to the monitoring items. "<User specified>" indicates that the identification information is specified by the user. The management system 100 uses the service management information to generate information corresponding to the monitoring items. For example, the management system 100 generates the service management information itself as information corresponding to the monitoring items, and also generates information corresponding to the monitoring items by performing statistical processing, conversion processing, etc. on the service management information.

[0032] The storage location 404 is a field for storing the type of the service providing system that stores the service management information. The acquisition API 405 is a field for storing the type of the API used to acquire the service management information.

[0033] The priority 406 is a field for storing a priority indicating the selection order of acquired route data generated using a template. In this embodiment, acquired route data closer to "1" is selected preferentially.

[0034] FIG. 5 is a diagram illustrating an example of the data structure of the acquired route management information 122 according to the first embodiment.

[0035] The acquired route management information 122 stores entries including a target system 501, a monitor item 502, service management information 503, a storage location 504, an acquired API 505, a priority 506, and a flag 507. One entry corresponds to one acquired route data.

[0036] The target system 501 is a field for storing identification information of the service providing system to be monitored. The monitoring item 502 is a field for storing identification information of the monitoring item.

[0037] Service management information 503 is a field for storing identification information of service management information used to generate information corresponding to a monitoring item. Storage location 504 is a field for storing identification information of a service providing system that stores the service management information. Acquisition API 505 stores identification information of an API used to acquire the service management information. Storage location 504 and acquisition API 505 are information that defines the acquisition route of the service management information.

[0038] The priority 506 is the same field as the priority 406. The flag 507 is a field that stores a flag indicating whether or not the acquired route corresponding to the acquired route data can be used. The flag 507 stores either "0", which indicates that the acquired route can be used, or "1", which indicates that the acquired route cannot be used. The flag 507 of each entry is set to "0" as the initial value.

[0039] FIG. 6 is a flowchart illustrating an example of an acquired route data generation process executed by the management system 100 according to the first embodiment.

[0040] When the acquired route data generating unit 113 receives registration or update of configuration data indicating the configuration of the service providing system, the acquired route data generating unit 113 executes the process described below.

[0041] The acquired route data generation unit 113 starts a loop process of the template after storing the configuration data in the configuration management information 121 (step S101). Specifically, the acquired route data generation unit 113 selects one template (entry) from the template management information 120.

[0042] The acquired route data generating unit 113 extracts values ​​corresponding to the target system 401, monitoring items 402, service management information 403, storage location 404, and acquisition API 405 of the template from the configuration data (step S102), and determines whether acquired route data can be generated (step S103). If a value cannot be acquired for at least one of the target system 401, monitoring items 402, service management information 403, storage location 404, and acquisition API 405 of the template, the acquired route data is not generated.

[0043] If the acquired route data cannot be generated, the acquired route data generation unit 113 proceeds to step S105. If the acquired route data can be generated, the acquired route data generation unit 113 generates the acquired route data and registers it in the acquired route management information 122 (step S104). After that, the acquired route data generation unit 113 proceeds to step S105.

[0044] In step S105, the acquired route data generating unit 113 determines whether or not the processing has been completed for all the templates (step S105).

[0045] If the processing has not been completed for all the templates, the obtained route data generating unit 113 returns to step S101. If the processing has been completed for all the templates, the obtained route data generating unit 113 ends the obtained route data generation processing.

[0046] FIG. 7 is a flowchart illustrating an example of the service management information acquisition process executed by the management system 100 according to the first embodiment.

[0047] When the service management information acquisition unit 111 detects an opportunity to acquire the managed service management information, it executes the process described below. Note that, as information specifying the service management information to be acquired, identification information of the service providing system to be monitored and the monitoring items is input.

[0048] The service management information acquisition unit 111 refers to the acquisition route management information 122 to identify the service management information corresponding to the combination of the service providing system to be monitored and the identification information of the monitoring item (step S201).

[0049] Specifically, the service management information acquisition unit 111 searches for acquisition route data (entry) in which a combination of the target system 501 and the value of the monitoring item 502 matches a combination of identification information of the service providing system to be monitored and the monitoring item.

[0050] The service management information acquisition unit 111 identifies an acquisition route through which the identified service management information can be acquired (step S202).

[0051] Specifically, the service management information acquiring unit 111 extracts acquired route data whose flag 507 is "0" from the acquired route data searched in step S201.

[0052] The service management information acquisition unit 111 selects an acquisition route to be used from the identified acquisition routes (step S203).

[0053] Specifically, the service management information acquisition unit 111 selects one piece of acquired route data based on the value of the priority 506 of the extracted acquired route data. In this embodiment, the acquired route data having the priority 506 value closest to 1 is selected. Note that the service management information acquisition unit 111 may select an acquired route in consideration of the load and service level (performance, availability) of the service providing system from which the information is acquired, in addition to the priority.

[0054] The service management information acquisition unit 111 acquires the service management information via the selected acquisition route (step S204).

[0055] FIG. 8 is a flowchart illustrating an example of the acquired route confirmation process executed by the management system 100 according to the first embodiment.

[0056] When the acquisition route selection unit 112 detects an opportunity to check whether the acquired route can be used, the acquisition route selection unit 112 executes the process described below. Possible execution opportunities include failure to acquire service management information, occurrence of a fault in the service providing system, an increase in load, a decrease in the service level, or the implementation of maintenance.

[0057] The acquired route selection unit 112 identifies an acquired route that cannot be used (step S301).

[0058] For example, if the execution trigger is a failure to acquire service management information, the acquisition route selection unit 112 refers to the acquisition route management information 122 and searches for an entry in which the combination of values ​​of the storage location 504 and the acquisition API 505 matches the combination of values ​​used when acquiring the service management information.

[0059] For example, if the trigger for execution is a fault in the service providing system, an increase in load, a decrease in service level, or maintenance, the acquisition route selection unit 112 refers to the acquisition route management information 122 and searches for an entry in storage location 504 in which a value related to the service providing system is stored.

[0060] Note that the importance of each monitoring item may be set in advance, and only acquisition routes related to essential monitoring items may be identified.

[0061] The acquired route selection unit 112 sets a flag indicating that the acquired route cannot be used in the acquired route data corresponding to the identified acquired route (step S302). Specifically, the flag 507 is set to "1".

[0062] The acquisition route selection unit 112 starts a loop process of pairs of service providing systems to be monitored and monitoring items (step S303).

[0063] The acquisition route selection unit 112 determines whether or not all of the acquisition routes corresponding to the combination of the service providing system to be monitored and the monitoring item are unavailable (step S304).

[0064] When there is at least one usable acquisition route among the acquisition routes corresponding to the combination of the service providing system to be monitored and the monitoring item, the acquisition route selection unit 112 proceeds to step S306.

[0065] If all of the acquisition routes corresponding to the combination of the service providing system to be monitored and the monitoring items are unavailable, the acquisition route selection unit 112 generates and outputs recommended configuration data (step S305). After that, the acquisition route selection unit 112 proceeds to step S306. In step S305, the following process is executed.

[0066] (S305-1) The acquisition route selection unit 112 refers to the template management information 120 and searches for a template in which the combination of the target system 401 and the values ​​of the monitoring items 402 matches the combination of the type of the service providing system to be monitored and the type of the monitoring items.

[0067] (S305-2) The acquisition route selection unit 112 compares the searched template with the acquisition route data corresponding to the combination of the service providing system to be monitored and the monitoring item to identify an unused template. If there is no unused template, the acquisition route selection unit 112 ends the process of step S305.

[0068] (S305-3) The acquisition route selection unit 112 generates and outputs an unused template as recommended configuration data. After that, the acquisition route selection unit 112 ends the process of step S305. At this time, the acquisition route selection unit 112 may refer to the configuration management information 121 and set specific values ​​in some fields of the template.

[0069] The user can review the configuration of the service by referring to the recommended configuration data.

[0070] In step S306, the acquisition route selection unit 112 determines whether or not the processing has been completed for all combinations of service providing systems and monitoring items (step S306).

[0071] If the processing has not been completed for all pairs of service providing systems and monitoring items, the acquired route selection unit 112 returns to step S303. If the processing has been completed for all pairs of service providing systems and monitoring items, the acquired route selection unit 112 ends the acquired route confirmation processing.

[0072] In addition, after the service management information is successfully acquired, or after the service provision system has recovered from a fault, the load has been reduced, or maintenance has been completed, the acquisition route selection unit 112 executes processing similar to that of step S301, and sets a flag indicating that the acquisition route can be used in the acquisition route data corresponding to the identified acquisition route.

[0073] In this embodiment, the unavailable acquired route is specified using a flag, but the present invention is not limited to this. Any information that can specify the unavailable acquired route may be used.

[0074] According to the first embodiment, even if an incident occurs that makes it difficult to acquire service management information, such as failure to acquire service management information, a fault in the service providing system, an increase in load, a decrease in service level, or maintenance being performed, it is possible to acquire the service management information required for monitoring.

[0075] The present invention is not limited to the above-mentioned embodiment, but includes various modified examples. For example, the above-mentioned embodiment describes the configuration in detail to easily explain the present invention, and the present invention is not necessarily limited to the configuration including all the described configurations. Also, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0076] In addition, each of the above configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that realizes the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-mentioned embodiments, and the program code itself and the storage medium storing it constitute the present invention. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, etc.

[0077] Furthermore, the program code for realizing the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, Python, Java (registered trademark), etc.

[0078] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed over a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read out and execute the program code stored in the storage means or storage medium.

[0079] In the above-mentioned embodiment, the control lines and information lines are shown as those considered necessary for the explanation, and not all the control lines and information lines are shown in the product. All the components may be connected to each other. [Explanation of symbols]

[0080] 100 Management Systems 101 Foundation 102 Network 110 Service Monitoring Department 111 Service management information acquisition unit 112 Route selection section 113 Route acquisition data generation unit 120 Template Management Information 121 Configuration management information 122 Obtained route management information 200 calculator 201 Processor 202 Main storage 203 Secondary storage device 204 Network Interface 300 Management Server 301, 311, 321, 341 Service Management Information 310 Storage System 320 SDS(Software Defined Storage) 330 Server 331 Storage Volume 340 Log Management System

Claims

1. A computer system that connects to a plurality of boards, A service providing system for providing a service can be constructed on the platform, The service providing system holds at least one of service management information regarding the service provided by its own service providing system and service management information regarding the service provided by another service providing system, and provides one or more APIs; the computer system holds acquisition route management information storing identification information of the service providing system to be monitored, identification information of monitoring items, identification information of the service management information used to generate information corresponding to the monitoring items, and acquisition route data including an acquisition route of the service management information; the acquisition route is defined by a combination of identification information of the service providing system that stores the service management information used to generate information corresponding to the monitoring items and the API; The computer system comprises: When a confirmation opportunity for the available acquired route is detected, the acquired route management information is referenced to identify the unavailable acquired route, and the result is reflected in the acquired route management information; when detecting an opportunity to acquire the service management information used to generate information corresponding to the monitoring item, referring to the acquisition route management information to identify the acquisition route that can be used to acquire the service management information; Selecting one of the acquired routes from the identified acquired routes; a computer system that acquires the service management information used to generate information corresponding to the monitoring items via the selected acquisition route;

2. 2. The computer system of claim 1, When detecting, as the confirmation trigger, any one of the occurrence of a failure, an increase in load, a decrease in service level, and the implementation of maintenance of the service providing system, identifying the obtained route corresponding to the obtained route data including identification information of the service providing system as the obtained route that cannot be used; A computer system characterized in that, when a failure to acquire the service management information is detected as the confirmation trigger, the acquisition route corresponding to the acquisition route data including a set of identification information of the service providing system that stores the service management information and the API used to acquire the service management information is identified as an unusable acquisition route.

3. 2. The computer system of claim 1, The computer system is characterized in that the computer system assigns a flag indicating that the obtained route is unusable to the obtained route data corresponding to the obtained route that cannot be used.

4. 2. The computer system of claim 1, retaining template management information for storing a template of the acquisition route data, the template being configured from a type of the service providing system to be monitored, a type of the monitoring item, a type of the service management information, a type of the service providing system that stores the service management information, and a type of the API used to acquire the service management information; A computer system that generates the acquired route data by using configuration information of the service providing system and the template.

5. 5. The computer system of claim 4, when there is no acquisition route available for acquiring the service management information used to generate information corresponding to the monitoring items of the service providing system to be monitored, searching for the template including the service providing system and the type of the monitoring item by referring to the template management information; Identifying unused templates by comparing the searched templates with the acquired route data including identification information of the service providing system to be monitored and the monitoring items; A computer system that outputs the identified template.

6. A method for acquiring information executed by a computer system connected to a plurality of boards, comprising: A service providing system for providing a service can be constructed on the platform, The service providing system holds at least one of service management information regarding the service provided by its own service providing system and service management information regarding the service provided by another service providing system, and provides one or more APIs; the computer system holds acquisition route management information storing identification information of the service providing system to be monitored, identification information of monitoring items, identification information of the service management information used to generate information corresponding to the monitoring items, and acquisition route data including an acquisition route of the service management information; the acquisition route is defined by a combination of identification information of the service providing system that stores the service management information used to generate information corresponding to the monitoring items and the API; The method for acquiring the information includes: a first step in which, when a confirmation trigger for the available acquired route is detected, the computer system refers to the acquired route management information to identify the unavailable acquired route and reflect the result in the acquired route management information; a second step in which, when detecting an opportunity to acquire the service management information used to generate information corresponding to the monitoring items, the computer system refers to the acquisition route management information to identify the acquisition route that can be used to acquire the service management information; a third step of the computer system selecting one of the acquired routes from the identified acquired routes; and a fourth step in which the computer system acquires the service management information used to generate information corresponding to the monitoring items via the selected acquisition route.

7. 7. The method for acquiring information according to claim 6, The first step includes: a step in which, when detecting any one of occurrence of a failure, an increase in load, a decrease in a service level, and an implementation of maintenance of the service providing system as the confirmation trigger, the computer system specifies the obtained route corresponding to the obtained route data including identification information of the service providing system as an unavailable obtained route; When a failure to acquire the service management information is detected as the confirmation trigger, the computer system identifies the acquisition route corresponding to the acquisition route data, which includes a set of identification information of the service providing system that stores the service management information and the API used to acquire the service management information, as an unusable acquisition route.

8. 7. The method for acquiring information according to claim 6, A method for acquiring information, characterized in that the first step includes a step in which the computer system assigns a flag to the acquired route data corresponding to the identified acquired route, indicating that the acquired route cannot be used.

9. 7. The method for acquiring information according to claim 6, the computer system holds template management information storing a template of the acquisition route data, the template being configured from a type of the service providing system to be monitored, a type of the monitoring item, a type of the service management information, a type of the service providing system that stores the service management information, and a type of the API used to acquire the service management information; The information acquisition method includes a step of generating the acquired route data by the computer system using configuration information of the service providing system and the template.

10. 10. The method for acquiring information according to claim 9, when there is no acquisition route available for acquiring the service management information used for generating information corresponding to the monitoring items of the service providing system to be monitored, the computer system refers to the template management information and searches for the template including the service providing system and the type of the monitoring item; a step of the computer system comparing the searched template with the acquired route data including identification information of the service providing system to be monitored and the monitoring items, thereby identifying the template that is not being used; and a step of outputting the identified template by the computer system.

Images