CN108932184B - Monitoring device and method - Google Patents
Monitoring device and method Download PDFInfo
- Publication number
- CN108932184B CN108932184B CN201810646655.4A CN201810646655A CN108932184B CN 108932184 B CN108932184 B CN 108932184B CN 201810646655 A CN201810646655 A CN 201810646655A CN 108932184 B CN108932184 B CN 108932184B
- Authority
- CN
- China
- Prior art keywords
- monitoring
- data
- module
- collection
- identifier
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
Landscapes
- Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Mathematical Physics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention relates to the technical field of monitoring, and provides a monitoring device and a monitoring method, which are applied to monitoring equipment, wherein the monitoring device comprises a management module and a collection module, and the management module is communicated with the collection module; the management module is used for acquiring a monitoring task configuration file, generating a data collection request according to the monitoring task configuration file and sending the data collection request to the collection module, wherein the data collection request comprises a monitoring identifier; the collection module is used for acquiring monitoring data of a target monitoring object corresponding to the monitoring identification by using a preset remote management protocol according to the data collection request, and sending the monitoring data to the management module. Compared with the prior art, the embodiment of the invention does not need to deploy agent on the monitored object, thereby reducing the information security risk and the influence on the monitored object, and effectively saving manpower and time during large-scale monitoring.
Description
Technical Field
The embodiment of the invention relates to the technical field of monitoring, in particular to a monitoring device and a monitoring method.
Background
With the continuous development of cloud computing and big data technologies, the IT management requirements of enterprises are changing. The continuous expansion of monitoring scale, the continuous increase of monitoring object types and huge monitoring data volume put higher requirements on the performance of the monitoring system.
Currently, monitoring of monitoring objects is realized by common open source monitoring software, for example, Zabbix, the supported monitoring modes include agent, SNMP, IPMI, and JMX, the agent mode is the most common monitoring mode of Zabbix, an agent program is installed at a monitored end, and the Zabbix server end communicates with the agent program to collect monitoring data of all monitoring objects. However, the agent mode has poor safety, affects the operation of the monitored object, and has information safety risk, and meanwhile, due to high deployment difficulty, a large amount of labor and time are needed to be spent in large-scale monitoring.
Disclosure of Invention
An embodiment of the present invention is directed to a monitoring apparatus and method for improving the above problem.
In order to achieve the above purpose, the embodiment of the present invention adopts the following technical solutions:
in a first aspect, an embodiment of the present invention provides a monitoring apparatus, where the monitoring apparatus includes a management module and a collection module, where the management module is in communication with the collection module; the management module is used for acquiring a monitoring task configuration file, generating a data collection request according to the monitoring task configuration file and sending the data collection request to the collection module, wherein the data collection request comprises a monitoring identifier; the collection module is used for acquiring the monitoring data of the target monitoring object corresponding to the monitoring identification by using a preset remote management protocol according to the data collection request and sending the monitoring data to the management module.
In a second aspect, an embodiment of the present invention further provides a monitoring method, where the method includes: acquiring a monitoring task configuration file, and generating a data collection request according to the monitoring task configuration file, wherein the data collection request comprises a monitoring identifier; and acquiring the monitoring data of the target monitoring object corresponding to the monitoring identification by using a preset remote management protocol according to the data collection request.
Compared with the prior art, the monitoring device and the monitoring method provided by the embodiment of the invention have the advantages that when a monitored object needs to be monitored, firstly, the management module generates a data collection request according to the monitoring configuration file and sends the data collection request to the collection module; then, the collection module acquires the monitoring data of the target monitoring object by using a preset remote management protocol according to the data collection request and sends the monitoring data as a response to the management module. Compared with the prior art, the embodiment of the invention does not need to deploy agent on the monitored object, thereby reducing the information security risk and the influence on the monitored object, and effectively saving manpower and time during large-scale monitoring.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 shows a first block diagram of a monitoring device according to an embodiment of the present invention.
Fig. 2 shows a flow chart of a monitoring method provided by the embodiment of the invention.
Fig. 3 shows a second block diagram of the monitoring device according to the embodiment of the present invention.
Fig. 4 is a block diagram of a monitoring apparatus provided in an embodiment of the present invention.
An icon: 20-a monitoring device; 21-a first information database; 22-a second information database; 301-a management module; 302-a collection module; 40-monitoring the object; 201-a processor; 202-a memory; 203-bus; 204-a communication interface; 300-monitoring device.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Referring to fig. 1, fig. 1 is a block diagram illustrating a monitoring device 20 according to an embodiment of the present invention. The monitoring device 20 may be implemented in a cloud computing environment, which may be a mainframe, a single server, or a cluster of servers, such as physical servers, cloud servers, and the like. The monitoring device 20 may be configured with a first information database 21 and a second information database 22, the first information database 21 may be a relational database, e.g. MySQL database, oracle database, etc., and the second information database 22 may be a time series database, e.g. infiluxdb database, OpenTSDB database, etc.
In the embodiment of the present invention, the management module 301 and the collection module 302 may be pre-established on the monitoring device 20, and the management module 301 and the collection module 302 may be configured on the same monitoring device 20 or on different monitoring devices 20.
In the embodiment of the present invention, the management module 301 communicates with the second information database 22, the collection module 302 communicates with the first information database 21, the first information database 21 stores object information and object identifiers of a plurality of monitored objects 40, and the second information database 22 stores monitoring index data of the monitored objects 40.
The first information database 21 and the second information database 22 are not limited to be disposed on the monitoring device 20, and the monitoring device 20 is not limited to be disposed on the monitoring device 20 as long as the management module 301 can communicate with the second information database 22 and the collection module 302 can communicate with the first information database 21.
In the embodiment of the present invention, the monitoring device 20 communicates with at least one monitoring object 40, and may monitor all of the at least one monitoring object 40, where the monitoring object 40 may be a physical server, a host, or the like, or may also be an operating system, a virtual machine, a database, a network device, a middleware, or the like. Specifically, the management module 301 is in communication with the collection module 302, and the collection module 302 is in communication with each of the at least one monitoring object 40. The management module 301 is configured to manage the monitoring task, that is, the management module 301 sends a data collection request to the collection module 302 according to the monitoring task; the collecting module 302 is configured to collect monitoring data, after receiving the data collection request sent by the managing module 301, the collecting module 302 obtains object information of the target monitoring object from the first information database 21 according to the data collection request, and connects to the target monitoring object by using the object information to obtain monitoring data of the target monitoring object, and sends the monitoring data to the managing module 301 as a response to the data collection request, and the managing module 301 generates monitoring index data according to the monitoring data and stores the monitoring index data in the second information database 22. First, the
One embodiment of the invention
Referring to fig. 2, fig. 2 is a flowchart illustrating a monitoring method according to an embodiment of the present invention. The monitoring method comprises the following steps:
step S101, acquiring a monitoring task configuration file, and generating a data collection request according to the monitoring task configuration file, wherein the data collection request comprises a monitoring identifier.
In this embodiment of the present invention, the management module 301 may obtain a monitoring task configuration file, and generate a data collection request according to the monitoring task configuration file, where the monitoring task configuration file may be written by a user in advance according to a monitoring task to be monitored and stored in the monitoring device 20. The monitoring task configuration file may be a configuration file in a yaml format, which includes a plurality of monitoring tasks, each of which includes a monitoring object type and a monitoring identifier, and further includes a monitoring data acquisition interval time and a monitoring data acquisition timeout time, for example, the monitoring configuration file may be:
the monitoring configuration file includes 2 monitoring tasks, where uuid represents a monitoring identifier, and the monitoring identifier is a unique identifier of the monitored object 40; the exporter-endpoint represents a service endpoint of the collection module 302, which may characterize the type of the monitoring object 40, and the type of the monitoring object 40 may include an operating system, a virtual machine, a database, a network device, middleware, and the like; the script _ interval represents the monitoring data acquisition interval time, and the script _ timeout represents the monitoring data acquisition timeout time; params denotes the parameter list of the http request, and the above example shows that the http request has a parameter target with the same value as uuid.
In an embodiment of the present invention, a method for generating a data collection request according to a monitoring profile may include:
firstly, the management module 301 obtains a plurality of monitoring tasks included in a monitoring task configuration file, wherein each monitoring task includes a monitoring object type and a monitoring identifier, and each monitoring task is run by a thread;
then, the management module 301 generates a data collection request corresponding to each monitoring task according to the monitoring object type and the monitoring identifier of each monitoring task, that is, the data collection request corresponding to each monitoring task may include one monitoring object type and one monitoring identifier. Each thread running the monitoring task periodically sends a data collection request to the collection module 302 according to the monitoring data collection interval time in the monitoring task, waits for the response of the collection module 302 within the monitoring data collection timeout time, and extracts the monitoring data from the response message.
In the embodiment of the present invention, after the management module 301 generates the data collection request according to the monitoring task configuration file, the data collection request is sent to the collection module 302 according to the type of the monitoring object. There may be a plurality of collection modules 302, and each collection module 302 is in communication with the management module 301, and each collection module 302 is preset with a monitoring object type identifier to represent communication with a type of monitoring object 40, where one monitoring object type identifier corresponds to one monitoring object type. That is, when there are a plurality of collection modules 302, one collection module 302 is used to collect monitoring data of one type of monitoring object 40, for example, if a user wants to monitor both a Linux operating system and a network device, two collectors need to be run, each of which implements collection of the monitoring data with different data collection logic.
In the embodiment of the present invention, the management module 301 sends the data collection request to the collection module 302 according to the corresponding relationship between the monitored object type and the monitored object type identifier, for example, if the monitored object type included in the data collection request is a virtual machine, the management module 301 sends the data collection request to the collection module 302 whose monitored type identifier is a virtual machine; if the monitoring object type included in the data collection request is an operating system, the management module 301 sends the data collection request to the collection module 302 whose monitoring type is identified as an operating system.
And step S102, acquiring the monitoring data of the target monitoring object corresponding to the monitoring identification by using a preset remote management protocol according to the data collection request.
In the embodiment of the present invention, after receiving the data collection request sent by the management module 301, the collection module 302 obtains the monitoring data of the target monitoring object corresponding to the monitoring identifier by using a preset remote management protocol according to the data collection request, and sends the monitoring data to the management module 301 as a response to the data collection request. The preset remote Management Protocol may be, but is not limited to, SSH (Secure Shell), SNMP (Simple Network Management Protocol), HTTP (HyperText Transfer Protocol), and the like. For example, the Linux operating system collection module is connected to the Linux operating system by using an SSH protocol, and executes a Linux operating system command; the network equipment collecting module is connected to the network equipment by using an SNMP protocol and executes the SNMP WALK/GET operation; and the virtualization collection module calls an HTTP API of the virtualization platform to acquire the monitoring data.
In the embodiment of the present invention, since the collection module 302 can obtain the monitoring data of the monitored object 40 by using the preset remote management protocol, it is not necessary to deploy the collection module 302 as an agent in the monitored object 40.
In an embodiment of the present invention, the method for the collection module 302 to collect monitoring data according to the data collection request may include: first, the collection module 302 queries a target object identifier consistent with the monitoring identifier from a plurality of object identifiers stored in the first information database 21 according to the data collection request; then, the collection module 302 obtains object information corresponding to the target object identifier from the first information database 21; finally, the collection module 302 connects to the target monitoring object according to a preset remote management protocol by using the object information to obtain the monitoring data of the target monitoring object.
The first information database 21 may be a relational database, for example, a MySQL database, an oracle database, and the like, and the first information database 21 stores a monitoring object information recording table, where monitoring object information of a plurality of monitoring objects 40 is recorded in the monitoring object recording table, each piece of monitoring object information includes object information and an object identifier, the object information is a unique identifier for representing the monitoring object 40, and the object information includes basic information required for connecting to the monitoring object 40, for example, an IP (Internet Protocol, network Protocol), a user name, a password, and the like. For example, the format of the monitoring object information recording table is shown in table 1 below:
table 1 monitored object information recording table
Wherein, the uuid field is a main key, which is used to store the object identifier of the monitored object 40, and needs to be consistent with the monitoring identifier in the monitoring task configuration file; the monitor _ info is used to store object information of the monitored object 40, which is a JSON-formatted character string containing basic information required to connect to the monitored object 40, such as IP, user name, password, and the like.
In this embodiment of the present invention, the collection module 302 may be a network server, and after receiving the data collection request sent by the management module 301, extract the monitoring identifier of the target monitoring object from the data collection request, then query the object information of the target monitoring object from the first information database 21 according to the monitoring identifier, connect the monitoring information to the target monitoring object to obtain the monitoring data, and finally send the monitoring data to the management module 301 as a response to the data collection request. The function of acquiring the monitoring data by the collection module 302 is implemented by an interface, so that the user can support monitoring of various types of monitoring objects 40 by implementing the interface according to the monitoring requirement. Assuming that there are two collection modules 302 currently, one collection module 302 is used to monitor the Linux operating system, and the other collection module 302 is used to monitor the network device, each collection module 302 has different data collection logic, if a user needs to increase monitoring of a virtualized resource (e.g., a virtual machine), the virtualized collection module can be obtained only by implementing the virtualized data collection logic, then the virtualized collection module is run, configuration of the virtualized resource is added in a monitored object configuration file, and the type of the monitored object in the monitored object configuration file (e.g., the service endpoint extender-endpoint of the collection module 302 in the example of the monitored configuration file in step S101) is configured as the virtualized resource to be monitored.
In the embodiment of the present invention, after receiving the monitoring data sent by the collecting module 302, the managing module 301 may generate monitoring index data according to a preset data structure according to the monitoring data, so as to facilitate user query, so that the embodiment of the present invention further includes step S103.
And step S103, generating monitoring index data according to the monitoring data and a preset data structure, and storing the monitoring index data in a second information database.
In the embodiment of the present invention, after receiving the monitoring data sent by the collecting module 302, the managing module 301 generates monitoring index data according to a preset data structure according to the monitoring data and stores the monitoring index data in the second information database 22. The monitoring data sent by the collection module 302 to the management module 301 includes index data and metadata of the target monitoring object, where the metadata may be a monitoring index of the target monitoring object, the index data may be a numerical value of the monitoring index of the target monitoring object, and the monitoring index is related to a specific service of the target monitoring object, for example, the monitoring index of the operating system may be a CPU usage rate, a memory usage rate, a disk IO usage rate, a network port rate, and the like. For example, the monitoring index of a certain monitoring object 40 is the total number of monitoring http requests, the http requests may be classified into GET, PUT, POST, DELETE, and the like according to the method, and in addition, the http requests also have corresponding status codes, so that both the http requests and the status codes belong to metadata, and the metadata has significance for analyzing the monitoring data from different dimensions. Assuming that the monitoring index is the http request number, the obtained monitoring data is as follows: and the number of GET requests of http is 100, the metadata is the http request method GET, and the index data is the number of GET requests, namely 100.
In this embodiment, the monitoring index data includes a data name, index data, metadata, and a timestamp, where the data name represents the meaning of the monitoring index data and can uniquely represent the monitoring index data, and the data name can be generated according to the monitoring data or flexibly set by a user according to the needs of the user; metadata may be a collection of key-value pairs, where keys are fixed and values are varied; the index data can be a numerical value of a monitoring index, and when the metadata is determined, the index data is also uniquely determined; the time stamp may be a time when the management module 301 receives the monitoring data of the target monitoring object. The monitoring index data may be represented in JSON format, for example, one piece of monitoring index data is:
where, metric represents the data name, labels represents the metadata, which labels contains two key-value pairs: "method": GET "and" code ": 200", value denotes index data, and timestamp denotes a time stamp.
In an embodiment of the present invention, a method for generating monitoring index data may include: firstly, generating a data name according to monitoring data; then, the time stamp when the management module 301 acquires the monitoring data of the target monitoring object is read; finally, monitoring index data is generated according to the data name, the index data, the metadata and the timestamp and stored in the second information database 22.
The second information database 22 may be a time-series database, such as an infiluxdb database, an OpenTSDB database, and the like, where the second information database 22 stores monitoring index data, each monitoring index data is stored in a data table, and a table name of the data table is a data name of the monitoring index data, and for example, a structure of the data table is as shown in table 2 below:
table 2 monitoring index data storage table
| Time stamp | uuid | Metadata key-value pair 1 | Metadata key-value pair 2 … | Index data |
The time stamp columns arrange data according to a time sequence, the number and the name of the metadata key-value pair columns are not fixed and are related to specific monitoring indexes, and indexes are built in the uuid columns and the metadata key-value pair columns.
In this embodiment of the present invention, the management module 301 further includes a data read-write interface, and after the management module 301 generates the monitoring index data, the monitoring index data is sent to the data read-write interface, and the data read-write interface can read and write the second information database 22. Specifically, the data read-write interface and the second information database 22 may use SQL statements for reading and writing, and encapsulate query statements, and the user may use the query statements to query the monitoring index data in the second information database 22, where the format of the query statements may be: data name { metadata 1 name ═ value of metadata 1, metadata 2 name ═ value of metadata 2 "… }, each of which is a filtering condition, and a user can query monitoring index data from different dimensions by setting different metadata combinations.
In the embodiment of the present invention, the management module 301, the collection module 302, the first information database 21, and the second information database 22 all operate in a docker container manner. When there are multiple collection modules 302, each container runs one collection module 302, each collection module 302 is responsible for monitoring one type of monitoring object 40, and the processes of each collection module 302 are completely independent. In addition, the monitoring device 20 in the embodiment of the present invention needs to install a docker environment and a container management tool, for example, kubernets, and the monitoring device 20 may be a single server or a server cluster. By realizing containerization of the management module 301, the collection module 302, the first information database 21 and the second information database 22, expandability is enhanced, deployment is facilitated, and cluster deployment is supported.
Compared with the prior art, the embodiment of the invention has the following beneficial effects:
first, the collection module 302 in the embodiment of the present invention only needs to be deployed on the monitoring device 20, so that the information security risk is reduced, the influence on the monitored object 40 is reduced, and a large amount of agents do not need to be deployed on the monitored object 40 during large-scale monitoring, thereby saving labor and time.
Secondly, because the low coupling is adopted between the collection modules 302 and the management module 301, and the isolation of the running environment is realized through containerization, the expandability is greatly enhanced, when the types of the monitoring objects need to be increased, new collection modules 302 can be added, and the monitoring of the monitoring objects 40 of any type can be supported.
Thirdly, a new data structure and a data storage mode are designed for monitoring index data, and efficient multidimensional data query operation can be supported for a user.
Finally, when the cluster is deployed, the container management tool can reasonably schedule the containers according to the load condition, and each container can be located on different nodes, so that the resource use of a single monitoring device 20 is reduced, and the performance is improved.
Second embodiment
Referring to fig. 3, fig. 3 is a block diagram illustrating a monitoring device 20 according to an embodiment of the present invention. The monitoring device 20 comprises a processor 201, a memory 202, a bus 203 and a communication interface 204, wherein the processor 201, the memory 202 and the communication interface 204 are connected through the bus 203; the processor 201 is used to execute executable modules, such as computer programs, stored in the memory 202.
The Memory 202 may include a high-speed Random Access Memory (RAM) and may further include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the monitoring server 20 and the monitored end is realized through at least one communication interface 204 (which may be wired or wireless).
The memory 202 is used for storing a program, such as the monitoring apparatus 300 shown in fig. 4. The monitoring apparatus 300 includes at least one software function module which may be stored in the memory 202 in the form of software or firmware (firmware) or fixed in an Operating System (OS) of the monitoring device 20. After receiving the execution instruction, the processor 201 executes the program to implement the monitoring method disclosed in the above embodiment of the present invention.
The processor 201 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 201. The Processor 201 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components.
The embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by the processor 201, implements the monitoring method disclosed in the above embodiment.
Third embodiment
Referring to fig. 4, fig. 4 is a block diagram illustrating a monitoring apparatus 300 according to an embodiment of the present invention. The monitoring apparatus 300 includes a management module 301 and a collection module 302.
The management module 301 is configured to obtain a monitoring task configuration file, generate a data collection request according to the monitoring task configuration file, and send the data collection request to the collection module, where the data collection request includes a monitoring identifier.
In the embodiment of the present invention, the manner of generating the data collection request according to the monitoring task configuration file by the management module 301 includes: acquiring a plurality of monitoring tasks contained in a monitoring task configuration file, wherein each monitoring task comprises a monitoring object type and a monitoring identifier; and generating a data collection request corresponding to each monitoring task according to the monitoring object type and the monitoring identification of each monitoring task.
In the embodiment of the present invention, there are multiple collection modules 302, and each collection module 302 is in communication with a management module, the data collection request further includes a monitoring object type, each collection module 302 presets a monitoring object type identifier to represent communication with a type of monitoring object, where one monitoring object type identifier corresponds to one monitoring object type; the management module 301 performs the manner of sending data collection requests to the collection module, including: and sending the data collection request to a collection module according to the corresponding relation between the type of the monitoring object and the type identifier of the monitoring object.
The collecting module 302 is configured to obtain monitoring data of the target monitoring object corresponding to the monitoring identifier by using a preset remote management protocol according to the data collecting request, and send the monitoring data to the management module.
In this embodiment of the present invention, the monitoring device 20 includes a first information database 21, the collecting module 302 communicates with the first information database 21, and the manner that the collecting module 302 executes to obtain the monitoring data of the target monitoring object corresponding to the monitoring identifier by using a preset remote management protocol according to the data collecting request includes: according to the data collection request, inquiring a target object identifier consistent with the monitoring identifier from the plurality of object identifiers; acquiring object information corresponding to the target object identifier from a first information database; and connecting the object information to the target monitoring object according to a preset remote management protocol to acquire the monitoring data of the target monitoring object.
The monitoring device 20 further comprises a second information database 22, the management module 301 being in communication with the second information database 22. The management module 301 is further configured to generate monitoring index data according to the monitoring data and a preset data structure, and store the monitoring index data.
In the embodiment of the present invention, the monitoring data includes index data and metadata of the target monitoring object, and the method for generating and storing the monitoring index data according to the monitoring data and the preset data structure performed by the management module 301 includes: generating a data name according to the monitoring data; reading a timestamp when the management module acquires monitoring data of a target monitoring object; and generating monitoring index data according to the data name, the index data, the metadata and the timestamp and storing the monitoring index data in a second information database.
In summary, the monitoring apparatus and method provided in the embodiments of the present invention are applied to a monitoring device, where the monitoring apparatus includes a management module and a collection module, and the management module is in communication with the collection module; the management module is used for acquiring a monitoring task configuration file, generating a data collection request according to the monitoring task configuration file and sending the data collection request to the collection module, wherein the data collection request comprises a monitoring identifier; the collecting module is used for acquiring monitoring data of a target monitoring object corresponding to the monitoring identification by using a preset remote management protocol according to the data collecting request and sending the monitoring data to the management module. Compared with the prior art, the embodiment of the invention does not need to deploy agent on the monitored object, thereby reducing the information security risk and the influence on the monitored object, and effectively saving manpower and time during large-scale monitoring.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, 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 invention. 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.
In addition, the functional modules in the embodiments of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Claims (7)
1. A monitoring device is applied to monitoring equipment and comprises a management module and a plurality of collection modules, wherein the management module is communicated with each collection module; each collection module is communicated with a first information database, and object information and object identifiers of a plurality of monitored objects are stored in the first information database in advance; each collection module is preset with a monitoring object type identifier to represent communication with a type of monitoring object, wherein one monitoring object type identifier corresponds to one monitoring object type;
the management module is used for acquiring a monitoring task configuration file, generating a data collection request according to the monitoring task configuration file, and sending the data collection request to the collection module according to the corresponding relation between the type of the monitored object and the type identifier of the monitored object, wherein the monitoring task configuration file comprises a plurality of monitoring tasks, each monitoring task comprises a monitoring identifier and a type of the monitored object, and the data collection request comprises the monitoring identifier and the type of the monitored object;
the collection module is configured to:
according to the data collection request, inquiring a target object identifier consistent with the monitoring identifier from a plurality of object identifiers;
acquiring object information corresponding to the target object identifier from the first information database;
connecting the object information to a target monitoring object according to a preset remote management protocol to acquire monitoring data of the target monitoring object and sending the monitoring data to the management module;
the management module, each collection module and the first information database are operated in a container mode, each container operates one collection module, each collection module is responsible for monitoring one type of monitoring object, and the processes of each collection module are independent.
2. The apparatus of claim 1, wherein the management module performs the manner of generating a data collection request based on the monitoring task profile, comprising:
acquiring a plurality of monitoring tasks contained in the monitoring task configuration file, wherein each monitoring task comprises a monitoring object type and a monitoring identifier;
and generating a data collection request corresponding to each monitoring task according to the monitoring object type and the monitoring identification of each monitoring task.
3. The apparatus of claim 1, wherein the management module is in communication with a second information database; and the management module is also used for generating monitoring index data according to the monitoring data and a preset data structure and storing the monitoring index data to the second information database.
4. The apparatus according to claim 3, wherein the monitoring data includes index data and metadata of the target monitoring object, and the manner in which the management module executes to generate monitoring index data according to a preset data structure and store the monitoring index data in the second information database according to the monitoring data includes:
generating a data name according to the monitoring data;
reading a timestamp when the management module acquires the monitoring data of the target monitoring object;
and generating the monitoring index data according to the data name, the index data, the metadata and the timestamp and storing the monitoring index data in the second information database.
5. A monitoring method is characterized in that the monitoring method is applied to a monitoring device of monitoring equipment, the monitoring device comprises a management module and a plurality of collection modules, and the management module is communicated with each collection module; each collection module is communicated with a first information database, and object information and object identifiers of a plurality of monitored objects are stored in the first information database in advance; each collection module is preset with a monitoring object type identifier to represent communication with a type of monitoring object, wherein one monitoring object type identifier corresponds to one monitoring object type; the method comprises the following steps:
the management module acquires a monitoring task configuration file, generates a data collection request according to the monitoring task configuration file, and sends the data collection request to the collection module according to the corresponding relation between the type of the monitored object and the type identifier of the monitored object, wherein the monitoring task configuration file comprises a plurality of monitoring tasks, each monitoring task comprises a monitoring identifier and a type of the monitored object, and the data collection request comprises the monitoring identifier and the type of the monitored object;
the collecting module queries a target object identifier consistent with the monitoring identifier from a plurality of object identifiers according to the data collecting request;
the collection module acquires object information corresponding to the target object identifier from the first information database;
the collection module is connected to a target monitoring object according to a preset remote management protocol by using the object information to acquire monitoring data of the target monitoring object;
the management module, each collection module and the first information database are operated in a container mode, each container operates one collection module, each collection module is responsible for monitoring one type of monitoring object, and the processes of each collection module are independent.
6. The method of claim 5, wherein the generating a data collection request based on the monitoring task profile comprises:
acquiring a plurality of monitoring tasks contained in the monitoring task configuration file, wherein each monitoring task comprises a monitoring object type and a monitoring identifier;
and generating a data collection request corresponding to each monitoring task according to the monitoring object type and the monitoring identification of each monitoring task.
7. The method of claim 5, wherein the monitoring device is in communication with a second information database; the method further comprises the following steps:
and generating monitoring index data according to the monitoring data and a preset data structure and storing the monitoring index data to the second information database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810646655.4A CN108932184B (en) | 2018-06-21 | 2018-06-21 | Monitoring device and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810646655.4A CN108932184B (en) | 2018-06-21 | 2018-06-21 | Monitoring device and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108932184A CN108932184A (en) | 2018-12-04 |
| CN108932184B true CN108932184B (en) | 2022-05-17 |
Family
ID=64446228
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810646655.4A Active CN108932184B (en) | 2018-06-21 | 2018-06-21 | Monitoring device and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108932184B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109582547A (en) * | 2018-12-11 | 2019-04-05 | 平安科技（深圳）有限公司 | Electronic device, monitoring data alarm method and storage medium |
| CN109871815B (en) * | 2019-02-26 | 2021-07-20 | 新华三技术有限公司 | Method and device for inquiring monitoring information |
| CN112152824B (en) * | 2019-06-26 | 2023-07-11 | 北京神州泰岳软件股份有限公司 | Performance index data acquisition method and device |
| CN111694854B (en) * | 2020-06-05 | 2023-07-21 | 北京百度网讯科技有限公司 | Regional access monitoring method and device, electronic equipment and storage medium |
| CN113941901B (en) * | 2020-07-17 | 2024-04-23 | 智能云科信息科技有限公司 | Machine tool cutter monitoring method, machine tool cutter monitoring device and electronic equipment |
| CN112199249A (en) * | 2020-09-16 | 2021-01-08 | 中国建设银行股份有限公司 | Monitoring data processing method, device, equipment and medium |
| CN112181785B (en) * | 2020-10-21 | 2023-02-24 | 鹏城实验室 | Method, terminal and storage medium for automatically adding monitoring equipment |
| CN113010372A (en) * | 2020-12-08 | 2021-06-22 | 云智慧（北京）科技有限公司 | Distributed implementation method and system for API monitoring |
| CN112596986A (en) * | 2020-12-31 | 2021-04-02 | 恩亿科(北京)数据科技有限公司 | Monitoring method and device |
| CN114253808A (en) * | 2021-12-21 | 2022-03-29 | 奇安信科技集团股份有限公司 | Object state monitoring method and device |
| CN116170341B (en) * | 2022-12-23 | 2024-04-09 | 中国联合网络通信集团有限公司 | Virtualization platform monitoring method, device, system and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103516555A (en) * | 2013-10-23 | 2014-01-15 | 中国科学院信息工程研究所 | Network device monitoring method and system |
| CN105095044A (en) * | 2015-06-04 | 2015-11-25 | 曙光信息产业(北京)有限公司 | SNMP based server monitoring method and apparatus |
| CN107959588A (en) * | 2017-12-07 | 2018-04-24 | 郑州云海信息技术有限公司 | Cloud resource management method, cloud resource management platform and the management system of data center |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9912522B2 (en) * | 2015-04-29 | 2018-03-06 | Cisco Technology, Inc. | Automatic task tracking |
-
2018
- 2018-06-21 CN CN201810646655.4A patent/CN108932184B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103516555A (en) * | 2013-10-23 | 2014-01-15 | 中国科学院信息工程研究所 | Network device monitoring method and system |
| CN105095044A (en) * | 2015-06-04 | 2015-11-25 | 曙光信息产业(北京)有限公司 | SNMP based server monitoring method and apparatus |
| CN107959588A (en) * | 2017-12-07 | 2018-04-24 | 郑州云海信息技术有限公司 | Cloud resource management method, cloud resource management platform and the management system of data center |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108932184A (en) | 2018-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108932184B (en) | Monitoring device and method | |
| US20180060132A1 (en) | Stateful resource pool management for job execution | |
| CN110650038B (en) | Security event log collecting and processing method and system for multiple classes of supervision objects | |
| CN109918349B (en) | Log processing method, log processing device, storage medium and electronic device | |
| CN107544832B (en) | Method, device and system for monitoring process of virtual machine | |
| US10860604B1 (en) | Scalable tracking for database udpates according to a secondary index | |
| US10019679B2 (en) | Management apparatus and management method of information processing apparatus | |
| JP2021515330A (en) | Data retention handling for data object stores | |
| JP6633642B2 (en) | Method and device for processing data blocks in a distributed database | |
| CN107844274B (en) | Hardware resource management method, device and terminal based on super-fusion storage system | |
| CN103488793A (en) | User behavior monitoring method based on information retrieval | |
| CN113468019A (en) | Hbase-based index monitoring method, device, equipment and storage medium | |
| CN112306700A (en) | Abnormal RPC request diagnosis method and device | |
| CN114143171B (en) | Alarm root cause positioning method and system based on TR069 protocol | |
| WO2015139565A1 (en) | Heterogeneous logging system management configuration | |
| CN107515807B (en) | Method and device for storing monitoring data | |
| US11599510B2 (en) | Methods, systems, and computer readable mediums for performing metadata-driven data collection | |
| US11805338B2 (en) | Systems and methods for enabling smart network interface card as an advanced telemetry appliance | |
| CN107515864B (en) | Method and equipment for monitoring workflow | |
| JP2013171542A (en) | Performance analysis device, method for analyzing performance, and performance analysis program | |
| CN112579406B (en) | Log call chain generation method and device | |
| CN114860432A (en) | Method and device for determining information of memory fault | |
| CN111078975B (en) | Multi-node incremental data acquisition system and acquisition method | |
| US11836125B1 (en) | Scalable database dependency monitoring and visualization system | |
| JP7006077B2 (en) | Management system, management method, and management program |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |