Management device, management method, and management program

Abstract

To provide a management device which enables management of an overall picture of interfaces between components constituting a system.SOLUTION: A management device provided herein comprises a display unit configured to display a list of specifications of interfaces in or between components for each common layer according to interface information designed for each component constituting a system.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present disclosure relates to a management device, a management method, and a management program for managing the state of a system. [Background technology]

[0002] Various methods for managing the state of a system environment have been proposed. For example, Patent Document 1 describes a cloud configuration visualization system that grasps the configuration of a cloud environment. The system described in Patent Document 1 grasps the configuration of a cloud environment by acquiring configuration information in the cloud environment and displaying the acquired information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2016 / 103421 Summary of the Invention [Problem to be solved by the invention]

[0004] As the scale of the system environment increases, the amount of information to be managed regarding the interfaces between each component such as devices and modules also increases. Therefore, even in a large-scale system, it is desirable to be able to easily manage the overall picture of the interfaces between the components that make up the system.

[0005] Therefore, an object of the present disclosure is to provide a management device, a management method, and a management program that can manage the overall picture of the interfaces between the components that make up a system. [Means for solving the problem]

[0006] The management device according to the present disclosure is characterized by having a display unit that displays a list of interface specifications within or between components of the system, for each common layer, in accordance with interface information designed for each component that makes up the system.

[0007] The management method according to the present disclosure is characterized in that a computer displays a list of interface specifications within or between components of a system, for each common layer, in accordance with interface information designed for each component.

[0008] The management program according to the present disclosure is characterized in that it causes a computer to execute a display process that lists the interface specifications within or between components of a system, by common layer, in accordance with interface information designed for each component. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to manage an overall picture of the interfaces between the components that make up the system. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is an explanatory diagram illustrating a configuration example of an embodiment of a management device of the present disclosure. [Figure 2] FIG. 10 is an explanatory diagram showing an example of interface information. [Figure 3] FIG. 10 is an explanatory diagram showing an example of a list of interface specifications. [Figure 4] FIG. 10 is an explanatory diagram showing an example of a method for inquiring about detailed contents of an interface. [Figure 5] FIG. 10 is an explanatory diagram showing another example of displaying interface specifications. [Figure 6] 10 is a flowchart illustrating an example of the operation of the management device. [Figure 7] FIG. 10 is an explanatory diagram illustrating a configuration example of another embodiment of a management device of the present disclosure. [Figure 8]FIG. 10 is an explanatory diagram showing another example of a list of interface specifications. [Figure 9] FIG. 10 is an explanatory diagram showing an example of a method for inquiring about detailed contents of an interface. [Figure 10] FIG. 10 is an explanatory diagram showing an example of detailed content of an interface. [Figure 11] 10 is a flowchart illustrating another example of the operation of the management device. [Figure 12] 1 is a block diagram illustrating an overview of a management device according to the present disclosure. [Figure 13] FIG. 1 is a schematic block diagram illustrating the configuration of a computer according to at least one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0012] Embodiment 1. 1 is an explanatory diagram showing an example of the configuration of an embodiment of a management device according to the present disclosure. The management device 100 of this embodiment includes a storage unit 110, an input unit 120, an extraction unit 130, and a display unit 140.

[0013] The storage unit 110 stores various types of information used by the management device 100 for processing. In this embodiment, the storage unit 110 also stores interface specifications designed for each component that constitutes the system to be managed. The components that constitute the system are, for example, servers and terminal devices. However, the components are not limited to computers such as servers and terminal devices, and may also be devices such as sensors.

[0014] In addition, the interface specifications include various information about the interface (hereinafter sometimes referred to as interface information), such as the presence or absence of connections within or between components, the type of connection, the content of the connection, and design values ​​such as load.

[0015] The input unit 120 accepts various inputs from a user. In this embodiment, the input unit 120 also accepts input of interface information including the specifications of the designed interface. Note that the format of the interface information is preferably determined in advance from the viewpoint of the extraction process described below.

