Information processing system, information processing method, and program

The system addresses the lack of container monitoring in Kubernetes by integrating a container information extraction unit and service information collection, enabling efficient resource management and optimization within containers.

JP7581687B2Active Publication Date: 2024-11-13NEC CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2020127891
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-07-29
Publication Date
2024-11-13
Estimated Expiration
2040-07-29

AI Technical Summary

Technical Problem

Existing container orchestration tools like Kubernetes lack the capability to monitor container information effectively, making it difficult to manage and optimize resource usage within containers.

Method used

An information processing system and method that includes a container information extraction unit to gather data within containers, a service information collection unit to gather service data from a master node, and a data storage unit to associate and store this information, allowing for the monitoring and management of container and service information.

Benefits of technology

Enables effective monitoring and management of container information, optimizing resource usage and ensuring that containers do not exceed predefined limits, thereby improving system performance and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007581687000001
    Figure 0007581687000001
  • Figure 0007581687000002
    Figure 0007581687000002
  • Figure 0007581687000003
    Figure 0007581687000003
Patent Text Reader

Abstract

To provide an information processing system that monitors internal information on a container managed by a container orchestration tool.SOLUTION: An information processing system includes a container information extraction unit that extracts container information as information used in the inside of a container managed by a container orchestration tool, and a container information output unit that outputs the container information extracted by the container information extraction unit to the outside of the container.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing system, an information processing method, and a program. [Background technology]

[0002] In OS (operating system) virtualization technology, containers are used that bundle together libraries and applications required to run applications (for example, Patent Literature 1). Containers are managed in an integrated manner by a container orchestration tool such as Kubernetes.

[0003] When building an information processing system using a container orchestration tool, applications are provided by deploying them on containers, but depending on the user's settings, it is possible to multiplex containers when the amount of access to an application increases or for the purpose of clustering. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-42484 A Summary of the Invention [Problem to be solved by the invention]

[0005] In order to integrate and manage containers using a container orchestration tool, it is desirable to monitor information used inside the container (container information). However, Patent Document 1 does not disclose anything about monitoring container information.

[0006] SUMMARY OF THE PRESENT DISCLOSURE An object of the present invention is to provide an information processing system, an information processing method, and a program that solve the above-mentioned problems. [Means for solving the problem]

[0007] According to a first aspect of this embodiment, an information processing system includes: a container information extraction unit that extracts container information that is information used inside a container managed by a container orchestration tool; a container information output unit that outputs the container information extracted by the container information extraction unit to an outside of the container; a service information collection unit that collects service information that is information about a service constructed by a plurality of the containers, the service information being information currently used by the service from the master node by transmitting inquiry information including a name of the service to a master node; a container information collection unit that collects the container information output from the container information output unit; an information processing unit that associates the container information collected by the container information collection unit with the service information collected by the service information collection unit and stores them in a data storage unit; a first worker node including the service information collection unit, the container information collection unit, and the information processing unit, and to which the container is assigned; a second worker node including the container information extraction unit and the container information output unit, and to which the container is assigned; and the master node that manages the first worker node and the second worker node. .

[0008] According to a second aspect of this embodiment, an information processing method includes: An information processing method executed by an information processing system having a first worker node to which a container is assigned, a second worker node to which the container is assigned, and a master node that manages the first worker node and the second worker node, the method including: collecting service information that is information on a service constructed by a plurality of the containers, the service information being information currently used by the service being collected from the master node by sending query information including a name of the service to the master node; extracting container information that is information used inside the container managed by a container orchestration tool; outputting the extracted container information outside the container; collecting the output container information; and storing the collected container information and the collected service information in association with each other. .

[0009] According to a third aspect of this embodiment, the program includes: The method causes a computer having a container orchestration tool installed in an information processing system having a first worker node to which a container is assigned, a second worker node to which the container is assigned, and a master node that manages the first worker node and the second worker node to execute the following: extracting container information that is information used inside a container managed by the container orchestration tool; outputting the extracted container information to the outside of the container; collecting service information that is information on a service constructed by a plurality of the containers, the service information being information currently used by the service from the master node by sending query information including a name of the service to the master node; collecting the output container information; and storing the collected container information and the collected service information in association with each other. . Effect of the Invention

