Plug-in monitoring method and terminal equipment

Abstract

The invention relates to the technical field of computers, in particular to a plug-in monitoring method and terminal device.Based on a terminal architecture of a task management end, a data storage end and at least one task execution end, script plug-in data and collection task data are synchronized to the data storage end through the task management end; and the task execution end is used for allocating corresponding target script plug-ins to different acquisition tasks, so that the task execution end can be controlled to execute the target script plug-ins, index monitoring of different acquisition task information is completed, data transmission of different hosts or plug-ins is integrated through the data storage end, and the data transmission efficiency is improved. Direct data transmission between the host and the plug-in is reduced, and the technical problem of low monitoring efficiency between the host or the plug-in in the prior art is avoided.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a plug-in monitoring method and terminal equipment. Background Art

[0002] With the continuous development of software technology, plug-in architecture has gradually become the mainstream. The plug-in architecture makes software functions modular, which is convenient for expansion and maintenance. Especially when monitoring hosts and components, by using different acquisition plug-ins for monitoring, the monitoring system can flexibly adapt to the monitoring needs of various hosts and components.

[0003] However, different hosts and components have different characteristics and monitoring requirements. For example, a database server may need to monitor its performance indicators, number of connections, etc., while network equipment needs to monitor its bandwidth utilization, packet loss rate, etc. There are also compatibility issues between different plug-ins. The existing plug-in monitoring technology has low monitoring efficiency when facing the monitoring requirements between plug-ins and hosts.

[0004] The above contents are only for assisting the understanding of the technical solution of the present invention, and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of the present invention is to provide a plug-in monitoring method and a terminal device, aiming to solve the technical problem of low monitoring efficiency between hosts or plug-ins in the prior art.

[0006] To achieve the above object, the present invention provides a plug-in monitoring method, the plug-in monitoring method is applied to a terminal device, the terminal device includes a task management end, a data storage end and at least one task execution end, the data storage end is respectively connected to the task management end and each task execution end;

[0007] The method comprises the following steps:

[0008] The task management end synchronizes script plug-in data and collects task data to the data storage end;

[0009] The data storage terminal stores the script plug-in data and the acquisition task data;

[0010] The task execution end obtains the collection task information and script plug-in information in the data storage end;

[0011] The task execution end executes the target script plug-in according to the script plug-in information to obtain the monitoring indicators corresponding to the collection task information.

[0012] In some embodiments, the plug-in monitoring method further includes:

[0013] The task management terminal determines the resource type corresponding to the collection task object according to the collection task data;

[0014] The task management end associates a script plug-in according to the resource type, and the script plug-in monitors at least one monitoring indicator of the collection task object.

[0015] In some embodiments, the plug-in monitoring method further includes:

[0016] The task management terminal determines whether the monitoring indicators of the same collection task object are associated with multiple script plug-ins;

[0017] If the monitoring indicators of the same collection task object are associated with multiple script plug-ins, the task management end retains one script plug-in and removes the remaining associated script plug-ins.

[0018] In some embodiments, the plug-in monitoring method further includes:

[0019] The task management end obtains parameter configuration information of the collection task and identity identification information of each task execution end;

[0020] The task management end associates the parameter configuration information with the identity identification information to obtain collection task data.

[0021] In some embodiments, the plug-in monitoring method further includes:

[0022] Each task execution end periodically initiates polling to the data storage end, and when the polling is successful, establishes a communication connection between the data storage end and the target task execution end, the target task execution end being the task execution end that succeeds in the polling.

[0023] In some embodiments, the plug-in monitoring method further includes:

[0024] The target task execution end queries the target collection task information of the collection task data in the data storage end according to the identity identification information of the target task execution end.

[0025] In some embodiments, the plug-in monitoring method further includes:

[0026] The target task execution end determines the associated target script plug-in information according to the resource type.

[0027] In some embodiments, the plug-in monitoring method further includes:

[0028] The target task execution end determines the execution mode of the target script plug-in corresponding to the target script plug-in information according to the target acquisition task information;

[0029] The target task execution end executes the target script plug-in according to the execution mode to obtain the monitoring index corresponding to the target collection task information.