[0016] Fig. 2 is an explanatory diagram showing an example of interface information. In the example shown in Fig. 2, the interface information includes an interface layer, an interface group, an interface ID, an interface name, a data amount, an access frequency, and an interface FROM / TO (a server name, a host name, an IP, a module, etc.).

[0017] The extraction unit 130 extracts interface specifications from the input interface information. The extraction unit 130 may extract interface specifications from interface information in any manner. For example, if the format of the interface information is predetermined as described above, the extraction unit 130 may extract the necessary interface specifications according to that format. The extraction unit 130 stores the extracted interface specifications in the storage unit 110.

[0018] The display unit 140 displays interface specifications. Specifically, the display unit 140 displays a list of interface specifications within or between components in accordance with interface information designed for each component that makes up the system. In particular, in this embodiment, the display unit 140 displays a list of interface specifications for each layer of a common protocol.

[0019] The protocol layer for displaying the list may be predetermined, and may be, for example, the OSI (Open Systems Interconnection) reference model or the TCP / IP (Transmission Control Protocol / Internet Protocol) layer model.

[0020] In order to display the list, it is preferable that the display unit 140 displays some of the interface specifications in a simple format (symbols, abbreviations, numerical values, etc.). Fig. 3 is an explanatory diagram showing an example of a list display of interface specifications. In the example shown in Fig. 3, the presence or absence of connections (presence or absence of interfaces) between the components (specifically, servers or terminals) shown vertically and horizontally is displayed in a matrix format using circles and hyphens (-).

[0021] As shown in the example of Figure 3, displaying the interface specifications in a matrix format for each component makes it possible to flexibly respond to additions and changes to systems and interfaces. Note that in the example shown in Figure 3, some of the interface specifications are displayed for each device, which is a component within the system, but the display unit can be any unit, such as a system unit, a server unit, or a group unit of components.

[0022] Note that some of the interface specifications are not limited to the presence or absence of an interface. For example, the type of interface or the direction of the interface may be displayed by a symbol, the connection details may be displayed by an abbreviation, or a numerical value representing the design value of the load, etc. may be displayed.

[0023] In addition, in order to make it easy to check the detailed contents of the interface from the list display, the display unit 140 may display the interface specifications in a list in a manner that associates the simplified display with the detailed contents of the interface specifications (for example, a link, etc.).

[0024] Fig. 4 is an explanatory diagram showing an example of a method for inquiring about detailed interface content. In the example shown in Fig. 4, as a result of selecting detailed interface specifications between terminal A in system A and terminal B in system B, display unit 140 displays a list of interface types existing between these components. Furthermore, Fig. 4 shows that as a result of selecting the displayed interface, display unit 140 displays even more detailed interface specifications.

[0025] Furthermore, the display unit 140 may display a list of interface specifications for each further component within the component (for example, a module within a server or a terminal). For example, when a component in a matrix is ​​specified, the display unit 140 may display a list of interface specifications for each further component that makes up the specified component. For example, in the example shown in FIG. 3, when server A is selected (clicked), the display unit 140 may display a list of interface specifications by similarly displaying a matrix for each module within the server.

[0026] 3 illustrates an example in which interface specifications are displayed as a two-dimensional list for each layer. That is, the display unit 140 may display the interface specifications for a selected layer in two dimensions. The display unit 140 may also display the layer configuration in three dimensions (3D) instead of two dimensions.

[0027] Alternatively, the display unit 140 may display (visualize) interface specifications that center on the characteristic component and indicate relationships with other components. Fig. 5 is an explanatory diagram showing another example of displaying interface specifications. The example shown in Fig. 5 shows that the display unit 140 displays interface specifications that center on an arbitrary server B and indicate relationships with servers A and C.

