WO2021232842A1 - 一种获取Docker容器内虚拟机监控数据的方法及装置 - Google Patents

一种获取Docker容器内虚拟机监控数据的方法及装置 Download PDF

Info

Publication number
WO2021232842A1
WO2021232842A1 PCT/CN2021/073760 CN2021073760W WO2021232842A1 WO 2021232842 A1 WO2021232842 A1 WO 2021232842A1 CN 2021073760 W CN2021073760 W CN 2021073760W WO 2021232842 A1 WO2021232842 A1 WO 2021232842A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring data
virtual machine
container
docker
cloud platform
Prior art date
Application number
PCT/CN2021/073760
Other languages
English (en)
French (fr)
Inventor
赖广涛
季统凯
贺忠堂
Original Assignee
国云科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 国云科技股份有限公司 filed Critical 国云科技股份有限公司
Publication of WO2021232842A1 publication Critical patent/WO2021232842A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the embodiments of the present application relate to the technical field of container management, and in particular, to a method, device, electronic device, and storage medium for obtaining virtual machine monitoring data in a Docker container.
  • Container technology uses the characteristics of the Linux operating system to isolate resources, making resources more fully and effectively utilized.
  • cloud computing platforms have become more and more complex to update and iterate, and more and more various services are used, leading to deployment, installation, testing, delivery, and transportation.
  • problems facing maintenance There are also more and more problems facing maintenance.
  • Docker container technology the application of Docker container technology has become more and more extensive, making cloud computing platform containerization a mainstream solution to the current problems of complex project deployment and difficult update iterations.
  • Docker container isolates different applications deployed on the same server from resources, storage, and the network through its own isolation mechanism.
  • the services in the container cannot communicate freely without interfering with each other, which makes it very difficult to obtain the monitoring data of the virtual machine in the container.
  • the embodiments of the present application provide a method, device, electronic device, and storage medium for acquiring virtual machine monitoring data in a Docker container, which can acquire virtual machine monitoring data in a Docker container without destroying the independence between containers.
  • an embodiment of the present application provides a method for obtaining virtual machine monitoring data in a Docker container, including:
  • the monitoring data acquisition command is issued to the cloud platform container through the Docker management process
  • the cloud platform container runs a monitoring data acquisition script based on the monitoring data acquisition command, acquires corresponding virtual machine monitoring data, and returns the acquired virtual machine monitoring data to the Docker management process;
  • the Docker management process sends the virtual machine monitoring data to the collection terminal, and the collection terminal pushes the virtual machine monitoring data to the monitoring service container, the collection terminal is deployed on the host machine, and the cloud platform container
  • the monitoring service container is a unit that runs independently of each other.
  • the method includes:
  • pre-mounting the monitoring data acquisition script to the cloud platform container through the collection terminal includes:
  • the collection terminal mounts the monitoring data acquisition script to the cloud platform container based on the storage volume mounting mechanism of Docker.
  • issuing monitoring data acquisition commands to the cloud platform container through the Docker management process further includes:
  • a timer is deployed in advance, and the timer periodically triggers data collection based on the frequency set by the collection terminal.
  • the cloud platform container running a monitoring data obtaining script based on the monitoring data obtaining command to obtain corresponding virtual machine monitoring data includes:
  • the cloud platform container receives the monitoring data acquisition command
  • cloud platform containers there are multiple cloud platform containers, and multiple cloud platform containers run independently of each other.
  • the method further includes:
  • an apparatus for obtaining virtual machine monitoring data in a Docker container including:
  • the trigger module is used to issue monitoring data acquisition commands to the cloud platform container through the Docker management process when data collection is triggered;
  • the acquisition module is configured to run a monitoring data acquisition script based on the monitoring data acquisition command through the cloud platform container, acquire corresponding virtual machine monitoring data, and return the acquired virtual machine monitoring data to the Docker management process;
  • the push module is configured to send the virtual machine monitoring data to the collection terminal through the Docker management process, and the collection terminal pushes the virtual machine monitoring data to the monitoring service container, and the collection terminal is deployed on the host machine ,
  • the cloud platform container and the monitoring service container are units that operate independently of each other.
  • an electronic device including:
  • Memory and one or more processors
  • the memory is used to store one or more programs
  • the one or more processors When the one or more programs are executed by the one or more processors, the one or more processors implement the method for acquiring virtual machine monitoring data in a Docker container as described in the first aspect.
  • the embodiments of the present application provide a storage medium containing computer-executable instructions, when the computer-executable instructions are executed by a computer processor, the computer-executable instructions are used to execute the acquisition of virtual data in a Docker container as described in the first aspect.
  • the method of machine monitoring data when the computer-executable instructions are executed by a computer processor, the computer-executable instructions are used to execute the acquisition of virtual data in a Docker container as described in the first aspect. The method of machine monitoring data.
  • the monitoring data acquisition command is issued to the cloud platform container through the Docker management process, and the cloud platform container runs the monitoring data acquisition script based on the monitoring data acquisition command to acquire the corresponding virtual machine monitoring data, and will acquire
  • the obtained virtual machine monitoring data is returned to the Docker management process, and the virtual machine monitoring data is sent to the collection terminal through the Docker management process, and the collection terminal pushes the virtual machine monitoring data to the monitoring service container.
  • the virtual machine monitoring data in the cloud platform container can be obtained without destroying the independence between Docker containers, and the virtual machine monitoring data can be transferred between two Docker containers that run independently of each other. In this way, the data communication between Docker containers can be optimized, and a good cloud platform container operation management effect can be achieved.
  • FIG. 1 is a flowchart of a method for obtaining monitoring data of a virtual machine in a Docker container according to Embodiment 1 of the present application;
  • Figure 2 is a schematic diagram of Docker container deployment in the first embodiment of the present application
  • FIG. 3 is a flowchart of virtual machine monitoring data acquisition in Embodiment 1 of the present application.
  • FIG. 4 is a schematic structural diagram of an apparatus for acquiring monitoring data of a virtual machine in a Docker container provided by the second embodiment of the present application;
  • FIG. 5 is a schematic structural diagram of an electronic device provided in Embodiment 3 of the present application.
  • This application provides a method for acquiring virtual machine monitoring data in a Docker container, which aims to deploy the collection terminal, and the collection terminal issues commands through the Docker management process, so that the cloud platform container can run the monitoring data acquisition script to obtain the cloud platform container.
  • the virtual machine monitoring data of each virtual machine is further sent to the collection terminal, and the collection terminal is pushed to the monitoring service container.
  • Docker uses its own isolation mechanism to isolate different applications deployed on the same server from resources, storage, and the network. Between the Docker containers isolated on the network, the services between the containers cannot communicate freely without interfering with each other.
  • a method for acquiring virtual machine monitoring data in a Docker container is provided to solve the technical problem that it is difficult to transmit virtual machine monitoring data between existing Docker containers.
  • Figure 1 shows a flow chart of a method for obtaining virtual machine monitoring data in a Docker container provided in Embodiment 1 of the present application.
  • the method for obtaining virtual machine monitoring data in a Docker container provided in this embodiment may be containerized by Docker.
  • Executed by a computing platform the Docker containerized cloud computing platform may be implemented by software and/or hardware, and the Docker containerized cloud computing platform may be composed of two or more physical entities.
  • the method for obtaining virtual machine monitoring data in a Docker container specifically includes:
  • Docker is an open source application container engine.
  • Docker container refers to the unit where Docker divides the resources, storage, and network on the server and provides them to the application independent operation unit.
  • a cloud platform container and a monitoring service container are deployed based on Docker, and the cloud platform service and monitoring service are deployed in two independent Docker containers on the network, and the network and resources between the services are Under the premise of isolation, data transmission between independent Docker containers on two networks (virtual machine monitoring data in the embodiment of this application) is realized through the collection terminal deployed on the server and the Docker management process.
  • the collection terminal when data is transferred between Docker containers, the collection terminal is used as the data transmission intermediary between the cloud platform container and the monitoring service container. When virtual machine monitoring data is transmitted, the collection terminal is used to collect data from the cloud platform container. The virtual machine monitoring data further pushes the collected virtual machine monitoring data to the monitoring service container.
  • the collection terminal of the embodiment of the present application is deployed on a host machine (ie, a server). It is a jar program that collects virtual machine monitoring data running on the server, and does not rely on a Docker container.
  • the collection terminal deploys a timer in advance, and the timer periodically triggers data collection based on the frequency set by the collection terminal. The timer can repeatedly trigger the same operation at the same frequency without interruption.
  • the data acquisition frequency is preset through the acquisition terminal, and the monitoring data acquisition operation is triggered correspondingly to perform data acquisition.
  • the collection terminal uses the Docker management process to issue a monitoring data acquisition command to the cloud platform container, and the cloud platform container performs virtual machine monitoring data collection in response to this monitoring data acquisition command.
  • the Docker management process refers to the process used for container management that the Docker service starts automatically. When the Docker service starts, the Docker management process is also started synchronously.
  • the Docker management process has the highest authority used by the container, allowing each Docker container to execute specified commands and operations.
  • the monitoring data acquisition command is issued to the cloud platform container through the Docker management process, and the cloud platform container is allowed to execute the specified command to obtain the virtual machine monitoring data inside the container.
  • the command format for obtaining monitoring data is "docker exec[cloud platform container name][command]", where "[cloud platform container name]” refers to the name of the Docker container that has deployed cloud platform services, and "[command]” refers to It is a command that instructs the cloud platform container to obtain virtual machine monitoring data.
  • the cloud platform container runs a monitoring data acquisition script based on the monitoring data acquisition command, acquires corresponding virtual machine monitoring data, and returns the acquired virtual machine monitoring data to the Docker management process.
  • the cloud platform container triggers the running of the monitoring data acquisition script based on the monitoring data acquisition command issued by the Docker management process to acquire the monitoring data of the virtual machine in the cloud platform container.
  • the monitoring data acquisition script was mounted to the cloud platform container in advance through the collection terminal.
  • the collection terminal mounts the monitoring data acquisition script to the cloud platform container based on the storage volume mounting mechanism of Docker.
  • the virtual machine monitoring data is acquired by running the monitoring data acquisition script.
  • the virtual machine monitoring data acquisition process includes:
  • the cloud platform container receives the monitoring data acquisition command
  • S1202 Run a monitoring data acquisition script based on the monitoring data acquisition command, where the monitoring data acquisition script includes an executable command file for acquiring various monitoring data of the virtual machine;
  • S1203 Scan the information of each virtual machine in the cloud platform container based on the executable command file to obtain corresponding result data, and use the result data as virtual machine monitoring data.
  • the monitoring data acquisition script includes executable command files used to obtain various monitoring data of the virtual machine. By executing these executable command files, each virtual machine on the cloud platform container is scanned in real time, virtual machine information is collected, and the corresponding virtual machine monitoring is obtained. data.
  • the execution script can be saved in the cloud platform container without rebuilding the container.
  • secondary development is required to encode the execution script into the cloud platform container, and the execution file needs to be updated.
  • Using the Docker-based storage volume mounting mechanism of the embodiment of the present application to mount the monitoring data acquisition script can facilitate updating and upgrading the monitoring data acquisition script without affecting the business logic of the container itself. Its pluggability is relatively high.
  • Mount the monitoring data acquisition script to the container by mounting the storage volume.
  • the monitoring data acquisition script can be directly mounted, and the collection terminal and the cloud platform container can be connected through the Docker management process. Communication, there is no need to transform and rebuild the cloud platform container, so that the effect of adding control virtual machine monitoring data without restarting the service, its pluggability is relatively high.
  • the virtual machine monitoring data collected by the monitoring data acquisition script is extracted through the Docker management process.
  • each cloud platform container receives the monitoring data acquisition command according to the cloud platform container name indicated by the monitoring data acquisition command of the Docker management process to collect the virtual machine monitoring data.
  • the Docker management process sends the virtual machine monitoring data to a collection terminal, and the collection terminal pushes the virtual machine monitoring data to a monitoring service container, the collection terminal is deployed on a host machine, and the cloud
  • the platform container and the monitoring service container are units that operate independently of each other.
  • the Docker management process is based on receiving the virtual machine monitoring data and sending it to the collection terminal, which can then push it to the monitoring service container to realize the transfer of virtual machine monitoring data between Docker containers.
  • the monitoring service of the monitoring service container is a service for collecting and analyzing virtual machine monitoring data of the cloud platform.
  • the collection terminal pushes the virtual machine monitoring data, it pushes the virtual machine monitoring data through the port exposed by the monitoring service container for monitoring services.
  • the monitoring service container After receiving the virtual machine monitoring data, the monitoring service container performs business processing and analysis on the virtual machine monitoring data through the monitoring service container, and saves it in the database of the monitoring service container for subsequent business calls.
  • the embodiment of the present application can isolate the network and resources between services, so that the cloud platform container and the monitoring service container can be separated Operate independently of each other.
  • the virtual machine monitoring data of the cloud platform container is collected through the collection terminal on the server and the Docker management process, and the collected virtual machine monitoring data is transferred between two independent Docker containers on the network to achieve Docker.
  • the data communication between containers greatly improves the independence of cloud platform services and monitoring services, and obtains a better cloud platform container operation management effect.
  • the update and upgrade of the execution file are more convenient.
  • the Docker management process to trigger the execution of command files inside the container, while monitoring the cloud platform virtual machine, it does not affect the business logic of its cloud platform service itself, ensuring that the cloud platform can be achieved in two containers that are not interconnected in principle.
  • a series of operations such as the collection, push, and storage of virtual machine monitoring data.
  • the monitoring data acquisition command is issued to the cloud platform container through the Docker management process, and the cloud platform container runs the monitoring data acquisition script based on the monitoring data acquisition command to acquire the corresponding virtual machine monitoring data.
  • the virtual machine monitoring data is returned to the Docker management process, and the virtual machine monitoring data is sent to the collection terminal through the Docker management process, and the collection terminal pushes the virtual machine monitoring data to the monitoring service container.
  • the virtual machine monitoring data in the cloud platform container can be obtained without destroying the independence between Docker containers, and the virtual machine monitoring data can be transferred between two Docker containers that run independently of each other. In this way, the data communication between Docker containers can be optimized, and a good cloud platform container operation management effect can be achieved.
  • FIG. 4 is a schematic structural diagram of an apparatus for obtaining virtual machine monitoring data in a Docker container provided in the second embodiment of the application.
  • the device for acquiring virtual machine monitoring data in a Docker container provided in this embodiment specifically includes: a triggering module 21, an acquiring module 22, and a pushing module 23.
  • the trigger module 21 is used to issue monitoring data acquisition commands to the cloud platform container through the Docker management process when data collection is triggered;
  • the obtaining module 22 is configured to run a monitoring data obtaining script based on the monitoring data obtaining command through the cloud platform container, obtain corresponding virtual machine monitoring data, and return the obtained virtual machine monitoring data to the Docker management process;
  • the push module 23 is configured to send the virtual machine monitoring data to the collection terminal through the Docker management process, and the collection terminal pushes the virtual machine monitoring data to the monitoring service container, and the collection terminal is deployed on the host machine ,
  • the cloud platform container and the monitoring service container are units that operate independently of each other.
  • the monitoring data acquisition command is issued to the cloud platform container through the Docker management process, and the cloud platform container runs the monitoring data acquisition script based on the monitoring data acquisition command to acquire the corresponding virtual machine monitoring data.
  • the virtual machine monitoring data is returned to the Docker management process, and the virtual machine monitoring data is sent to the collection terminal through the Docker management process, and the collection terminal pushes the virtual machine monitoring data to the monitoring service container.
  • the virtual machine monitoring data in the cloud platform container can be obtained without destroying the independence between Docker containers, and the virtual machine monitoring data can be transferred between two Docker containers that run independently of each other. In this way, the data communication between Docker containers can be optimized, and a good cloud platform container operation management effect can be achieved.
  • the apparatus for obtaining virtual machine monitoring data in a Docker container provided in the second embodiment of the present application can be used to execute the method for obtaining virtual machine monitoring data in a Docker container provided in the first embodiment above, and has corresponding functions and beneficial effects.
  • the third embodiment of the present application provides an electronic device.
  • the electronic device includes a processor 31, a memory 32, a communication module 33, an input device 34, and an output device 35.
  • the number of processors in the electronic device may be one or more, and the number of memories in the electronic device may be one or more.
  • the processor, memory, communication module, input device, and output device of the electronic device can be connected via a bus or other methods.
  • the memory 32 can be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the method for obtaining virtual machine monitoring data in a Docker container as described in any embodiment of this application (for example, the trigger module, the acquisition module, and the push module in the device for acquiring virtual machine monitoring data in the Docker container).
  • the memory may mainly include a program storage area and a data storage area, where the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, etc.
  • the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory may further include a memory remotely provided with respect to the processor, and these remote memories may be connected to the device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the communication module 33 is used for data transmission.
  • the processor 31 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in the memory, that is, realizes the above-mentioned method of obtaining virtual machine monitoring data in the Docker container.
  • the input device 34 can be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the device.
  • the output device 35 may include a display device such as a display screen.
  • the electronic device provided above can be used to execute the method for obtaining virtual machine monitoring data in a Docker container provided in the first embodiment above, and has corresponding functions and beneficial effects.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions, when the computer-executable instructions are executed by a computer processor, a method for acquiring virtual machine monitoring data in a Docker container is executed, which acquires the Docker container
  • the method for internal virtual machine monitoring data includes: when data collection is triggered, a monitoring data acquisition command is issued to a cloud platform container through the Docker management process; the cloud platform container runs a monitoring data acquisition script based on the monitoring data acquisition command to acquire Corresponding virtual machine monitoring data, the acquired virtual machine monitoring data is returned to the Docker management process; the Docker management process sends the virtual machine monitoring data to the collection terminal, and the collection terminal sends the The virtual machine monitoring data is pushed to the monitoring service container, the collection terminal is deployed on the host machine, and the cloud platform container and the monitoring service container are units that operate independently of each other.
  • Storage medium any of various types of storage devices or storage devices.
  • the term "storage medium” is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc. ; Non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements.
  • the storage medium may further include other types of memory or a combination thereof.
  • the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system connected to the first computer system through a network (such as the Internet).
  • the second computer system can provide the program instructions to the first computer for execution.
  • the term “storage medium” may include two or more storage media residing in different locations (for example, in different computer systems connected through a network).
  • the storage medium may store program instructions (for example, embodied as a computer program) executable by one or
  • the storage medium containing computer-executable instructions provided by the embodiments of the present application is not limited to the method for obtaining virtual machine monitoring data in a Docker container as described above, and any embodiments of the present application can also be implemented. Related operations in the provided method for obtaining virtual machine monitoring data in a Docker container.
  • the apparatus, storage medium, and electronic device for acquiring virtual machine monitoring data in a Docker container provided in the above embodiments can execute the method for acquiring virtual machine monitoring data in a Docker container provided in any embodiment of this application, which is not described in detail in the above embodiments.
  • the method for obtaining virtual machine monitoring data in a Docker container provided by any embodiment of the present application please refer to the method for obtaining virtual machine monitoring data in a Docker container provided by any embodiment of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