[0010] According to the present invention, container information can be monitored. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 illustrates an example of a configuration of an information processing system according to a first embodiment. [Diagram 2] FIG. 4 is a diagram illustrating an example of related information stored in a data storage unit of the first embodiment. [Diagram 3] FIG. 2 is a sequence diagram of the information processing system up to construction of a service according to the first embodiment. [Figure 4] FIG. 11 is a sequence diagram of the information processing system after the service of the first embodiment is constructed. [Diagram 5] 4 is a flowchart showing the flow of operations of a data monitoring unit according to the first embodiment. FIG. [Figure 6] FIG. 11 illustrates an example of a configuration of an information processing system according to a second embodiment. [Figure 7] This figure illustrates issues that arise when building a system on Kubernetes. [Figure 8] This figure illustrates issues that arise when building a system on Kubernetes. [Figure 9] This figure illustrates issues that arise when building a system on Kubernetes. [Figure 10] FIG. 2 is a diagram illustrating a minimum configuration of an information processing system according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an information processing system according to an embodiment will be described with reference to the drawings.

[0013] (First embodiment) FIG. 1 is a diagram illustrating an example of a configuration of an information processing system 1 according to a first embodiment. The information processing system 1 uses a container orchestration tool such as Kubernetes to integrate and manage a plurality of containers. The information processing system 1 illustrated below integrates and manages a plurality of containers using Kubernetes. Kubernetes is an open source framework that manages the deployment, scaling, and the like of containerized applications. A container is a collection of libraries and applications required to run an application.

[0014] In the information processing system 1 of this embodiment, the following environment is assumed. (1) A service is built on multiple containers. (2) The service is built using the Kubernetes Operator. (3) Container operations are performed by an orchestration tool (Kubernetes), which defines information for identifying the node on which the container runs and information for accessing the services running on the container. (4) A Web server or application server of a client-server model that has an architecture that allows separation of an application section and a framework section for service execution.

[0015] An example of the configuration of the information processing system 1 will be described below.

[0016] 1, an information processing system 1 includes a master node 100, a first worker node 200, and a second worker node 300. The configuration of the information processing system 1 corresponds to a so-called Kubernetes cluster.

[0017] The master node 100 may be a single physical server or a virtual machine. The master node 100 may be a computer on which software for the master function of Kubernetes is installed. The master node 100 manages the first worker node 200 and the second worker node 300. That is, the master node 100 is a group of components responsible for the operation and management of Kubernetes, and manages the entire Kubernetes cluster. The configuration of the master node 100 is well known, so detailed explanation will be omitted, but it has components such as an API server, a scheduler, a controller manager, and a data store (etcd).

[0018] The first worker node 200 is assigned one or more containers and runs the containers to provide services, i.e., the first worker node 200 executes containerized applications.

[0019] The second worker node 300 is assigned one or more containers and runs the containers to provide services, i.e., the second worker node 300 executes containerized applications.

[0020] The following describes the configuration of the first worker node 200. The first worker node 200 has a container 110, a storage unit 120, and a container 130. A Kubernetes Operator (software) is installed in the first worker node 200, and the Kubernetes Operator holds the container 110, the storage unit 120, and the container 130.

[0021] The container 110 includes a service providing function unit 111 .

[0022] The service providing function unit 111 acquires a service deployment request from the outside, which includes a service definition (container image), service limit values, and upper limit values ​​of information on internal resources used within the container (hereinafter referred to as "container information"). After receiving the service deployment request, the service providing function unit 111 builds the service on Kubernetes based on the service definition. In addition, the service providing function unit 111 registers the name of the service and the limit values ​​of the service in the storage unit 120. After receiving the service deployment request, the service providing function unit 111 stores the upper limit value of the container information in the container 130.

[0023] Here, the container information is information indicating the usage status of container resources, and includes, for example, at least one of information on the CPU used in the container, memory usage status, and request flow rate. For example, if the container information includes all of the information on the CPU, memory usage, and request flow rate, the upper limit value of the container information includes the upper limit value of the CPU information, the upper limit value of memory usage, and the upper limit value of the number of requests.