[0028] The input unit 120, the extraction unit 130, and the display unit 140 are realized by a computer processor (e.g., a CPU (Central Processing Unit), a GPU (Graphics Processing Unit)) that operates according to a program (management program). For example, the program may be stored in the storage unit 10 of the management device 100, and the processor may read the program and operate as the input unit 120, the extraction unit 130, and the display unit 140 according to the program.

[0029] Furthermore, the functions of the input unit 120, the extraction unit 130, and the display unit 140 may be provided in a SaaS (Software as a Service) format. Furthermore, the input unit 120, the extraction unit 130, and the display unit 140 may each be realized by dedicated hardware.

[0030] Furthermore, some or all of the components of each device may be realized by general-purpose or dedicated circuits, processors, etc., or a combination of these. These may be configured by a single chip, or by multiple chips connected via a bus. Some or all of the components of each device may be realized by a combination of the above-mentioned circuits, etc., and programs.

[0031] Furthermore, when some or all of the components of the management device 100 are realized by multiple information processing devices, circuits, etc., the multiple information processing devices, circuits, etc. may be centrally or decentralized. For example, the information processing devices, circuits, etc. may be realized as a client-server system, a cloud computing system, or the like, in a form in which each is connected via a communication network.

[0032] Next, an example of the operation of the management device of this embodiment will be described. Fig. 6 is a flowchart showing an example of the operation of the management device 100 of this embodiment. In accordance with interface information designed for each component that makes up the system, the display unit 140 displays a list of interface specifications within the component or between the component for each common layer (step S11).

[0033] As described above, in this embodiment, the display unit 140 displays a list of interface specifications within or between components of a system for each common layer in accordance with interface information designed for each component of the system. This allows for management of the overall picture of interfaces between the components of the system.

[0034] For example, when the system to be managed is large-scale, the amount of information involved is large, and the nature of interface documentation means that the scope of interface documentation that can be viewed at one time is limited. This makes it difficult and time-consuming to grasp the overall picture across documents. Furthermore, if you try to understand interface specifications from multiple angles, additional registration is required. Furthermore, if interface specifications are changed, the work of revising interface documentation and confirming the scope of impact also requires time and effort.

[0035] On the other hand, in this embodiment, the display unit 140 displays a list of interface specifications, which improves visibility and also improves review accuracy. Also, since the display unit 140 displays a list of interface specifications, the information can be digitized, which makes it possible to use it as a substitute for interface documents.

[0036] Furthermore, since the display unit 140 displays a list based on the interface specifications, scalability (addition or modification of the system, addition or modification of the interface) can be improved, and it is also easy to check the extent of the impact of additions or modifications.

[0037] Embodiment 2. Next, a second embodiment of the present disclosure will be described, which is a management device that manages the difference between the specifications at the time of design and the situation at the time of implementation.

[0038] 7 is an explanatory diagram showing a configuration example of a second embodiment of a management device according to the present disclosure. The management device 200 of this embodiment includes a storage unit 210, a collection unit 220, an extraction unit 230, a difference identification unit 240, and a display unit 250.

[0039] The storage unit 210 stores interface specifications designed for each component element, similar to the storage unit 110 of the first embodiment. Furthermore, in this embodiment, the storage unit 210 stores interface logs acquired by the collection unit 220 (described later) and interface statuses extracted by the extraction unit 230. The storage unit 210 is also realized by, for example, a magnetic disk or the like.

[0040] The collection unit 220 acquires interface logs from the system components. The form of the interface logs is not particularly limited, and may be logs that are collected sequentially when the components are operating, or logs that are output all at once to a file, etc. The collection unit 220 stores the acquired interface logs in the storage unit 210.

[0041] The extraction unit 230 extracts the interface status from the acquired interface log. The content indicating the interface status is arbitrary, and examples include an actual measurement value such as the amount of data, and an error occurrence status.

[0042] It is also possible that the interface log does not match the expected format. In such cases, the extraction unit 230 may, for example, convert the extracted log content into a management format or aggregate it to match the format. The extraction unit 230 may also use a pre-trained model to extract the log format and the range of patterns that can be taken by the variable part without prior definition. Since methods for extracting logs as needed are widely known, detailed explanations will be omitted here.