本申请实施例公开了一种获取Docker容器内虚拟机监控数据的方法、装置、电子设备及存储介质。本申请实施例提供的技术方案，在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器，云平台容器基于监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的虚拟机监控数据返回至Docker管理进程，通过Docker管理进程将虚拟机监控数据发送至采集端，由采集端将虚拟机监控数据推送至监控服务容器。采用上述技术手段，可以在不破坏Docker容器间独立性的前提下，获取云平台容器内的虚拟机监控数据，并将虚拟机监控数据在相互独立运行的两个Docker容器间进行传递。以此来优化Docker容器间的数据通讯，实现良好的云平台容器运行管理效果。

Description

一种获取Docker容器内虚拟机监控数据的方法及装置 技术领域
本申请实施例涉及容器管理技术领域，尤其涉及一种获取Docker容器内虚拟机监控数据的方法、装置、电子设备及存储介质。
背景技术
容器技术是利用Linux操作系统的特性进行资源隔离，使得资源更充分和有效利用。随着云计算平台的高速发展和应用服务容器潮流的兴起，云计算平台更新迭代得越来越复杂，其使用到的各种服务越来越多，导致其在部署安装，测试，交付，运维等方面面临的问题也越来越多。而随着Docker容器技术的发展，Docker容器技术的应用也越来越广泛，使得云计算平台容器化成为了当前解决项目部署复杂、更新迭代困难问题的一种主流解决方案。
目前，在传统的Docker容器化云计算平台服务方式中，Docker容器通过自身的隔离机制使得部署在同一台服务器上的不同应用从资源、存储以及网络上进行了隔离。但是，在各个网络隔离容器之间，容器内的服务在做到互不干扰的同时也无法自由的数据通讯，导致对容器内虚拟机的监控数据的获取非常困难。
发明内容
本申请实施例提供一种获取Docker容器内虚拟机监控数据的方法、装置、电子设备及存储介质，能够在不破坏容器间独立性的前提下，获取Docker容器内虚拟机监控数据。
在第一方面，本申请实施例提供了一种获取Docker容器内虚拟机监控数据的方法，包括：
在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器；
所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的所述虚拟机监控数据返回至所述Docker管理进程；
所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端 将所述虚拟机监控数据推送至监控服务容器，所述采集端部署于宿主机上，所述云平台容器与监控服务容器为相互独立运行的单位。
进一步的，在所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本之前，包括：
通过所述采集端预先将所述监控数据获取脚本挂载至所述云平台容器中。
进一步的，通过所述采集端预先将所述监控数据获取脚本挂载至所述云平台容器中，包括：
所述采集端基于Docker的存储卷挂载机制将所述监控数据获取脚本挂载至所述云平台容器中。
进一步的，所述在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器，还包括：
预先部署定时器，定时器基于所述采集端设置的频率定时触发进行数据采集。
进一步的，所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，包括：
所述云平台容器接收所述监控数据获取命令；
基于所述监控数据获取命令运行监控数据获取脚本，所述监控数据获取脚本包括用于获取虚拟机各项监控数据的可执行命令文件；
基于所述可执行命令文件扫描所述云平台容器内的各个虚拟机信息，获取对应的结果数据，以所述结果数据作为虚拟机监控数据。
进一步的，所述云平台容器为多个，多个所述云平台容器相互独立运行。
进一步的，在所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端将所述虚拟机监控数据推送至监控服务容器之后，还包括：
通过所述监控服务容器对所述虚拟机监控数据进行业务处理和解析，并保存至所述监控服务容器的数据库中。
在第二方面，本申请实施例提供了一种获取Docker容器内虚拟机监控数据的装置，包括：
触发模块，用于在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器；
获取模块，用于通过所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的所述虚拟机监控数据 返回至所述Docker管理进程；
推送模块，用于通过所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端将所述虚拟机监控数据推送至监控服务容器，所述采集端部署于宿主机上，所述云平台容器与监控服务容器为相互独立运行的单位。
在第三方面，本申请实施例提供了一种电子设备，包括：
存储器以及一个或多个处理器；
所述存储器，用于存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如第一方面所述的获取Docker容器内虚拟机监控数据的方法。
在第四方面，本申请实施例提供了一种包含计算机可执行指令的存储介质，所述计算机可执行指令在由计算机处理器执行时用于执行如第一方面所述的获取Docker容器内虚拟机监控数据的方法。
本申请实施例在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器，云平台容器基于监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的虚拟机监控数据返回至Docker管理进程，通过Docker管理进程将虚拟机监控数据发送至采集端，由采集端将虚拟机监控数据推送至监控服务容器。采用上述技术手段，可以在不破坏Docker容器间独立性的前提下，获取云平台容器内的虚拟机监控数据，并将虚拟机监控数据在相互独立运行的两个Docker容器间进行传递。以此来优化Docker容器间的数据通讯，实现良好的云平台容器运行管理效果。
附图说明
图1是本申请实施例一提供的一种获取Docker容器内虚拟机监控数据的方法的流程图；
图2是本申请实施例一中的Docker容器部署示意图；
图3是本申请实施例一中的虚拟机监控数据获取流程图；
图4是本申请实施例二提供的一种获取Docker容器内虚拟机监控数据的装置的结构示意图；
图5是本申请实施例三提供的一种电子设备的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面结合附图对本申请 具体实施例作进一步的详细描述。可以理解的是，此处所描述的具体实施例仅仅用于解释本申请，而非对本申请的限定。另外还需要说明的是，为了便于描述，附图中仅示出了与本申请相关的部分而非全部内容。在更加详细地讨论示例性实施例之前应当提到的是，一些示例性实施例被描述成作为流程图描绘的处理或方法。虽然流程图将各项操作(或步骤)描述成顺序的处理，但是其中的许多操作可以被并行地、并发地或者同时实施。此外，各项操作的顺序可以被重新安排。当其操作完成时所述处理可以被终止，但是还可以具有未包括在附图中的附加步骤。所述处理可以对应于方法、函数、规程、子例程、子程序等等。
本申请提供的一种获取Docker容器内虚拟机监控数据的方法，旨在通过部署采集端，采集端通过Docker管理进程下发命令，使云平台容器运行监控数据获取脚本，以获取云平台容器上各个虚拟机的虚拟机监控数据，并进一步将虚拟机监控数据上送至采集端，由采集端推送至监控服务容器。以实现虚拟机监控数据的采集及Docker容器间的虚拟机监控数据传递。相对于传统的Docker容器化云计算平台，其在运行过程中，Docker通过自身的隔离机制使得部署在同一台服务器上的不同应用从资源、存储以及网络上进行了隔离。而在网络隔离的Docker容器之间，容器间的服务在做到互不干扰的同时也无法自由地进行数据通讯。这也导致云平台容器内虚拟机监控数据的获取难度较大，进而影响云平台容器的运行管理效果。基于此，提供本申请实施例的一种获取Docker容器内虚拟机监控数据的方法，以解决现有的Docker容器间难以进行虚拟机监控数据传递的技术问题。
实施例一：
图1给出了本申请实施例一提供的一种获取Docker容器内虚拟机监控数据的方法的流程图，本实施例中提供的获取Docker容器内虚拟机监控数据的方法可以由Docker容器化云计算平台执行，该Docker容器化云计算平台可以通过软件和/或硬件的方式实现，该Docker容器化云计算平台可以是两个或多个物理实体构成。
下述以Docker容器化云计算平台为执行获取Docker容器内虚拟机监控数据的方法的主体为例，进行描述。参照图1，该获取Docker容器内虚拟机监控数据的方法具体包括：
S110、在触发进行数据采集时，通过Docker管理进程下发监控数据获取命 令至云平台容器。
具体的，Docker是一个开源的应用容器引擎。Docker容器指的是Docker将服务器上的资源、存储、网络划分好并提供给应用独立运行的单位。参照图2，本申请实施例中，基于Docker部署有云平台容器和监控服务容器，将云平台服务、监控服务部署到网络独立的2个Docker容器内，并在做到服务之间网络、资源隔离的前提下，通过服务器上部署的采集端和Docker管理进程实现两个网络上独立的Docker容器之间的数据(本申请实施例为虚拟机监控数据)传递。
进一步的，在进行Docker容器之间的数据传递时，以采集端作为云平台容器和监控服务容器之间的数据传递中介，在进行虚拟机监控数据传递时，通过采集端从云平台容器上采集虚拟机监控数据，进一步将采集到的虚拟机监控数据推送至监控服务容器。需要说明的是，本申请实施例的采集端部署在宿主机(即服务器)上，它是在服务器上运行的一个采集虚拟机监控数据的jar程序，不依赖于Docker容器。采集端通过预先部署定时器，定时器基于所述采集端设置的频率定时触发进行数据采集。定时器能够在相同的频率不间断的重复触发相同的操作，通过采集端预先设置好数据采集频率，并对应定时触发监控数据采集操作，进行数据采集。采集端在触发进行监控数据采集时，利用Docker管理进程下发监控数据获取命令至云平台容器，由云平台容器响应于这一监控数据获取命令进行虚拟机监控数据采集。其中，Docker管理进程指的是Docker服务自启的用于容器管理的进程，当Docker服务启动时，Docker管理进程也会同步启动。Docker管理进程拥有容器使用的最高权限，可让各个Docker容器执行指定的命令与操作。本实施中，通过Docker管理进程下发监控数据获取命令至云平台容器，让云平台容器执行指定的命令从而获取容器内部的虚拟机监控数据。监控数据获取命令格式为“docker exec[云平台容器名称][命令]”，其中，“[云平台容器名称]”指的是已部署云平台服务的Docker容器名称，“[命令]”指的是指示云平台容器进行虚拟机监控数据获取的命令。
S120、所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的所述虚拟机监控数据返回至所述Docker管理进程。
具体的，云平台容器基于Docker管理进程下发的监控数据获取命令，触发运行监控数据获取脚本，获取云平台容器内虚拟机的监控数据。在此之前，为 了能够从云平台容器内获取虚拟机监控数据，通过所述采集端预先将所述监控数据获取脚本挂载至所述云平台容器中。并且，在挂载监控数据获取脚本时，所述采集端基于Docker的存储卷挂载机制将所述监控数据获取脚本挂载至所述云平台容器中。后续在进行虚拟机监控数据获取时，通过运行该监控数据获取脚本进行虚拟机监控数据获取。
参照图3，虚拟机监控数据获取流程包括：
S1201、所述云平台容器接收所述监控数据获取命令；
S1202、基于所述监控数据获取命令运行监控数据获取脚本，所述监控数据获取脚本包括用于获取虚拟机各项监控数据的可执行命令文件；
S1203、基于所述可执行命令文件扫描所述云平台容器内的各个虚拟机信息，获取对应的结果数据，以所述结果数据作为虚拟机监控数据。
由于预先通过Docker的存储卷挂载机制将采集端的监控数据获取脚本挂载到云平台容器中，后续在接收监控数据获取命令后，运行该监控数据获取脚本进行虚拟机监控数据的获取。监控数据获取脚本包括用于获取虚拟机各项监控数据的可执行命令文件，通过执行这些可执行命令文件，实时扫描云平台容器上的各个虚拟机，采集虚拟机信息，获取相应的虚拟机监控数据。
本申请实施例通过Docker的存储卷挂载机制，无需重建容器即可将执行脚本保存到云平台容器当中。相对于传统的监控数据获取脚本部署方式，需要二次开发将执行脚本编码到云平台容器内部，并且需要更新执行文件。而使用本申请实施例基于Docker的存储卷挂载机制挂载监控数据获取脚本的方式，可便于更新、升级监控数据获取脚本，同时也不影响容器自身的业务逻辑。其拔插性相对较高。通过存储卷挂载的方式将监控数据获取脚本挂载到容器内，在已有的云平台容器的基础上可直接挂载监控数据获取脚本，并通过Docker管理进程进行采集端与云平台容器的通信，也无需改造和重建云平台容器，做到不重启服务而添加控制虚拟机监控数据的效果，其拔插性相对较高。
进一步的，基于监控数据获取脚本采集到的虚拟机监控数据，通过Docker管理进程进行提取。本申请实施例中，所述云平台容器为多个，多个所述云平台容器相互独立运行。则在虚拟机监控数据采集时，各个云平台容器根据Docker管理进程的监控数据获取命令指示的云平台容器名称，对应接收监控数据获取命令进行虚拟机监控数据采集。并且，在将虚拟机监控数据返回至Docker管理进程时，可在虚拟机监控数据上附上自身的云平台容器名称，以便于Docker管 理进程明确虚拟机监控数据的来源。
S130、所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端将所述虚拟机监控数据推送至监控服务容器，所述采集端部署于宿主机上，所述云平台容器与监控服务容器为相互独立运行的单位。
Docker管理进程基于接收到虚拟机监控数据，将其上送至采集端，采集端即可将其推送至监控服务容器，以实现虚拟机监控数据在Docker容器间的传递。监控服务容器的监控服务是针对云平台的虚拟机监控数据进行采集与分析的服务。采集端在推送虚拟机监控数据时，通过监控服务容器进行监控服务时所暴露出的端口推送这一虚拟机监控数据。监控服务容器接收到虚拟机监控数据后，通过所述监控服务容器对所述虚拟机监控数据进行业务处理和解析，并保存至所述监控服务容器的数据库中，以用于后续的业务调用。
需要说明的是，本申请实施例通过将云平台服务、监控服务部署到网络独立的两个Docker容器内，可以做到服务之间网络、资源的隔离，使云平台容器与监控服务容器之间相互独立运行。并且，通过服务器上的采集端和Docker管理进程进行云平台容器的虚拟机监控数据采集，并将采集到的虚拟机监控数据在两个网络独立的Docker容器之间进行传递，以此来实现Docker容器之间的数据通讯，极大地提高云平台服务与监控服务的独立性，得到较好的云平台容器运行管理效果。对于传统的云平台，其若要支持监控数据的采集，需要建立在云平台容器与监控服务容器之间可以网络互通、存储资源互通的前提下，才能做到监控云平台虚拟机的效果。而这又违背了Docker容器之间的独立性的原则。显然，正确的云平台架构方式应该是云平台服务与监控服务互不干扰的。基于此，使用本申请实施获取Docker容器内虚拟机监控数据的方法，可以解决现有的Docker容器间难以进行虚拟机监控数据传递的技术问题，同时可以对老旧的、本不支持监控数据推送的云平台容器进行功能上的拓展，并且无需进行二次开发与重建容器。进一步的，通过使用监控数据获取脚本挂载的方式，使得执行文件的更新、升级更加便利。通过Docker管理进程触发容器内部执行命令文件，在实现监控云平台虚拟机的同时，也不影响其云平台服务自身的业务逻辑，确保能在原则上网络不互通的两个容器内做到云平台虚拟机监控数据的采集、推送、保存等一系列操作。
上述，在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器，云平台容器基于监控数据获取命令运行监控数据获取脚本， 获取对应的虚拟机监控数据，将获取到的虚拟机监控数据返回至Docker管理进程，通过Docker管理进程将虚拟机监控数据发送至采集端，由采集端将虚拟机监控数据推送至监控服务容器。采用上述技术手段，可以在不破坏Docker容器间独立性的前提下，获取云平台容器内的虚拟机监控数据，并将虚拟机监控数据在相互独立运行的两个Docker容器间进行传递。以此来优化Docker容器间的数据通讯，实现良好的云平台容器运行管理效果。
实施例二：
在上述实施例的基础上，图4为本申请实施例二提供的一种获取Docker容器内虚拟机监控数据的装置的结构示意图。参考图4，本实施例提供的获取Docker容器内虚拟机监控数据的装置具体包括：触发模块21、获取模块22和推送模块23。
其中，触发模块21用于在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器；
获取模块22用于通过所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的所述虚拟机监控数据返回至所述Docker管理进程；
推送模块23用于通过所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端将所述虚拟机监控数据推送至监控服务容器，所述采集端部署于宿主机上，所述云平台容器与监控服务容器为相互独立运行的单位。
上述，在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器，云平台容器基于监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的虚拟机监控数据返回至Docker管理进程，通过Docker管理进程将虚拟机监控数据发送至采集端，由采集端将虚拟机监控数据推送至监控服务容器。采用上述技术手段，可以在不破坏Docker容器间独立性的前提下，获取云平台容器内的虚拟机监控数据，并将虚拟机监控数据在相互独立运行的两个Docker容器间进行传递。以此来优化Docker容器间的数据通讯，实现良好的云平台容器运行管理效果。
本申请实施例二提供的获取Docker容器内虚拟机监控数据的装置可以用于执行上述实施例一提供的获取Docker容器内虚拟机监控数据的方法，具备相应的功能和有益效果。
实施例三：
本申请实施例三提供了一种电子设备，参照图5，该电子设备包括：处理器31、存储器32、通信模块33、输入装置34及输出装置35。该电子设备中处理器的数量可以是一个或者多个，该电子设备中的存储器的数量可以是一个或者多个。该电子设备的处理器、存储器、通信模块、输入装置及输出装置可以通过总线或者其他方式连接。
存储器32作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序以及模块，如本申请任意实施例所述的获取Docker容器内虚拟机监控数据的方法对应的程序指令/模块(例如，获取Docker容器内虚拟机监控数据的装置中的触发模块、获取模块和推送模块)。存储器可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器可进一步包括相对于处理器远程设置的存储器，这些远程存储器可以通过网络连接至设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
通信模块33用于进行数据传输。
处理器31通过运行存储在存储器中的软件程序、指令以及模块，从而执行设备的各种功能应用以及数据处理，即实现上述的获取Docker容器内虚拟机监控数据的方法。
输入装置34可用于接收输入的数字或字符信息，以及产生与设备的用户设置以及功能控制有关的键信号输入。输出装置35可包括显示屏等显示设备。
上述提供的电子设备可用于执行上述实施例一提供的获取Docker容器内虚拟机监控数据的方法，具备相应的功能和有益效果。
实施例四：
本申请实施例还提供一种包含计算机可执行指令的存储介质，所述计算机可执行指令在由计算机处理器执行时用于执行一种获取Docker容器内虚拟机监控数据的方法，该获取Docker容器内虚拟机监控数据的方法包括：在触发进行 数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器；所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的所述虚拟机监控数据返回至所述Docker管理进程；所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端将所述虚拟机监控数据推送至监控服务容器，所述采集端部署于宿主机上，所述云平台容器与监控服务容器为相互独立运行的单位。
存储介质——任何的各种类型的存储器设备或存储设备。术语“存储介质”旨在包括：安装介质，例如CD-ROM、软盘或磁带装置；计算机系统存储器或随机存取存储器，诸如DRAM、DDR RAM、SRAM、EDO RAM，兰巴斯(Rambus)RAM等；非易失性存储器，诸如闪存、磁介质(例如硬盘或光存储)；寄存器或其它相似类型的存储器元件等。存储介质可以还包括其它类型的存储器或其组合。另外，存储介质可以位于程序在其中被执行的第一计算机系统中，或者可以位于不同的第二计算机系统中，第二计算机系统通过网络(诸如因特网)连接到第一计算机系统。第二计算机系统可以提供程序指令给第一计算机用于执行。术语“存储介质”可以包括驻留在不同位置中(例如在通过网络连接的不同计算机系统中)的两个或更多存储介质。存储介质可以存储可由一个或多个处理器执行的程序指令(例如具体实现为计算机程序)。
当然，本申请实施例所提供的一种包含计算机可执行指令的存储介质，其计算机可执行指令不限于如上所述的获取Docker容器内虚拟机监控数据的方法，还可以执行本申请任意实施例所提供的获取Docker容器内虚拟机监控数据的方法中的相关操作。
上述实施例中提供的获取Docker容器内虚拟机监控数据的装置、存储介质及电子设备可执行本申请任意实施例所提供的获取Docker容器内虚拟机监控数据的方法，未在上述实施例中详尽描述的技术细节，可参见本申请任意实施例所提供的获取Docker容器内虚拟机监控数据的方法。
上述仅为本申请的较佳实施例及所运用的技术原理。本申请不限于这里所述的特定实施例，对本领域技术人员来说能够进行的各种明显变化、重新调整及替代均不会脱离本申请的保护范围。因此，虽然通过以上实施例对本申请进行了较为详细的说明，但是本申请不仅仅限于以上实施例，在不脱离本申请构思的情况下，还可以包括更多其他等效实施例，而本申请的范围由权利要求的范围决定。