[0030] In some embodiments, the plug-in monitoring method further includes:

[0031] The data storage end monitors the directory data of each task execution end in real time, and stores the directory data accordingly.

[0032] In addition, to achieve the above-mentioned purpose, the present invention also proposes a terminal device, characterized in that the terminal device includes: a memory, a processor, and a plug-in monitoring program stored in the memory and executable on the processor, and the plug-in monitoring program is configured to implement the steps of the plug-in monitoring method described above.

[0033] The present invention proposes a terminal architecture of a task management end, a data storage end and at least one task execution end, and the data storage end is respectively connected to the task management end and each task execution end, and based on the architecture, script plug-in data and collection task data are synchronized to the data storage end through the task management end; the data storage end stores the script plug-in data and the collection task data; the task execution end obtains the collection task information and script plug-in information in the data storage end; the task execution end executes the target script plug-in according to the script plug-in information to obtain the monitoring index corresponding to the collection task information, thereby synchronizing the script plug-in data and the collection task data to the data storage end through the task management end, and assigning the corresponding target script plug-in to different collection tasks through the task execution end, so that the task execution end can be controlled to execute the target script plug-in, thereby completing the index monitoring of different collection task information, integrating the data transmission of different hosts or plug-ins through the data storage end, reducing the direct data transmission between the host and the plug-in, and avoiding the technical problem of low monitoring efficiency between hosts or plug-ins in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 This is a flow chart of a first embodiment of a plug-in monitoring method of the present invention;

[0035] Figure 2 This is a flow chart of a second embodiment of the plug-in monitoring method of the present invention;

[0036] Figure 3 A schematic diagram of the architecture of a terminal device according to an embodiment of a plug-in monitoring method of the present invention.

[0037] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0038] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not intended to limit the present invention.

[0039] The embodiment of the present invention provides a plug-in monitoring method, referring to Figure 1 , Figure 1 The figure is a flow chart of a first embodiment of a plug-in monitoring method of the present invention.

[0040] In this embodiment, the plug-in monitoring method includes the following steps:

[0041] Step S10: The task management end synchronizes the script plug-in data and the collected task data to the data storage end.

[0042] In this embodiment, the executor of this embodiment is a terminal device, wherein the terminal device has functions such as data processing, data communication and program running. The terminal device can be a computer terminal device or other network device, and of course it can also be other devices with similar functions, and this embodiment does not limit this.

[0043] It should be understood that different data acquisition plug-ins may use different interface protocols and data formats during operation. In traditional technology, the host is generally connected to multiple data acquisition plug-ins. After collecting data, the data acquisition plug-in will transmit the collected data to the host for data processing or data analysis. In this process, in order for the collected data to be transmitted smoothly, the host is generally required to support different interface protocols to avoid confusion in the format of the collected data or the inability to receive it. However, it is precisely because different plug-ins support different interface protocols that the host needs to maintain a higher protocol carrying capacity.

[0044] At the same time, as an external component of the host, the stability of the acquisition plug-in will directly affect the stability of data monitoring. If a plug-in fails or works abnormally, it may cause the monitoring data to be lost or distorted, thereby affecting the normal operation of the host. The plug-in itself will also be updated and replaced. If the host or component is updated and upgraded, in order to ensure that the plug-in can operate normally, the plug-in also needs to be updated and upgraded. However, the update and upgrade of the plug-in often lags behind and cannot be updated synchronously. This is also a problem existing in the prior art. In summary, in the prior art, various reasons will lead to low monitoring efficiency between hosts or plug-ins, which cannot meet the data monitoring needs of users.

[0045] Based on this, the present application proposes a terminal architecture of a task management end, a data storage end and at least one task execution end, and synchronizes the script plug-in data and the collection task data to the data storage end through the task management end, and assigns corresponding target script plug-ins to different collection tasks through the task execution end, so that the task execution end can be controlled to execute the target script plug-in, thereby completing the indicator monitoring of different collection task information, and integrating the data transmission of different hosts or plug-ins through the data storage end, reducing the direct data transmission between the host and the plug-in, eliminating the need for the host to carry a large number of interface protocols, and improving the data transmission efficiency between the host and the plug-in.