[0043] The difference identification unit 240 identifies the difference between the interface status and the interface specifications. Specifically, the difference identification unit 240 identifies interfaces where the difference between the interface status and the interface specifications exceeds a predetermined standard. This difference is the difference between design and implementation, and can be said to indicate the degree of deviation from the design value. Therefore, the difference identification unit 240 may detect the possibility of an abnormality occurring in the corresponding interface (for example, the possibility of a failure) or a location with a high load, based on the identified difference.

[0044] Similar to the display unit 140 of the first embodiment, the display unit 250 displays a list of interface specifications within or between components in accordance with interface information designed for each component constituting the system. Furthermore, the display unit 250 of this embodiment may display an interface for which a difference has been identified by the difference identification unit 240 in a manner that allows the interface to be distinguished from other interfaces according to the difference.

[0045] Specifically, the display unit 250 may display an interface whose difference exceeds a predetermined standard in a manner that allows it to be distinguished from other interfaces. Furthermore, the display unit 250 may further change the display manner depending on the degree to which the difference exceeds the standard. Furthermore, the display unit 250 may change the display manner depending on the type of difference from the standard.

[0046] Fig. 8 is an explanatory diagram showing another example of a list of interface specifications. In the example shown in Fig. 8, an excess or deficiency was identified in the interface between Server D of System A and Server B by comparing it with the design values, and the corresponding area is displayed with a darker shaded area. Also, in the example shown in Fig. 8, a deviation in interface timing, etc., was identified in the interface between Terminal A of System A and Terminal B of System B by comparing it with the design values, and the corresponding area is displayed with a lighter shaded area.

[0047] The method for changing the display mode is not limited to the shading as exemplified in Fig. 8, and the mode may be changed by, for example, color, etc. For example, the darkly shaded areas as exemplified in Fig. 8 may be displayed in red, and the lightly shaded areas may be displayed in orange.

[0048] Furthermore, the display unit 250 may display the reason for identifying the difference in the detailed content of the interface. Fig. 9 is an explanatory diagram showing an example of a method for inquiring about the detailed content of the interface. In the example shown in Fig. 9, the interface in which a difference has been identified is displayed in bold italic, and the details of the reason for the detection are also displayed. Note that instead of being displayed in bold italic, that part may be displayed in red.

[0049] The display unit 250 may also display a list of interfaces in order of data volume or access frequency, etc. Fig. 10 is an explanatory diagram showing an example of detailed interface content. In the example shown in Fig. 10, interfaces are listed and displayed in order of the amount of data on a specified day.

[0050] In this way, by listing the design values ​​and actual measured values ​​in terms of data volume, access frequency, etc., it becomes possible to identify areas that are likely to become problematic or areas that may become problematic as actual measured values.

[0051] The collection unit 220, extraction unit 230, difference identification unit 240, and display unit 250 are realized by a processor of a computer that operates according to a program (management program).

[0052] Next, the operation of the management device 200 of this embodiment will be described. Fig. 11 is an explanatory diagram showing an example of the operation of the management device 200 of this embodiment. The extraction unit 230 extracts the interface status from the interface log acquired from the component (step S21). The difference identification unit 240 identifies the difference between the interface status and the interface specifications (step S22). Then, the display unit 250 displays the interface for which a difference has been identified in a manner that allows it to be distinguished from other interfaces according to the difference (step S23).

[0053] As described above, in this embodiment, the extraction unit 230 extracts the interface status from the interface log acquired from the component, and the difference identification unit 240 identifies the difference between the interface status and the interface specifications. Then, the display unit 250 displays the interface for which a difference has been identified in a manner that allows it to be distinguished from other interfaces according to the difference. Therefore, in addition to the effect of the first embodiment, deviations from the specifications can be discovered early.

