System configuration management device and method

Abstract

To provide a system configuration management device capable of reducing management man hours at occurrence of a failure or the like.SOLUTION: In an information processing system constituted on a cloud, information of first logs outputted by respective applications, second logs outputted by execution bases of respective services provided by the information processing system, and the like is collected, an application graph is generated where respective applications are taken as first logs, and call relations between respective applications are taken as edges on the basis of the collected first logs and an analysis result of source codes of respective applications, a service graph is generated where respective services are taken as second nodes and call relations of respective services are taken as edges on the basis of the collected second logs and setting information of respective services, and an integrated graph being a graph network indicating correspondence relations between respective application and respective services is created on the basis of the application graph and the service graph.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a system configuration management device and method, and is suitable for application to a system configuration management device that manages the system configuration of a system built using a public cloud, for example. [Background technology]

[0002] In the past, the mainstream form of business systems implemented by companies and government agencies was on-premise, where servers and other equipment were owned and operated in-house. In contrast, in recent years, an increasing number of companies have been building business systems using public clouds.

[0003] In this case, although the execution platform used in the public cloud can be checked using the console for each service provided by the public cloud vendor, it was difficult to check, for example, which service was using each functional component. This caused problems, such as when a failure occurred, in that it was time-consuming and laborious to identify the source of the failure.

[0004] In this regard, for example, Patent Document 1 discloses an information processing device equipped with a function to identify first-tier applications in a business system from among the applications in the business system using a business server list including the addresses of servers in the business system, and an application list including the names of applications running in the business system, the addresses of the servers on which the applications are running, and the source and destination addresses of the applications, and to determine and aggregate applications in the second and subsequent tiers in the business system that have the same application name as those that have the same role, based on the application list and the addresses of the servers on which the first-tier applications are running.

[0005] Furthermore, with this information processing device, even if multiple business systems are being managed, the business system to which an application belongs can be automatically identified, and applications can be aggregated and displayed for each business system, allowing the system administrator to create an application configuration diagram that allows them to grasp the current configuration at a glance. This has the effect of making it easy to understand the configuration of running applications in an environment where multiple applications are running on multiple servers, and facilitating the identification of the location of a failure when one occurs. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-128597 Summary of the Invention [Problem to be solved by the invention]

[0007] However, the invention disclosed in Cited Document 1 has the problem that it cannot be applied to a system configuration that does not use a server. For example, in the case of an on-premise server, information about the applications that run on the server is registered on the server, so the relationship between the server and the applications can be understood by referring to that information, but in the case of a configuration that does not use a server, such as a message platform, such information is not set in the message platform in advance, so it is not possible to obtain information that can serve as a clue to identify the location of a failure when it occurs.

[0008] Furthermore, the invention disclosed in Reference 1 only allows for understanding the relationship between servers and applications (which applications are running on which servers), and has the problem that it is not possible to understand the relationship between servers.

[0009] On the other hand, AWS (Amazon Web Service) offers a service called "Workload Discovery" that allows for the automatic creation of architecture diagrams of target systems, and there are several other services available besides AWS that assist in the creation of architecture diagrams.

[0010] However, there was a problem in that it was difficult to identify the correspondence between services and applications using only the architecture diagram created by such a service.In addition, public clouds may also contain services other than the target system (such as services for management and testing instances), and if all of these were included in the architecture diagram, there was a problem in that it was difficult to accurately identify the services related to the target system.

[0011] The present invention has been made in consideration of the above points, and aims to propose a system configuration management device and method that can instantly grasp the relationship between cloud services and the applications that provide those cloud services, and can reduce management efforts when a failure occurs, etc. [Means for solving the problem]

[0012] In order to solve this problem, the present invention provides a configuration management device for managing an information processing system built on a cloud, which includes a collection unit that collects first logs output by each application of the information processing system, second logs output by an execution platform of each service provided by the information processing system, analysis results of the source code of each of the applications, and configuration information of each of the services; an application graph creation unit that generates an application graph, which is a graph network in which each of the applications is represented as a first node, call relationships between each of the applications are represented as edges, and the first nodes are arranged in the execution order of the corresponding applications, based on the first logs and the analysis results of the source code of each of the applications collected by the collection unit; a service graph creation unit that creates a service graph, which is a graph network in which each of the services is represented as a second node, call relationships between each of the services are represented as edges, and the second nodes are arranged in the execution order of the corresponding services, based on the second logs and configuration information of each of the services collected by the collection unit; and an integrated graph creation unit that creates an integrated graph, which is a graph network that represents the correspondence between each of the applications and each of the services, based on the application graph and the service graph.

[0013] Furthermore, in the present invention, a configuration management method executed by a configuration management device that manages an information processing system built on a cloud includes a first step of collecting first logs output by each application of the information processing system, second logs output by an execution platform of each service provided by the information processing system, analysis results of the source code of each of the applications, and configuration information of each of the services; a second step of generating an application graph, which is a graph network in which each of the applications is a first node and call relationships between each of the applications are edges, and the first nodes are arranged in the execution order of the corresponding applications, based on the collected first logs and the analysis results of the source code of each of the applications, and creating a service graph, which is a graph network in which each of the services is a second node and call relationships between each of the services are edges, and the second nodes are arranged in the execution order of the corresponding services, based on the collected second logs and configuration information of each of the services; and a third step of creating an integrated graph, which is a graph network that represents the correspondence between each of the applications and each of the services, based on the application graph and the service graph.