[0046] It can be understood that script plug-in data refers to the script plug-in information currently supported by the collection objects of each resource type, such as: script plug-in category, name, operating environment and operating parameters, etc., and collection task data refers to the resources of the collection task, the collection parameter configuration data corresponding to the resources, the specific execution end data for executing the collection task, etc. This embodiment does not impose specific restrictions on this.

[0047] In a specific implementation, the task management end may be a controller or control chip in a terminal device, the data storage end may be a memory or other non-volatile memory in a terminal device, and the task execution end may be a running memory in a terminal device, and its running memory stores a specific execution process for executing monitoring tasks, which is mainly used to obtain monitoring indicators corresponding to the collected task information.

[0048] Furthermore, the plug-in monitoring method further includes:

[0049] The task management terminal determines the resource type corresponding to the collection task object according to the collection task data;

[0050] The task management end associates a script plug-in according to the resource type, and the script plug-in is used to monitor at least one monitoring indicator of the collection task object.

[0051] Specifically, the collection task objects include but are not limited to databases, software programs, external terminal devices, etc. The resource types of each collection task object are different, and the indicators that need to be monitored are also different. For example: for a database, the monitoring indicators may be the database occupancy rate, remaining memory, and reading speed, etc. For a software program, the corresponding monitoring indicators may be the software program's operating cycle, operating status, etc. This embodiment does not impose specific restrictions on this.

[0052] It can be understood that different resource types of acquisition task objects can correspond to different plug-in methods. Therefore, in this embodiment, the acquisition script can be inserted through a variety of different plug-in methods, such as custom Python scripts, open source Promethus ePorter, etc. This embodiment does not impose specific restrictions on this.

[0053] Furthermore, the plug-in monitoring method further includes:

[0054] The task management terminal determines whether the monitoring indicators of the same collection task object are associated with multiple script plug-ins;

[0055] If the monitoring indicators of the same collection task object are associated with multiple script plug-ins, the task management end retains one script plug-in and removes the remaining associated script plug-ins.

[0056] In the specific implementation, one resource type is supported to connect to multiple different plug-ins. Each plug-in corresponds to a specific indicator. When there are multiple plug-ins monitoring the same indicator, the duplicate indicators can be filtered to reduce the data cache pressure and improve the data validity. At the same time, poor quality data can be eliminated according to the monitoring data of different plug-ins to improve data processing efficiency.

[0057] Step S20: The data storage terminal stores the script plug-in data and the acquisition task data.

[0058] It should be understood that the data storage end synchronizes the script plug-in data and collection task data generated by the task management end in real time, thereby improving the efficiency of driving the script plug-in and avoiding the impact of invalid or faulty script plug-ins. By synchronizing the collection task data in real time, the efficiency of obtaining monitoring data can be improved. Compared with the traditional technology of periodically obtaining monitoring data or running logs, it is more efficient, the terminal device has a higher utilization rate of monitoring data and a faster response.

[0059] Furthermore, the data storage end monitors the directory data of each task execution end in real time, and stores the directory data accordingly.

[0060] The data storage end also stores the monitoring data collected by each task execution end. Since the task execution end can execute multiple collection tasks, collect multiple indicators, etc., after the monitoring data is collected by the task execution end, it will be classified according to the collection tasks, resource category objects or indicators, etc. When storage is needed, the data storage end can monitor the directory data of each task execution end in real time, and store the directory data accordingly, so as to facilitate the subsequent data processing or data analysis process of the terminal device.

[0061] Step S30: the task execution end obtains the collection task information and script plug-in information in the data storage end.

[0062] Step S40: The task execution end executes the target script plug-in according to the script plug-in information to obtain the monitoring indicator corresponding to the collection task information.

[0063] In the specific implementation, a task execution end can only process one collection task at the same time. Therefore, when the task execution end needs to obtain the monitoring indicators corresponding to the collection task information, it can pre-acquire the specific collection task information and script plug-in information stored in the data storage end, so that it can associate the corresponding script plug-in and define the execution method of the script plug-in to improve the efficiency of information acquisition.