[0054] For example, in the case of a large-scale system, because a large amount of information is handled, there are cases where differences between the design and implementation go unnoticed until they manifest as a defect. On the other hand, in this embodiment, the difference identification unit 240 identifies differences from the interface specifications, which prevents oversights and also makes it possible to detect symptoms of an abnormality before it is detected in the system log.

[0055] Furthermore, by combining the management device 200 of this embodiment with the outputs of system monitoring software, security software, and backup management software, it becomes possible to manage the system in a more multifaceted and centralized manner. These functions may be implemented using the outputs of the other software described above, or the management device 200 may implement these functions. Examples of the outputs here include CPU usage, memory usage, HDD usage, system logs, security diagnosis execution timing, and backup execution timing.

[0056] Next, an overview of the present disclosure will be described. Fig. 12 is a block diagram showing an overview of a management device of the present disclosure. A management device 80 (e.g., management device 100, management device 200) according to the present disclosure includes a display unit 81 (e.g., display unit 140, display unit 250) that displays a list of interface specifications within or between components (e.g., devices, modules, etc.) that make up a system, for each common (e.g., protocol) layer, in accordance with interface information designed for each component.

[0057] Such a configuration allows for a global view of the interfaces between the components that make up the system.

[0058] Furthermore, the display unit 81 may display part of the interface specifications in a simplified form (for example, a circle or a hyphen).

[0059] Furthermore, the display unit 81 may display a list of interface specifications in a manner that associates the display in a simplified manner with detailed content of the interface specifications (for example, by link, etc.).

[0060] Furthermore, when an association mode is specified, the display unit 81 may display detailed content of the interface.

[0061] Furthermore, the management device 80 may include a status extraction unit (e.g., extraction unit 230) that extracts the status of an interface from the interface log acquired from the component, and a difference identification unit (e.g., difference identification unit 240) that identifies the difference between the interface status and the interface specifications. The display unit 81 may then display the interface for which a difference has been identified in a manner that allows the interface to be distinguished from other interfaces according to the difference.

[0062] Specifically, the display unit 81 may display an interface whose difference exceeds a predetermined standard in a manner that makes it possible to distinguish it from other interfaces.

[0063] Additionally, the display unit 81 may change the display mode depending on the type of difference.

[0064] The management device 80 may also include an input unit (e.g., input unit 120) that accepts input of interface information including the specifications of the designed interface, and a specification extraction unit (e.g., extraction unit 130) that extracts the specifications of the interface within or between components from the interface information.

[0065] 13 is a schematic block diagram showing the configuration of a computer according to at least one embodiment. The computer 1000 includes a processor 1001, a main memory device 1002, an auxiliary memory device 1003, and an interface 1004. The computer 1000 may also be connected to a computer that executes a mathematical programming solver, an annealing machine, a simulator, or the like.

[0066] The above-mentioned management device 80 is implemented in a computer 1000. The operations of the above-mentioned processing units are stored in the form of a program (management program) in an auxiliary storage device 1003. The processor 1001 reads the program from the auxiliary storage device 1003, loads it into the main storage device 1002, and executes the above-mentioned processing in accordance with the program.

[0067] In at least one embodiment, the auxiliary storage device 1003 is an example of a non-transitory tangible medium. Other examples of non-transitory tangible media include a magnetic disk, a magneto-optical disk, a CD-ROM (Compact Disc Read-only memory), a DVD-ROM (Read-only memory), and a semiconductor memory connected via the interface 1004. In addition, when this program is distributed to the computer 1000 via a communication line, the computer 1000 that receives the program may load the program into the main storage device 1002 and execute the above processing.

[0068] The program may also be a program for realizing part of the above-described functions. Furthermore, the program may be a so-called differential file (differential program) that realizes the above-described functions in combination with another program already stored in the auxiliary storage device 1003.

[0069] A part or all of the above-described embodiments can be described as, but not limited to, the following supplementary notes.