[0014] According to the configuration management device and method of the present invention, it is possible to immediately grasp the relationships between cloud services and the applications that provide the cloud services based on the created integrated graph. [Effects of the Invention]

[0015] According to the present invention, it is possible to realize a system configuration management device and method that can reduce the number of management steps when a failure occurs. [Brief explanation of the drawings]

[0016] [Figure 1] 1 is a block diagram showing a configuration of a system configuration management system according to an embodiment of the present invention; [Figure 2] FIG. 1 is a conceptual diagram illustrating an application graph, a service graph, and an integration graph. [Figure 3] FIG. 2 is a block diagram showing the logical configuration of a system configuration management device. [Figure 4] 10 is a diagram illustrating an example of the configuration of a source analysis result database. [Figure 5] 10 is a diagram showing an example of the configuration of a service information database. [Figure 6] 1 is a diagram illustrating an example of the configuration of an application graph database. [Figure 7] 1 is a diagram illustrating an example of the configuration of a service graph database. [Figure 8] 1 is a diagram showing an example of the configuration of an integrated graph database. [Figure 9A] FIG. 10 is a diagram illustrating an example of a screen configuration of a system configuration diagram display screen. [Figure 9B] FIG. 10 is a diagram illustrating an example of a screen configuration of an application configuration diagram display screen. [Figure 9C] FIG. 10 is a diagram illustrating an example of the screen configuration of an integrated diagram display screen. [Figure 10] 10 is a flowchart showing the processing procedure of a collection process. [Figure 11] 10 is a flowchart showing the processing steps of an application graph creation process. [Figure 12] 10 is a flowchart illustrating a processing procedure for creating a service graph. [Figure 13] 10 is a flowchart showing the processing procedure of an integrated graph creation process. DETAILED DESCRIPTION OF THE INVENTION

[0017] An embodiment of the present invention will be described in detail below with reference to the drawings.

[0018] (1) Configuration of the system configuration management system according to this embodiment In Fig. 1, reference numeral 1 denotes an overall system configuration management system according to this embodiment. This system configuration management system 1 comprises one or more business systems 2, a source management system 3, a configuration management device 4, and one or more user terminals 5. These business systems 2, source management systems 3, configuration management devices 4, and user terminals 5 are all interconnected via a network 6 such as the Internet.

[0019] The business system 2 is an information processing system that is built by the user on a public cloud to carry out the user's business. The source control system 3 is a computer device that manages (holds) the source code of each business application of each business system 2.

[0020] The configuration management device 4 is a computer device that manages the system configuration of each business system 2, and is configured with a processor 11, a main memory device 12, an auxiliary memory device 13, and a communication device 14 connected to each other via an internal bus 10.

[0021] The processor 11 is configured with a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), and has the function of controlling the operation of the entire configuration management device 4. The main memory device 12 is configured with, for example, a non-volatile semiconductor memory, and is used as a working memory for the processor 11.

[0022] The auxiliary storage device 13 is configured by a large-capacity nonvolatile storage device such as a hard disk device or SSD (Solid State Memory), and is used to store various programs and data that needs to be stored for a long period of time.

[0023] The programs stored in the auxiliary memory device 13 are read from the auxiliary memory device 13 to the main memory device 12 when the configuration management device 4 is started up or when needed, and the programs read into the main memory device 12 are executed by the processor 11, thereby performing various processes for the entire configuration management device 4 as described below.

[0024] The communication device 14 is configured by, for example, a NIC (Network Interface Card) and performs protocol control during communication with the business system 2, the source management system 3, or the user terminal 5 via the network 6.

[0025] The user terminal 5 is a communication terminal device used by each user of each business system 2, and is used by these users to request an analysis of the system configuration of their own business system 2 from the configuration management device 4 (hereinafter, this request will be referred to as a system configuration analysis request).

[0026] (2) System configuration management function according to this embodiment Next, we will explain the system configuration management function according to this embodiment, which is installed in the configuration management device 4. This system configuration management function is a function that analyzes the correspondence between business applications and services for each business system 2 based on log information of time-series logs (hereinafter referred to as application logs) output from each business application of that business system 2 and log information of time-series logs (hereinafter referred to as service logs) related to the various services provided by that business system 2 output from the execution platform that executes these services, and presents the analysis results as a graph.

[0027] In practice, when the configuration management device 4 receives the above-mentioned system configuration analysis request from the user terminal 5 in response to user operation, it collects the analysis results of the source code of each business application in the user's business system 2 and the application logs of these business applications, and determines the execution order of these business applications and the call relationships between them based on the collected information. Then, based on these determination results, the configuration management device 4 creates a graph network (hereinafter referred to as an application graph) 20, such as that shown on the left side of Figure 2, with business applications as nodes and call relationships as edges.

[0028] The configuration management device 4 also collects and analyzes the service logs of each service provided by the business system 2 and various setting information (including whether or not a business application is deployed) set for each service in the business system 2, and determines the execution order of these services and the call relationships between services based on the analysis results. Based on these determination results, the configuration management device 4 then creates a graph network (hereinafter referred to as a service graph) 21 as shown in the center of Fig. 2, with services as nodes and call relationships as edges.

[0029] Then, based on the application graph 20 and service graph 21 generated as described above, the configuration management device 4 compares the execution times of each application log and each service log, and creates an integrated graph 22 as shown on the right side of Fig. 2 by integrating the application graph 20 and the service graph 21. At this time, the configuration management device 4 superimposes the collected information of the application logs and service logs. The configuration management device 4 then transmits screen data of a screen displaying the created integrated graph 22 to the user terminal 5 that sent the system configuration analysis request, and causes the user terminal 5 to display the screen.