Claims (10)

  1. 一种获取Docker容器内虚拟机监控数据的方法，其特征在于，包括：
    在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器；
    所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的所述虚拟机监控数据返回至所述Docker管理进程；
    所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端将所述虚拟机监控数据推送至监控服务容器，所述采集端部署于宿主机上，所述云平台容器与监控服务容器为相互独立运行的单位。
  2. 根据权利要求1所述的获取Docker容器内虚拟机监控数据的方法，其特征在于，在所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本之前，包括：
    通过所述采集端预先将所述监控数据获取脚本挂载至所述云平台容器中。
  3. 根据权利要求2所述的获取Docker容器内虚拟机监控数据的方法，其特征在于，通过所述采集端预先将所述监控数据获取脚本挂载至所述云平台容器中，包括：
    所述采集端基于Docker的存储卷挂载机制将所述监控数据获取脚本挂载至所述云平台容器中。
  4. 根据权利要求1所述的获取Docker容器内虚拟机监控数据的方法，其特征在于，所述在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器，还包括：
    预先部署定时器，定时器基于所述采集端设置的频率定时触发进行数据采集。
  5. 根据权利要求1所述的获取Docker容器内虚拟机监控数据的方法，其特征在于，所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，包括：
    所述云平台容器接收所述监控数据获取命令；
    基于所述监控数据获取命令运行监控数据获取脚本，所述监控数据获取脚本包括用于获取虚拟机各项监控数据的可执行命令文件；
    基于所述可执行命令文件扫描所述云平台容器内的各个虚拟机信息，获取对应的结果数据，以所述结果数据作为虚拟机监控数据。
  6. 根据权利要求1所述的获取Docker容器内虚拟机监控数据的方法，其特征在于，所述云平台容器为多个，多个所述云平台容器相互独立运行。
  7. 根据权利要求1所述的获取Docker容器内虚拟机监控数据的方法，其特征在于，在所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端将所述虚拟机监控数据推送至监控服务容器之后，还包括：
    通过所述监控服务容器对所述虚拟机监控数据进行业务处理和解析，并保存至所述监控服务容器的数据库中。
  8. 一种获取Docker容器内虚拟机监控数据的装置，其特征在于，包括：
    触发模块，用于在触发进行数据采集时，通过Docker管理进程下发监控数据获取命令至云平台容器；
    获取模块，用于通过所述云平台容器基于所述监控数据获取命令运行监控数据获取脚本，获取对应的虚拟机监控数据，将获取到的所述虚拟机监控数据返回至所述Docker管理进程；
    推送模块，用于通过所述Docker管理进程将所述虚拟机监控数据发送至采集端，由所述采集端将所述虚拟机监控数据推送至监控服务容器，所述采集端部署于宿主机上，所述云平台容器与监控服务容器为相互独立运行的单位。
  9. 一种电子设备，其特征在于，包括：
    存储器以及一个或多个处理器；
    所述存储器，用于存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-7任一所述的获取Docker容器内虚拟机监控数据的方法。
  10. 一种包含计算机可执行指令的存储介质，其特征在于，所述计算机可执行指令在由计算机处理器执行时用于执行如权利要求1-7任一所述的获取Docker容器内虚拟机监控数据的方法。