[0064] This embodiment synchronizes script plug-in data and collection task data to the data storage end through the task management end, and assigns corresponding target script plug-ins to different collection tasks through the task execution end, so that the task execution end can be controlled to execute the target script plug-in, thereby completing the indicator monitoring of different collection task information, and integrating the data transmission of different hosts or plug-ins through the data storage end, reducing the direct data transmission between the host and the plug-in, and avoiding the technical problem of low monitoring efficiency between hosts or plug-ins in the prior art.

[0065] refer to Figure 2 , Figure 2 This is a flow chart of a second embodiment of a plug-in monitoring method of the present invention.

[0066] Based on the above first embodiment, the plug-in monitoring method of this embodiment further includes:

[0067] Step S50: The task management end obtains parameter configuration information of the collection task and identity identification information of each task execution end.

[0068] Step S60: The task management terminal associates the parameter configuration information with the identity identification information to obtain collection task data.

[0069] It should be noted that when the task management end executes the collection task, in order to improve the collection efficiency and avoid the script plug-in being unable to associate with the resource object corresponding to the collection task, when determining the execution task of each task management end, the parameter configuration information and collection task data corresponding to the identity identification information can be obtained according to the identity identification information of each task management end, for example: Figure 3 , Figure 3There are two task execution ends. If the task execution end A-agent needs to be able to read the remaining memory in the database, the task management end can generate the collection task data of A-agent-database-remaining memory and store it in the data storage end. When each task execution end is polled, the task execution end A-agent can read the collection task data and read the remaining memory of the database. However, since the collection task data is limited to being executed by only the task execution end A-agent, the task execution end B-agent will not read the collection task data when polling.

[0070] The identity information may be a local address, a unique name, a unique number, or other identifiable code, data, or text of the task execution end, and this embodiment does not impose any specific limitation on this.

[0071] Furthermore, the plug-in monitoring method further includes:

[0072] Each task execution end periodically initiates polling to the data storage end, and when the polling is successful, establishes a communication connection between the data storage end and the target task execution end, the target task execution end being the task execution end that succeeds in the polling.

[0073] In a specific implementation, polling means that the task execution end initiates communication connection requests to the data storage end in turn. If the task execution end A-agent polls successfully, a communication connection can be established between the data storage end and the task execution end A-agent to perform data transmission. For the task execution end that fails to establish a communication connection, its operating status does not need to be considered in this embodiment.

[0074] Furthermore, the plug-in monitoring method further includes:

[0075] The target task execution end queries the target collection task information of the collection task data in the data storage end according to the identity identification information of the target task execution end.

[0076] After successfully establishing a communication connection between the target task execution end and the data storage end, the target task execution end can query the data storage end for information on each target collection task based on its own identity information, so as to facilitate subsequent execution of the corresponding collection task.

[0077] Furthermore, the plug-in monitoring method further includes:

[0078] The target task execution end determines the associated target script plug-in information according to the resource type.

[0079] It is understandable that due to the different categories of collection task objects, a target script plug-in corresponding to the collection task object is required so that the monitoring data can be collected normally.

[0080] Furthermore, the plug-in monitoring method further includes:

[0081] The target task execution end determines the execution mode of the target script plug-in corresponding to the target script plug-in information according to the target acquisition task information;

[0082] The target task execution end executes the target script plug-in according to the execution mode to obtain the monitoring index corresponding to the target collection task information.

[0083] In the specific implementation, the task execution end defines the execution mode of each collection plug-in according to the script plug-in and collection parameters assigned by its identity identification information, and then executes the collection script at a regular interval to obtain the monitored indicator information and upload it to the data storage end for subsequent terminal devices to read.

[0084] In this embodiment, the parameter configuration information of the collection task and the identity identification information of each task execution end are obtained through the task management end; the task management end associates the parameter configuration information and the identity identification information to obtain the collection task data, and obtains the collection task data and script plug-in corresponding to the corresponding identity identification information through the task execution end, thereby improving the efficiency of data acquisition and avoiding the generation of invalid monitoring data.