[0030] As means for realizing the system configuration management function of this embodiment as described above, the system configuration management device of this embodiment includes, as shown in FIG. 3, a collection unit 30, an application graph creation unit 31, a service graph creation unit 32, an integrated graph creation unit 33, and a display unit 34, as well as a log database 35, a source analysis result database 36, a service information database 37, an application graph database 38, a service graph database 39, and an integrated graph database 40.

[0031] Of these, the collection unit 30, application graph creation unit 31, service graph creation unit 32, integrated graph creation unit 33, and display unit 34 are functional units that are realized when the processor 11 executes the corresponding programs that are read from the auxiliary storage device 13 described above with reference to Fig. 1 to the main storage device 12. The log database 35, source analysis result database 36, service information database 37, application graph database 38, service graph database 39, and integrated graph database 40 are databases that store information created in the course of a series of processes related to the system configuration management function, and are stored and maintained in the auxiliary storage device 13.

[0032] The collection unit 30 is a functional unit having a function of collecting necessary information from the business system 2 and the source management system 3 in response to the above-mentioned system configuration analysis request transmitted from the user terminal 5 in response to a user operation.

[0033] In practice, the collection unit 30 collects, from the business system 2 specified in the system configuration analysis request (hereinafter referred to as the target business system 2), an application log 42 containing time-series information output by each business application of the business system 2, and a service log 43 containing time-series information output by an execution platform that executes a service. The collection unit 30 then stores the collected application log 42 and service log 43 in a log database 35.

[0034] The collection unit 30 also collects, from the source management system 3, the source code of each business application of the target business system 2 managed by the source management system 3. The collection unit 30 then analyzes each of the collected source codes to detect the application name, repository (storage location), development language, etc. of each business application, and stores the detected information in the source analysis result database 36.

[0035] Furthermore, the collection unit 30 collects setting information 41 of settings related to each service that the user has made to the target business system 2 from the target business system 2 , and stores the collected setting information in the service information database 37 .

[0036] The application graph creation unit 31 creates an application graph 20 (Figure 2) based on the application logs 42 of each business application of the target business system 2 stored in the log database 35 and the source code of each business application of the target business system 2 stored in the source analysis result database 36, and stores the data of the created application graph 20 in the application graph database 38.

[0037] In addition, the service graph creation unit 32 creates a service graph 21 (Figure 2) based on the service logs 43 of each service stored in the log database 35 and the configuration information 41 of each service provided by the target business system 2 that is stored in advance in the service information database 37, and stores the data of the created service graph 21 in the service graph database 39.

[0038] The integrated graph creation unit 33 determines the correspondence between these business applications and services based on the time when each business application, recognized based on each application log 42 stored in the application graph database 38, executed processing, and the time when each service, recognized based on each service log 43 stored in the service graph database 39, was performed. Furthermore, the integrated graph creation unit 33 creates an integrated graph 22 ( FIG. 2 ) that integrates the application graph 20 and the service graph 21 based on the determination result, and stores the data of the created integrated graph 22 in the integrated graph database 40.

[0039] 9A to 9C based on various data stored in each database, such as the application graph database 38, the service graph database 39, and the integrated graph database 40, and on operation input from the user to the user terminal 5, and transmits screen data of these generated screens to the user terminal 5. As a result, based on this screen data, these screens are sequentially displayed on the user terminal 5 in response to user operations.

[0040] On the other hand, the source analysis result database 36 is a database that stores the analysis results of the source code of each business application of the target business system 2, which are executed by the collection unit 30 as described above. As shown in Fig. 4, this source analysis result database 36 has a table structure that includes an analysis result ID column 36A, an application name column 36B, a repository name column 36C, a development language column 36D, and an analysis execution time column 36E. In the source analysis result database 36, one record (row) in Fig. 4 corresponds to the analysis result of one business application of the target business system 2.

[0041] The application name field 36B stores the name of the corresponding business application (application name). This application name is assumed to be originally included in the source code. The analysis result ID field 36A stores an identifier (analysis result ID) unique to the analysis result that is assigned to the analysis result in the source analysis result database 36.

[0042] The repository name field 36C stores the repository (storage location) where the corresponding business application is stored in the business system 2, and the development language field 36D stores the development language of the business application detected by analysis. Furthermore, the analysis execution time field 36E stores the time when the analysis of the corresponding business application was executed.

[0043] Therefore, in the example of Figure 4, the analysis result assigned the analysis result ID "AP-1" is the analysis result of an analysis of a business application called "App-A" performed on "2022 / 9 / 29 00:00:00", the repository in which the business application is stored is "Repo-1", and the development language of the business application is "React".

[0044] The service information database 37 is a database that stores various information including setting information related to each service provided by the target business system 2, which is collected from the target business system 2 by the collection unit 30. As shown in Fig. 5, the service information database 37 has a table structure including a service ID column 37A, a service name column 37B, an application deployment presence / absence column 37C, a setting item column 37D, and an information update time column 37E. In the service information database 37, one record corresponds to one service provided by the target business system 2.

[0045] The service ID column 37A stores an identifier (service ID) that is unique to the corresponding service and is assigned to that service, and the service name column 37B stores the name of that service (service name).

[0046] The application deployment presence / absence column 37C stores information indicating whether any business application was deployed when the corresponding service was provided ("Yes" if deployed, "No" if not). Furthermore, the setting item column 37D stores the actual settings for various setting items of the corresponding service (including the identification information of the service when the next service is called), and the information update time column 37E stores the time (date and time) when the information of the record was updated.

