CN115809119A - Monitoring method, system and device for container arrangement engine - Google Patents
Monitoring method, system and device for container arrangement engine Download PDFInfo
- Publication number
- CN115809119A CN115809119A CN202211672491.5A CN202211672491A CN115809119A CN 115809119 A CN115809119 A CN 115809119A CN 202211672491 A CN202211672491 A CN 202211672491A CN 115809119 A CN115809119 A CN 115809119A
- Authority
- CN
- China
- Prior art keywords
- index
- monitoring
- monitoring component
- component
- cluster
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 373
- 238000000034 method Methods 0.000 title claims abstract description 47
- 239000012634 fragment Substances 0.000 claims abstract description 237
- 239000003795 chemical substances by application Substances 0.000 claims abstract description 143
- 238000013467 fragmentation Methods 0.000 claims abstract description 8
- 238000006062 fragmentation reaction Methods 0.000 claims abstract description 8
- 230000004083 survival effect Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 10
- 230000002776 aggregation Effects 0.000 description 17
- 238000004220 aggregation Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 16
- 230000008859 change Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000004364 calculation method Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 238000012806 monitoring device Methods 0.000 description 3
- 230000009193 crawling Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Exhaust Gas After Treatment (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a monitoring method, a system and a device of a container arrangement engine. One embodiment of the method comprises: determining the fragmentation number of the monitoring component according to the acquisition configuration file of the container arrangement engine cluster by the index acquisition agent component in the index acquisition agent component cluster and the monitoring component; the monitoring components are segmented to obtain monitoring component segments with the number of the segments; and for each monitoring component fragment in the monitoring component fragments with the fragment number, acquiring index data corresponding to the monitoring component fragment from the index acquisition agent component cluster, and monitoring the container arrangement engine cluster. The monitoring component can be automatically transversely expanded based on the index acquisition agent component in the application to adapt to the monitoring tasks of the container arrangement engine clusters of various scales, so that the practicability of the monitoring component and the application range of the monitoring tasks are improved.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a container monitoring technology, and especially relates to a monitoring method, a system and a device for a container arrangement engine.
Background
Many monitoring indexes corresponding to the native Kubernetes cluster need to be generated on the basis of aggregation, and when the Kubernetes cluster is gradually enlarged, the data scale of a single instance of a monitoring component prometheus is continuously increased, so that huge pressure on calculation and storage is caused. However, the monitoring component prometheus originally only supports standalone deployment.
Disclosure of Invention
The embodiment of the application provides a monitoring method, a monitoring system, a monitoring device, a computer readable medium and electronic equipment of a container arrangement engine.
In a first aspect, an embodiment of the present application provides a method for monitoring a container arrangement engine, including: determining the number of fragments of the monitoring component according to the acquisition configuration file of the container arrangement engine cluster by the monitoring component through an index acquisition agent component in the index acquisition agent component cluster; the monitoring components are segmented to obtain monitoring component segments with the number of the segments; and for each monitoring component fragment in the monitoring component fragments with the fragment number, acquiring index data corresponding to the monitoring component fragment from the index acquisition agent component cluster, and monitoring the container arrangement engine cluster.
In some examples, the fragmenting the monitoring component to obtain the monitoring component fragments with the number of fragments includes: dividing the acquisition configuration file to obtain a plurality of sub-acquisition configuration files; the monitoring component is segmented according to the plurality of sub-acquisition configuration files to obtain monitoring component segments with the number of the segments; and establishing a corresponding relation between the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments with the number of fragments.
In some examples, for each monitoring component fragment in the monitoring component fragments of the number of fragments, obtaining the index data corresponding to the monitoring component fragment from the index collection agent component cluster includes: for each monitoring component fragment in the monitoring component fragments with the fragment number, determining a target object to be monitored by the monitoring component fragment according to a sub-acquisition configuration file corresponding to the monitoring component fragment; and acquiring the index data corresponding to the monitoring component fragment from the index acquisition agent component which is responsible for pulling the index data from the target object to be monitored of the monitoring component fragment in the index acquisition agent component cluster.
In some examples, the determining the number of fragments of the monitoring component according to the collection configuration file of the monitoring component for the container arrangement engine cluster comprises: generating an index grabbing task for the container arrangement engine cluster according to the acquisition configuration file through a configuration manager; executing an index grabbing task through a task manager, and acquiring index data corresponding to a target object in a container arrangement engine cluster; and determining the fragment number of the monitoring component according to the index data acquired by the task manager through the metadata manager.
In some examples, the determining, by the metadata manager, the number of segments of the monitoring component according to the index data obtained by the task manager includes: and determining the fragment number of the monitoring component by the metadata manager according to the index data acquired by the task manager by adopting a load balancing strategy.
In some examples, the metric collection broker component further comprises a cluster manager, and the method further comprises: determining, by a cluster manager, a survival state of an index collection agent component in a cluster of index collection agent components; generating a node on-line and off-line event for the index collection agent component according to the survival state; and generating an index capture task for the container arrangement engine cluster according to the acquisition configuration file through the configuration manager, wherein the index capture task comprises the following steps: and generating an index capturing task for the container arrangement engine cluster according to the acquisition configuration file and the node online and offline event through a configuration manager.
In a second aspect, an embodiment of the present application provides a monitoring system for a container orchestration engine, including: the index acquisition agent component cluster is used for determining the fragment number of the monitoring components according to the acquisition configuration file of the container arrangement engine cluster by the monitoring components through the index acquisition agent components in the index acquisition agent component cluster; the monitoring components are segmented to obtain monitoring component segments with the number of the segments; and the monitoring component is used for acquiring index data corresponding to the monitoring component fragments from the index acquisition agent component cluster for each monitoring component fragment in the monitoring component fragments with the number of fragments, and monitoring the container arrangement engine cluster.
In some examples, the cluster of metric collection proxy components is further to: dividing the acquisition configuration file to obtain a plurality of sub-acquisition configuration files; the monitoring component is segmented according to the plurality of sub-acquisition configuration files to obtain monitoring component segments with the number of the segments; and establishing a corresponding relation between the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments with the number of fragments.
In some examples, the monitoring component further to: for each monitoring component fragment in the monitoring component fragments with the fragment number, determining a target object to be monitored by the monitoring component fragment according to a sub-acquisition configuration file corresponding to the monitoring component fragment; and acquiring the index data corresponding to the monitoring component fragment from the index acquisition agent component which is responsible for pulling the index data from the target object to be monitored of the monitoring component fragment in the index acquisition agent component cluster.
In some examples, the index collection agent component includes a configuration manager, a task manager, and a metadata manager, and a configuration manager to generate an index crawling task for the container orchestration engine cluster according to the collection configuration file; the task manager is used for executing the index grabbing task and acquiring index data corresponding to the target object in the container arrangement engine cluster; and the metadata manager is used for determining the fragment number of the monitoring component according to the index data acquired by the task manager.
In some examples, the metadata manager is further to: and determining the fragment number of the monitoring component by the metadata manager according to the index data acquired by the task manager by adopting a load balancing strategy.
In some examples, the metric collection agent component further comprises: the cluster manager is used for determining the survival state of the index collection agent components in the index collection agent component cluster; generating a node on-line and off-line event for the index collection agent component according to the survival state; and the configuration manager is further used for generating an index capturing task for the container arrangement engine cluster according to the acquisition configuration file and the node online and offline event.
In a third aspect, an embodiment of the present application provides a monitoring apparatus for a container arrangement engine, including: the determining unit is configured to determine the fragment number of the monitoring component according to the acquisition configuration file of the monitoring component to the container arrangement engine cluster through the index acquisition proxy component in the index acquisition proxy component cluster; the slicing unit is configured to slice the monitoring components to obtain monitoring component slices with the number of the slices; and the monitoring unit is configured to acquire index data corresponding to the monitoring component fragments from the index acquisition agent component cluster for each monitoring component fragment in the monitoring component fragments with the number of fragments, and monitor the container arrangement engine cluster.
In some examples, the above-mentioned fragmentation unit is further configured to: dividing the acquisition configuration file to obtain a plurality of sub-acquisition configuration files; the monitoring component is segmented according to the plurality of sub-acquisition configuration files to obtain monitoring component segments with the number of the segments; and establishing a corresponding relation between the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments with the number of fragments.
In some examples, the monitoring unit is further configured to: for each monitoring component fragment in the monitoring component fragments with the fragment number, determining a target object to be monitored by the monitoring component fragment according to a sub-acquisition configuration file corresponding to the monitoring component fragment; and acquiring the index data corresponding to the monitoring component fragment from the index acquisition agent component which is responsible for pulling the index data from the target object to be monitored of the monitoring component fragment in the index acquisition agent component cluster.
In some examples, the metric collection agent component includes a configuration manager, a task manager, and a metadata manager, and the determination unit is further configured to: generating an index grabbing task for the container arrangement engine cluster according to the acquisition configuration file through a configuration manager; executing an index grabbing task through a task manager, and acquiring index data corresponding to a target object in a container arrangement engine cluster; and determining the fragment number of the monitoring component according to the index data acquired by the task manager through the metadata manager.
In some examples, the determining unit is further configured to: and determining the fragment quantity of the monitoring assembly by adopting a load balancing strategy through the metadata manager according to the index data acquired by the task manager.
In some examples, the metric collection broker component further comprises a cluster manager, and the apparatus further comprises: a generation unit configured to determine, by a cluster manager, a survival status of an index collection agent component in a cluster of index collection agent components; generating a node on-line and off-line event for the index collection agent component according to the survival state; and the above-mentioned determining unit, further configured to: and generating an index capturing task for the container arrangement engine cluster according to the acquisition configuration file and the node online and offline event through a configuration manager.
In a fourth aspect, the present application provides a computer-readable medium, on which a computer program is stored, where the program, when executed by a processor, implements the method as described in any implementation manner of the first aspect.
In a fifth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a storage device having one or more programs stored thereon, which when executed by one or more processors, cause the one or more processors to implement a method as described in any implementation of the first aspect.
According to the monitoring method and the monitoring device for the container arrangement engine, the number of the fragments of the monitoring component is determined through the index acquisition agent component in the index acquisition agent component cluster according to the acquisition configuration file of the monitoring component to the container arrangement engine cluster; the monitoring component is divided into pieces, and the monitoring component pieces with the piece number are obtained; for each monitoring component fragment in the monitoring component fragments with the fragment number, index data corresponding to the monitoring component fragment is obtained from the index acquisition agent component cluster, and the container arrangement engine cluster is monitored, so that the monitoring component can be automatically transversely expanded based on the index acquisition agent component, the monitoring tasks of the container arrangement engine cluster with various scales are adapted, and the practicability of the monitoring component and the application range of the monitoring tasks are improved.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings:
FIG. 1 is an exemplary system architecture diagram in which one embodiment of the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of a monitoring method of a container orchestration engine according to the present application;
fig. 3 is a schematic diagram of an application scenario of a monitoring method of the container orchestration engine according to the present embodiment;
FIG. 4 is a flow diagram of yet another embodiment of a monitoring method of a container orchestration engine according to the present application;
FIG. 5 is a block diagram of one embodiment of a monitoring system of a container orchestration engine according to the present application;
FIG. 6 is a block diagram of one embodiment of an index collection agent component according to the present application;
FIG. 7 is a block diagram of one embodiment of a monitoring device of a container orchestration engine according to the present application;
FIG. 8 is a schematic block diagram of a computer system suitable for use in implementing embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
FIG. 1 illustrates an exemplary architecture 100 in which the container orchestration engine monitoring methods, systems, and apparatus of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The communication connections between the terminal devices 101, 102, 103 form a topological network and the network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may be hardware devices or software that support network connections for data interaction and data processing. When the terminal devices 101, 102, and 103 are hardware, they may be various electronic devices supporting network connection, information acquisition, interaction, display, processing, and the like, including but not limited to smart phones, tablet computers, electronic book readers, laptop portable computers, desktop computers, and the like. When the terminal apparatuses 101, 102, 103 are software, they can be installed in the electronic apparatuses listed above. It may be implemented, for example, as multiple software or software modules for providing distributed services, or as a single software or software module. And is not particularly limited herein.
The server 105 may be a server that provides various services, for example, a background processing server that deploys a container orchestration engine cluster to process various operation requests issued by the terminal devices 101, 102, 103 based on various applications deployed in the container orchestration engine. The server can automatically perform horizontal expansion on the monitoring component based on the index acquisition agent component so as to adapt to the monitoring tasks of the container arrangement engine clusters of various scales. As an example, the server 105 may be a cloud server.
The server may be hardware or software. When the server is hardware, it may be implemented as a distributed server cluster composed of multiple servers, or may be implemented as a single server. When the server is software, it may be implemented as multiple pieces of software or software modules (e.g., software or software modules for providing distributed services) or as a single piece of software or software module. And is not particularly limited herein.
It should be further noted that the monitoring method of the container orchestration engine provided in the embodiment of the present application may be executed by a server, or may be executed by a terminal device, or may be executed by the server and the terminal device in cooperation with each other. Accordingly, each part (for example, each unit) included in the monitoring apparatus of the container arrangement engine may be entirely disposed in the server, may be entirely disposed in the terminal device, and may be disposed in the server and the terminal device, respectively.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. When the electronic device on which the monitoring method of the container orchestration engine operates does not need to perform data transmission with other electronic devices, the system architecture may include only the electronic device (e.g., a server or a terminal device) on which the monitoring method of the container orchestration engine operates.
With continued reference to FIG. 2, a flow 200 of one embodiment of a monitoring method of a container orchestration engine is shown, comprising the steps of:
In this embodiment, an execution main body (for example, a terminal device or a server in fig. 1) of the monitoring method of the container arrangement engine may determine, through an index collection agent component in the index collection agent component cluster, the number of fragments of the monitoring component according to a collection configuration file of the monitoring component for the container arrangement engine cluster.
In the container arrangement engine cluster, a plurality of containers can be created, an application instance runs in each container, and then management, discovery and access to the group of application instances are realized through a built-in load balancing strategy. The container layout engine cluster comprises multiple acquisition components such as a kube-state-metrics, a kubel, a node-Exporter, a pod-metric and an Exporter, and is responsible for acquiring index data of bottom components of container layout engines such as various containers, pods and nodes and self-defined indexes of business components corresponding to various applications.
The collection configuration file comprises the target objects (objects) in the container arrangement engine cluster which are required to be monitored by the monitoring component. Specifically, the target object to be monitored is described in a scrape _ config fragment in the acquisition configuration file. The scrape _ config fragment specifies a set of target objects, which are instances, and parameters that specify the end points of index acquisition and describe how the index acquisition is performed on these target objects.
According to the collection configuration file, the index collection agent component can pull target data from various collection components in the container arrangement engine cluster. And then, determining the fragment number of the monitoring component according to the index data acquired by the index acquisition agent component cluster. Wherein the container orchestration engine may be, for example, kubernets and the monitoring component may be, for example, prometheus.
As an example, the execution subject may determine the number of pieces of the monitoring component based on the data size of the index data acquired by the index collection agent component cluster. In the process of determining the number of fragments of the monitoring component, all the fragments of the monitoring component can be adapted to the data scale of the index data acquired by the index acquisition agent component cluster.
As yet another example, the execution agent may split the monitoring component according to a function or service dimension of the container orchestration engine, determining a number of shards of the monitoring component. That is, if the monitoring component collects more services, one monitoring component fragment is configured to collect and store only the index of one or a certain part of the services, so as to split the monitoring component into a plurality of monitoring component fragments according to the services to be collected by the monitoring component.
In some optional implementations of this embodiment, the metric collection agent component includes a configuration manager, a task manager, and a metadata manager. In this implementation, the executing entity may execute the step 201 as follows:
firstly, generating an index grabbing task for a container arrangement engine cluster according to a collection configuration file through a configuration manager.
The configuration manager is responsible for arranging ServiceMonitor/Podmonitor in the engine cluster by list & watch containers, and generating a Prometheus format indicator capture task, namely outputting an event of indicator capture task change.
And secondly, executing an index grabbing task through a task manager, and acquiring index data corresponding to the target object in the container arrangement engine cluster.
The task manager is responsible for maintaining a grabbing task list and executing relevant Relay operations, including filtering out unnecessary grabbing tasks based on a drop rule. The input of the event is the event of index grabbing task change, and the output is metrics (index data) in the format of Exporter.
Thirdly, determining the fragment number of the monitoring component according to the index data acquired by the task manager through the metadata manager.
The metadata manager is responsible for caching the index data and maintaining metadata of container/pod/node in the container arrangement engine and monitoring the component fragment. And, the pod and node change is realized based on Operator sdk (Software Development Kit), including maintaining the cache between container and pod and between pod and node.
In the implementation mode, the configuration manager, the task manager and the metadata manager in the index collection agent component respectively perform their own functions and cooperate with each other to determine the number of fragments of the monitoring component, so that the information processing efficiency of the index collection agent component is improved.
In some optional implementations of this embodiment, the executing body may execute the third step by: and determining the fragment number of the monitoring component by the metadata manager according to the index data acquired by the task manager by adopting a load balancing strategy.
Based on the load balancing strategy, the data volume between each monitoring component fragment can be balanced while each monitoring component fragment meets the monitoring task, and the balance between the monitoring component fragments and the utilization rate of the monitoring component fragments are improved.
The calculation of some aggregation indexes in the container arrangement engine depends on a large number of original indexes, and the original indexes occupy a large amount of memory of the monitoring component and bring large calculation pressure to a CPU. The aggregation indicators are generally divided into two categories, kubernetes original aggregation indicators and component-defined service aggregation indicators. The kubernets original aggregation indicator is known in advance and is precalculated, while the service aggregation indicator is unpredictable in its specific indicator and magnitude. For an original aggregation index of kubernets, an aggregation index which generally needs to be concerned by users at a cluster level of the kubernets dimension can be specified, the aggregation index is calculated in an index collection agent component in advance, the magnitude of the aggregation index is determined, and the aggregation index is divided into fixed monitoring components to be acquired and calculated in a slicing mode. The Kubernetes native aggregated indicators can be excluded from the load balancing strategy, that is, only the collection configuration except the built-in Kubernetes aggregated task is subjected to load balancing, which is also beneficial to the classification statistics and data analysis of subsequent indicator data and the reduction of the influence range of the fault period. In the implementation mode, the index collection agent component has collection and calculation capacity, the aggregation index can be determined without depending on a service discovery mechanism and aggregation calculation of the monitoring component, and aggregation calculation is directly performed on the Kubernetes original index by using the index collection agent component, so that resources of any monitoring component are not occupied. As for the index aggregation by using the monitoring component or the index aggregation by using the index collection agent component, the method can be flexibly selected and applied according to the specific kubernets cluster scale and application scene.
In some optional implementations of this embodiment, the index collection agent component further includes a cluster manager. In this implementation, the execution main body may further perform the following operations: determining, by a cluster manager, a survival state of an index collection agent component in a cluster of index collection agent components; and generating a node on-line and off-line event for the index collection agent component according to the survival state.
As an example, the execution agent may determine the survival status of the index collection agent components in the index collection agent component cluster according to the pod change event. The pod change event refers to pod change of the index collection agent component, such as pod change time of adding, deleting, changing and the like. Adding an index collection agent component pod or hanging up an index collection agent component pod can affect the copying of the configuration file of the monitoring component fragment, and the node online and offline event is the response of the node after the node acquires the pod change. The cluster manager is essentially an operator, which monitors the change of the index collection agent component cluster at any time, and when finding that a certain pod (e.g., script-agent-0) of an index collection agent component is hung, the cluster manager generates a node online and offline event, e.g., "script-agent-0 is hung", and sends the node online and offline event to the configuration manager.
In this implementation, the executing body may execute the first step as follows: and generating an index capturing task for the container arrangement engine cluster according to the acquisition configuration file and the node online and offline event through a configuration manager.
In the implementation mode, the survival state of the index acquisition agent component in the index acquisition agent component cluster is determined through the cluster manager, and the index grabbing task is adjusted according to the specific condition of the index acquisition agent component cluster, so that the monitoring flexibility and the response timeliness are improved.
In this embodiment, the execution main body may segment the monitoring component to obtain the monitoring component segments of the number of segments.
Specifically, the executing body may use a hashmod configured in a Relabel rule in the monitoring component promemeus to fragment the nodes in the container orchestration engine cluster. Each Prometheus instance only captures data in the slice of one of the container orchestration engine clusters, thereby dispersing the metric data among the different Prometheus instances. Each Prometheus instance can be considered a monitoring component shard.
As an example, the executing agent may first calculate a hash value according to one or more tags of each target object; then, taking the determined number of the fragments as a modulus, performing modulus on the obtained hash value, wherein different moduli correspond to different fragments.
In some optional implementations of this embodiment, the executing main body may execute the step 202 by: firstly, dividing an acquisition configuration file to obtain a plurality of sub-acquisition configuration files; then, the monitoring components are segmented according to the plurality of sub-acquisition configuration files to obtain the monitoring component segments with the number of segments; and finally, establishing a corresponding relation between the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments with the number of the fragments.
And in the monitoring component, configuring the acquisition configuration file through the ServiceMonitor and the Podmonitor. And dividing the acquisition configuration file, namely dividing the ServiceMonitor into a plurality of sub-configuration files, wherein the keep rule in each sub-configuration file is different and is used for reserving the target object corresponding to the sub-configuration file.
For the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments of the number of fragments, the execution main body may adopt a load balancing strategy to establish a corresponding relationship between the sub-configuration files and the monitoring component fragments, so as to balance index data of a target object responsible for the monitoring component fragments.
In this implementation manner, a specific manner for fragmenting the monitoring components is provided, and a target object to be monitored by each monitoring component fragment can be made clear, so that each monitoring component fragment can accurately obtain index data of the target object to be monitored.
In this embodiment, the executing body may, for each monitoring component fragment of the monitoring component fragments of the number of fragments, obtain index data corresponding to the monitoring component fragment from the index collection agent component cluster, and monitor the container arrangement engine cluster.
Specifically, the executing entity may determine in advance a correspondence between the monitoring component fragments (monitoring component instances) and the fragments of the index data of the container arrangement engine cluster, and further acquire, for each monitoring component fragment of the monitoring component fragments of the number of fragments, a fragment of the index data corresponding to the monitoring component fragment from the index collection agent component cluster to monitor the container arrangement engine cluster.
By way of example, targets with specific output modulus values can be retained or discarded through a keep rule or a drop rule configured in a Relabel rule, so as to screen out index data corresponding to each monitoring component fragment.
In some optional implementations of this embodiment, the executing main body may execute the step 203 by: firstly, for each monitoring component fragment in the monitoring component fragments with the number of fragments, determining a target object to be monitored by the monitoring component fragment according to a sub-acquisition configuration file corresponding to the monitoring component fragment; and then, acquiring the index data corresponding to the monitoring component fragment from the index acquisition agent component which is responsible for pulling the index data from the target object to be monitored of the monitoring component fragment in the index acquisition agent component cluster.
As an example, after determining the target object to be monitored by each monitoring component fragment, the target object to be monitored by each monitoring component fragment may be screened from the index collection agent component cluster based on a drop rule or a keep rule in a Relabel rule.
The single-instance monitoring component is limited by specifications of a Central Processing Unit (CPU), a memory, a disk and the like of the machine, and the amount of index data which can be calculated by pulling is limited. The large-scale index data inevitably occupies more memory, the process of continuously pulling the large-scale index data inevitably consumes more CPU, and the storage days and the storage quantity of the index data falling into the disk are also inevitably limited. The data volume pressure of each monitoring component fragment is balanced by expanding the quantity of the monitoring component fragments (monitoring component instances), but the pod number of the monitoring components is not changed, so that the data volume bottleneck of a single-instance monitoring component is broken through to a certain extent.
With continued reference to fig. 3, fig. 3 is a schematic diagram 300 of an application scenario of the monitoring method of the container orchestration engine according to the present embodiment. A large-scale container orchestration engine cluster 301 in the middle of deployment in a server cluster. The container layout engine cluster 301 includes multiple acquisition components such as a kube-state-metrics, a kubel, a node-Exporter, a pod-metric, and an Exporter, and is responsible for acquiring index data of bottom components of container layout engines such as various containers, pods, and nodes and customized indexes of service components corresponding to applications. Index collection agent components in the index collection agent component cluster 302 acquire index data of the container arrangement engine cluster 301 from various collection components according to collection configuration files of the container arrangement engine cluster 301 of the monitoring component 303, and determine the number of fragments of the monitoring component 303 according to the acquired index data; the monitoring components 303 are segmented to obtain monitoring component segments with the number of the segments; for each monitoring component fragment in the monitoring component fragments of the number of fragments, index data corresponding to the monitoring component fragment is acquired from the index collection agent component cluster 302, and the container arrangement engine cluster 301 is monitored.
In the method provided by the above embodiment of the present application, the number of fragments of the monitoring component is determined according to the acquisition configuration file of the monitoring component for the container arrangement engine cluster through the index acquisition proxy component in the index acquisition proxy component cluster; the monitoring components are segmented to obtain monitoring component segments with the number of the segments; for each monitoring component fragment in the monitoring component fragments with the fragment number, index data corresponding to the monitoring component fragment is obtained from the index acquisition agent component cluster, and the container arrangement engine cluster is monitored, so that the monitoring component can be automatically transversely expanded based on the index acquisition agent component, the monitoring tasks of the container arrangement engine cluster with various scales are adapted, and the practicability of the monitoring component and the application range of the monitoring tasks are improved.
With continued reference to FIG. 4, there is shown a schematic flow chart 400 of yet another embodiment of a monitoring method for a container orchestration engine according to the present application, comprising the steps of:
And step 402, generating an index capture task for the container arrangement engine cluster according to the acquisition configuration file and the node online and offline event through a configuration manager.
And 403, executing the index grabbing task through the task manager, and acquiring index data corresponding to the target object in the container arrangement engine cluster.
And step 404, determining the fragment number of the monitoring component according to the index data acquired by the task manager through the metadata manager.
And 406, fragmenting the monitoring component according to the plurality of sub-acquisition configuration files to obtain the monitoring component fragments with the number of fragments.
As can be seen from this embodiment, compared with the embodiment corresponding to fig. 2, the flow 400 of the monitoring method for a container arrangement engine in this embodiment specifically illustrates a process of determining the number of fragments of a monitoring component based on an index acquisition agent component, a process of fragmenting the monitoring component, and a process of acquiring corresponding index data by each monitoring component fragment, where the monitoring component can be automatically and laterally expanded based on the index acquisition agent component to adapt to monitoring tasks of container arrangement engine clusters of various scales, so as to further improve the practicability of the monitoring component and the application range of the monitoring tasks.
With continuing reference to fig. 5, a schematic structural diagram of a monitoring system of a container orchestration engine is shown, where the system embodiment corresponds to the method embodiment shown in fig. 2, and includes a container orchestration engine cluster 501, an index collection agent component cluster 502, and a monitoring component 503.
The index collection agent component cluster 502 is used for determining the fragment number of the monitoring components according to the collection configuration file of the container arrangement engine cluster by the monitoring components through the index collection agent components in the index collection agent component cluster; the monitoring component is divided into pieces, and the monitoring component pieces with the piece number are obtained; and the monitoring component 503 is configured to, for each monitoring component segment in the monitoring component segments of the segment number, obtain index data corresponding to the monitoring component segment from the index collection agent component cluster, and monitor the container arrangement engine cluster.
In some optional implementations of this embodiment, the index collection agent component cluster is further configured to: dividing the acquisition configuration file to obtain a plurality of sub-acquisition configuration files; the monitoring component is segmented according to the plurality of sub-acquisition configuration files to obtain monitoring component segments with the number of the segments; and establishing a corresponding relation between the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments with the number of fragments.
In some optional implementations of this embodiment, the monitoring component is further configured to: for each monitoring component fragment in the monitoring component fragments with the fragment number, determining a target object to be monitored by the monitoring component fragment according to a sub-acquisition configuration file corresponding to the monitoring component fragment; and acquiring the index data corresponding to the monitoring component fragment from the index acquisition agent component which is responsible for pulling the index data from the target object to be monitored of the monitoring component fragment in the index acquisition agent component cluster.
With continued reference to fig. 6, in some alternative implementations of this embodiment, the index collection agent group 600 includes a configuration manager 601, a task manager 602, and a metadata manager 603, and a configuration manager for generating an index crawling task for the container arrangement engine cluster according to a collection configuration file; the task manager is used for executing the index grabbing task and acquiring index data corresponding to the target object in the container arrangement engine cluster; and the metadata manager is used for determining the fragment number of the monitoring component according to the index data acquired by the task manager.
In some optional implementations of this embodiment, the metadata manager is further configured to: and determining the fragment number of the monitoring component by the metadata manager according to the index data acquired by the task manager by adopting a load balancing strategy.
With continued reference to fig. 6, in some optional implementations of this embodiment, the index collection agent component further includes: cluster manager 604 for determining a survival status of an index collection agent component in a cluster of index collection agent components; generating a node on-line and off-line event for the index collection agent component according to the survival state; and the configuration manager is further used for generating an index grabbing task for the container arrangement engine cluster according to the acquisition configuration file and the node online and offline event.
In this embodiment, the monitoring system of the container arrangement engine can automatically perform horizontal expansion on the monitoring component based on the index acquisition proxy component to adapt to the monitoring tasks of the container arrangement engine clusters of various scales, so that the practicability of the monitoring component and the application range of the monitoring tasks are improved.
With continuing reference to fig. 7, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of a monitoring apparatus for a container arrangement engine, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be applied to various electronic devices.
As shown in fig. 7, the monitoring apparatus of the container arrangement engine includes: a determining unit 701 configured to determine, by an index collection agent component in the index collection agent component cluster, a fragmentation number of a monitoring component according to a collection configuration file of the monitoring component for the container arrangement engine cluster; the fragmentation unit 702 is configured to fragment the monitoring component to obtain monitoring component fragments of the number of fragments; the monitoring unit 703 is configured to, for each monitoring component segment in the monitoring component segments of the segment number, obtain index data corresponding to the monitoring component segment from the index collection agent component cluster, and monitor the container arrangement engine cluster.
In some optional implementations of this embodiment, the above-mentioned fragmentation unit 702 is further configured to: dividing the acquisition configuration file to obtain a plurality of sub-acquisition configuration files; the monitoring component is segmented according to the plurality of sub-acquisition configuration files to obtain monitoring component segments with the number of the segments; and establishing a corresponding relation between the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments with the number of fragments.
In some optional implementations of this embodiment, the monitoring unit 703 is further configured to: for each monitoring component fragment in the monitoring component fragments with the fragment number, determining a target object to be monitored by the monitoring component fragment according to a sub-acquisition configuration file corresponding to the monitoring component fragment; and acquiring the index data corresponding to the monitoring component fragment from the index acquisition agent component which is responsible for pulling the index data from the target object to be monitored of the monitoring component fragment in the index acquisition agent component cluster.
In some optional implementations of this embodiment, the index collection agent component includes a configuration manager, a task manager, and a metadata manager, and the determining unit 701 is further configured to: generating an index grabbing task for the container arrangement engine cluster according to the acquisition configuration file through a configuration manager; executing an index grabbing task through a task manager, and acquiring index data corresponding to a target object in a container arrangement engine cluster; and determining the fragment number of the monitoring component according to the index data acquired by the task manager through the metadata manager.
In some optional implementations of this embodiment, the determining unit 701 is further configured to: and determining the fragment number of the monitoring component by the metadata manager according to the index data acquired by the task manager by adopting a load balancing strategy.
In some optional implementation manners of this embodiment, the index collection agent component further includes a cluster manager, and the apparatus further includes: a generating unit (not shown in the figures) configured to determine, by the cluster manager, a survival status of the index collection agent components in the cluster of index collection agent components; generating a node on-line and off-line event for the index collection agent component according to the survival state; and the above-mentioned determining unit 701, further configured to: and generating an index capturing task for the container arrangement engine cluster according to the acquisition configuration file and the node online and offline event through a configuration manager.
In this embodiment, a determining unit in the monitoring apparatus of the container arrangement engine determines the number of fragments of the monitoring component according to the acquisition configuration file of the monitoring component for the container arrangement engine cluster through the index acquisition proxy component in the index acquisition proxy component cluster; the fragmentation unit fragments the monitoring component to obtain monitoring component fragments with the number of fragments; the monitoring unit acquires index data corresponding to the monitoring component fragments from the index acquisition agent component cluster for each monitoring component fragment in the monitoring component fragments with the fragment number, and monitors the container arrangement engine cluster, so that the monitoring component can be automatically transversely expanded based on the index acquisition agent component, monitoring tasks of the container arrangement engine cluster with various scales are adapted, and the practicability of the monitoring component and the application range of the monitoring tasks are improved.
Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use in implementing devices of embodiments of the present application (e.g., devices 101, 102, 103, 105 shown in FIG. 1). The apparatus shown in fig. 8 is only an example, and should not bring any limitation to the function and the scope of use of the embodiments of the present application.
As shown in fig. 8, a computer system 800 includes a processor (e.g., CPU, central processing unit) 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data necessary for the operation of the system 800 are also stored. The processor 801, the ROM802, and the RAM803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that the computer program read out therefrom is mounted on the storage section 808 as necessary.
In particular, according to embodiments of the present application, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the processor 801, performs the above-described functions defined in the methods of the present application.
It should be noted that the computer readable medium of the present application can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the client computer, partly on the client computer, as a stand-alone software package, partly on the client computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the client computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a determination unit, a slicing unit, and a monitoring unit. For example, the determining unit may also be described as a unit that determines the number of fragments of the monitoring component according to the collection configuration file of the monitoring component for the container arrangement engine cluster.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the computer device to: determining the number of fragments of the monitoring component according to the acquisition configuration file of the container arrangement engine cluster by the monitoring component through an index acquisition agent component in the index acquisition agent component cluster; the monitoring component is divided into pieces, and the monitoring component pieces with the piece number are obtained; and for each monitoring component fragment in the monitoring component fragments with the number of fragments, acquiring index data corresponding to the monitoring component fragment from the index acquisition agent component cluster, and monitoring the container arrangement engine cluster.
The foregoing description is only exemplary of the preferred embodiments of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (15)
1. A method of monitoring a container orchestration engine, comprising:
determining the fragmentation number of a monitoring component according to a collection configuration file of the monitoring component for a container arrangement engine cluster through an index collection agent component in an index collection agent component cluster;
the monitoring components are segmented to obtain the monitoring component segments of the number of the segments;
and for each monitoring component fragment in the monitoring component fragments with the number of the fragments, acquiring index data corresponding to the monitoring component fragment from the index collection agent component cluster, and monitoring the container arrangement engine cluster.
2. The method of claim 1, wherein the slicing the monitoring component to obtain the sliced number of monitoring component slices comprises:
dividing the acquisition configuration file to obtain a plurality of sub-acquisition configuration files;
fragmenting the monitoring component according to the plurality of sub-acquisition configuration files to obtain the monitoring component fragments of the number of the fragments;
and establishing a corresponding relation between the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments with the number of the fragments.
3. The method of claim 2, wherein the obtaining, for each monitoring component slice of the number of monitoring component slices, index data corresponding to the monitoring component slice from the index collection agent component cluster comprises:
for each monitoring component fragment in the monitoring component fragments with the fragment number, determining a target object to be monitored by the monitoring component fragment according to a sub-acquisition configuration file corresponding to the monitoring component fragment;
and acquiring the index data corresponding to the monitoring component fragment from the index acquisition agent component which is responsible for pulling the index data from the target object to be monitored of the monitoring component fragment in the index acquisition agent component cluster.
4. The method of claim 1, wherein the metric collection agent component comprises a configuration manager, a task manager, and a metadata manager, and
the determining of the fragment number of the monitoring component according to the acquisition configuration file of the monitoring component to the container arrangement engine cluster through the index acquisition agent component in the index acquisition agent component cluster comprises the following steps:
generating an index grabbing task for the container arrangement engine cluster according to the acquisition configuration file through the configuration manager;
executing the index grabbing task through the task manager, and acquiring index data corresponding to a target object in the container arrangement engine cluster;
and determining the fragment number of the monitoring component according to the index data acquired by the task manager through the metadata manager.
5. The method of claim 4, wherein the determining, by the metadata manager, the number of segments of the monitoring component according to the index data obtained by the task manager comprises:
and determining the fragment quantity of the monitoring component by the metadata manager according to the index data acquired by the task manager by adopting a load balancing strategy.
6. The method of claim 4, wherein the metric collection agent component further comprises a cluster manager, and
further comprising:
determining, by the cluster manager, a survival status of an index collection agent component in the cluster of index collection agent components;
generating a node on-line and off-line event for the index collection agent component according to the survival state; and
generating an index grabbing task for the container arrangement engine cluster according to the acquisition configuration file through the configuration manager, wherein the index grabbing task comprises
And generating an index capture task for the container arrangement engine cluster according to the acquisition configuration file and the node on-line and off-line events through the configuration manager.
7. A monitoring system for a container orchestration engine comprising:
the index acquisition agent component cluster is used for determining the fragment number of the monitoring components according to the acquisition configuration file of the container arrangement engine cluster by the monitoring components through the index acquisition agent components in the index acquisition agent component cluster; the monitoring components are segmented to obtain the monitoring component segments of the number of the segments;
and the monitoring component is used for acquiring index data corresponding to each monitoring component fragment in the monitoring component fragments with the number of the fragments from the index acquisition agent component cluster and monitoring the container arrangement engine cluster.
8. The system of claim 7, wherein the cluster of metric collection agent components is further configured to:
dividing the acquisition configuration file to obtain a plurality of sub-acquisition configuration files; fragmenting the monitoring component according to the plurality of sub-acquisition configuration files to obtain the monitoring component fragments of the number of the fragments; and establishing a corresponding relation between the sub-configuration files in the plurality of sub-configuration files and the monitoring component fragments in the monitoring component fragments of the fragment number.
9. The system of claim 8, wherein the monitoring component is further configured to:
for each monitoring component fragment in the monitoring component fragments with the fragment number, determining a target object to be monitored by the monitoring component fragment according to a sub-acquisition configuration file corresponding to the monitoring component fragment; and acquiring the index data corresponding to the monitoring component fragment from the index acquisition agent component which is responsible for pulling the index data from the target object to be monitored of the monitoring component fragment in the index acquisition agent component cluster.
10. The system of claim 7, wherein the metric collection agent component comprises a configuration manager, a task manager, and a metadata manager, and
the configuration manager is used for generating an index grabbing task for the container arrangement engine cluster according to the acquisition configuration file;
the task manager is used for executing the index grabbing task and acquiring index data corresponding to a target object in the container arrangement engine cluster;
and the metadata manager is used for determining the fragment number of the monitoring component according to the index data acquired by the task manager.
11. The system of claim 10, wherein the metadata manager is further to:
and determining the fragment quantity of the monitoring component by the metadata manager according to the index data acquired by the task manager by adopting a load balancing strategy.
12. The system of claim 10, wherein the metric collection agent component further comprises:
the cluster manager is used for determining the survival state of the index collection agent components in the index collection agent component cluster; generating a node on-line and off-line event for the index collection agent component according to the survival state; and
the configuration manager is further configured to generate an index capture task for the container arrangement engine cluster according to the acquisition configuration file and the node online and offline event.
13. A monitoring apparatus of a container orchestration engine, comprising:
the determining unit is configured to determine the fragment number of the monitoring component according to the acquisition configuration file of the monitoring component to the container arrangement engine cluster through an index acquisition agent component in the index acquisition agent component cluster;
the fragmentation unit is configured to fragment the monitoring components to obtain monitoring component fragments of the number of fragments;
and the monitoring unit is configured to acquire index data corresponding to the monitoring component fragments from the index acquisition agent component cluster for each monitoring component fragment in the monitoring component fragments of the number of fragments, and monitor the container arrangement engine cluster.
14. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-6.
15. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method recited in any of claims 1-6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211672491.5A CN115809119A (en) | 2022-12-26 | 2022-12-26 | Monitoring method, system and device for container arrangement engine |
| PCT/CN2023/123785 WO2024139516A1 (en) | 2022-12-26 | 2023-10-10 | Method, system and apparatus for monitoring container orchestration engine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211672491.5A CN115809119A (en) | 2022-12-26 | 2022-12-26 | Monitoring method, system and device for container arrangement engine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115809119A true CN115809119A (en) | 2023-03-17 |
Family
ID=85486854
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211672491.5A Pending CN115809119A (en) | 2022-12-26 | 2022-12-26 | Monitoring method, system and device for container arrangement engine |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115809119A (en) |
| WO (1) | WO2024139516A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117014284A (en) * | 2023-10-08 | 2023-11-07 | 北京凌云雀科技有限公司 | Inspection system, inspection method, electronic equipment and storage medium |
| WO2024139516A1 (en) * | 2022-12-26 | 2024-07-04 | 京东科技信息技术有限公司 | Method, system and apparatus for monitoring container orchestration engine |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10091057B2 (en) * | 2015-12-28 | 2018-10-02 | Ca, Inc. | Configuring distributed monitoring systems |
| CN110262899B (en) * | 2019-06-20 | 2021-05-11 | 华云数据控股集团有限公司 | Monitoring component elastic expansion method and device based on Kubernetes cluster and controlled terminal |
| CN112130996A (en) * | 2020-09-22 | 2020-12-25 | 腾讯科技（深圳）有限公司 | Data monitoring control system, method and device, electronic equipment and storage medium |
| CN113342618B (en) * | 2021-06-30 | 2024-06-18 | 深圳前海微众银行股份有限公司 | Distributed monitoring cluster management method, device and computer readable storage medium |
| CN114564314A (en) * | 2022-03-15 | 2022-05-31 | 京东科技信息技术有限公司 | Method and device for collecting monitoring data in cluster |
| CN115809119A (en) * | 2022-12-26 | 2023-03-17 | 京东科技信息技术有限公司 | Monitoring method, system and device for container arrangement engine |
-
2022
- 2022-12-26 CN CN202211672491.5A patent/CN115809119A/en active Pending
-
2023
- 2023-10-10 WO PCT/CN2023/123785 patent/WO2024139516A1/en unknown
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024139516A1 (en) * | 2022-12-26 | 2024-07-04 | 京东科技信息技术有限公司 | Method, system and apparatus for monitoring container orchestration engine |
| CN117014284A (en) * | 2023-10-08 | 2023-11-07 | 北京凌云雀科技有限公司 | Inspection system, inspection method, electronic equipment and storage medium |
| CN117014284B (en) * | 2023-10-08 | 2023-12-19 | 北京凌云雀科技有限公司 | Inspection system, inspection method, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024139516A1 (en) | 2024-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11755452B2 (en) | Log data collection method based on log data generated by container in application container environment, log data collection device, storage medium, and log data collection system | |
| CN115809119A (en) | Monitoring method, system and device for container arrangement engine | |
| CN109327351B (en) | Method and device for collecting log data in real time, electronic equipment and storage medium | |
| CN110262807B (en) | Cluster creation progress log acquisition system, method and device | |
| CN111124819A (en) | Method and device for monitoring full link | |
| US20170324807A1 (en) | Proactive content push for enhancing real-time service delivery via cloud | |
| US10956214B2 (en) | Time frame bounded execution of computational algorithms | |
| CN114625597A (en) | Monitoring operation and maintenance system, method and device, electronic equipment and storage medium | |
| CN110928934A (en) | Data processing method and device for business analysis | |
| CN111352903A (en) | Log management platform, log management method, medium, and electronic device | |
| CN114785690B (en) | Monitoring method based on service grid and related equipment | |
| CN111752807A (en) | Resource monitoring method based on Kubernetes | |
| CN113032237B (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN113422808B (en) | Internet of things platform HTTP information pushing method, system, device and medium | |
| CN111831503A (en) | Monitoring method based on monitoring agent and monitoring agent device | |
| CN113312321A (en) | Abnormal monitoring method for traffic and related equipment | |
| CN108540439A (en) | Data analysis method and system, equipment and storage medium | |
| CN110807058B (en) | Method and system for exporting data | |
| CN111274104B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN111698109A (en) | Method and device for monitoring log | |
| CN114756301A (en) | Log processing method, device and system | |
| CN114035861A (en) | Cluster configuration method and device, electronic equipment and computer readable medium | |
| CN113672472A (en) | Disk monitoring method and device | |
| CN112688982B (en) | User request processing method and device | |
| CN113282455A (en) | Monitoring processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |