CN116541250A - Monitoring method and electronic equipment - Google Patents
Monitoring method and electronic equipment Download PDFInfo
- Publication number
- CN116541250A CN116541250A CN202310723812.8A CN202310723812A CN116541250A CN 116541250 A CN116541250 A CN 116541250A CN 202310723812 A CN202310723812 A CN 202310723812A CN 116541250 A CN116541250 A CN 116541250A
- Authority
- CN
- China
- Prior art keywords
- monitoring
- data acquisition
- information
- acquisition component
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 410
- 238000000034 method Methods 0.000 title claims abstract description 72
- 238000012423 maintenance Methods 0.000 abstract description 7
- 238000013480 data collection Methods 0.000 description 30
- 238000004891 communication Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013528 artificial neural network Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- FASDKYOPVNHBLU-ZETCQYMHSA-N pramipexole Chemical compound C1[C@@H](NCCC)CCC2=C1SC(N)=N2 FASDKYOPVNHBLU-ZETCQYMHSA-N 0.000 description 1
- 229960003089 pramipexole Drugs 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Abstract
The application provides a monitoring method and electronic equipment, wherein the method is applied to a monitoring system and comprises the following steps: receiving information of a data acquisition assembly, wherein the information of the data acquisition assembly at least comprises monitoring interface information of the data acquisition assembly; the data acquisition component is associated with a monitoring object and is used for carrying out data acquisition on the monitoring object; and acquiring the data of the monitoring object acquired by the data acquisition component according to the monitoring interface information. According to the method and the device, after the data acquisition assembly is deployed, the information of the data acquisition assembly including the monitoring interface information is actively sent to the monitoring system, so that the situation that the information of the data acquisition assembly is manually added at the monitoring system end is avoided, the monitoring process is simplified, and the later maintenance is convenient.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a monitoring method and an electronic device.
Background
The monitoring system, for example, the pramipexole (poucheus), monitors the monitored object, and the monitored object is required to provide a monitoring interface required by the monitoring system for the monitoring system, so that the monitoring system can monitor the monitored object through the monitoring interface. However, many monitoring objects cannot directly provide a monitoring interface required by the monitoring system, so a third party, namely a data acquisition component, is introduced between the monitoring system and the monitoring objects, for example, an Exporter, and the data acquisition component firstly acquires data of the monitoring objects according to the monitoring related interface provided by the monitoring objects, and then provides the data of the monitoring objects for the monitoring system.
However, the monitoring system can not automatically find the deployed data acquisition components related to each monitored object. After the data acquisition assembly is deployed, the monitoring system can grasp the monitoring data of the monitored object from the data acquisition assembly only after the related information of the data acquisition assembly is manually added to the monitoring system, so that the complex monitoring is caused, and the maintenance is inconvenient.
Disclosure of Invention
In view of the above, the application provides a monitoring method and electronic equipment, which can realize that the information of a data acquisition component is not required to be added to a monitoring system manually, simplify the monitoring process and facilitate later maintenance.
An embodiment of the present application provides a monitoring method, applied to a monitoring system, including:
receiving information of a data acquisition assembly, wherein the information of the data acquisition assembly at least comprises monitoring interface information of the data acquisition assembly; the data acquisition component is associated with a monitoring object and is used for carrying out data acquisition on the monitoring object;
and acquiring the data of the monitoring object acquired by the data acquisition component according to the monitoring interface information.
By adopting the technical scheme, after the data acquisition assembly is deployed, the deployment platform actively transmits the information of the data acquisition assembly comprising the monitoring interface information to the monitoring system, and the monitoring system acquires the data of the monitored object from the data acquisition assembly according to the information of the data acquisition assembly, so that the manual addition of the information of the data acquisition assembly at the monitoring system end is avoided, the monitoring process is simplified, and the later maintenance is convenient.
In one possible implementation manner, after receiving the information of the data acquisition component, the method further includes:
detecting whether unloading information is received or not, wherein the unloading information is used for representing that the data acquisition component is unloaded;
and deleting the information of the data acquisition component under the condition that the receiving of the unloading information is detected.
By adopting the technical scheme, the monitoring system is prevented from carrying out data acquisition on the unloaded data acquisition assembly, so that data acquisition failure is avoided.
In one possible implementation, the monitoring object includes a headquarter monitoring object and at least one subsection monitoring object, and the monitoring system includes: a main monitoring system for monitoring data of the headquarter monitoring object, and a sub-monitoring system for monitoring data of the sub-monitoring objects, one of the sub-monitoring systems corresponding to one of the sub-monitoring objects, the main monitoring system including a display interface;
the method further comprises the steps of:
the main monitoring system receives the data of the sub-monitoring objects sent by the sub-monitoring system;
the general monitoring system displays the data of the general monitoring object and the data of the branch monitoring object on the display interface;
The general monitoring system stores the data of the general monitoring object and the data of the branch monitoring object into a database.
By adopting the technical scheme, the monitoring display of the data acquired by the user is realized, and the integrated centralized monitoring display is also realized.
In one possible implementation, the information of the data acquisition component further includes tag information of the data acquisition component;
after the data of the monitoring object acquired by the data acquisition component is acquired, the method further comprises the following steps:
and displaying the data of the monitoring object according to the label information.
By adopting the technical scheme, the flexible display of the data of the monitored object is realized, and the observability of the data of the monitored object is also improved.
A second aspect of the embodiments of the present application provides a monitoring method, applied to a deployment platform, including:
deploying the data acquisition component according to resource information for representing deployment resources, and obtaining information of the data acquisition component; the data acquisition component is associated with a monitoring object and is used for carrying out data acquisition on the monitoring object;
the information of the data acquisition component is sent to a monitoring system, and the information of the data acquisition component at least comprises monitoring interface information of the data acquisition component; the monitoring system is used for acquiring the data of the monitoring object acquired by the data acquisition component according to the monitoring interface information.
By adopting the technical scheme, the manual addition of information of the data acquisition component at the monitoring system end is avoided, the monitoring process is simplified, and the later maintenance is convenient.
In one possible implementation, after the information of the data acquisition component is sent to the monitoring system, the method further includes:
detecting the existence state of the data acquisition component;
and under the condition that the data acquisition component is detected to be unloaded, unloading information is sent to the monitoring system, and the monitoring system is used for deleting the information of the data acquisition component according to the unloading information.
By adopting the technical scheme, the monitoring system is prevented from carrying out data acquisition on the unloaded data acquisition assembly, so that data acquisition failure is avoided.
In one possible implementation, the deployment data acquisition component includes:
detecting the deployment state of the monitoring object;
and deploying the data acquisition component under the condition that the monitoring object is deployed.
By adopting the technical scheme, the data acquisition component is deployed along with the deployment of the monitoring object, the trouble that the data acquisition component and the monitoring object are independently deployed is solved, and the problem that the data acquisition component and the monitoring object are not associated can be avoided.
In one possible implementation, the deployment data acquisition component includes:
configuring a preset label for the data acquisition component; the information of the data acquisition component further comprises label information of the data acquisition component; the monitoring system is used for displaying the data of the monitoring object according to the tag information.
By adopting the technical scheme, the monitoring system is beneficial to data display and data filtering of the data of the monitored object according to the preset label.
In one possible implementation, after the deploying the data acquisition component, the method further includes:
detecting the existence state of the monitoring object;
and unloading the data acquisition component under the condition that the monitored object is detected to be unloaded.
By adopting the technical scheme, the data acquisition component is unloaded along with the unloading of the monitoring object, so that the problem of false alarm caused by that the data acquisition component is not unloaded because the monitoring object is unloaded is solved.
In a third aspect, an embodiment of the present application provides a monitoring device, where the device has a function of implementing the method provided in the first aspect or the second aspect. The functions may be realized by hardware, or may be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium comprising computer instructions that, when run on an electronic device, cause the electronic device to perform the monitoring method according to the first or second aspect.
In a fifth aspect, an embodiment of the present application provides an electronic device, where the electronic device includes a processor and a memory, where the memory is configured to store instructions, and the processor is configured to invoke the instructions in the memory, so that the electronic device performs the monitoring method according to the first aspect or the second aspect.
In a sixth aspect, embodiments of the present application provide a computer program product which, when run on a computer, causes the computer to perform the monitoring method according to the first or second aspect.
It will be appreciated that the monitoring apparatus according to the third aspect, the computer readable storage medium according to the fourth aspect, the electronic device according to the fifth aspect, and the computer program product according to the sixth aspect correspond to the methods according to the first aspect or the second aspect, and therefore, the advantages achieved by the monitoring apparatus according to the third aspect, the computer readable storage medium according to the fourth aspect, and the electronic device according to the fifth aspect may refer to the advantages provided in the corresponding methods, and are not repeated herein.
Drawings
In order to more clearly illustrate the technical solutions of the present application or the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is one of the flowcharts of the monitoring method shown in an exemplary embodiment of the present application.
FIG. 2 is a schematic diagram of a deployment platform, as shown in an exemplary embodiment of the present application.
FIG. 3 is a second flowchart of a monitoring method according to an exemplary embodiment of the present application.
Fig. 4 is a schematic structural view of a monitoring system according to an exemplary embodiment of the present application.
FIG. 5 is a third flowchart of a monitoring method according to an exemplary embodiment of the present application.
Fig. 6 is a schematic diagram of integrated monitoring provided herein.
Fig. 7 is a fourth flowchart of a monitoring method shown in an exemplary embodiment of the present application.
Fig. 8 is a fifth flow chart of a monitoring method shown in an exemplary embodiment of the present application.
Fig. 9 is a flowchart of a monitoring method according to an exemplary embodiment of the present application.
Fig. 10 is a flow chart of a monitoring method according to an exemplary embodiment of the present application.
Fig. 11 is a flowchart eight of a monitoring method shown in an exemplary embodiment of the present application.
Fig. 12 is a flowchart of a monitoring method according to an exemplary embodiment of the present application.
Fig. 13 is a flowchart of a monitoring method according to an exemplary embodiment of the present application.
Fig. 14 is a schematic diagram of a hardware structure of an electronic device according to an exemplary embodiment of the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the present application will be clearly and completely described below with reference to the drawings in the present application, and it is apparent that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without undue burden, are within the scope of the present application.
It should be noted that "at least one" in this application means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and the representation may have three relationships, for example, a and/or B may represent: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The terms "first," "second," "third," "fourth" and the like in the description and in the claims and drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.
As shown in fig. 1, fig. 1 is one of flowcharts illustrating a monitoring method according to an exemplary embodiment of the present application, and in an exemplary embodiment, the monitoring method is applied to a monitoring system, including steps 101 and 102, which are described in detail below:
step 101, receiving information of a data acquisition assembly, wherein the information of the data acquisition assembly at least comprises monitoring interface information of the data acquisition assembly; the data acquisition component is associated with a monitoring object and is used for carrying out data acquisition on the monitoring object.
Specifically, after the data acquisition component is deployed by the deployment platform, the deployment platform can obtain the information of the data acquisition component, and the monitoring system receives the information of the data acquisition component sent by the deployment platform.
For ease of understanding, the structure of the deployment platform will be described first.
As shown in fig. 2, fig. 2 is a schematic structural diagram of a deployment platform 200 according to an exemplary embodiment of the present application, where the deployment platform 200 includes: the monitoring object deployment/offloading module 210 and the data acquisition component deployment/offloading module 220 and the information transmission module 230.
The monitoring object deployment/uninstallation module 210 is used to deploy or uninstall the monitoring object.
The data acquisition component deployment/uninstallation module 220 is configured to deploy a data acquisition component associated with a monitored object when the monitored object is deployed; and unloading the data acquisition component associated with the monitored object when unloading the monitored object.
The information sending module 230 is configured to send the obtained information of the data acquisition component to the monitoring system when the data acquisition component is deployed; and when the data acquisition component is unloaded, unloading information used for representing that the data acquisition component is unloaded is sent to the monitoring system.
The monitoring object deployment/offloading module 210 may include an application virtual machine deployment/offloading module 211 and an application container deployment/offloading module 212, where the application virtual machine deployment/offloading module 211 is configured to deploy or offload an application virtual machine; the application container deployment/offloading module 212 is used to deploy or offload application containers.
The data acquisition component deployment/uninstallation module 220 may include an information generation/deletion module 221 and a tag configuration/deletion module 222, wherein the information generation/deletion module 221 is configured to generate information of the data acquisition component when the data acquisition component is deployed; and deleting the information of the data acquisition component when the data acquisition component is unloaded. The tag configuration/deletion module 222 is configured to configure a preset tag for the data acquisition component when the data acquisition component is deployed; and deleting the label of the data acquisition component when the data acquisition component is unloaded.
The information of the data acquisition component may include monitoring interface information of the data acquisition component, which is information that may indicate data communication with the data acquisition component. For example, the monitoring interface information is a monitoring interface link, a monitoring interface type, and the like.
The information of the data acquisition component can also comprise deployment address information of the data acquisition component, wherein the deployment address information is information which can indicate the position of the deployed data acquisition component.
For example, the deployment address information may be the host ip address and port information of the deployed data acquisition component, or may be the domain name address of the deployed data acquisition component.
The monitoring objects and the data acquisition components are deployed on the deployment platform 200, one data acquisition component is associated with one monitoring object, and each data acquisition component performs data acquisition on the associated monitoring object to acquire the data of the monitoring object.
Step 102, acquiring the data of the monitoring object acquired by the data acquisition component according to the monitoring interface information.
Specifically, the monitoring system can perform data communication with the data acquisition component according to the monitoring interface information, and acquire the data of the monitored object acquired by the data acquisition component, so that the monitoring system 400 realizes the monitoring of the monitored object.
In this embodiment, after the data acquisition component is deployed, the deployment platform 200 actively transmits the information of the data acquisition component including the monitoring interface information to the monitoring system, and the monitoring system acquires the data of the monitored object from the data acquisition component according to the information of the data acquisition component, so that the manual addition of the information of the data acquisition component at the monitoring system end is avoided, the monitoring process is simplified, and the later maintenance is convenient.
As shown in fig. 3, fig. 3 is a second flowchart of a monitoring method according to an exemplary embodiment of the present application, in an exemplary embodiment, after step 101, that is, after receiving the information of the data acquisition component, the monitoring method may further include step 201 and step 202. In this embodiment, a process of deleting information of the data acquisition component after the data acquisition component is unloaded is proposed.
In step 201, it is detected whether unloading information is received, where the unloading information is used to characterize that the data acquisition component is unloaded.
Specifically, after receiving the information of the data acquisition component, the monitoring system stores the information of the data acquisition component in a configuration document, and then actively acquires the data of the monitoring object from the corresponding data acquisition component according to the information of the data acquisition component in the configuration document.
If the data collection component corresponding to the information of a certain data collection component stored in the configuration document is unloaded by the deployment platform 200, the monitoring system 400 still performs data collection according to the information of the data collection component in the configuration document, and in this case, the monitoring system 400 also performs data collection on the unloaded data collection component, which may cause data collection failure.
To avoid the occurrence of data collection failure, the monitoring system 400 needs to know whether the data collection component corresponding to the information of the data collection component in the configuration document is unloaded, which may be specifically described as follows: monitoring system 400 detects in real-time whether offload information sent by deployment platform 200 is received, which may characterize that the data acquisition component is offloaded. Thus, by detecting whether the offload information is received, it can be made clear whether the data acquisition component is offloaded.
And 202, deleting information of the data acquisition component under the condition that the receiving of unloading information is detected.
Specifically, when the detection of receiving the unloading information indicates that the data acquisition component is unloaded, the information corresponding to the unloaded data acquisition component needs to be deleted from the configuration document, so as to avoid data acquisition failure caused by data acquisition of the unloaded data acquisition.
In the case where the uninstalled information is not detected, it indicates that the data acquisition component is not uninstalled, and therefore, the monitoring system 400 may directly perform data acquisition according to the information of the data acquisition component in the configuration document.
In some embodiments, the offload information may include identification information for identifying the data acquisition components, one for each, from which the monitoring system 400 may determine which particular data acquisition component was offloaded, thereby making it clear that the data acquisition component information needs to be deleted from the configuration document.
An offload message may include an identification message to characterize a data acquisition component being offloaded; an offload message also includes a plurality of identification messages to characterize the offloading of the plurality of data acquisition components. The particular settings may be determined based on the communication capabilities between the monitoring system 400 and the deployment platform 200.
In this embodiment, the monitoring system 400 determines whether the data acquisition component is unloaded by detecting whether the unloading information is received, and deletes the information of the data acquisition component under the condition that the data acquisition component is unloaded, so that the data acquisition of the unloaded data acquisition component is not performed, and thus the data acquisition failure is avoided.
For ease of understanding, the structure of the monitoring system 400 will be described.
As shown in fig. 4, fig. 4 is a schematic structural diagram of a monitoring system according to an exemplary embodiment of the present application, and the monitoring system 400 includes a main monitoring system 410 and at least one sub-monitoring system 420, where the main monitoring system 410 is communicatively connected to each sub-monitoring system 420.
The overall monitoring system 410 includes a presentation interface 4101, where the presentation interface 4101 can present data acquired by the overall monitoring system, and the presentation interface 4101 can be a visualization tool Grafana.
The monitoring object may include a headquarter monitoring object and at least one subsection monitoring object. For example, if a manufacturer is provided with a headquarter and a plurality of branches, the headquarter monitoring object may be the headquarter of the manufacturer, and the branch monitoring object may be the plurality of branches of the manufacturer.
A headquarter monitoring system 410 performs data monitoring on a headquarter monitoring object and a sub-monitoring system 420 performs data monitoring on a sub-monitoring object.
As shown in fig. 5, fig. 5 is a third flowchart of a monitoring method according to an exemplary embodiment of the present application, and in an exemplary embodiment, before or after or simultaneously with step 102, that is, before or after or simultaneously with acquiring the data of the monitored object acquired by the data acquisition component, the monitoring method may further include steps 501 to 503.
In step 501, the general monitoring system 410 receives the data of the sub-monitoring objects sent by the sub-monitoring system 420.
Specifically, the data collected by the master monitoring system 410 and the data collected by the sub-monitoring system 420 are stored in the local databases by default, so that the data are stored in a scattered manner, and centralized management is difficult.
In order to centrally manage data, each sub-monitoring system 420 is federally connected to the general monitoring system 410, so that each sub-monitoring system 420 can send the collected data of the sub-monitoring object to the general monitoring system 410, and the general monitoring system 410 can obtain the data of the general monitoring object and the data of each sub-monitoring object, thereby preliminarily aggregating the scattered data.
In step 502, the head office monitoring system 410 displays the head office monitoring object data and the branch monitoring object data on the display interface 4101.
Specifically, the general monitoring system 410 transmits the data of the general monitoring object and the data of each of the sub monitoring objects to the display interface 4101, and performs visual display on the display interface 4101, so as to perform more intuitive monitoring on the general monitoring object and each of the sub monitoring objects.
In step 503, the central monitoring system stores the data of the central monitoring object and the data of the branch monitoring objects in the database.
Specifically, the head office monitoring system 410 stores the data of the head office monitoring object and the data of the branch monitoring object to a database, for example, a time series database. The general monitoring system 410 in the other monitoring systems also stores the data of the general monitoring object and the data of the branch monitoring object in the database, thereby realizing integrated centralized monitoring.
Fig. 6 is a schematic diagram of integrated monitoring provided in the present application, as shown in fig. 6, the general monitoring system a performs data monitoring on the general monitoring object 1, and the sub-monitoring system A1 performs data monitoring on the sub-monitoring object 11. The sub-monitoring system A2 performs data monitoring on the sub-monitoring object 12, and the main monitoring system a receives data of the sub-monitoring object 11 transmitted by the sub-monitoring system A1 and receives data of the sub-monitoring object 12 transmitted by the sub-monitoring system A2. The general monitoring system A displays the data of the general monitoring object 1, the sub monitoring object 11 and the sub monitoring object 12 on a display interface A and sends the data to a database.
The main monitoring system B performs data monitoring on the main monitoring object 2, the sub-monitoring system B1 performs data monitoring on the split monitoring object 21, and the sub-monitoring system B2 performs data monitoring on the split monitoring object 22. The total monitoring system B receives the data of the sub-monitoring object 21 transmitted by the sub-monitoring system B1 and the data of the sub-monitoring object 22 transmitted by the sub-monitoring system B2. The general monitoring system B displays the data of the general monitoring object 2, the sub monitoring object 21 and the sub monitoring object 22 on the display interface B and sends the data to the database.
The database displays the received data of the headquarter monitoring object 1, the subsection monitoring object 11, the subsection monitoring object 12, the headquarter monitoring object 2, the subsection monitoring object 21 and the subsection monitoring object 22 on the display interface C.
In this embodiment, each sub-monitoring system 420 first federally corresponds to the general monitoring system 410, and displays the acquired data on the display interface 4101 of the general monitoring system 410, so as to realize monitoring and displaying of the acquired data. The different general monitoring systems 410 remotely write the data into the unified database, and display the data in the database on the display interface of the docking database, thereby realizing integrated centralized monitoring display.
As shown in fig. 7, fig. 7 is a flowchart illustrating a monitoring method according to an exemplary embodiment of the present application, in an exemplary embodiment, after step 102, that is, after acquiring the data of the monitored object acquired by the data acquisition component, the monitoring method may further include step 701.
And step 701, displaying the data of the monitoring object according to the label information.
Specifically, the information of the data acquisition component further includes label information of the data acquisition component, and the label information can be a predefined manufacturer label, a predefined area label, a predefined item label and the like. The data acquired by the monitoring system 400 from the data acquisition component also carries the tag information, so that the data of the monitored object can be displayed on the display interface 4101 according to the tag information.
The display mode can be partition display, and one region displays data carrying the same tag information; the display mode may also be a centralized display mode, and data of different tag information is directly displayed on the display interface 4101.
In some embodiments, the monitoring system 400 may first filter the data collected from the data collection component according to the tag information, enabling accurate collection and saving of data storage space.
According to the embodiment, the data of the monitoring object can be displayed in different forms according to the tag information, so that the flexible display of the data of the monitoring object is realized, and the observability of the data of the monitoring object is also improved.
As shown in fig. 8, fig. 8 is a fifth flowchart of a monitoring method according to an exemplary embodiment of the present application, and in an exemplary embodiment, the monitoring method is applied to the deployment platform 200, including steps 801 and 802, which are described in detail below:
step 801, deploying a data acquisition component according to resource information for representing deployment resources, and obtaining information of the data acquisition component; the data acquisition component is associated with a monitoring object and is used for carrying out data acquisition on the monitoring object.
Specifically, the deployment platform 200 obtains resource information from the resource platform, where the resource information may represent a deployment resource on the resource platform that can be used for deployment, and the deployment resource may deploy a base resource, middleware, a platform resource, or an application resource that needs to be used by the data acquisition component and the monitoring object. The deployment platform 200 determines deployment resources according to the resource information, and deploys the data acquisition component by applying the deployment resources to obtain information of the data acquisition component.
The monitoring objects and the data acquisition components are deployed on the deployment platform 200, one data acquisition component is associated with one monitoring object, and each data acquisition component performs data acquisition on the associated monitoring object to acquire the data of the monitoring object.
Step 802, transmitting information of the data acquisition component to the monitoring system 400, wherein the information of the data acquisition component at least comprises monitoring interface information of the data acquisition component; the monitoring system 400 is configured to obtain data of the monitored object collected by the data collection component according to the monitoring interface information.
The information of the data acquisition component may include monitoring interface information of the data acquisition component, which is information that may indicate data communication with the data acquisition component. For example, the monitoring interface information is a monitoring interface link, a monitoring interface type, and the like.
The information of the data acquisition component can also comprise deployment address information of the data acquisition component, wherein the deployment address information is information which can indicate the position of the deployed data acquisition component.
For example, the deployment address information may be the host ip address and port information of the deployed data acquisition component, or may be the domain name address of the deployed data acquisition component.
The deployment platform 200 sends the information of the data acquisition component to the monitoring system 400, and the monitoring system 400 can perform data communication with the data acquisition component according to the monitoring interface information and acquire the data of the monitored object acquired by the data acquisition component, so that the monitoring system 400 monitors the monitored object.
In this embodiment, after the data acquisition components are deployed, the deployment platform 200 actively transmits the information of the data acquisition components including the monitoring interface information to the monitoring system 400, and the monitoring system 400 acquires the data of the monitored object from the data acquisition components according to the information of the data acquisition components, so that the addition of the information of the data acquisition components at the end of the monitoring system 400 by hand is avoided, the monitoring process is simplified, and the later maintenance is convenient.
As shown in fig. 9, fig. 9 is a sixth flowchart of a monitoring method shown in an exemplary embodiment of the present application, in which step 801 may include step 901 and step 902.
Step 901, detecting the deployment state of a monitoring object;
specifically, in the related art, the data acquisition component and the monitoring object are deployed separately, and after the data acquisition component and the monitoring object are deployed, the data acquisition component and the monitoring object are associated, but the data acquisition component is not associated with the monitoring object, so that the problem that the data acquisition component cannot acquire the data of the monitoring object exists.
In order to solve the trouble of independent deployment of the data acquisition component and the monitoring object and the problem of no association, the data acquisition component and the associated monitoring object are bound before the data acquisition component and the monitoring object are deployed.
Before deploying the data acquisition component, the deployment platform 200 needs to detect the deployment status of the monitoring object, and determine whether the monitoring object is deployed.
In step 902, in the case that the monitored object is detected to be deployed, a data acquisition component is deployed.
Specifically, in the case where it is detected that the monitoring object is deployed, the deployment platform 200 deploys the data acquisition component; in the event that a monitored object is detected not to be deployed, the deployment platform 200 does not deploy the data acquisition component either.
According to the embodiment, the data acquisition component is deployed along with the deployment of the monitoring object, the trouble that the data acquisition component and the monitoring object are independently deployed is solved, and the problem that the data acquisition component and the monitoring object are not associated can be avoided.
As shown in fig. 10, fig. 10 is a seventh flowchart of a monitoring method shown in an exemplary embodiment of the present application, in which step 801 may include step 1001.
Step 1001, configuring a preset tag for a data acquisition component.
Specifically, the deployment platform 200 configures a preset tag for the data acquisition component when deploying the data acquisition component. The preset labels may be manufacturer labels, area labels and project labels, and the information of the data acquisition component obtained by the deployment platform 200 further includes label information of the data acquisition component.
The tag information is also carried by the data acquired by the monitoring system 400 from the data acquisition component, so that the data of the monitored object can be displayed on the display interface 3101 according to the tag information.
In some embodiments, the monitoring system 400 may partially filter the data collected from the data collection assembly based on the tag information, enabling accurate collection and saving of data storage space.
In this embodiment, when the data acquisition component is deployed, the deployment platform 200 configures a preset tag for the data acquisition component, which is beneficial for the monitoring system 400 to perform data display and data filtering on the data of the monitored object according to the preset tag.
As shown in fig. 11, fig. 11 is a flowchart eight of a monitoring method shown in an exemplary embodiment of the present application, in an exemplary embodiment, after step 801, i.e., after deploying the data acquisition component, the monitoring method may further include step 1101 and step 1102.
Step 1101, detecting a presence state of a monitored object.
Specifically, in the case where the monitored object is unloaded and the associated data acquisition component is not unloaded, there is a problem in that the monitored object is not unloaded by false alarm.
In order to solve the problem of false alarm, after the deployment platform 200 deploys the data acquisition component, the deployment platform 200 needs to detect the presence state of the monitoring object in real time.
In step 1102, in the case that the monitored object is detected to be uninstalled, the data acquisition component is uninstalled.
Specifically, in the case that the monitored object is detected to be unloaded, the data acquisition component associated with the monitored object is unloaded. And deleting the information of the data acquisition assembly while unloading the data acquisition assembly associated with the monitoring object.
According to the embodiment, the data acquisition component is unloaded along with the unloading of the monitoring object, so that the problem of false alarm caused by the fact that the monitoring object is unloaded and the data acquisition component is not unloaded is solved.
As shown in fig. 12, fig. 12 is a flowchart of a monitoring method shown in an exemplary embodiment of the present application, in an exemplary embodiment, after step 802, i.e., after the information of the data acquisition component is sent to the monitoring system 400, the monitoring method may further include steps 1201 and 1202.
Step 1201 detects a presence state of a data acquisition component.
Specifically, after receiving the information of the data collection component, the monitoring system 400 stores the information of the data collection component in the configuration document, and then actively collects the data of the monitoring object from the corresponding data collection component according to the information of the data collection component in the configuration document.
If the data collection component corresponding to the information of a certain data collection component stored in the configuration document is unloaded by the deployment platform 200, the monitoring system 400 still performs data collection according to the information of the data collection component in the configuration document, and in this case, the monitoring system 400 also performs data collection on the unloaded data collection component, which may cause data collection failure.
To avoid the occurrence of a failure in data collection, the monitoring system 400 needs to know whether the data collection component corresponding to the information of the data collection component in the configuration document is uninstalled.
Because the data acquisition component is deployed on the deployment platform 200, the monitoring system 400 cannot directly detect the presence state of the data acquisition component, and the deployment platform 200 is required to detect the presence state of the data acquisition component in real time, where the presence state may include an unloaded state and an unloaded state.
In step 1202, in the case that the data acquisition component is detected to be uninstalled, the uninstalled information is sent to the monitoring system 400, and the monitoring system 400 is configured to delete the information of the data acquisition component according to the uninstalled information.
Specifically, in the event that the data acquisition component is detected to be offloaded, the deployment platform 200 sends offload information to the monitoring system 400, which may characterize the data acquisition component as offloaded. Thus, the monitoring system 400 can ascertain whether the data acquisition component is offloaded by detecting whether the offload information is received.
In the case that the monitoring system 400 detects that the unloading information is received, the information corresponding to the unloaded data acquisition component needs to be deleted from the configuration document, so as to avoid data acquisition failure caused by data acquisition of the unloaded data acquisition.
In this embodiment, the deployment platform 200 detects the existence state of the data acquisition component, and sends unloading information to the monitoring system 400 when detecting that the data acquisition component is unloaded, so that the monitoring system 400 deletes the information of the corresponding data acquisition component according to the unloading information, thereby avoiding data acquisition failure.
Fig. 13 is a flowchart of a monitoring method according to an exemplary embodiment of the present application, as shown in fig. 13, and in an exemplary embodiment, the monitoring method may include:
In step 1301, the deployment platform 200 captures resource information from the resource platform.
In step 1302, the deployment platform 200 deploys the monitoring object and the data acquisition component according to the resource information, and configures a preset tag for the data acquisition component.
In step 1303, after the data acquisition component is deployed, the deployment platform 200 sends the information of the data acquisition component to the monitoring system 400.
At step 1304, the monitoring system 400 adds information of the data collection component to the configuration document.
In step 1305, the monitoring system 400 collects data of the monitored object from the data collection assembly according to the information of the data collection assembly.
In step 1306, the monitoring system 400 writes the data of the monitored object to the database.
Step 1307, the display interface in butt joint with the database queries the data of the monitoring object in the database according to the label information.
Step 1308, the display interface in butt joint with the database displays the monitoring data according to the label information.
As shown in fig. 14, fig. 14 is a schematic diagram of a hardware structure of an electronic device 1400 provided in an exemplary embodiment of the present application, where the electronic device 1400 may include a processor 1401, a memory 1402, and a communication bus 1403. Memory 1402 is used to store one or more computer programs 1404. One or more computer programs 1404 are configured to be executed by the processor 1401. The one or more computer programs 1404 include instructions that can be used to implement the monitoring methods described above for execution in the electronic device 1400.
It is to be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 1400. In other embodiments, electronic device 1400 may include more or less components than those shown, or certain components may be combined, or certain components may be split, or different arrangements of components.
The processor 1401 may include one or more processing units, such as: the processor 1401 may include an application processor (application processor, AP), a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a DSP, a CPU, a baseband processor, and/or a neural-network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.
The processor 1401 may also have a memory provided therein for storing instructions and data. In some embodiments, the memory in the processor 1401 is a cache memory. The memory may hold instructions or data that the processor 1401 has just used or recycled. If the processor 1401 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 1401 is reduced, thus improving the efficiency of the system.
In some embodiments, the processor 1401 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a SIM interface, and/or a USB interface, among others.
In some embodiments, memory 1402 may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card), at least one disk storage device, a Flash memory device, or other volatile solid-state storage device.
The present embodiment also provides a computer storage medium having stored therein computer instructions which, when executed on an electronic device, cause the electronic device to perform the above-described related method steps to implement the monitoring method in the above-described embodiments.
The embodiment also provides a chip which is electrically connected with the electronic equipment and used for controlling the electronic equipment to execute the related method steps to realize the monitoring method in the embodiment.
The present embodiment also provides a computer program product which, when run on a computer, causes the computer to perform the above-mentioned related steps to implement the monitoring method in the above-mentioned embodiments.
The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are used to execute the corresponding methods provided above, so that the beneficial effects thereof can be referred to the beneficial effects in the corresponding methods provided above, and will not be described herein.
From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated unit may be stored in a readable storage medium if implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application.
Claims (10)
1. A monitoring method, applied to a monitoring system, comprising:
receiving information of a data acquisition assembly, wherein the information of the data acquisition assembly at least comprises monitoring interface information of the data acquisition assembly; the data acquisition component is associated with a monitoring object and is used for carrying out data acquisition on the monitoring object;
and acquiring the data of the monitoring object acquired by the data acquisition component according to the monitoring interface information.
2. The method of monitoring of claim 1, further comprising, after receiving the information of the data acquisition component:
detecting whether unloading information is received or not, wherein the unloading information is used for representing that the data acquisition component is unloaded;
and deleting the information of the data acquisition component under the condition that the receiving of the unloading information is detected.
3. The monitoring method according to claim 1, wherein the monitoring object includes a headquarter monitoring object and at least one subsection monitoring object, the monitoring system including: a main monitoring system for monitoring data of the headquarter monitoring object, and a sub-monitoring system for monitoring data of the sub-monitoring objects, one of the sub-monitoring systems corresponding to one of the sub-monitoring objects, the main monitoring system including a display interface;
The method further comprises the steps of:
the main monitoring system receives the data of the sub-monitoring objects sent by the sub-monitoring system;
the general monitoring system displays the data of the general monitoring object and the data of the branch monitoring object on the display interface;
the general monitoring system stores the data of the general monitoring object and the data of the branch monitoring object into a database.
4. The monitoring method of claim 1, wherein the information of the data acquisition component further comprises tag information of the data acquisition component;
after the data of the monitoring object acquired by the data acquisition component is acquired, the method further comprises the following steps:
and displaying the data of the monitoring object according to the label information.
5. A method of monitoring, applied to a deployment platform, comprising:
deploying the data acquisition component according to resource information for representing deployment resources, and obtaining information of the data acquisition component; the data acquisition component is associated with a monitoring object and is used for carrying out data acquisition on the monitoring object;
the information of the data acquisition component is sent to a monitoring system, and the information of the data acquisition component at least comprises monitoring interface information of the data acquisition component; the monitoring system is used for acquiring the data of the monitoring object acquired by the data acquisition component according to the monitoring interface information.
6. The monitoring method of claim 5, further comprising, after transmitting the information of the data acquisition component to a monitoring system:
detecting the existence state of the data acquisition component;
and under the condition that the data acquisition component is detected to be unloaded, unloading information is sent to the monitoring system, and the monitoring system is used for deleting the information of the data acquisition component according to the unloading information.
7. The method of monitoring of claim 6, wherein the deploying a data acquisition component comprises:
detecting the deployment state of the monitoring object;
and deploying the data acquisition component under the condition that the monitoring object is deployed.
8. The method of monitoring of claim 6, wherein the deploying a data acquisition component comprises:
configuring a preset label for the data acquisition component; the information of the data acquisition component further comprises label information of the data acquisition component; the monitoring system is used for displaying the data of the monitoring object according to the tag information.
9. The method of monitoring of claim 6, further comprising, after the deploying the data acquisition component:
Detecting the existence state of the monitoring object;
and unloading the data acquisition component under the condition that the monitored object is detected to be unloaded.
10. An electronic device comprising a processor and a memory for storing instructions, the processor for invoking the instructions in the memory to cause the electronic device to monitor a method according to any of claims 1-4 or a method according to any of claims 5-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310723812.8A CN116541250A (en) | 2023-06-19 | 2023-06-19 | Monitoring method and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310723812.8A CN116541250A (en) | 2023-06-19 | 2023-06-19 | Monitoring method and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116541250A true CN116541250A (en) | 2023-08-04 |
Family
ID=87445533
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310723812.8A Pending CN116541250A (en) | 2023-06-19 | 2023-06-19 | Monitoring method and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116541250A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102231138A (en) * | 2011-07-08 | 2011-11-02 | 上海交通大学 | Accurate memory data acquisition system and method of computer |
| CN107239379A (en) * | 2017-05-10 | 2017-10-10 | 杭州铭师堂教育科技发展有限公司 | Database performance Automatic monitoring systems based on salt |
| US20200328936A1 (en) * | 2019-04-09 | 2020-10-15 | Elasticsearch B.V. | Data Shipper Agent Management and Configuration Systems and Methods |
| CN111831362A (en) * | 2020-07-28 | 2020-10-27 | 浪潮云信息技术股份公司 | Method for automatic discovery, classification, deployment and management of K8s environment monitoring |
| CN114490270A (en) * | 2022-02-14 | 2022-05-13 | 挂号网（杭州）科技有限公司 | Data acquisition method and device |
-
2023
- 2023-06-19 CN CN202310723812.8A patent/CN116541250A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102231138A (en) * | 2011-07-08 | 2011-11-02 | 上海交通大学 | Accurate memory data acquisition system and method of computer |
| CN107239379A (en) * | 2017-05-10 | 2017-10-10 | 杭州铭师堂教育科技发展有限公司 | Database performance Automatic monitoring systems based on salt |
| US20200328936A1 (en) * | 2019-04-09 | 2020-10-15 | Elasticsearch B.V. | Data Shipper Agent Management and Configuration Systems and Methods |
| CN111831362A (en) * | 2020-07-28 | 2020-10-27 | 浪潮云信息技术股份公司 | Method for automatic discovery, classification, deployment and management of K8s environment monitoring |
| CN114490270A (en) * | 2022-02-14 | 2022-05-13 | 挂号网（杭州）科技有限公司 | Data acquisition method and device |
Non-Patent Citations (2)
| Title |
|---|
| 任德敬: "基于OpenStack的资源监控和计费系统的设计与实现", 《中国优秀硕士学位论文全文数据库》, no. 2, pages 139 - 182 * |
| 支连意: "云环境中集群监控数据采集与分析系统的研究与实现", 《中国优秀硕士学位论文全文数据库》, pages 139 - 377 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI450103B (en) | Remote management systems and methods for servers, and computer program products thereof | |
| US9954727B2 (en) | Automatic debug information collection | |
| CN105868149B (en) | Serial port information transmission method and device | |
| CN110320891B (en) | Railway vehicle braking system CAN bus message maintenance monitoring system and monitoring method | |
| CN111625419B (en) | Log acquisition method, system, equipment and computer readable storage medium | |
| CN100472468C (en) | Computer system, computer network and method | |
| CN111182251B (en) | Video backup method and device applied to online patrol synchronous transcoding and with hot-pluggable storage medium | |
| CN103778024A (en) | Server system and message processing method thereof | |
| US7801981B2 (en) | Remote monitoring system, remote monitoring method for electronic apparatus, low order monitoring apparatus, notification method of apparatus monitoring information, high order monitoring apparatus, communication method of maintenance data, program and recording medium | |
| CN115543872A (en) | Equipment management method and device and computer storage medium | |
| CN116541250A (en) | Monitoring method and electronic equipment | |
| CN113010122A (en) | Image forming apparatus monitoring apparatus, method, system, and storage medium | |
| CN111382004B (en) | Parameter backup method and device, parameter restoration method and device and backup restoration system | |
| US7356683B2 (en) | System and method for monitoring BIOS messages of remote computers by a local server | |
| CN103795857B (en) | Information processing method and electronic equipment | |
| CN115543746A (en) | Graphics processor monitoring method, system and device and electronic equipment | |
| CN114218000A (en) | Log management method and device, electronic equipment and computer readable storage medium | |
| CN113590492A (en) | Information processing method, system, electronic device and computer readable storage medium | |
| CN113849135A (en) | Log access method and device and server | |
| CN113722211A (en) | BMC (baseboard management controller) debugging method, device and system and embedded equipment | |
| CN113254094A (en) | ZYNQ-based data acquisition control display method and device and storage medium | |
| CN111190848A (en) | Method and device for reading GPU (graphics processing Unit) by server | |
| CN113900890B (en) | Method, device, equipment and medium for collecting server component information | |
| CN109120422B (en) | Remote server system capable of obtaining hardware information and management method thereof | |
| CN109697144B (en) | Hard disk detection method of electronic equipment and electronic equipment |
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 |