[0024] The storage unit 120 is, for example, a shared directory, and stores the name of the service and the limit value of the service.

[0025] The container 130 holds an information collection unit 131, an information management unit 132, an internal resource restriction unit 133, and an information output unit 134. Here, the first worker node 200 has a function called an agent (e.g., kubelet). In this agent, the information collection unit 131, the information management unit 132, the internal resource restriction unit 133, and the information output unit 134 are held.

[0026] The information collection unit 131 includes a service information collection unit 400 , a container information collection unit 410 , and an information processing unit 420 .

[0027] The service information collection unit 400 makes an inquiry to the master node 100 and collects service information, which is information on a target service (hereinafter referred to as a "target service"), from the master node 100. This service information is information on resources currently being used by the target service (e.g., information on the CPU and memory).

[0028] The container information collection unit 410 acquires access information including a container in which the target service runs and the actual address of the container from the master node 100. Then, the container information collection unit 410 accesses the second worker node 300 based on the access information to collect container information of one or more containers in the second worker node 300. This container information indicates, for example, resource information of one container. Therefore, when there are multiple containers in the second worker node 300, the container information collection unit 410 collects container information for each of the containers.

[0029] The information processing unit 420 associates the container information collected by the container information collection unit 410 with the service information collected by the service information collection unit 400 and stores them in the information management unit 132 .

[0030] The information management unit 132 has a data storage unit 430 that stores information. The data storage unit 430 stores associated information in which container information and service information are associated with each other by the information processing unit 420. Fig. 2 is a diagram showing an example of the associated information stored in the data storage unit 430.

[0031] As an example, the data storage unit 430 stores the related information in a table format as shown in Fig. 2. The data storage unit 430 is provided with a related information table in which the related information is stored.

[0032] In the related information table, the first category information, the second category information, and the third category information are hierarchically related to each other.

[0033] The first category information stores information for identifying whether the information is about a service or about a container.

[0034] The second category information is information that identifies the type of resource in the first category information. For example, the resource is information on the CPU, memory information (memory usage), request flow rate information, etc. The second category information is associated with information on the service stored as the first category information and information on the container stored as the first category information.

[0035] The third category information is information that further specifies the second category information. For example, in CPU information, the number of cores and CPU time are each stored as the third category information. For example, in service information, memory information is the usage amount of one memory. For example, in container-related information (container information), heap memory usage and non-heap memory usage are each stored as the third category information as information that specifies memory information. In container-related information (container information), for example, the number of requests corresponding to each URL is stored as the third category information as information that specifies request flow information.

[0036] This associates the container information with the service information, making it possible to identify the information contained in each of the container information and the service information.

[0037] The internal resource limiting unit 133 includes an upper limit value storage unit 440 and a data monitoring unit 450 .

[0038] The upper limit storage unit 440 stores the upper limit of the container information.

[0039] The data monitoring unit 450 monitors the related information stored in the data storage unit 430. The data monitoring unit 450 checks whether the target service is using container information at or above a preset upper limit, i.e., the upper limit stored in the upper limit storage unit 440. If the check shows that the container information is being used at or above the upper limit, the data monitoring unit 450 causes the service providing function unit 111 to reduce the number of pods, which are collections of containers.

[0040] The information output unit 134 is capable of reading the related information stored in the data storage unit 430 and outputting it to the user.

[0041] The configuration of the second worker node 300 will be described below. The second worker node 300 has a container 310. That is, the second worker node 300 is a server that runs the container 310 deployed by the master node 100. The container 310 provides a specific service. The container 310 includes an application unit 500 and a framework unit 510.

[0042] The application unit 500 is an entity that provides a particular service.

[0043] The framework unit 510 is a framework for running applications.

[0044] The framework unit 510 has a metrics function provided by the framework unit 510. The framework unit 510 has a container information extraction unit 600 and a container information output unit 610. For example, the container information extraction unit 600 and the container information output unit 610 are implemented in the framework unit 510 by extending the metrics function.

[0045] The container information extraction unit 600 extracts container information that is information used inside the container 310. As an example, the container information extracted by the container information extraction unit 600 is information on the CPU used by the container 310 (number of cores and time), memory usage (heap and non-heap), and request flow rate.