PCT/CN2021/073760 2020-05-22 2021-01-26 一种获取Docker容器内虚拟机监控数据的方法及装置 WO2021232842A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010442961.3A CN111651237A (zh) 2020-05-22 2020-05-22 一种获取Docker容器内虚拟机监控数据的方法及装置
CN202010442961.3 2020-05-22

Publications (1)

Publication Number Publication Date
WO2021232842A1 true WO2021232842A1 (zh) 2021-11-25

Family

ID=72346855

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/073760 WO2021232842A1 (zh) 2020-05-22 2021-01-26 一种获取Docker容器内虚拟机监控数据的方法及装置

Country Status (2)

Country Link
CN (1) CN111651237A (zh)
WO (1) WO2021232842A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114978963A (zh) * 2022-04-26 2022-08-30 西安交通大学 一种网络系统监控分析方法、装置、电子设备及存储介质
CN115733731A (zh) * 2022-11-18 2023-03-03 济南浪潮数据技术有限公司 一种云主机中gpu监控方法、装置、宿主机和存储介质
CN116644423A (zh) * 2023-07-25 2023-08-25 山东捷讯通信技术有限公司 一种容器攻击的监控的方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111651237A (zh) * 2020-05-22 2020-09-11 国云科技股份有限公司 一种获取Docker容器内虚拟机监控数据的方法及装置
CN114077577A (zh) * 2021-11-18 2022-02-22 支付宝(杭州)信息技术有限公司 基于跨容器的文件数据采集方法及文件数据采集装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106776212A (zh) * 2016-12-09 2017-05-31 中电科华云信息技术有限公司 容器集群部署多进程应用的监管系统及方法
CN107070860A (zh) * 2016-12-27 2017-08-18 北京粉笔蓝天科技有限公司 一种监控数据的收集方法、装置和系统
CN107689953A (zh) * 2017-08-18 2018-02-13 中国科学院信息工程研究所 一种面向多租户云计算的容器安全监控方法及系统
CN111651237A (zh) * 2020-05-22 2020-09-11 国云科技股份有限公司 一种获取Docker容器内虚拟机监控数据的方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107294772B (zh) * 2017-05-23 2020-09-01 中电万维信息技术有限责任公司 一种结合Docker实现动态管理监控服务系统
CN107832116A (zh) * 2017-11-13 2018-03-23 郑州云海信息技术有限公司 一种基于Grafana实现虚拟机实例监控的方法
CN108009004B (zh) * 2017-12-01 2022-01-21 广东电网有限责任公司佛山供电局 基于Docker的业务应用可用度测量监控的实现方法
CN108156225B (zh) * 2017-12-15 2021-02-05 南瑞集团有限公司 基于容器云平台的微应用监控系统和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106776212A (zh) * 2016-12-09 2017-05-31 中电科华云信息技术有限公司 容器集群部署多进程应用的监管系统及方法
CN107070860A (zh) * 2016-12-27 2017-08-18 北京粉笔蓝天科技有限公司 一种监控数据的收集方法、装置和系统
CN107689953A (zh) * 2017-08-18 2018-02-13 中国科学院信息工程研究所 一种面向多租户云计算的容器安全监控方法及系统
CN111651237A (zh) * 2020-05-22 2020-09-11 国云科技股份有限公司 一种获取Docker容器内虚拟机监控数据的方法及装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114978963A (zh) * 2022-04-26 2022-08-30 西安交通大学 一种网络系统监控分析方法、装置、电子设备及存储介质
CN115733731A (zh) * 2022-11-18 2023-03-03 济南浪潮数据技术有限公司 一种云主机中gpu监控方法、装置、宿主机和存储介质
CN116644423A (zh) * 2023-07-25 2023-08-25 山东捷讯通信技术有限公司 一种容器攻击的监控的方法及装置