[0085] An embodiment of the present application also provides a terminal device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus, and the memory stores computer programs; when the processor executes the program stored in the memory, the above-mentioned plug-in monitoring method is implemented.

[0086] The communication bus mentioned in the above terminal device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0087] Communication interface: Communication between the above terminal devices and other devices.

[0088] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0089] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, and discrete hardware components.

[0090] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0091] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0092] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0093] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

[0094] It should be understood that the above is only an example and does not constitute any limitation on the technical solution of the present invention. In specific applications, technicians in this field can make settings as needed, and the present invention does not limit this.

[0095] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of the present invention. In practical applications, technicians in this field can select part or all of them according to actual needs to achieve the purpose of the present embodiment, and no limitation is made here.

[0096] In addition, for technical details not fully described in this embodiment, reference can be made to the plug-in monitoring method provided in any embodiment of the present invention, and will not be repeated here.

[0097] In addition, it should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0098] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0099] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory (ROM) / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0100] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

[0101] It is understandable that the system provided by the embodiment of the present invention corresponds to the method provided by the embodiment of the present invention, and the explanation, examples and beneficial effects of the relevant contents can refer to the corresponding parts in the above method.

Claims

1. A plug-in monitoring method, characterized in that: The plug-in monitoring method is applied to a terminal device, wherein the terminal device includes a task management end, a data storage end and at least one task execution end, and the data storage end is respectively connected to the task management end and each task execution end; The plug-in monitoring method comprises: The task management end synchronizes script plug-in data and collects task data to the data storage end; The data storage terminal stores the script plug-in data and the acquisition task data; The task execution end obtains the collection task data and script plug-in information in the data storage end; The task execution end executes the target script plug-in associated with the collection task data according to the script plug-in information to obtain the monitoring indicator corresponding to the collection task data.

2. The method according to claim 1, characterized in that The plug-in monitoring method further includes: The task management terminal determines the resource type corresponding to the collection task object according to the collection task data; The task management end associates a target script plug-in according to the resource type, and executes the target script plug-in based on the script plug-in information, wherein the target script plug-in monitors at least one monitoring indicator of the acquisition task object.

3. The method according to claim 2, characterized in that The plug-in monitoring method further includes: The task management terminal determines whether the monitoring indicators of the same collection task object are associated with multiple script plug-ins; If the monitoring indicators of the same collection task object are associated with multiple script plug-ins, the task management end retains one script plug-in and removes the remaining associated script plug-ins.

4. The method according to claim 1, characterized in that The plug-in monitoring method further includes: The task management end obtains parameter configuration information of the collection task and identity identification information of each task execution end; The task management end associates the parameter configuration information with the identity identification information to obtain collection task data.

5. The method according to claim 4, characterized in that The plug-in monitoring method further includes: Each task execution end periodically initiates polling to the data storage end, and when the polling is successful, establishes a communication connection between the data storage end and the target task execution end, the target task execution end being the task execution end that succeeds in the polling.

6. The method according to claim 5, characterized in that The plug-in monitoring method further includes: The target task execution end queries the target collection task information of the collection task data in the data storage end according to the identity identification information of the target task execution end.

7. The method according to claim 6, characterized in that The plug-in monitoring method further includes: The target task execution end determines the associated target script plug-in information according to the resource type.

8. The method according to claim 7, characterized in that The plug-in monitoring method further includes: The target task execution end determines the execution mode of the target script plug-in corresponding to the target script plug-in information according to the target acquisition task information; The target task execution end executes the target script plug-in according to the execution mode to obtain the monitoring index corresponding to the target collection task information.

9. The method according to claim 1, characterized in that The plug-in monitoring method further includes: The data storage end monitors the directory data of each task execution end in real time, and stores the directory data accordingly.

10. A terminal device, characterized in that: The terminal device comprises: a memory, a processor, and a plug-in monitoring program stored in the memory and executable on the processor, wherein the plug-in monitoring program is configured to implement the steps of the plug-in monitoring method according to any one of claims 1 to 9.

Images