[0047] Therefore, in the example of Figure 5, the service name of the service assigned the service ID "Svs-1" is "EC2" provided by "VM (Virtual Machine)", a dedicated business application to provide that service has been deployed, and the setting item for that business application is "HDD, Type (type of hard disk device used)". Figure 5 also shows that this information was updated at "2022 / 9 / 29 00:00:00".

[0048] The application graph database 38 is a database that stores data of the application graph 20 created by the application graph creation unit 31 as described above, and has a table structure including an application graph ID column 38A, an application node ID column 38B, an application name column 38C, an execution time column 38D, a connected application node ID column 38E, an information acquisition source column 38F, and an analysis execution time column 38G, as shown in Fig. 6. In the application graph database 38, one record in Fig. 6 corresponds to one node (hereinafter referred to as an application node) of one application graph 20.

[0049] The application graph ID field 38A stores an identifier (application graph ID) that is assigned to the corresponding application graph 20 and is unique to that application graph 20. The application node ID field 38B stores an identifier (application node ID) that is assigned to the corresponding application node in that application graph 20, and the application name field 38C stores the application name of the business application that corresponds to that application node.

[0050] Furthermore, the execution time column 38D stores the time when the business application executed some processing, as recognized from the application log 42 of the corresponding business application, and the connected application node ID column 38E stores the application node ID of the business application (hereinafter referred to as the connected business application) that was called by the corresponding business application and executed some processing following the business application.

[0051] Furthermore, the information acquisition source field 38F stores the source of information that identifies the application node ID of the connected business application stored in the connected application node ID field 38E of that record. In this case, examples of the information acquisition source include the application log 42 in FIG. 3 ("execution log" in FIG. 6) and "source code." Note that for business applications for which no connected business application exists, such as the business application with the application name "App-A" in FIG. 6, "execution log" is stored in the information acquisition source field 38F.

[0052] Furthermore, the analysis execution time field 38G stores the time when the application log 42 of the corresponding business application was analyzed to obtain the information of that record.

[0053] Therefore, in the example of Figure 6, for example, the application node "AN-2" in the application graph 20 assigned the application graph ID "AG-2" corresponds to the business application "App-B," and this business application executes processing at "2022 / 10 / 1 15:00:15," and then calls the business applications "AN-3" and "AN-4." Figure 6 also shows that this information was obtained from the "execution log," which is the application log 42 of the business application "App-B," and that this analysis was performed at "2022 / 9 / 29 00:00:00."

[0054] Service graph database 39 is a database that stores data on service graphs 21 created by service graph creation unit 32, and has a table structure including a service graph ID column 39A, a service node ID column 39B, a service ID column 39C, an execution time column 39D, a connected service node ID column 39E, a setting column 39F, an application deployment presence / absence column 39G, an information acquisition source column 39H, and an analysis execution time column 39I, as shown in Fig. 7. In service graph database 39, one record in Fig. 7 corresponds to one node (hereinafter referred to as a service node) in one service graph 21.

[0055] The service graph ID column 39A stores an identifier (service graph ID) assigned to the corresponding service graph 21 that is unique to that service graph 21. The service node ID column 39B stores an identifier (service node ID) assigned to the corresponding service node in that service graph 21, and the service ID column 39C stores an identifier (service ID) assigned to the service corresponding to that service node that is unique to that service.

[0056] The execution time column 39D stores the time when the service was executed as recognized from the service log 43 of the corresponding service, and the connected service node ID column 39E stores the service node ID of the service node corresponding to the service called by the corresponding service and executed subsequently to that service.

[0057] In addition, the settings column 39F stores the contents of various settings that have been made in advance for the corresponding service, and the application deployment column 39G stores information indicating whether or not any business application has been deployed to execute the corresponding service ("Yes" if deployed, "No" if not deployed).

[0058] Furthermore, information indicating the source of the information stored in each of the columns 39A to 39I of the record is stored in the information source column 39H. In this case, examples of the source of such information include the service log 43 in Fig. 3 ("execution log" in Fig. 7) and "setting information." Furthermore, the analysis execution time column 39I stores the time when the service log 43 of the corresponding service was analyzed to obtain the information of the record.

[0059] Therefore, in the example of Figure 7, for example, a node "SN-1" in the service graph 21 assigned a service graph ID of "SG-1" corresponds to a service with a service ID of "Svs-1." This service was executed on "2022 / 10 / 1 15:00:00" and subsequently called a service called "SN-2." Figure 7 also shows that the settings for this service are that the hard disk drive type is "xx" and the identifier is "xx" ("HDD:xx" and "Type:xx"), and that a business application is deployed to provide this service (the value of the application deployment column 39G is "Yes"). This information was obtained from the "Execution Log" and "Configuration Information." Figure 7 also shows that this analysis was performed on "2022 / 10 / 2 15:00:00."

[0060] The integrated graph database 40 is a database that stores data on the integrated graph 22 obtained by integrating the application graph 20 and the service graph 21, which are created by the integrated graph creation unit 33. As shown in FIG. 8 , the integrated graph database 40 has a table structure including an integrated graph ID column 40A, an integrated node ID column 40B, a service node ID column 40C, an application node ID column 40D, an execution time column 40E, a connected integrated node ID column 40F, an information creator column 40G, and an information update time column 40H. In the integrated graph database 40, one record corresponds to one node in the integrated graph 22 (hereinafter, referred to as an integrated node). Note that an integrated node in the integrated graph 22 is configured from an application node in the application graph 20 and / or a service node in the service graph 21.