Also Published As

Publication number Publication date
CN111651237A (zh) 2020-09-11

Similar Documents

Publication Publication Date Title
WO2021232842A1 (zh) 一种获取Docker容器内虚拟机监控数据的方法及装置
WO2021217871A1 (zh) 微服务集群部署方法、装置、计算机设备及存储介质
EP3944082A1 (en) Extending the kubernetes api in-process
US11301280B2 (en) System and method for managing a monitoring agent in an operating system of a virtual computing instance
US8924954B2 (en) Application software installation method and application software installation apparatus
US20230106118A1 (en) Distributed processing of transactions in a network using timestamps
CN107644030B (zh) 分布式数据库数据同步方法、相关装置及系统
WO2020103904A1 (zh) 云桌面升级方法、装置、云端服务器及存储介质
WO2021227564A1 (zh) 一种基于容器环境的应用自动交付系统
US9473356B2 (en) Automatic configuration of applications based on host metadata using application-specific templates
CN107220100A (zh) 一种开发运维方法、装置及云计算PaaS平台
CN105320718B (zh) 同步复制环境中的事务完成
US20080033902A1 (en) A Method for Providing Live File Transfer Between Machines
CN104050276A (zh) 一种分布式数据库的缓存处理方法及系统
US11042473B2 (en) Intelligent test case management for system integration testing
CN108259569B (zh) 一种基于ipsan共享存储的无代理连续数据保护方法及系统
CN111552540A (zh) 基于VMware云平台的资源同步方法及超融合云平台
CN106406933A (zh) 一种Tomcat集群一键自动部署方法
WO2016197688A1 (zh) 一种数据采集方法及装置
CN112416394B (zh) 一种服务升级方法、装置、存储介质及电子设备
US9588947B1 (en) Integrated administrative interface for open network programming applications
CN117729251A (zh) 边缘计算设备、嵌入式设备、控制系统及其构建方法
US10572503B2 (en) Database system, information processing device, method and medium
US20110307855A1 (en) Software project management apparatuses and methods thereof
US11949653B2 (en) Automated syncing of data between security domains

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21809602

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21809602

Country of ref document: EP

Kind code of ref document: A1