Monitoring index acquisition method and device
By analyzing the metric configuration file to obtain container group information and add tags, the problem of lack of effective tag information in the monitoring system in the kubernetes environment is solved, and more accurate and visual monitoring data is achieved.
Patent Information
- Application Number
- CN202411571446.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-05
- Publication Date
- 2025-02-18
AI Technical Summary
In the computing business scenario of the kubernetes environment, the existing monitoring system cannot effectively obtain the specific pod information of the container group, resulting in the lack of effective tag information, affecting the accuracy and visualization of the monitoring data.
By parsing the pre-generated indicator configuration file, obtain the information file storage path, file name and label field name of the container group, read the information file and parse the tag content, and add these tags to the monitoring indicator data of the file system and block device. And push to the monitoring system.
It realizes that pod information is attached to the monitoring indicator data of the file system and block equipment in the form of a tag and pushed to the monitoring system, which facilitates querying specific pod usage information through associated tag conditions, improving the accuracy and visualization of the monitoring data.
Smart Images
Figure CN119473783A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular to a monitoring indicator collection method and device. Background Art
[0002] The existing unified file storage system uses storage and computing separation technology to shield the heterogeneity of the underlying storage to achieve unified storage and management of data. Monitoring uses a separate component to collect business indicators. In some computing business scenarios in the Kubernetes environment, only the basic information of the file system mounted by the client can be seen, but the associated specific pod (container group) information cannot be seen, and the monitoring lacks effective label information. Summary of the invention
[0003] The embodiments of the present disclosure provide a monitoring indicator collection method and device.
[0004] In a first aspect, an embodiment of the present disclosure provides a monitoring indicator collection method, comprising: parsing a storage path, a file name, and a field name of a label of an information file of a container group from a pre-generated indicator configuration file, wherein the container group is mounted with a file system; reading the information file according to the storage path and the file name, and parsing the content corresponding to the field name from the information file as a label; collecting monitoring indicator data of the file system; adding the label to the monitoring indicator data of the file system, and pushing it to a monitoring system.
[0005] In some embodiments, the method further includes: parsing information of the block device mounted on the container group from the indicator configuration file; collecting monitoring indicator data of the block device; adding the tag to the monitoring indicator data of the block device, and pushing it to the monitoring system.
[0006] In some embodiments, the method further includes: querying monitoring indicator data of the file system according to the tag; and displaying the queried monitoring indicator data of the file system in a graphical manner.
[0007] In some embodiments, the method further includes: querying monitoring indicator data of the block device according to the tag; and displaying the queried monitoring indicator data of the block device in a graphical manner.
[0008] In some embodiments, collecting monitoring indicator data of the file system includes: parsing the business name of collecting the monitoring indicators of the file system from the indicator configuration file; registering a collection task for the monitoring indicators of the file system based on the business name; periodically executing the collection task; and counting the performance indicators of the collection task.
[0009] In some embodiments, collecting monitoring indicator data of the block device includes: parsing the service name of collecting the monitoring indicator of the block device from the indicator configuration file; registering a collection task for the monitoring indicator of the block device based on the service name; periodically executing the collection task; and counting the performance indicators of the collection task.
[0010] In a second aspect, an embodiment of the present disclosure provides a monitoring indicator collection device, comprising: a parsing unit, configured to parse out a storage path, a file name, and a field name of a label of an information file of a container group from a pre-generated indicator configuration file, wherein the container group is mounted with a file system; a reading unit, configured to read the information file according to the storage path and the file name, and parse out the content corresponding to the field name from the information file as a label; a collection unit, configured to collect monitoring indicator data of the file system; a labeling unit, configured to add the label to the monitoring indicator data of the file system, and push it to the monitoring system.
[0011] In some embodiments, the parsing unit is further configured to: parse the information of the block device mounted by the container group from the indicator configuration file; the collection unit is further configured to: collect the monitoring indicator data of the block device; the labeling unit is further configured to: add the label to the monitoring indicator data of the block device and push it to the monitoring system.
[0012] In some embodiments, the device further includes a query unit configured to: query the monitoring indicator data of the file system according to the tag; and display the queried monitoring indicator data of the file system in a graphical manner.
[0013] In some embodiments, the apparatus further includes a query unit configured to: query the monitoring indicator data of the block device according to the tag; and display the queried monitoring indicator data of the block device in a graphical manner.
[0014] In some embodiments, the collection unit is further configured to: parse the business name of collecting monitoring indicators of the file system from the indicator configuration file; register a collection task for the monitoring indicators of the file system based on the business name; periodically execute the collection task; and count the performance indicators of the collection task.
[0015] In some embodiments, the collection unit is further configured to: parse the business name of the monitoring indicators of the block device from the indicator configuration file; register a collection task for the monitoring indicators of the block device based on the business name; periodically execute the collection task; and count the performance indicators of the collection task.
[0016] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a storage device on which one or more computer programs are stored, and when the one or more computer programs are executed by the one or more processors, the one or more processors implement a method as described in any one of the first aspects.
[0017] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method as described in any one of the first aspects.
[0018] In a fifth aspect, an embodiment of the present disclosure provides a computer program product, including a computer program, which implements the method as described in any one of the first aspects when executed by a processor.
[0019] The monitoring indicator collection method and device provided by the embodiments of the present disclosure can flexibly specify the correspondence between monitoring indicators and labels through a unified customized indicator configuration file, locate the pod file through the directory and volume information where the pod information file is located, and attach the obtained pod information to the monitoring indicators of the corresponding file system in the form of labels after parsing. After being pushed to the monitoring system, the specific pod usage information of the file system can be queried through the associated label conditions.
[0020] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Other features, objects and advantages of the present disclosure will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:
[0022] Figure 1 is an exemplary system architecture diagram in which an embodiment of the present disclosure may be applied;
[0023] Figure 2 is a flow chart of an embodiment of a monitoring indicator collection method according to the present disclosure;
[0024] Figure 3 is a flow chart of another embodiment of the monitoring indicator collection method according to the present disclosure;
[0025] Figure 4 is a schematic diagram of an application scenario of the monitoring indicator collection method disclosed in the present invention;
[0026] Figure 5 is a structural schematic diagram of an embodiment of a monitoring indicator collection device according to the present disclosure;
[0027] Figure 6 It is a structural diagram of a computer system of an electronic device suitable for implementing an embodiment of the present disclosure. DETAILED DESCRIPTION
[0028] The present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It is also necessary to explain that, for ease of description, only the parts related to the relevant invention are shown in the accompanying drawings.
[0029] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.
[0030] Figure 1 An exemplary system architecture is shown to which an embodiment of the monitoring indicator collection method or monitoring indicator collection device disclosed in the present invention can be applied.
[0031] like Figure 1 As shown, the system architecture may include a business layer, an indicator collector, and a monitoring system. The business layer may include object storage, cloud hard disks, general flash storage, underlying storage, big data, etc. The business layer interacts with the indicator collector through a business interface.
[0032] Export the pod information to the pod file of the specified path in advance, export the mounted device information to the block information file of the specified path, and write the path of the pod file and the path of the block information file into the indicator configuration file. The indicator configuration file also records the label-related information. The indicator collector reads the indicator configuration file, parses the path of the pod file and the path of the block information file, and then locates the pod file according to the path and reads the label corresponding to each business indicator. After the indicator collector pulls the business data through the business interface, it performs indicator statistics according to the indicator information list, parses the customized indicators from the business data, and extracts the collected indicators. Push the indicator data to the monitoring system. The indicator collector can also pull indicator data from the monitoring system and return it to the business layer through the business interface, so that the business layer can query business indicators according to labels.
[0033] It should be noted that the monitoring system can be hardware or software. When the monitoring system is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or it can be implemented as a single server. When the monitoring system is software, it can be implemented as multiple software or software modules (for example, multiple software or software modules used to provide distributed services), or it can be implemented as a single software or software module. No specific limitation is made here. The server can also be a server of a distributed system, or a server combined with a blockchain. The server can also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.
[0034] It should be noted that the monitoring indicator collection method provided in the embodiments of the present disclosure is generally executed by an indicator collector, and accordingly, the monitoring indicator collection device is generally arranged in the indicator collector.
[0035] It should be understood that Figure 1 The number of business layers, indicator collectors, and monitoring systems in the example is only illustrative. Any number of business layers, indicator collectors, and monitoring systems may be provided as required.
[0036] Continue to refer Figure 2 , shows a process 200 of an embodiment of a monitoring indicator collection method according to the present disclosure. The monitoring indicator collection method includes the following steps:
[0037] Step 201: parse the storage path, file name and label field name of the information file of the container group from the pre-generated indicator configuration file.
[0038] In this embodiment, the execution subject of the monitoring indicator collection method (for example Figure 1 The indicator collector shown in the figure can read the indicator configuration file. The indicator configuration file can be configured as follows: the path of the pod file, the pod file name (including the volume ID and the volume mount instance ID), the mount point directory of the file system (fs) mounted by the pod, the block device name used by the pod, and the field name of the label (specify which fields in the pod file are added to the indicator as labels). If multiple pods use the same block device, the information of these pods will be exported to the same pod file in JSON array format. The content of the indicator configuration file can be shown in the following example:
[0039] Name:CustomProducer#Define the producer name
[0040] Dir: / var / run / cbs / dev#Specify the block device process information file directory used by the client
[0041] LocalLabels:#Local label group
[0042] -Dir: / var / run / cbd / dev / pod_infos#Specify the directory where the pod file exported from k8s is located
[0043] GenLabelIdx: true #Specify whether to generate a label with an idx suffix and attach it to the indicator
[0044] FilenameSelectors:#pod file tag: Find the corresponding file based on the volume ID and volume mount instance ID
[0045] Keys:
[0046] -VolumeId#Specifies the volume ID that needs to be parsed from the runtime block device file
[0047] Keys:
[0048] -InstanceUuid#Specifies the volume mount instance ID that needs to be parsed from the runtime block device file
[0049] Filesystems:#Filesystem Tags
[0050] -Keys:
[0051] -fs_mount_path#Specifies the file system mount point directory that needs to be obtained from the pod file
[0052] BlockDevices:#Block device tags
[0053] -Keys:
[0054] -device_name#Specifies the block device name that needs to be obtained from the pod file
[0055] ConfigSelectKeys:#Specify which Labels can be attached to the indicator
[0056] podUuid:#Specify the value of labelpodUuid to be the pod_uuid value in the pod file
[0057] Keys:
[0058] -pod_uuid
[0059] podName:#Specify the value of LabelpodName to be the pod_name value in the pod file
[0060] Keys:
[0061] -pod_name
[0062] Step 202: read the information file according to the storage path and file name, and parse the content corresponding to the field name from the information file as a label.
[0063] In this embodiment, the pod information file is read according to the storage path and file name of the pod file. For example, the pod information file is located according to the volume information volumeId and InstanceId information, and the content corresponding to the field name of the label is parsed from the pod information file, that is, the label, for example, pod_uuid or pod_name is used as the label, or both are used as labels.
[0064] Step 203: Collect monitoring indicator data of the file system.
[0065] In this embodiment, a thread for collecting data can be started, waiting for tasks and asynchronously executing the collected monitoring index data of the file system, for example, URL interface performance, block device performance, file system performance, etc.
[0066] Step 204: Add the tag to the monitoring indicator data of the file system and push it to the monitoring system.
[0067] In this embodiment, the tag extracted in step 202 is added to the monitoring indicator data of the file system collected in step 203. Then it can be pushed to the monitoring system. The monitoring system can be a common service monitoring system and time series database on the market, which can provide a common data model and a quick data collection, storage and query interface.
[0068] Optionally, before the monitoring indicator data of the file system is pushed to the monitoring system, it can be converted into monitoring data in a standard format required by the monitoring system, and then pushed to the monitoring system after being compressed.
[0069] The method provided by the above-mentioned embodiment of the present disclosure can flexibly specify the correspondence between monitoring indicators and labels through a unified customized indicator configuration file, locate the pod file through the directory and volume information where the pod information file is located, and attach the obtained pod information to the monitoring indicators of the corresponding file system in the form of labels after parsing. After being pushed to the monitoring system, the specific pod usage information of the file system can be queried through the associated label conditions.
[0070] In some optional implementations of this embodiment, the method further includes: querying the monitoring indicator data of the file system according to the label in the monitoring system; and displaying the queried monitoring indicator data of the file system in a graphical manner. The monitoring indicator data of the file system can be queried through the previously defined labels. For example, by entering pod_uuid or pod_name in the monitoring system, the monitoring indicator data of the file system containing pod_uuid or pod_name can be queried. Then display it in a graphical manner. Using labeling can facilitate the query and display of the monitoring indicator data of the file system, facilitate the location and discovery of problems, and improve the user experience.
[0071] In some optional implementations of this embodiment, the collection of monitoring indicator data of the file system includes: parsing the service name of the monitoring indicator of the file system from the indicator configuration file; registering the collection task for the monitoring indicator of the file system based on the service name; periodically executing the collection task; and counting the performance indicators of the collection task. The indicator configuration file may include the service name, such as the "CustomProducer" mentioned above. The service name may be registered for the collection task of the monitoring indicator of the file system. When the unified indicator collection service is started, the directory where the service configuration file is located will be specified, all service configuration file lists will be read according to the directory, the file list will be traversed, the file contents will be read one by one, and the base class producer will be parsed according to the unified service configuration file specification, and the producer of the corresponding service will be constructed according to the service name in the configuration, and added to the global producer list, providing a list of all service producers that need to be collected for the periodic timing task. According to the service concurrency configuration, multiple threads are started to process the collection task, and the reception of the collection task is realized through the channel (pipeline), and the task delivered by the periodic collection indicator thread is synchronized with the task, and the pipeline will process the collection task if it gets the collection task.
[0072] The performance indicators of the collection tasks can also be pushed to the monitoring system.
[0073] Further references Figure 3 , which shows a process 300 of another embodiment of a monitoring indicator collection method. The process 300 of the monitoring indicator collection method includes the following steps:
[0074] Step 301: parse the storage path, file name and tag field name of the information file of the container group from the pre-generated indicator configuration file.
[0075] Step 302: read the information file according to the storage path and file name, and parse the content corresponding to the field name from the information file as a label.
[0076] Steps 301-302 are substantially the same as steps 201-202, and thus are not described in detail herein.
[0077] Step 303: parse the information of the block device mounted by the container group from the indicator configuration file.
[0078] In this embodiment, as described above, the indicator configuration file may also include information of the block device mounted by the container group, and the information of the block device may include a block device process information file directory and a block device name.
[0079] Step 304: Collect monitoring indicator data of the block device.
[0080] In this embodiment, monitoring indicator data of the block device, for example, IO interface statistics data, is collected based on the information of the block device.
[0081] Step 305: Add the tag to the monitoring indicator data of the block device and push it to the monitoring system.
[0082] In this embodiment, the tag obtained in step 302 is added to the monitoring index data of the block device and pushed to the monitoring system. The monitoring system can be a common service monitoring system and time series database on the market, which can provide a common data model and a quick data collection, storage and query interface.
[0083] Optionally, before the monitoring indicator data is pushed to the monitoring system, it can be converted into monitoring data in a standard format required by the monitoring system, and then pushed to the monitoring system after being compressed.
[0084] In some optional implementations of this embodiment, the method further includes: querying the monitoring indicator data of the block device according to the label in the monitoring system; and displaying the queried monitoring indicator data of the block device in a graphical manner. The monitoring indicator data of the block device can be queried through the previously defined labels. For example, by entering pod_uuid or pod_name in the monitoring system, the monitoring indicator data of the block device containing pod_uuid or pod_name can be queried. Then display it in a graphical manner. Using labeling can facilitate the query and display of the monitoring indicator data of the block device, facilitate the location and discovery of problems, and improve the user experience.
[0085] In some optional implementations of this embodiment, collecting the monitoring index data of the block device includes: parsing the service name of the monitoring index of the block device from the index configuration file; registering the collection task of the monitoring index of the block device based on the service name; periodically executing the collection task; and counting the performance index of the collection task. The service name may be included in the index configuration file, such as the "CustomProducer" mentioned above. The service name may be registered for the collection task of the monitoring index of the block device. When the unified index collection service is started, the directory where the service configuration file is located is specified, all service configuration file lists are read according to the directory, the file list is traversed, the file contents are read one by one, and the base class producer (producer) is parsed according to the unified service configuration file specification, and the producer of the corresponding service is constructed according to the service name in the configuration, and added to the global producer list, providing a list of all service producers that need to be collected for the periodic timing task. According to the service concurrency configuration, multiple threads are started to process the collection task, and the reception of the collection task is realized through the channel (pipeline), and the task delivered by the periodic collection index thread is synchronized with the task, and the pipeline processes the collection task if it gets the collection task.
[0086] The performance indicators of the collection tasks can also be pushed to the monitoring system.
[0087] Continue to see Figure 4 , Figure 4 FIG. 1 is a schematic diagram of an application scenario of the monitoring indicator collection method according to this embodiment. Figure 4 In the application scenario, the periodic task is initialized when the service starts, a new thread is started to execute the timer, and the task is executed after the specified time interval. If there is an Inflight task, it is regarded as a task that is executing indicator collection and the periodic collection is exited.
[0088] If there is no Inflight task, read the indicator configuration file list of all business configurations (each business corresponds to an indicator configuration file), traverse the file list, read the file contents one by one, and parse them into the base class producer, and build the producer of the corresponding business according to the business name in the configuration, and add it to the global producer list, providing a list of all business producers that need to be collected for periodic scheduled tasks. Traverse all registered business producers, each producer will start a thread to collect business indicator data concurrently. Start multiple threads to process collection tasks according to the service concurrency configuration. If a file system is configured in the indicator configuration file, the crawling task will be delivered to the file system crawler task pipeline, and then the crawling tasks will be taken out from the file system crawler task pipeline in turn, and the files will be counted according to the file system list, and the labels will be read from the pod file and added to the counted file system indicator data. If block devices are configured in the indicator configuration file, the crawling tasks are delivered to the block device crawler task pipeline, and then the crawling tasks are taken out from the block device crawler task pipeline in turn, the files are counted according to the file system list, and the labels are read from the pod file and added to the counted block device indicator data.
[0089] Wait for all business indicator data to be collected and pushed to the monitoring system, continue to collect statistics on the performance indicators of all concurrent collection tasks, and push them to the monitoring system. Finally, set the status of this periodic task to Idle, and wait for the next periodic timer to collect regularly. Add the pod information parsed from the k8s pod file to the customized business indicators collected periodically in the form of labels, convert them into standard monitoring data, and push them to the monitoring system after data compression.
[0090] Further references Figure 5 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a monitoring indicator collection device. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.
[0091] like Figure 5As shown, the monitoring indicator collection device 500 of this embodiment includes: a parsing unit 501, a reading unit 502, a collection unit 503 and a labeling unit 504. The parsing unit 501 is configured to parse the storage path, file name and field name of the label of the information file of the container group from the pre-generated indicator configuration file, wherein the container group is mounted with a file system; the reading unit 502 is configured to read the information file according to the storage path and the file name, and parse the content corresponding to the field name from the information file as a label; the collection unit 503 is configured to collect the monitoring indicator data of the file system; the labeling unit 504 is configured to add the label to the monitoring indicator data of the file system and push it to the monitoring system.
[0092] In this embodiment, the specific processing of the parsing unit 501, the reading unit 502, the collecting unit 503 and the marking unit 504 of the monitoring indicator collection device 500 can be referred to Figure 2 This corresponds to step 201, step 202, step 203 and step 204 in the embodiment.
[0093] In some optional implementations of this embodiment, the parsing unit 501 is further configured to: parse the information of the block device mounted on the container group from the indicator configuration file; the collection unit 502 is further configured to: collect the monitoring indicator data of the block device; the labeling unit 504 is further configured to: add the label to the monitoring indicator data of the block device, and push it to the monitoring system.
[0094] In some optional implementations of this embodiment, the device also includes a query unit (not shown in the drawings), which is configured to: query the monitoring indicator data of the file system according to the label; and display the queried monitoring indicator data of the file system in a graphical manner.
[0095] In some optional implementations of this embodiment, the device also includes a query unit (not shown in the drawings) configured to: query the monitoring indicator data of the block device according to the label; and display the queried monitoring indicator data of the block device in a graphical manner.
[0096] In some optional implementations of this embodiment, the collection unit 502 is further configured to: parse the business name of collecting the monitoring indicators of the file system from the indicator configuration file; register the collection task of the monitoring indicators of the file system based on the business name; periodically execute the collection task; and count the performance indicators of the collection task.
[0097] In some optional implementations of this embodiment, the collection unit 502 is further configured to: parse the business name of the monitoring indicators of the block device from the indicator configuration file; register the collection task of the monitoring indicators of the block device based on the business name; periodically execute the collection task; and count the performance indicators of the collection task.
[0098] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, storage and other aspects of user personal information involved in the technical solution of this disclosure are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security and national security.
[0099] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device and a readable storage medium.
[0100] An electronic device comprises: one or more processors; a storage device on which one or more computer programs are stored, and when the one or more computer programs are executed by the one or more processors, the one or more processors implement the method described in process 200 or 300.
[0101] A computer-readable medium stores a computer program, wherein the computer program implements the method described in process 200 or 300 when executed by a processor.
[0102] Figure 6 A schematic block diagram of an example electronic device 600 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.
[0103] like Figure 6As shown, the device 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 602 or a computer program loaded from a storage unit 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The computing unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0104] A number of components in the device 600 are connected to the I / O interface 605, including: an input unit 606, such as a keyboard, a mouse, etc.; an output unit 607, such as various types of displays, speakers, etc.; a storage unit 608, such as a disk, an optical disk, etc.; and a communication unit 609, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0105] The computing unit 601 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 601 performs the various methods and processes described above, such as the road area planning method. For example, in some embodiments, the road area planning method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 608. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 600 via the ROM 602 and / or the communication unit 609. When the computer program is loaded into the RAM 603 and executed by the computing unit 601, one or more steps of the road area planning method described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the road area planning method in any other appropriate manner (e.g., by means of firmware).
[0106] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0107] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0108] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0109] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0110] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.
[0111] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the respective computers and having a client-server relationship with each other. The server may be a server of a distributed system, or a server combined with a blockchain. The server may also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology. The server may be a server of a distributed system, or a server combined with a blockchain. The server may also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.
[0112] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.
[0113] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.
Claims
1. A monitoring indicator collection method, comprising: Parsing a storage path, a file name, and a field name of a label of an information file of a container group from a pre-generated indicator configuration file, wherein the container group is mounted with a file system; Read the information file according to the storage path and the file name, and parse the content corresponding to the field name from the information file as a label; Collecting monitoring indicator data of the file system; The tag is added to the monitoring indicator data of the file system and pushed to the monitoring system.
2. The method according to claim 1, wherein: The method further comprises: Parsing information of the block device mounted by the container group from the indicator configuration file; Collect monitoring indicator data of the block device; The tag is added to the monitoring indicator data of the block device and pushed to the monitoring system.
3. The method according to claim 1, wherein: The method further comprises: Querying monitoring indicator data of the file system according to the tag in the monitoring system; The queried monitoring indicator data of the file system is displayed in a graphical manner.
4. The method according to claim 2, wherein: The method further comprises: querying monitoring indicator data of the block device according to the tag in the monitoring system; The queried monitoring indicator data of the block device is displayed in a graphical manner.
5. The method according to claim 1, wherein: The collecting of monitoring indicator data of the file system includes: Parsing the service name of the monitoring indicator of the file system from the indicator configuration file; Registering a collection task for monitoring indicators of the file system based on the service name; Periodically executing the acquisition task; The performance indicators of the acquisition task are counted.
6. The method according to claim 2, wherein: The collecting of monitoring indicator data of the block device includes: Parsing the service name of the monitoring indicator of the block device from the indicator configuration file; Registering a collection task of monitoring indicators for the block device based on the service name; Periodically executing the acquisition task; The performance indicators of the acquisition task are counted.
7. A monitoring indicator collection device, comprising: A parsing unit is configured to parse a storage path, a file name, and a field name of a label of an information file of a container group from a pre-generated indicator configuration file, wherein the container group is mounted with a file system; a reading unit, configured to read the information file according to the storage path and the file name, and parse the content corresponding to the field name from the information file as a label; A collection unit, configured to collect monitoring indicator data of the file system; The labeling unit is configured to add the label to the monitoring indicator data of the file system and push it to the monitoring system.
8. An electronic device comprising: one or more processors; a storage device having one or more computer programs stored thereon, When the one or more computer programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.
9. A computer readable medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.
10. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 6.