[0046] The container information output unit 610 outputs the container information extracted by the container information extraction unit 600 to the outside of the container 310 .

[0047] The framework unit 510 has a setting reflection function. The setting reflection function may be provided as one function of the framework.

[0048] (Operations up to building the service) The operation of the information processing system 1 up to the construction of a service will be described below with reference to Fig. 3. Fig. 3 is a sequence diagram of the information processing system 1 up to the construction of a service.

[0049] The user makes a deployment request for a service to the Kubernetes Operator (step S101). As an example, the user makes a deployment request for a service to the Kubernetes Operator after defining rules.

[0050] The Kubernetes Operator deploys the service based on a deployment request for the target service from the user (step S102). Specifically, the service providing function unit 111 held by the Kubernetes Operator builds the target service on Kubernetes based on the definition of the service specified by the user included in the deployment request for the service, and stores the upper limit value of the container information in the upper limit value storage unit 440 in the agent (step S103). The service providing function unit 111 registers the name of the target service stored by the Kubernetes Operator in step S102 and the setting value / limit value set for the target service in the storage unit 120 (step S104). This completes the construction of the target service.

[0051] (Operation after the service is created) The operation of the information processing system 1 after the service has been established will be described below with reference to Fig. 4. Fig. 4 is a sequence diagram of the information processing system 1 after the service has been established.

[0052] The information collection unit 131 of the agent reads the name of the target service stored in the storage unit 120, and the setting value and limit value set for the target service from the storage unit 120 (step S201).

[0053] The service information collection unit 400 queries the master node 100 using the name of the target service read in step S201 as a key, and collects service information, which is usage information of resources currently being used by the target service, from the master node 100 (step S202).

[0054] The container information collection unit 410 makes an inquiry to the master node 100 and acquires information indicating the container 310 in which the target service runs and the actual address of the container 310. Then, the container information collection unit 410 accesses the container information output unit 610 of the framework unit 510 based on the acquired information indicating the container 310 and the actual address of the container 310 (step S203).

[0055] When accessed by the container information collection unit 410, the container information extraction unit 600 extracts container information including information on the CPU used by this container 310 (number of cores and time), memory usage (heap and non-heap), and request flow rate (step S204). Then, the container information output unit 610 outputs the container information extracted by the container information extraction unit 600 to the container information collection unit 410 (step S205).

[0056] When the container information collection unit 410 receives the container information from the container information output unit 610, for example, the information collection unit 131 assigns to the container information a collection time (for example, UTC) required to obtain the container information (step S206). Then, the information collection unit 131 associates the service information collected by the service information collection unit 400 with the container information to which the collection time has been assigned (step S207), and stores the associated related information in the data storage unit 430 (step S208).

[0057] The process shown in FIG. 4 is repeated periodically as long as the agent exists.

[0058] The user can access the information output unit 134. By accessing the information output unit 134, the user can check the information registered in the data storage unit 430.

[0059] 5, the data monitoring unit 450 in the agent checks whether an upper limit setting exists (step S301), and if an upper limit setting exists, checks whether the target service is using the internal resources of the container at or above the defined upper limit (step S302). If the target service is using the internal resources of the container at or above the upper limit, the data monitoring unit 450 then requests the service providing function unit 111 to reduce the number of pods (step S303). Here, a pod is a collection of containers.

[0060] Second Embodiment 6 is a diagram illustrating an example of a configuration of an information processing system 1A according to the second embodiment. Like the information processing system 1, the information processing system 1A integrates and manages a plurality of containers by using a container orchestration tool represented by Kubernetes. The information processing system 1A differs from the first embodiment in that it does not have a Kubernetes Operator and a service providing function unit 111.

[0061] In the information processing system 1A according to the second embodiment, similarly to the first embodiment, the above environments (1) to (4) are assumed.

[0062] As shown in FIG. 6, the information processing system 1A includes a master node 100, a first worker node 200A, a second worker node 300, and a third worker node 700. The configuration of the information processing system 1A corresponds to a so-called Kubernetes cluster. In the following embodiments, the same reference numerals are used for the same contents as those described in the first embodiment, and the description is omitted as appropriate.