[0061] The integrated graph ID column 40A stores an identifier (integrated graph ID) unique to the corresponding integrated graph 22 that is assigned to that integrated graph 22, and the integrated node ID column 40B stores an identifier (integrated node ID) unique to the corresponding integrated node in that integrated graph 22 that is assigned to that integrated node.

[0062] In addition, the service node column 40C stores the service node ID of a service node that constitutes the corresponding integrated node if such a service node exists, and the application node ID column 40D stores the application node ID of an application node that constitutes the corresponding integrated node if such an application node exists.

[0063] The execution time column 40E stores the time when a service corresponding to a service node constituting the integrated node is executed, or when a business application corresponding to an application node constituting the integrated node executes a process.

[0064] In addition, the connected integration node ID column 40F stores the integration node ID of an integration node consisting of a service node corresponding to a service that was called by a corresponding service and executed subsequently to that service, or an application node corresponding to a business application that was called by a corresponding business application and executed processing.

[0065] Furthermore, the information creator field 40G stores information that serves as the basis (hereinafter referred to as the information creator field) for integrating the corresponding node in the application graph 20 with the corresponding node in the service graph 21. In this case, the information creator field may include the execution time of the corresponding business application or service, or the setting information for the corresponding service (see the information acquisition field 39H in FIG. 7). Furthermore, the information update time field 40H stores the time when the information of the record was last updated.

[0066] 8, the integrated node "IN-1" in the integrated graph 22 "IG-1" is an integrated node that integrates the service node "SN-1" in the service graph 21 and the application node "AN-1" in the application graph 20, and is shown to be connected to the integrated node "IN-2" in the same integrated graph 22. Figure 8 also shows that the service corresponding to the service node "SN-1" in the service graph 21 and the business application corresponding to the application node "AN-1" in the application graph 20 have the same execution time, "2022 / 10 / 1 15:00:00," and this "execution time" is the basis for integrating the service node "SN-1" and the application node "AN-1." It also shows that the update time of this record was "2022 / 10 / 1 15:00:00."

[0067] (3) Screen layout 9A to 9C show examples of screen configurations of various screens that are displayed on the user terminal 5 based on the screen data that is sent from the display unit 34 to the user terminal 5 that sent the system configuration analysis request described above targeting the user's business system 2 to the configuration management device 4 when the user operates the user terminal 5.

[0068] 9A shows a system configuration diagram display screen 50 that is initially displayed on the user terminal 5 in this case. This system configuration diagram display screen 50 is made up of a button display area 51 and a graph display area 52.

[0069] The graph display area 52 displays a service graph 21 that is drawn based on the data stored in the service graph database 39. In this service graph 21, by moving a cursor 54 onto one of the service nodes 55 and specifying that service node 55, a pop-up 56 can be displayed that displays various information about the service corresponding to that service node 55 (including information such as the service name and setting items stored in the service information database 37).

[0070] Also displayed in the button display area 51 are a system configuration diagram selection button 57, an application configuration diagram selection button 58, and an integrated diagram selection button 59. In this case, the system configuration diagram selection button 57 is highlighted on the system configuration diagram display screen 50 to make it clear that the service graph 21 is displayed in the graph display area 52. Specifically, on the system configuration diagram display screen 50, the frame of the system configuration diagram selection button 57 is displayed thicker than the frames of the application configuration diagram selection button 58 and the integrated diagram selection button 59.

[0071] On the other hand, on the system configuration diagram display screen 50 or the integrated diagram display screen 70 described later with reference to Figure 9C, the display screen can be switched to the application configuration diagram display screen 60 as shown in Figure 9B by clicking the application configuration diagram selection buttons 58, 77 displayed in the button display areas 51, 71.

[0072] This application configuration diagram display screen 60 is configured from a button display area 61 and a graph display area 62, similar to the system configuration diagram display screen 50.

[0073] The graph display area 62 displays an application graph 20 that is drawn based on the data stored in the application graph database 38. In this application graph 20, by moving a cursor 64 onto one of the application nodes 65 and specifying that application node 65, a pop-up 66 can be displayed that displays various information about the business application corresponding to that application node 65 (including information such as the application name and development language stored in the source analysis result database 36).

[0074] Also displayed in the button display area 61 are a system configuration diagram selection button 67, an application configuration diagram selection button 68, and an integrated diagram selection button 69. In this case, the application configuration diagram display screen 60 highlights the application configuration diagram selection button 68 to make it clear that the application graph 20 is displayed in the graph display area 62. Specifically, the application configuration diagram display screen 60 displays the frame of the application configuration diagram selection button 68 with a thicker border than the frames of the system configuration diagram selection button 67 and the integrated diagram selection button 69.

[0075] On the other hand, on the system configuration diagram display screen 50 or the application configuration diagram display screen 60, by clicking the integrated diagram selection button 59, 69 displayed in the button display area 51, 61, the display screen can be switched to the integrated diagram display screen 70 as shown in Figure 9C.

[0076] The integrated diagram display screen 70 is composed of a button display area 71, a graph display area 72, and a system component details display area 73.

[0077] The graph display area 72 displays an integrated graph 22 that is drawn based on the data stored in the integrated graph database 40. In this integrated graph 22, by moving a cursor 74 over a service node 55 or an application node 65 of an integrated node 75 that is made up of the service node 55 and / or application node 65 and specifying the service node 55 or application node 65, setting information for the service corresponding to the service node 55 or various information related to the business application that makes up the application node 65 can be displayed in a pop-up similar to the pop-ups 56 and 66 in Figures 9A and 9B.