[0070] (Note 1) A display unit is provided that displays a list of interface specifications within or between components for each common layer according to the interface information designed for each component that makes up the system. A management device characterized by:

[0071] (Appendix 2) The display unit displays part of the interface specifications in a simplified format. 2. The management device of claim 1.

[0072] (Appendix 3) The display unit displays a list of interface specifications in a manner that associates a simplified display with detailed interface specifications. 3. The management device of claim 2.

[0073] (Note 4) The display unit displays detailed content of the interface when the association mode is specified. 4. The management device of claim 3.

[0074] (Appendix 5) A status extraction unit that extracts the status of an interface from an interface log acquired from a component; a difference specifying unit that specifies a difference between the interface status and the interface specifications, The display unit displays the interface for which the difference has been identified in a manner that allows the interface to be distinguished from other interfaces according to the difference. 5. The management device according to claim 1, wherein the management device is a device for managing a plurality of data streams.

[0075] (Appendix 6) The display unit displays an interface whose difference exceeds a predetermined standard in a manner that makes it distinguishable from other interfaces. 6. The management device of claim 5.

[0076] (Note 7) The display changes its display mode depending on the type of difference. 6. The management device of claim 5.

[0077] (Appendix 8) An input unit that accepts input of interface information including the specifications of the designed interface; a specification extraction unit that extracts interface specifications within or between components from the interface information. 8. The management device according to claim 1, wherein the management device is a device for managing a plurality of data streams.

[0078] (Appendix 9) A computer lists the interface specifications within or between components of a system for each common layer, according to the interface information designed for each component. A management method characterized by:

[0079] (Appendix 10) The computer displays part of the interface specifications in a simplified form. Management method described in Appendix 9.

[0080] (Appendix 11) To the computer, A display process that lists interface specifications within or between components in accordance with the interface information designed for each component that makes up the system, for each common layer. A management program for running the program.

[0081] (Appendix 12) Display part of the interface specifications in a simplified form on the computer through display processing. The management program described in Appendix 11.

[0082] Although the present invention has been described above with reference to the embodiments and examples, the present invention is not limited to the above-described embodiments and examples. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. [Industrial Applicability]

[0083] The present invention is suitably applied to a management device that manages the status of a system, and is applicable to, for example, large-scale system development in general. [Explanation of symbols]

[0084] 100,200 Management device 110,210 Storage section 120 Input section 130 Extraction part 140 Display section 220 Collection Department 230 Extraction part 240 Difference identification part 250 Display section

Claims

1. A display unit is provided that displays a list of interface specifications within or between components for each common layer according to interface information designed for each component that constitutes the system. A management device characterized by:

2. The display unit displays a part of the interface specifications in a simplified form. The management device according to claim 1 .

3. The display unit displays a list of interface specifications in a manner that associates the display in a simplified manner with detailed content of the interface specifications. The management device according to claim 2.

4. The display unit displays detailed content of the interface when the association mode is specified. The management device according to claim 3.

5. a status extraction unit that extracts an interface status from an interface log acquired from the component; a difference specifying unit that specifies a difference between the interface status and the interface specifications, The display unit displays the interface for which the difference has been identified in a manner that allows the interface to be distinguished from other interfaces according to the difference. The management device according to any one of claims 1 to 4.

6. The display unit displays the interface whose difference exceeds a predetermined standard in a manner that makes it distinguishable from other interfaces. The management device according to claim 5.

7. The display unit changes the display mode depending on the type of difference. The management device according to claim 5.

8. an input unit that receives input of interface information including specifications of the designed interface; a specification extraction unit that extracts interface specifications within or between components from the interface information. The management device according to any one of claims 1 to 4.

9. The computer lists the interface specifications within or between components of the system for each common layer according to the interface information designed for each component. A management method characterized by:

10. On the computer, A display process that lists interface specifications within or between components in accordance with the interface information designed for each component that makes up the system, for each common layer. A management program for running the program.

Images