[0063] The first worker node 200A is assigned one or more containers and runs the containers to provide service #2.

[0064] The second worker node 300 is assigned one or more containers and runs the containers to provide service #1.

[0065] The third worker node 700 is assigned one or more containers and runs the containers to provide service #3, i.e., the second worker node 300 runs a containerized application.

[0066] The third worker node 700 is assigned one or more containers and runs the containers to provide service #3, i.e., the third worker node 700 executes containerized applications.

[0067] The configuration of the third worker node 700 will be described below. The third worker node 700 has a container 710. That is, the third worker node 700 runs the container 710 deployed by the master node 100. The container 710 provides a specific service #3. The container 710 includes an application unit 720.

[0068] The application unit 720 is an entity that provides a particular service #3.

[0069] The configuration of the first worker node 200A will be described below. The first worker node 200A has a container 130. Note that the Kubernetes Operator is not introduced to the first worker node 200A. In other words, if service information and container information are to be acquired for all services rather than a specific service, it is possible to collect the information without going through the Kubernetes Operator.

[0070] The service information collection unit 400 requests the master node 100 for service information registered on Kubernetes, and then collects information on all services based on that service information.

[0071] The container information collection unit 410 attempts to access each framework part based on the service information collected by the service information collection unit 400. Here, if there is a service that does not have a framework part (service #3 shown in FIG. 6), the container information collection unit 410 gives up collecting container information and collects container information only from the framework parts of collectable containers.

[0072] The following describes the issues that arise when building a system on Kubernetes, using Figs. 7 to 9. For example, in the example shown in Fig. 7, an application prepared by the user is composed of multiple containers, and each service has a virtual address that can be accessed. When monitoring is performed under these circumstances, the service information is monitored, and it is not possible to monitor the resource usage status within each container, i.e., the container information. Therefore, in order to monitor container information, a monitoring framework for analyzing this service information is required.

[0073] Kubernetes provides visualization and control of resources at the service and container levels, but when there are multiple processes inside a container, it is not possible to control the service based on that information, so there is a demand for monitoring container information.

[0074] To monitor container information, you can incorporate a unique collection process that collects container information for each container. In this case, as shown in Figure 8, service information and container information are generated as separate data, and it is not possible to determine that these two elements are related. Therefore, it is not possible to link container information with service information.

[0075] Resource restrictions in Kubernetes may be implemented by the master node on a per-service basis, as shown in Figure 9. Resource restrictions by Kubernetes can be implemented on a per-service or per-container basis, but in an environment such as that shown in Figure 9 where multiple processes exist within a container, restrictions specific to process A in which an application runs cannot be implemented.

[0076] In each of the above embodiments, the Metrics function that exists in the framework for executing an application is extended to have a function for extracting and outputting container information, thereby making it possible to monitor the container information.

[0077] In each of the above embodiments, a Kubernetes Operator is provided for building a container image including an application on Kubernetes, and the following functions are implemented within the Kubernetes Operator. -Extended service deployment capabilities maintained by Kubernetes Operator. -A function to collect service information and container information using the agent function. - Ability to limit container information using the Agent function.

[0078] By using the Kubernetes Operator, it is possible to associate service information with container information. Furthermore, by using the function to restrict container information, it is possible to monitor the resource usage status (container information) inside the container and suppress further resource usage.

[0079] An embodiment of a minimum configuration of the information processing system 1, 1A according to the embodiment will be described with reference to Fig. 10. The information processing system 1, 1A according to the embodiment has a container information extraction unit 600 and a container information output unit 610. The container information extraction unit 600 extracts container information, which is information used inside a container managed by a container orchestration tool. The container information output unit 610 outputs the container information extracted by the container information extraction unit 600 to the outside of the container. This allows the information processing system 1, 1A to monitor the container information.

[0080] The information processing system 1, 1A may be realized in whole or in part by a computer. In this case, the computer may include a processor such as a CPU or a GPU, and a computer-readable recording medium. The information processing system 1, 1A may be realized by recording a program for realizing the functions of the information processing system 1, 1A in whole or in part by a computer in the computer-readable recording medium, and reading and executing the program recorded in the recording medium into the processor. Here, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, and a storage device such as a hard disk built into a computer system. Furthermore, the "computer-readable recording medium" may also include a medium that dynamically holds a program for a short period of time, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and a medium that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or a client in that case. The program may be a program for realizing a part of the functions described above, or may be a program that can realize the functions described above in combination with a program already recorded in the computer system, or may be a program that is realized using a programmable logic device such as an FPGA.

[0081] The above program may also be transmitted from a computer system in which the program is stored in a storage device or the like to another computer system via a transmission medium, or by transmission waves in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has the function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The above program may also be for realizing part of the above-mentioned functions. Furthermore, it may be a so-called difference file (difference program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0082] Throughout the specification, when a part is described as "comprising" or "having" a certain element, this does not mean that it excludes other elements, but that it may further include other elements, unless specifically stated to the contrary.

[0083] The term "unit" in the specification means a unit that processes at least one function or operation, which may be embodied as hardware or software, or a combination of hardware and software. [Explanation of symbols]

[0084] 1,1A Information Processing System 100 Masternodes 131 Information Gathering Department 200 1st worker node 300 Secondary Worker Nodes 400 Service Information Collection Department 410 Container Information Collection Department 420 Information Processing Department 700 3rd worker nodes 110,130,310,710 Container

Claims

1. A container information extraction unit that extracts container information that is information used inside a container managed by a container orchestration tool; a container information output unit that outputs the container information extracted by the container information extraction unit to an outside of the container; a service information collection unit that collects service information, which is information on a service constructed by a plurality of the containers, and collects the service information, which is information currently being used by the service, from the master node by transmitting inquiry information including a name of the service to a master node; a container information collection unit that collects the container information output from the container information output unit; an information processing unit that associates the container information collected by the container information collecting unit with the service information collected by the service information collecting unit and stores the associated information in a data storage unit; a first worker node including the service information collection unit, the container information collection unit, and the information processing unit, and to which the container is assigned; a second worker node including the container information extraction unit and the container information output unit, the second worker node being assigned to the container; The master node that manages the first worker node and the second worker node; An information processing system having the above configuration.

2. The container information extraction unit extracts at least one of information on a CPU used in the container, a memory usage status, and information on a request flow rate as the container information. The information processing system according to claim 1 .

3. a data monitoring unit that monitors the container information stored in the data storage unit, the data monitoring unit confirming whether the container information is being used by the service at or above a preset upper limit value, and reducing the number of pods, which are collections of containers, when the container information is being used at or above the upper limit value; 3. The information processing system according to claim 1 or 2.

4. The container information collection unit acquires access information including the container in which the service is running and a real address of the container from the master node, and collects the container information by accessing the second worker node based on the access information. The information processing system according to any one of claims 1 to 3.

5. a service provision function unit that acquires a service deployment request including a definition of the service and an upper limit value of the container information, builds the service based on the service deployment request, and stores a name of the service and the upper limit value in the first worker node; The information processing system according to any one of claims 1 to 3.

6. An information processing method executed by an information processing system having a first worker node to which a container is assigned, a second worker node to which the container is assigned, and a master node that manages the first worker node and the second worker node, comprising: Collecting service information, which is information on a service constructed by a plurality of the containers, by sending inquiry information including a name of the service to the master node, and collecting the service information, which is information currently being used by the service, from the master node; Extracting container information, the container information being information used within the container managed by a container orchestration tool; outputting the extracted container information outside the container; Collecting the output container information; storing the collected container information and the collected service information in association with each other; An information processing method comprising:

7. A computer having a container orchestration tool installed in an information processing system having a first worker node to which a container is assigned, a second worker node to which the container is assigned, and a master node that manages the first worker node and the second worker node, Extracting container information, the container information being information used within a container managed by the container orchestration tool; outputting the extracted container information outside the container; Collecting service information, which is information on a service constructed by a plurality of the containers, by sending inquiry information including a name of the service to the master node, and collecting the service information, which is information currently being used by the service, from the master node; Collecting the output container information; storing the collected container information and the collected service information in association with each other; A program that executes the following.

Citation Information

Patent Citations

  • Computer system, parameter setting device, and program

    JP2020042484A

  • Integrated storage management between storage systems and container orchestrators

    US20190361626A1