[0078] However, when either the service node 55 or the application node 65 that constitutes the integrated node 75 is specified as described above, the setting information for the service corresponding to the service node 55 that constitutes the integrated node 75 and various information regarding the business application corresponding to the application node 65 that constitutes the integrated node 75 may be displayed together in a pop-up.

[0079] Also displayed in the button display area 71 are a system configuration diagram selection button 76, an application configuration diagram selection button 77, and an integrated diagram selection button 78. In this case, the integrated diagram selection button 78 is highlighted on the integrated diagram display screen 70 to make it clear that the integrated graph 22 is displayed in the graph display area 72. Specifically, in this embodiment, the frame of the integrated diagram selection button 78 is displayed thicker than the frames of the system configuration diagram selection button 76 and the application configuration diagram selection button 77.

[0080] Furthermore, the system configuration element details display area 73 displays an integrated node list 79 and a service details list 80. The integrated node list 79 has records associated with each integrated node 75, and these records store the names of services corresponding to the service nodes 55 that make up the corresponding integrated node 75, the names of business applications corresponding to the application nodes 65 that make up that integrated node 75, and the identifiers assigned to those integrated nodes 75, in association with each other.

[0081] On the integrated diagram display screen 70, by moving the cursor 74 onto a record in the integrated node list 79 that corresponds to a desired integrated node 75, the integrated node 75 associated with that record can be highlighted in the graph display area 72. Specifically, in this embodiment, the frames of the service nodes 55 and application nodes 65 that make up that integrated node 75 are displayed thicker than the frames of the service nodes 55 and application nodes 65 that make up other integrated nodes 75.

[0082] At this time, the name of the service corresponding to the service node 55 that constitutes the integrated node 75 ("Service" in Figure 9C), the contents of the various settings for that service ("Settings" in Figure 9C), their setting values ​​("Value" in Figure 9C), and the date on which these settings were made ("Confirm datetime" in Figure 9C) are each displayed in the service details list 80.

[0083] Furthermore, on the integrated diagram display screen 70, by moving the cursor 74 over a service node 55 or an application node 65 that constitutes a desired integrated node 75 in the graph display area 72, the record associated with that integrated node 75 on the integrated node list 79 is highlighted. Specifically, in the case of this embodiment, a frame 81 is displayed so as to surround that record.

[0084] In this case, too, the name of the service corresponding to the service node 55 that constitutes the integrated node 75, the contents of the various settings for that service, their setting values, and the date on which those settings were made are displayed in the service details list 80.

[0085] (4) Various processes related to the system configuration management function according to this embodiment Next, specific processing contents of various processes executed by each functional unit in the configuration management device 4 in relation to the system configuration management function of this embodiment will be described.

[0086] (4-1) Processing of collected parts 10 shows the flow of a series of processes (hereinafter referred to as collection processes) executed by the collection unit 30 (FIG. 3) of the configuration management device 4 upon receiving the above-mentioned system configuration analysis request transmitted from the user terminal 5 in response to a user operation. The collection unit 30 acquires necessary information from the target business system 2 and the source management system 3 according to the processing procedure shown in FIG.

[0087] In practice, when such a system configuration analysis request is received, the collection unit 30 starts the collection process shown in Figure 10, and first, based on the received system configuration analysis request, collects the source code of each business application that constitutes the business system to be analyzed (target business system) from the source management system 3 (S1).

[0088] Next, the collection unit 30 analyzes the source code of each business application collected in step S1 to detect the application name, repository, development language, etc. of these business applications (S2).The collection unit 30 also registers this information obtained by this analysis in a source analysis result database (S3).

[0089] Next, the collection unit 30 collects the application log 42 (FIG. 3) and the service log 43 (FIG. 3) from the target business system 2, and stores the collected application log 42 and service log 43 in the log database 35 (S4).

[0090] The collection unit 30 also collects service setting information 41 (FIG. 3) from the target business system 2 (S5), formats the collected setting information 41 as necessary, and stores it in the service information database 37 (S6).

[0091] Furthermore, the collection unit 30 calls the application graph creation unit 31 (FIG. 3) and the service graph creation unit 32 (FIG. 3), and then ends this collection process.

[0092] (4-2) Application graph creation process 11 shows the flow of a series of processes (hereinafter referred to as application graph creation processing) executed by application graph creation unit 31 called by collection unit 30. Application graph creation unit 31 creates an application graph according to the processing procedure shown in FIG.

[0093] In practice, when the application graph creation unit 31 is called by the collection unit 30, it starts the application graph creation process shown in Figure 11, and first reads and obtains the application logs 42 (Figure 3) of each business application of the target business system 2 from the log database 35 (Figure 3) (S10).

[0094] The application graph creation unit 31 also acquires the analysis results of the source code of each business application from the source analysis result database 36 (Figure 4) (S11), and sorts the acquired application logs 42 of each business application in chronological order (S12).

[0095] Next, the application graph creator 31 identifies the application name of the corresponding business application from each sorted application log 42, and generates an application node for each identified business application in the order sorted in step S12 (S13).

[0096] Furthermore, if the application graph creator 31 recognizes based on the application log 42 that there is a call relationship between two business applications, it creates an edge between the application nodes corresponding to the two business applications (S14).

[0097] Next, the application graph creation unit 31 executes an application graph creation process to create an application graph 20 (FIG. 2) for the target business system 2 (S15). At this time, when the application graph creation process is executed for the first time, the application graph creation unit 31 registers information about the application graph 20, which is made up of application nodes and edges created as described above, in the application graph database 38 (FIG. 6). Furthermore, when the application graph creation process is executed for the same target business system 2 for the second or subsequent times, the application graph creation unit 31 updates the application graph database 38 by overwriting only the difference between the application graph 20 created in steps S10 to S14 this time and the existing application graph 20 stored in the application graph database 38.

[0098] Then, when application graph creator 31 has finished storing the data of application graph 20 created as described above in application graph database 38, it ends this application graph creation process and calls integrated graph creator 33 (FIG. 3).

[0099] (4-3) Processing of the service graph creation part 12 shows the flow of a series of processes (hereinafter referred to as service graph creation processing) executed by service graph creation unit 32 called by collection unit 30. Service graph creation unit 32 creates service graph 21 according to the processing procedure shown in FIG.

[0100] In practice, when the service graph creation unit 32 is called by the collection unit 30, it starts the service graph creation process shown in Figure 12, and first reads and obtains the service logs 43 (Figure 3) of the services provided by the target business system 2 from the log database 35 (S20).

[0101] Service graph creation unit 32 also sorts the acquired service logs 43 in chronological order (S21), divides the sorted service logs 43 into service logs 43 for the same transaction, and generates a service node for each divided service log 43 for the same transaction (S22). Furthermore, service graph creation unit 32 refers to service information database 37 to identify the service corresponding to each service node created in step S22 (S23).

[0102] Next, the service graph creation unit 32 refers to the setting item column 37D of the record corresponding to each service provided by the target business system 2 in the service information database 37 (Figure 5), identifies the call relationship between these services, and creates edges between the service nodes corresponding to the services with the call relationship (S24).

[0103] Next, service graph creation unit 32 executes a service graph creation process to create a service graph 21 (FIG. 2) for target business system 2 (S25). At this time, when service graph creation unit 32 executes the service graph creation process for the first time, it registers information about service graph 21 made up of service nodes and edges created as described above in service graph database 39 (FIG. 7). Furthermore, when service graph creation unit 32 executes the service graph creation process for the same target business system 2 for the second or subsequent times, it updates service graph database 39 by overwriting only the difference between the service graph 21 created in steps S20 to S24 this time and the existing service graph 21 stored in service graph database 39.

[0104] Then, when service graph creator 32 has finished storing the data of service graph 21 created as described above in service graph database 39, it ends this service graph creation process and calls integrated graph creator 33 (FIG. 3).

[0105] (4-4) Integrated graph creation process 13 shows the flow of a series of processes (hereinafter referred to as integrated graph creation processing) executed by integrated graph creation unit 33 when called by both application graph creation unit 31 and service graph creation unit 32. Integrated graph creation unit 33 creates integrated graph 22 (FIG. 2) according to the processing procedure shown in FIG.

[0106] In practice, when the integrated graph creation unit 33 is called by both the application graph creation unit 31 and the service graph creation unit 32, it starts the integrated graph creation process shown in Figure 13, and first reads the data of the application graph 20 from the application graph database 38 and the data of the service graph 21 from the service graph database 39 (S30).

[0107] Next, the integrated graph creation unit 33 selects one application node in the application graph 20 (S31), and searches for a service node on the service graph 21 corresponding to a service whose execution time matches the execution time of the processing of the business application corresponding to the selected application node (S32).The integrated graph creation unit 33 then determines whether or not a service node on the service graph 21 corresponding to a service whose execution time matches the execution time of the processing of the business application selected in step S31 has been found (S33).

[0108] If the integrated graph creation unit 33 obtains a negative result in this determination, it returns to step S31, and thereafter executes step S31 and subsequent steps in the same manner as described above, while sequentially switching the application node selected in step S31 to other application nodes that have not yet been processed in step S32 and subsequent steps.

[0109] In response to this, if the integrated graph creation unit 33 obtains a positive result in the judgment of step S33, it generates an integrated node by integrating the application node selected in step S31 and the service node detected in step S32, and merges the information of these application nodes and service nodes into the generated integrated node (S34).

[0110] Next, the integrated graph creation unit 33 stores the information of the integrated node generated in step S34 in the integrated graph database 40 (S35). At this time, if the integrated graph creation unit 33 is registering the information of the integrated node in the integrated graph database 40 for the first time, it stores all of the information of the integrated node in the integrated graph database 40. Furthermore, if the information of the integrated node has already been stored in the integrated graph database 40, the integrated graph creation unit 33 updates the integrated graph database 40 by overwriting the difference with the information about the integrated node already stored in the integrated graph database 40.

[0111] Thereafter, the integrated graph creation unit 33 determines whether or not step S31 and subsequent steps have been executed for all application nodes in the application graph 20 (S36). If the integrated graph creation unit 33 obtains a negative result in this determination, it returns to step S31, and thereafter repeats steps S31 to S36 and subsequent steps in the same manner as described above.

[0112] When integrated graph creation unit 33 eventually completes execution of step S31 and subsequent steps for all application nodes in application graph 20 and obtains a positive result in step S36, it ends this integrated graph creation process.

[0113] (5) Effects of this embodiment As described above, in the system configuration management system 1 of this embodiment, the configuration management device 4 creates an application graph 20 and a service graph 21 based on the application log 42 output by each business application of the business system 2 constructed on the cloud, the service log 43 output by the execution platform of each service provided by the business system 2, the analysis results of the source code of each business application, and the configuration information of each service, and creates and displays an integrated graph 22 that shows the correspondence between each business application and each service based on the created application graph 20 and service graph 21.

[0114] Therefore, according to this system configuration management system 1, users can instantly understand the relationships between business applications and services based on the created integrated graph 22, making it easier to identify the location of a failure when it occurs, for example, thereby reducing management efforts when a failure occurs.

[0115] (6) Other embodiments In the above embodiment, the configuration management device 4 is constructed using one computer device, but the present invention is not limited to this, and the configuration management device 4 may also be constructed using multiple computer devices that make up a distributed computing system.

[0116] In the above-described embodiment, the system configuration diagram display screen 50, the application configuration diagram display screen 60, and the integrated diagram display screen 70 are configured as shown in Figures 9A to 9C, respectively. However, the present invention is not limited to this, and various other screen configurations can be widely applied.

[0117] Furthermore, in the above-described embodiment, the application graph 20 and the service graph 21 are integrated based on the execution times of business applications and services. However, the present invention is not limited to this, and the application nodes of the application graph 20 and the service nodes of the service graph 21 may be integrated based on information other than the execution times. [Industrial Applicability]

[0118] The present invention can be applied to a configuration management device that manages an information processing system built on a cloud. [Explanation of symbols]

[0119] 1...System configuration management system, 2...Business system, 3...Source management system, 4...System configuration management device, 5...User terminal, 11...Processor, 20...Application graph, 21...Service graph, 22...Integrated graph, 30...Collection unit, 31...Application graph creation unit, 32...Service graph creation unit, 33...Integrated graph creation unit, 34...Display unit, 35...Log database, 36...Source analysis result database, 37...Service information database, 38...Application graph database, 39...Service graph database, 40...Integrated graph database, 50...System configuration diagram display screen, 60...Application configuration diagram display screen, 70...Integrated diagram display screen.

Claims

1. A configuration management device that manages an information processing system built on a cloud, a collection unit that collects a first log output by each application of the information processing system, a second log output by an execution platform of each service provided by the information processing system, an analysis result of the source code of each of the applications, and setting information of each of the services; an application graph creation unit that generates an application graph, which is a graph network in which each of the applications is represented as a first node, a call relationship between each of the applications is represented as an edge, and the first nodes are arranged in the execution order of the corresponding applications, based on an analysis result of the first log and the source code of each of the applications collected by the collection unit; a service graph creation unit that creates a service graph, which is a graph network in which each of the services is represented as a second node, a call relationship between the services is represented as an edge, and the second nodes are arranged in the order in which the corresponding services are executed, based on the second logs and setting information of each of the services collected by the collection unit; an integrated graph creation unit that creates an integrated graph, which is a graph network that represents the correspondence between each of the applications and each of the services, based on the application graph and the service graph; A configuration management device comprising:

2. The integrated graph creation unit The integrated graph is created by integrating the first nodes of the applications and the second nodes of the services that have the same execution time based on the execution time of each of the applications and the execution time of each of the services.

2. The configuration management device according to claim 1.

3. The integrated graph is displayed on a first screen.

2. The configuration management device according to claim 1.

4. The display unit When any third node constituting the integrated graph is designated on the first screen, information on the application corresponding to the third node and / or information on the service corresponding to the second node is displayed in a pop-up.

4. The configuration management device according to claim 3.

5. The display unit In response to an external operation, a second screen displaying the application graph or a third screen displaying the service graph is generated and displayed.

4. The configuration management device according to claim 3.

6. The display unit When the first or second node constituting the posted application graph or service graph is designated on the second or third screen, information about the application corresponding to the first node or information about the service corresponding to the second node is displayed in a pop-up.

6. The configuration management device according to claim 5.

7. A configuration management method executed by a configuration management device that manages an information processing system built on a cloud, comprising: a first step of collecting a first log output by each application of the information processing system, a second log output by an execution platform of each service provided by the information processing system, an analysis result of the source code of each of the applications, and setting information of each of the services; a second step of generating an application graph, which is a graph network in which each of the applications is represented as a first node, call relationships between the applications are represented as edges, and the first nodes are arranged in the execution order of the corresponding applications, based on the collected first logs and analysis results of the source codes of the applications, and creating a service graph, which is a graph network in which each of the services is represented as a second node, call relationships between the services are represented as edges, and the second nodes are arranged in the execution order of the corresponding services, based on the collected second logs and configuration information of the services; a third step of creating an integrated graph, which is a graph network representing the correspondence between each of the applications and each of the services, based on the application graph and the service graph; A configuration management method comprising:

8. In the third step, the configuration management device The integrated graph is created by integrating the first nodes of the applications and the second nodes of the services that have the same execution time based on the execution time of each of the applications and the execution time of each of the services.

8. The configuration management method according to claim 7.

9. a fourth step of generating and displaying a first screen containing the integrated graph; The configuration management method of claim 7, further comprising:

10. In the fourth step, the configuration management device When any third node constituting the integrated graph is designated on the first screen, information on the application corresponding to the third node and / or information on the service corresponding to the second node is displayed in a pop-up.

10. The configuration management method according to claim 9.

11. In the fourth step, the configuration management device In response to an external operation, screen data of a second screen displaying the application graph or a third screen displaying the service graph is generated and displayed.

10. The configuration management method according to claim 9.

12. In the fourth step, the configuration management device When the first or second node constituting the posted application graph or service graph is designated on the second or third screen, information about the application corresponding to the first node or information about the service corresponding to the second node is displayed in a pop-up. The configuration management method of claim 11.

Images