CN114650218A - Data acquisition method, equipment, system and storage medium - Google Patents
Data acquisition method, equipment, system and storage medium Download PDFInfo
- Publication number
- CN114650218A CN114650218A CN202011503058.XA CN202011503058A CN114650218A CN 114650218 A CN114650218 A CN 114650218A CN 202011503058 A CN202011503058 A CN 202011503058A CN 114650218 A CN114650218 A CN 114650218A
- Authority
- CN
- China
- Prior art keywords
- data
- equipment
- format file
- state data
- communication connection
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 94
- 238000004891 communication Methods 0.000 claims abstract description 66
- 238000012545 processing Methods 0.000 claims abstract description 35
- 230000010354 integration Effects 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 9
- 238000012544 monitoring process Methods 0.000 description 52
- 230000006870 function Effects 0.000 description 51
- 230000015654 memory Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 16
- 230000001953 sensory effect Effects 0.000 description 12
- 239000010979 ruby Substances 0.000 description 4
- 229910001750 ruby Inorganic materials 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000009434 installation Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 210000001072 colon Anatomy 0.000 description 1
- 238000005056 compaction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013139 quantization Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5048—Automatic or semi-automatic definitions, e.g. definition templates
-
- 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 discloses a data acquisition method, which is applied to first equipment, wherein the first equipment can monitor at least one second equipment through communication connection with the at least one second equipment; the method comprises the following steps: determining a target format file corresponding to any second equipment; the target format file is used for any second equipment to obtain at least one state data and arrange the at least one state data to obtain alarm data carrying type information; sending the target format file to any second equipment through communication connection; and acquiring the alarm data sent by any second equipment through communication connection. The application also discloses a data acquisition method applied to the second device, the first device, the second device, a data acquisition system and a computer readable storage medium. The data acquisition method provided by the application reduces the processing load of the first equipment and the loss probability of the alarm data, and enables the first equipment to monitor the second equipment more flexibly and comprehensively.
Description
Technical Field
The present application relates to the field of information technology, and in particular, to a data acquisition method, device, system, and computer-readable storage medium.
Background
In practical application, in order to ensure stable operation of diversified cloud devices, stable provision of various types of cloud services, and stable response of mass data requests, the cloud devices, the cloud services, and the data request response process need to be monitored in real time. In the related art, in order to monitor the cloud environment in real time, various alarm templates are generally defined at a monitoring end, and when the physical machine device sends the captured alarm data to the monitoring end, the monitoring end determines the alarm category corresponding to the alarm data according to the matching relationship between the received alarm data and the alarm templates. However, in the above alarm data processing method, when the amount of alarm data received by the monitoring end is large, the data processing load of the monitoring end increases rapidly, and the alarm template fixed to the monitoring end also causes insufficient monitoring flexibility, which also easily causes data loss due to the fact that new types of alarm data cannot be successfully matched.
Disclosure of Invention
The application provides a data acquisition method, equipment, a system and a computer readable storage medium. The problems that the data processing load of a monitoring terminal is overlarge, the flexibility of a monitoring mode is insufficient, and alarm data are easily lost in the related technology can be solved.
The data acquisition method provided by the application is realized as follows:
the method is applied to first equipment, and the first equipment can monitor at least one second equipment through communication connection with the second equipment; the method comprises the following steps:
determining a target format file corresponding to any second equipment; the target format file is used for the any second equipment to acquire at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
sending the object format file to any second device through the communication connection;
and acquiring the alarm data sent by any second device through the communication connection.
In some embodiments, the determining the target format file corresponding to the second device includes:
acquiring at least one function configuration file; each function configuration file comprises any type of state data acquired by any second equipment and rules for sorting any type of state data;
determining the target format file based on at least one of the functional profiles.
In some embodiments, said determining said target format file based on at least one said functional configuration file comprises:
acquiring a requirement configuration file; the requirement configuration file represents requirement data of any second device for acquiring the at least one state data;
integrating at least one function configuration file based on the requirement configuration file to obtain an integration result;
and determining the target format file based on the integration result.
In some embodiments, said sending said object format file to said any second device via said communication connection comprises:
under the condition that the first equipment detects that any second equipment is in an environment ready state through the communication connection, the target format file is sent to any second equipment through the communication connection; wherein the environment ready state indicates that any second device is in a state in which a state data environment has been configured.
The application also provides a data acquisition method, which is applied to second equipment, wherein communication connection is established between the second equipment and first equipment, and the first equipment can monitor the second equipment through the communication connection; the method comprises the following steps:
receiving a target format file sent by the first equipment through the communication connection; the target format file is determined by the first device and used for the second device to obtain at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
acquiring the at least one state data based on the target format file, and sorting the at least one state data to obtain the alarm data;
and sending the alarm data to the first equipment through the communication connection.
In some embodiments, the obtaining the at least one status data based on the target format file, and sorting the at least one status data to obtain the alarm data includes:
acquiring a first rule and a second rule based on the target format file; wherein the first rule includes a manner in which the second device acquires the at least one status data; the second rule comprises a rule for sorting the at least one state data;
acquiring the at least one state data based on the first rule;
and sorting each type of state data in the at least one type of state data based on the second rule to obtain the alarm data.
The application also provides a first device, wherein a communication connection is established between the first device and at least one second device, and the at least one second device is monitored; the first device includes: the device comprises a first processing module, a first sending module and a first receiving module; wherein:
the first processing module is used for determining a target format file corresponding to any second device; the target format file is used for the any second equipment to acquire at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
the first sending module is configured to send the target format file to any one of the second devices through the communication connection;
the first receiving module is configured to obtain the alarm data sent by any one of the second devices through the communication connection.
The application also provides a second device, wherein a communication connection is established between the second device and the first device; the second device comprises a second receiving module, a second processing module and a second sending module; wherein:
the second receiving module is configured to receive, through the communication connection, the target format file sent by the first device; the target format file is determined by the first device and used for the second device to obtain at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
the second processing module is configured to obtain the at least one type of state data based on the target format file, and sort the at least one type of state data to obtain the alarm data;
the second sending module is configured to send the alarm data to the first device through the communication connection.
The present application further provides a data acquisition system comprising a first device as described in any of the previous embodiments and a second device as described in any of the previous embodiments.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a data acquisition method as applied to a first device as described in any of the preceding claims, or a data acquisition method as applied to a second device as described in any of the preceding claims.
As can be seen from the above, in the data acquisition method applied to the first device, the first device can monitor the at least one second device through the communication connection with the at least one second device; after determining that any second device corresponds to any second device and is used for obtaining at least one type of state data and sorting the state data to obtain a target format file of alarm data carrying type information, sending the target format file to any second device through communication connection, and then receiving the alarm data carrying type information sent by any second device.
Therefore, the data acquisition method applied to the first equipment can set the corresponding target format file according to the requirement for monitoring any second equipment, so that the second equipment can acquire the required state data to obtain the alarm data which corresponds to the monitoring requirement and carries the type information, on one hand, the first equipment can monitor any second equipment more flexibly and comprehensively, and the probability of data loss caused by the fact that the new type state data of any second equipment cannot be matched can be reduced; on the other hand, when the first device is a server device, the load generated by performing matching operation on the alarm data again by the monitoring server in the related art can be relieved.
Drawings
FIG. 1 is a schematic diagram illustrating a process flow of alarm data processing in the related art;
fig. 2 is a schematic flowchart of a first data acquisition method applied to a first device according to the present disclosure;
fig. 3 is a schematic flowchart of a second data acquisition method applied to a first device according to the present application;
FIG. 4 is a flowchart illustrating an implementation of a data acquisition method according to the present disclosure;
fig. 5 is a flowchart of an implementation of the data acquisition method applied to the second device provided in the present application;
fig. 6 is a flowchart of a data acquisition method applied to a first device and a second device provided in the present application;
FIG. 7 is a schematic structural diagram of a first apparatus provided herein;
FIG. 8 is a schematic structural diagram of a second apparatus provided herein;
fig. 9 is a schematic structural diagram of a data acquisition system provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The present application relates to the field of information technology, and in particular, to a data acquisition method, device, system, and computer-readable storage medium.
Fig. 1 is a schematic diagram illustrating a processing flow of alarm data in the related art.
In fig. 1, the processing of the alarm data may include the steps of:
And 102, loading an alarm template on the server side equipment for monitoring.
And 103, when the alarm data is received, determining a template alarm according to the alarm data and the alarm template.
And step 104, reporting the template alarm to a superior gateway.
The alarm template in the above alarm data processing method of the related art is determined according to the analysis requirement of the upper gateway, and is not determined according to the operation characteristics of the actual monitored object, so that such an alarm template cannot realize the differentiated and flexible operation state monitoring of each monitored object, and cannot reflect the actual monitoring requirement of each monitored object client. On the other hand, when the number of alarms reported by the monitored object client increases rapidly, the matching computation of the monitoring end increases rapidly, and if the alarm template file is not maintained and updated in time, the problem of alarm missing is easily caused, so that some alarm data of serious levels or some sensitive alarm data may be lost.
In order to solve the above problems, embodiments of the present application provide a data acquisition method, which reduces processing load of a first device, that is, a monitoring end, on alarm data and a probability of loss of the alarm data, and can set a corresponding target format file according to a second device, so that the first device monitors the second device more flexibly and comprehensively.
Fig. 2 is a schematic flowchart of a first data acquisition method applied to a first device according to an embodiment of the present disclosure. It should be noted that the data acquisition method applied to the first device may be implemented by a processor of the first device. The Processor of the first Device may be at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, and a microprocessor.
In one embodiment, the first device may be an electronic device that is on the same cloud platform as the at least one second device and is capable of monitoring the at least one second device. The cloud platform may be the government affair cloud mentioned above, and may also be a cloud computing platform such as Openstack. The first device may be a device capable of monitoring at least one of an operating system operating state, a hardware usage, an application operating state, a process and/or thread operating state, and the like, in the at least one second device. The hardware may include a network card, a port, a hard disk, and the like.
In one embodiment, the first device may be an electronic device configured with an environment having a monitoring function. Illustratively, the environment of the monitoring function may be ansible. The ansable is an automatic operation and maintenance tool, and is developed based on Python, so that functions of batch system configuration, batch program deployment, batch operation commands and the like are realized.
In one embodiment, the type of the at least one second device may be different, and for example, the type of the second device may be differentiated according to functions, such as a control node and a computing node in Openstack. Illustratively, any second device may be equipped with a device capable of collecting and acquiring application software of the operating state of the second device. The application software may include an application monitoring box.
In one embodiment, any of the second devices may be a Sensu-configured device. Where Sensu is an open source infrastructure and application monitoring solution that can monitor server, related services and application health and send alerts and notifications through third party integration. Sensu is written in Ruby and can use a RabbitMQ or Redis to process messages, which uses Redis to store data.
In an embodiment, the first device monitors the at least one second device by acquiring the specific type of operation status information sent by the at least one second device. Illustratively, the first device may be monitoring the second device when a specified condition is met. Wherein, the specified condition may include at least one of the following: the carrying load of the at least one second device exceeds a preset threshold, the designated operation time period of the at least one second device, the operation mode of the at least one second device is switched, the number of the connections established between the at least one second device and the access client exceeds a designated value, and the like.
As shown in fig. 2, the data obtaining method provided in the embodiment of the present application may include the following steps:
The target format file is used for any second device to obtain at least one state data and arrange the at least one state data to obtain alarm data carrying type information.
In one embodiment, the type information may indicate the type of the alarm data, and may also be identification information defined in the object format file.
In one embodiment, the status data may represent operation status data of any second device, or operation status data of a specified type of any second device, or operation status data within a specified time period of any second device, or operation status data sent when any second device meets a specified condition.
In one embodiment, the status data may include hardware operational status data or software operational status data of the second device. The hardware running state data may include memory utilization rate, hard disk utilization rate, network card load rate, port occupation condition, and the like; the software running state data may include operating system running state data, application software running state data, process running state data, thread running state data, and the like.
In one embodiment, the object format file may include at least one type of information. Wherein the type information may indicate at least one of a device type of the second device, a type of the status data; the method can also comprise the steps of sorting at least one type of state data to obtain a rule of alarm data carrying type information; conditions and timing for acquiring at least one status data may also be included. For example, the target format files corresponding to different second devices may be different.
In one embodiment, sending the target-format file to any of the second devices may be an operation performed immediately after the target-format file is determined, or may be an operation performed after any of the second devices is ready.
In an implementation manner, the alarm data sent by any second device may be data obtained by sorting the state data according to the target format file, and may carry information such as original state information corresponding to the state data, an alarm level corresponding to the state information, type information corresponding to the state information, and a source of the state information.
As can be seen from the above, in the data acquisition method applied to the first device, the first device can monitor the at least one second device through the communication connection with the at least one second device; after determining that the target format file corresponding to any second device is used for any second device to obtain at least one type of state data and sort the state data to obtain the alarm data carrying the type information, the target format file can be sent to any second device through communication connection, and the alarm data carrying the type information sent by any second device can also be received.
Therefore, the data acquisition method applied to the first device provided by the embodiment of the application can set the corresponding target format file according to the requirement for monitoring any second device, so that the second device can acquire the required state data to obtain the alarm data corresponding to the monitoring requirement, and thus, on one hand, the first device can monitor any second device more flexibly and comprehensively, and the probability of data loss caused by the fact that the new type state data of any second device cannot be matched can be reduced; on the other hand, when the first device is a server device, the load generated by performing matching operation on the alarm data again by the monitoring server in the related art can be relieved.
Based on the foregoing embodiments, the present application provides a data acquisition method applied to a first device.
Fig. 3 is a schematic flowchart illustrating a second data acquisition method applied to a first device according to an embodiment of the present disclosure. The data acquisition method may include the steps of:
Each function configuration file comprises any second device for acquiring any type of state data and rules for sorting any type of state data.
In one embodiment, each function profile may include at least one type of acquisition rule for status data and a collation rule.
In one embodiment, the obtaining rule of the state data may include conditions and timing for obtaining the state data; or may include a determination rule for obtaining a range of types of status data; or rules that include a determination of the manner of acquisition of the status data.
In one embodiment, the state data acquiring rule may be embodied by a state data acquiring script. Illustratively, the state data acquisition script may be a rule that constrains at least one of a type, condition, timing, manner, state data storage location, etc. of the state data to be acquired. For example, the obtaining rule of the status data may include a plurality of obtaining rules. For example, the first acquisition rule may indicate an opportunity to acquire the status data; the second acquisition rule may indicate a condition for acquiring the status data, and the like.
In one embodiment, the rules for organizing the status data may include at least one of: rules for screening and sorting status data, rules for quantizing and classifying status data according to quantization results, and rules for adding type information to sorting results of status data. For example, the type information may be embodied in the form of identification information, and the identification information may be included in each function profile.
In one embodiment, each function profile may be determined by an application or system with monitoring function installed in the first device or an automated monitoring tool installed in the first device. Each function profile may be obtained, for example, by an ansable installed in the first device. Illustratively, each function profile may be a. yml file defined in the ansable.
Yml files may be embodied, for example, as follows:
{ name: mem _ use, command: "check-memory-percent", type: "memory", and align _ title: "memory utilization exceeds threshold", oid:1.3.6.1.4.1.49022.2.21.2.1.5}
In the code, name, mem _ use, command, check-memory-percent, type, memory, arm _ title, memory utilization exceeding a threshold and oid:1.3.6.1.4.1.49022.2.21.2.1.5 are all in the form of key-value pairs.
The name is mem _ use, and the name which indicates the state parameter required to be acquired in the current function configuration file is mem _ use; the command indicates that the command to be executed in the current function configuration file is check-memory-percent; the type of the state parameter acquired from the current function configuration file is 'memory'; the alarm _ title is used for indicating that the alarm _ title corresponding to the acquired state data in the current function configuration file is 'the memory utilization rate exceeds the threshold'; OID:1.3.6.1.4.1.49022.2.21.2.1.5, the Object Identification (OID) of the state parameter that represents the current function profile acquisition is "1.3.6.1.4.1.49022.2.21.2.1.5".
In an embodiment, the check-memory-percentage corresponding to the command may be an underlying monitoring instruction, or a script that can be automatically executed, or a script that can be triggered to be executed when a certain condition is met.
In one embodiment, multiple x. yml files may be defined, such as first.yml, second.yml, and third.yml, among others. Each of these documents yml has only one type of status data constrained.
In one embodiment, the target format file is determined based on at least one function configuration file, and the target format file may be determined by combining at least one function configuration file and performing a compaction and combination process on a combination result.
In one embodiment, step 302 may be further implemented by step a 1-step A3:
and step A1, acquiring a requirement configuration file.
The requirement configuration file represents requirement data of any second equipment for acquiring at least one state data.
In one embodiment, the requirement profile may be determined according to any one of the following conditions: the method comprises the following steps of monitoring the requirement of any second device, the operating characteristic of any second device, the attribute parameter of any second device, an operating system loaded by any second device, the function of any second device, an application program with higher operating frequency, the load of data processing, the type of processing data, the type facing a client, the time period for initiating data access by the client and the like.
In one embodiment, the requirement profile may be sent to the first device by any of the second devices, or set by and stored in the first device.
Step A2, integrating at least one function configuration file based on the demand configuration file to obtain an integrated result.
In one embodiment, the integration result may be obtained by:
selecting a target function configuration file from at least one function configuration file based on the requirement configuration file, and integrating the target function configuration file to obtain an integration result; or after the target function configuration files are obtained, removing redundant information in each target function configuration file, and integrating the removal results to obtain an integration result.
Step A3, based on the integration result, determining the target format file.
In one embodiment, the target format file is determined based on the integration result, which may be determined by integrating the obtaining rule and the sorting rule of the plurality of status parameters in the integration result.
In an embodiment, after determining the target format file based on the integration result, a network Protocol (IP) address of the second device corresponding to the target format file, and a user name and a password may be added to the integration result, so as to obtain the target format file.
In one embodiment, the determined target format file may represent the role played by any second device in the monitored process based on the integration result, and therefore, the target format file may also be referred to as a role definition file.
In one embodiment, under the condition that the function configuration file is the × yml file, the corresponding first target format file ff.yml may be in the form of:
in the above code, checks represent process keywords; common represents a parameter list needing to be monitored; the data in the first { } corresponds to a first function profile; the data in the second { } corresponds to a second function profile.
In the above code, the data in each { } is organized in key-value pairs.
In the code, name is cpu _ use, which indicates that the name of the state data is "cpu _ use"; command, "/opt/sensory/embedded/bin/Ruby/opt/sensory/embedded/bin/check-cpu. rb-w85-c 90", indicating that the command for acquiring the monitoring data is "/opt/sensory/embedded/bin/Ruby/opt/sensory/embedded/bin/check-cpu. rb-w85-c 90"; type "CPU", which indicates that the type of the monitored status data is "CPU"; the "CPU utilization rate exceeds the threshold value" indicates that the alarm data corresponding to the state data has the "CPU utilization rate exceeds the threshold value"; OID:1.3.6.1.4.1.49022.2.15.2.1.3.48, the OID corresponding to the alarm data is "1.3.6.1.4.1.49022.2.15.2.1.3.48".
In the above code, name _ use, which indicates that the name of the state data is "disk _ usag"; command, "/opt/sensory/embedded/bin/rub/opt/sensory/check-disk-use. rb-t xfs, ext4-w 85" "/opt/sensory/embedded/bin/rub/opt/sensory/embedded/bin/check-disk-use. rb-t xfs, ext4-w 85"; type: "disk", which means that the type of the monitored status data is "disk"; the alarm _ title is that the utilization rate of the disk space exceeds a threshold value, and the alarm _ title of the alarm data corresponding to the state data is shown as that the utilization rate of the disk space exceeds the threshold value; OID:1.3.6.1.4.1.49022.2.21.2.1.4, the OID corresponding to the alarm data is "1.3.6.1.4.1.49022.2.21.2.1.4".
In one embodiment, under the condition that the function configuration file is the × yml file, the corresponding first target format file ff.yml may be in the form of:
in the code, name is interface, and the name of the monitored state data is 'interface'; command, "/opt/send/embedded/bin/check _ linux _ binding-disable-sysfs", means that command for acquiring monitoring data is "/opt/send/embedded/bin/check _ linux _ binding-disable-sysfs"; the type represents the monitored state data, namely the type is the network card; the alarm data corresponding to the state data is called 'network card exception'; OID:1.3.6.1.4.1.49022.2.21.2.1.3, the OID corresponding to the alarm data is "1.3.6.1.4.1.49022.2.21.2.1.3".
In the code, name is swap _ use, which indicates that the name of the state data is swap _ use; "command/opt/sensory/embedded/bin/rub/opt/sensory/bin/check-swap-character. rb-w85-c 90" represents "command/opt/sensory/embedded/bin/rub/opt/sensory/embedded/bin/check-swap-character. rb-w85-c 90" for acquiring monitoring data; type: "SWAP", which means that type of the monitored status data is "SWAP"; the alarm _ title indicates that the alarm _ title of the alarm data corresponding to the state data is 'the SWAP utilization rate exceeds the threshold'; OID:1.3.6.1.4.1.49022.2.15.2.1.3.51, the OID corresponding to the alarm data is "1.3.6.1.4.1.49022.2.15.2.1.3.51".
Illustratively, step 303 may also be implemented by:
and under the condition that the first equipment is connected through communication and detects that any second equipment is in an environment ready state, the target format file is sent to any second equipment through the communication connection.
And the environment ready state indicates that any second device is in a state of configuring the environment for acquiring the state data.
In one embodiment, the environment ready state may indicate that any second device has successfully installed an application that captures at least one of any type of state data, and that the application is already in a ready state; or any second device has been successfully configured with a framework that captures at least one of any type of status data and that is capable of normal operation; or any second device has successfully installed a client with a monitoring function, such as a Sensu client, and the Sensu client can operate normally.
In an embodiment, in the process of sending the target format file to any second device through communication connection, the target format file may be converted according to the monitoring environment configured in the first device and the monitoring environment configured in any second device, so as to obtain data with a simpler format.
In one embodiment, the more compact format may be a lightweight data exchange format. A more compact format may be a JavaScript Object Notation (JSON).
Illustratively, one possible JSON format of data is as follows:
in the above code, all data is stored in the form of key value pairs, for example, the keys of checks correspond to the keywords checks in the foregoing file, and the corresponding values are:
in the above codes, command, interval, handle, address _ type, address _ oil, and standalone are all keys in the JSON data format, and data following the colon of each key above indicates a value corresponding to each key.
In the above code, the item corresponds to data in each { } of the keyword common in the target format file. The item.name is the same as a key value corresponding to the keyword name in each { } in the target format file, and may be "cpu _ use" as an example; command is the same as the key value corresponding to the keyword command in each { } in the target format file, and can be "/opt/sensu/embedded/bin/Ruby/opt/sensu/embedded/bin/check-cpu. rb-w85-c 90"; type is the same as the key value corresponding to the keyword type in each { } in the target format file, and exemplarily, the item type may be "CPU"; item _ aim _ title corresponds to a keyword (aim _ title) in each { } in the object format file, and may be, for example, "CPU utilization exceeds a threshold"; item can be the same as the key value corresponding to the keyword oid in each { } in the target format file, and can be "1.3.6.1.4.1.49022.2.15.2.1.3.48" for example; .
In the above code, the value corresponding to interval is 300, which may represent the time interval of status data acquisition, and the unit thereof may be milliseconds; the value corresponding to the handler is "SNMP", which indicates that the status data sent to the first device is packaged into a Simple Network Management Protocol (SNMP) trap message format. SNMP is a part of TCP/IP protocol family, and management information can be conveniently exchanged among devices through SNMP; the value of standalone is true, which may indicate that the monitoring framework in the second device is capable of operating independently.
Illustratively, the actual JSON data corresponding to the above JSON format may be as follows:
the meaning of each key-value pair in the above code has been described previously and is not described herein again.
Compared with the yml file, the JSON format is simpler, the data composition is clearer, and therefore convenience is provided for any second device to acquire state data and fill the state data.
For example, the data acquisition method provided by the embodiment of the present application may further implement configuration of any second device environment state through steps B1-B2:
and step B1, acquiring the device identification of any second device.
In one embodiment, the device identifier of any second device may include a physical address of any second device, an IP address of any second device, or a user name and a password of any second device.
In an embodiment, the device identifier of any second device may be sent to the first device by any second device, or obtained according to a requirement configuration file.
In one embodiment, the device identification of any second device may be added to the host field in the x. yml file, as follows:
[1]
83.245.2.33
[2]
83.245.2.32
[physicalservers:children]
1
2
in the above code, [1]83.245.2.33 denotes that the IP address of the first second device is 83.245.2.33; [2]83.245.2.32 indicates that the second device has an IP address of 83.245.2.32; children 12 indicates that the physical servers group includes the first and second devices, that is, the current monitoring target of the first device includes the first and second devices.
And step B2, sending the environment configuration instruction to any second equipment through the communication connection based on the equipment identification.
And the environment configuration instruction is used for configuring an environment for acquiring at least one type of state data by any second equipment.
In one embodiment, the environment configuration instruction may include an environment that any second device can configure, for example, any second device can configure a Sensu client. That is, the environment in which the different second device is configured may be determined according to actual parameters of the second device.
Exemplarily, sending the environment configuration instruction to any second device under the condition that the infrastructure is deployed in the first device may be implemented by batch deployment of the infrastructure. The first device can perform batch deployment operation through the ansable according to the specific monitoring requirement of any second device.
Illustratively, the specific monitoring requirement includes an attribute parameter of any second device, wherein the attribute parameter of any second device may include a hardware attribute parameter and/or a software attribute parameter of any second device. The hardware attribute parameters include hardware configuration of any second device, such as a CPU master frequency, memory capacity, a hard disk, a network card, a port, and the like; the software attribute parameters comprise an operating system installed on any second device, target application software needing to be monitored, a target thread needing to be monitored, a target process needing to be monitored and the like. In this way, targeted monitoring of multiple second devices by the first device can be achieved.
In one embodiment, the first device may instruct each second device to complete the installation of the Sensu client through the batch deployment of the ansable, so that each second device can successfully configure an environment for acquiring at least one of any type of state data.
In one embodiment, the environment configuration command sent by the first device may be executed simultaneously with sending the object format file. For example, the target format file may be sent to any second device as an additional parameter of the environment configuration instruction, and after the second device performs the environment configuration operation based on the environment configuration instruction, the target format file may be directly parsed.
Through the above operations, after the second device completes the environment for acquiring at least one of any type of state data according to the environment configuration instruction sent by the first device, the first device may detect that the second device is in an environment ready state through the communication connection.
And step 304, acquiring alarm data sent by any second equipment through communication connection.
Fig. 4 is a flowchart of a specific implementation of the data acquisition method according to the embodiment of the present application.
As shown in fig. 4, under the condition that an ansable, a function configuration file, and a target format file are installed in a first device yml, and a Sensu client is installed in any second device, a specific implementation flowchart of the data acquisition method provided in the embodiment of the present application may include the following steps:
Illustratively, there may be more than one number of function profiles.
And step 403, acquiring a target format file (· yml) corresponding to each second device.
For example, the target format file corresponding to each second device may be different.
Illustratively, the definition host field may determine a monitoring object of the first device, i.e., the second device.
Through the operations of step 403 and step 404, the monitoring role of any second device can be determined, i.e. differential monitoring of at least one second device is achieved.
And step 405, executing an ansable instruction to install the Sensu client.
Illustratively, executing the ansable instruction to install the Sensu client may be an operation that the first device instructs any of the second devices to perform.
Illustratively, the completion of the installation may indicate that the Sensu is successfully installed in any of the second devices, and the information that the Sensu is successfully installed in any of the second devices may be sent by the second devices to the first device.
So far, the environment for monitoring and acquiring the state data between the first device and at least one second device is configured.
As can be seen from the above, when the data obtaining method provided in the embodiment of the present application is applied to a first device, at least one function configuration file indicating a rule that any second device obtains any type of status data and arranges the any type of status data is obtained, a target format file for any second device to obtain at least one type of status data and arrange the at least one type of status data to obtain alarm data carrying type information is determined based on the at least one function configuration file, the target format file is sent to any second device through a communication connection between the first device and any second device, and then the alarm data sent by any second device is obtained.
Therefore, according to the data acquisition method provided by the embodiment of the application, the target format file corresponding to any second equipment is determined in the first equipment and is sent to any second equipment, so that any second equipment can acquire state data and arrange the state data to obtain alarm data carrying type information, on one hand, the calculated amount of performing type matching after the first equipment receives the alarm data is reduced, and on the other hand, flexible and high-pertinence monitoring on any second equipment is realized; and moreover, according to the target format file acquired by any second device, the omission probability of new types of alarm data in any second device is reduced.
Based on the foregoing embodiments, the present application provides a data acquisition method applied to a second device. The first equipment and the second equipment are connected in a communication mode, and the first equipment can monitor the second equipment through the communication connection.
Fig. 5 is a flowchart illustrating an implementation of a data obtaining method applied to a second device according to an embodiment of the present application. The method may be implemented by a processor of the second device.
The processor of the second device may be at least one of an application specific integrated circuit ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, and microprocessor.
In fig. 5, the data obtaining method applied to the second device according to the embodiment of the present application may include the following steps:
The target format file is determined by the first device and used for the second device to obtain at least one state data and arrange the at least one state data to obtain the alarm data carrying the type information.
In an embodiment, the obtaining of at least one type of status data based on the target format file, and sorting the at least one type of status data to obtain the alarm data may be implemented by:
and integrating the target format file to obtain an alarm template. The alarm template may be more concise data than the format of the target format file. Illustratively, the alarm template may be JSON data. And each valid data in the object format file is carried in the JSON data. Illustratively, the integrating the target format file to obtain the alarm template may be performed after the environment configuration is successful in the second device.
As can be seen from the above, in the data obtaining method applied to the second device, a communication connection is established between the second device and the first device, the first device can monitor the second device through the communication connection, the second device can receive the target format file sent by the first device through the communication connection, obtain at least one type of state data based on the target format file, then sort the at least one type of state data to obtain the alarm data, and send the alarm data to the first device.
Therefore, according to the data acquisition method applied to the second device provided by the embodiment of the application, after receiving the target format file sent by the first device, the second device can acquire the state data according to the target format file and arrange the state data, so that the first device can flexibly and pertinently monitor the second device; moreover, because the target format file corresponds to the second device, the probability of losing the new type of state data in the second device is also reduced; moreover, after the second device sorts the state data to obtain the alarm data carrying the type information, the alarm data is sent to the first device, and the operation amount of obtaining the alarm data of the accurate type by performing type matching on the state data after the first device receives each state data is also reduced.
In some embodiments, before step 501, the second device may further receive, through the communication connection, the environment configuration instruction sent by the first device. And configuring the environment for acquiring the state data based on the environment configuration instruction.
And the environment configuration instruction is used for configuring the environment for acquiring at least one state data of any type by the second equipment.
In some embodiments, step 502 may be implemented by step C1-step C3:
and step C1, acquiring the first rule and the second rule based on the target format file.
The first rule comprises a mode that the second equipment acquires at least one state data; and the second rule comprises a rule for sorting at least one type of state data.
In one embodiment, the first rule and the second rule are obtained based on the target format file, and the method may be that an alarm template is obtained based on the target format file, and then the first rule and the second rule are obtained based on the alarm template.
In one embodiment, the first rule may include information on the type, timing, condition, etc. of the acquired status data; the second rule may include at least one of a script or a method for collating the at least one type of status data.
And step C2, acquiring at least one state data based on the first rule.
In one embodiment, the at least one status data is obtained based on the first rule, and the at least one status data is obtained based on information such as type, timing, condition, and the like of the obtained status data.
And step C3, based on the second rule, sorting each type of state data in the at least one type of state data to obtain alarm data.
In one embodiment, the alarm data may be based on a script or method for sorting at least one status data, and the at least one status data is sorted according to the script or method, so as to obtain the alarm data.
In one embodiment, the alarm data obtained by the second device carries information such as an alarm level, an alarm type, a second device identifier, and an alarm occurrence time.
Based on the foregoing embodiments, embodiments of the present application provide a data acquisition method applied to a first device and a second device. Fig. 6 is a flowchart illustrating a data acquisition method applied to a first device 601 and a second device 602 according to an embodiment of the present application.
In fig. 6, first, a communication connection is established between a first device 601 and a second device 602; secondly, the first device 601 performs a status check to determine whether the second device 602 is in an environment ready state; then, in the case of detecting that the second device is in an environment ready state, the first device 601 sends a target format file to the second device 602; finally, the second device 602 sends the alarm data to the first device 301, and illustratively, after receiving the target format file, the second device 602 obtains the status data based on the target format file, and obtains the alarm data according to the status data.
As can be seen from the above, the data acquisition method applied to the first device 601 and the second device 602 provided in the embodiment of the present application reduces the computation amount of the first device for matching the alarm data type; the method and the device realize flexible and more targeted monitoring on the second equipment and reduce the probability of losing the new type of state data in the second equipment.
Based on the foregoing embodiments, fig. 7 is a schematic structural diagram of a first device 601 provided in this embodiment of the present application. In the first device 601 provided in the embodiment of the present application, a communication connection is established between the first device 601 and at least one second device 602, and the at least one second device 602 is monitored; the first device includes: a first processing module 701, a first sending module 702 and a first receiving module 703; wherein:
a first processing module 701, configured to determine a target format file corresponding to any second device; the target format file is used for any second device to obtain at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
a first sending module 702, configured to send the target format file to any second device through a communication connection.
The first receiving module 703 is configured to obtain, through a communication connection, alarm data sent by any second device.
In some embodiments, the first processing module 701 is configured to obtain at least one function configuration file; each function configuration file comprises any second device for acquiring any type of state data and rules for sorting any type of state data.
The first processing module 701 is further configured to determine a target format file based on the at least one function configuration file.
In some embodiments, the first processing module 701 is configured to obtain a requirement configuration file; the requirement configuration file represents requirement data of any second equipment for acquiring at least one state data.
The first processing module 701 is further configured to integrate at least one function configuration file based on the requirement configuration file to obtain an integration result; and determining the target format file based on the integration result.
In some embodiments, the first sending module 702 is configured to send the target format file to any second device through a communication connection if the first device detects that any second device is in an environment ready state through the communication connection; and the environment ready state represents that any second equipment is in a state of being configured to acquire at least one state data environment of any type.
It should be noted that, for example, the first processing module 701, the first sending module 702, and the first receiving module 703 may be implemented by a processor of the first device, and specifically, the processor may be at least one of an application specific integrated circuit ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, and a microprocessor. It is understood that the electronic device for implementing the above-mentioned processor function may be other electronic devices, and the embodiments of the present application are not particularly limited.
Thus, the first device 601 provided in this embodiment of the present application can set a corresponding target format file according to a need for monitoring any second device 602, so that the second device 602 can obtain required state data to obtain alarm data corresponding to a monitoring need, on one hand, the first device 601 can monitor any second device 602 more flexibly and comprehensively, and can also reduce a probability of data loss caused by a fact that new type state data of any second device 602 cannot be matched; on the other hand, when the first device 601 is a server device, the load caused by performing matching operation again on the received alarm data by the monitoring server in the related art can be alleviated.
Based on the foregoing embodiments, the present application provides a second device 602. Fig. 8 is a schematic structural diagram of a second device 602 according to an embodiment of the present disclosure.
In fig. 8, a communication connection is established between a second device 602 and a first device 601; the second device 602 includes a second receiving module 801, a second processing module 802, and a second sending module 803; wherein:
a second receiving module 801, configured to receive, through a communication connection, a target format file sent by a first device; the target format file is determined by the first equipment and used for the second equipment to acquire at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
the second processing module 802 is configured to obtain at least one type of state data based on the target format file, and sort the at least one type of state data to obtain alarm data;
a second sending module 803, configured to send the alarm data to the first device through the communication connection.
In some embodiments, the second processing module 802 is configured to obtain the first rule and the second rule based on the target format file; the first rule comprises a mode that the second equipment acquires at least one state data; a second rule comprising a rule for collating at least one status data;
the second processing module 802 is further configured to obtain at least one status data based on the first rule; and based on the second rule, sorting the state data of each type in the at least one type of state data to obtain alarm data.
It should be noted that, for example, the second receiving module 801, the second processing module 802, and the second sending module 803 may be implemented by a processor of the second device, and specifically, the processor may be at least one of an application specific integrated circuit ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, and a microprocessor. It is understood that the electronic device for implementing the above-mentioned processor function may be other electronic devices, and the embodiments of the present application are not limited in particular.
After receiving the target format file sent by the first device 601, the second device 602 provided in the embodiment of the application can acquire the state data according to the target format file and arrange the state data, thereby implementing flexible and targeted monitoring of the second device 602 by the first device 601; moreover, since the object format file corresponds to the second device 602, the probability that the new type of state data in the second device 602 is lost is also reduced; moreover, after the second device 602 sorts the state data to obtain the alarm data carrying the type information, the alarm data is sent to the first device 601, which also reduces the amount of operation that the first device 601 can obtain the accurate type of alarm data by performing type matching on the state data after receiving each state data.
Based on the foregoing embodiments, the present application provides a data acquisition system 9. Fig. 9 is a schematic structural diagram of a data acquisition system 9 according to an embodiment of the present application. As shown in fig. 9, the data acquisition system 9 includes a first device 601 and a second device 602 according to any of the previous embodiments.
Based on the foregoing embodiments, the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements any one of the foregoing data acquisition methods applied to a first device or any one of the foregoing data acquisition methods applied to a second device.
In some embodiments, functions of or modules included in the apparatus provided in the embodiments of the present invention may be used to execute the method described in the above method embodiments, and specific implementation thereof may refer to the description of the above method embodiments, and for brevity, will not be described again here.
The foregoing description of the various embodiments is intended to highlight various differences between the embodiments, and the same or similar parts may be referred to each other, and for brevity, will not be described again herein.
The methods disclosed in the method embodiments provided by the present invention can be combined arbitrarily without conflict to obtain a new method embodiment.
Features disclosed in each product embodiment provided by the invention can be combined arbitrarily to obtain a new product embodiment without conflict.
The features disclosed in the method or device embodiments of the invention may be combined in any combination to arrive at new method or device embodiments without conflict.
The computer-readable storage medium may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a magnetic Random Access Memory (FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical Disc, or a Compact Disc Read-Only Memory (CD-ROM); and may be various electronic devices such as mobile phones, computers, tablet devices, personal digital assistants, etc., including one or any combination of the above-mentioned memories.
It should be noted that, in this document, 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 like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, and an optical disk), and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method described in the embodiments of the present application.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all the equivalent structures or equivalent processes that can be directly or indirectly applied to other related technical fields by using the contents of the specification and the drawings of the present application are also included in the scope of the present application.
Claims (10)
1. The data acquisition method is applied to first equipment, and the first equipment can monitor at least one second equipment through communication connection with the second equipment; the method comprises the following steps:
determining a target format file corresponding to any second device; the target format file is used for the any second equipment to acquire at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
sending the target format file to any second device through the communication connection;
and acquiring the alarm data sent by any second equipment through the communication connection.
2. The method of claim 1, wherein determining the object format file corresponding to the any second device comprises:
acquiring at least one function configuration file; each function configuration file comprises any type of state data acquired by any second equipment and rules for sorting any type of state data;
determining the object format file based on at least one of the function profiles.
3. The method of claim 2, wherein determining the object format file based on the at least one function configuration file comprises:
acquiring a requirement configuration file; wherein the requirement configuration file represents requirement data of the at least one state data acquired by any one second device;
integrating at least one function configuration file based on the requirement configuration file to obtain an integration result;
and determining the target format file based on the integration result.
4. The method of claim 1, wherein said sending the object format file to the any second device via the communication connection comprises:
under the condition that the first equipment detects that any second equipment is in an environment ready state through the communication connection, the target format file is sent to any second equipment through the communication connection; wherein the environment ready state indicates that any second device is in a state in which a state data environment has been configured.
5. A data acquisition method is characterized in that the method is applied to second equipment, communication connection is established between the second equipment and first equipment, and the first equipment can monitor the second equipment through the communication connection; the method comprises the following steps:
receiving a target format file sent by the first equipment through the communication connection; the target format file is determined by the first device and used for the second device to obtain at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
acquiring the at least one state data based on the target format file, and sorting the at least one state data to obtain the alarm data;
and sending the alarm data to the first equipment through the communication connection.
6. The method according to claim 5, wherein the obtaining the at least one status data based on the object format file and sorting the at least one status data to obtain the alarm data comprises:
acquiring a first rule and a second rule based on the target format file; wherein the first rule includes a manner in which the second device acquires the at least one status data; the second rule comprises a rule for sorting the at least one state data;
acquiring the at least one state data based on the first rule;
and sorting each type of state data in the at least one type of state data based on the second rule to obtain the alarm data.
7. A first device, wherein a communication connection is established between the first device and at least one second device, and at least one of the second devices is monitored; the first device includes: the device comprises a first processing module, a first sending module and a first receiving module; wherein:
the first processing module is used for determining a target format file corresponding to any second device; the target format file is used for the any second equipment to acquire at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
the first sending module is configured to send the target format file to any one of the second devices through the communication connection;
the first receiving module is configured to obtain the alarm data sent by any one of the second devices through the communication connection.
8. A second device, wherein a communication connection is established between the second device and the first device; the second device comprises a second receiving module, a second processing module and a second sending module; wherein:
the second receiving module is configured to receive, through the communication connection, the target format file sent by the first device; the target format file is determined by the first device and used for the second device to obtain at least one state data and arrange the at least one state data to obtain alarm data carrying type information;
the second processing module is configured to obtain the at least one type of state data based on the target format file, and sort the at least one type of state data to obtain the alarm data;
the second sending module is configured to send the alarm data to the first device through the communication connection.
9. A data acquisition system, characterized in that the data acquisition system comprises a first device according to claim 7 and a second device according to claim 8.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the data acquisition method of any one of claims 1 to 4 or 5 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011503058.XA CN114650218B (en) | 2020-12-17 | 2020-12-17 | Data acquisition method, device, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011503058.XA CN114650218B (en) | 2020-12-17 | 2020-12-17 | Data acquisition method, device, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114650218A true CN114650218A (en) | 2022-06-21 |
| CN114650218B CN114650218B (en) | 2023-12-12 |
Family
ID=81991523
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011503058.XA Active CN114650218B (en) | 2020-12-17 | 2020-12-17 | Data acquisition method, device, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114650218B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115834333A (en) * | 2022-11-24 | 2023-03-21 | 苏州睿芯通量科技有限公司 | Multi-type equipment monitoring method and device, electronic equipment and storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102035685A (en) * | 2010-12-20 | 2011-04-27 | 中兴通讯股份有限公司 | Alarm treating method and DPI (Deep Packet Inspection) device |
| CN106961352A (en) * | 2017-03-29 | 2017-07-18 | 努比亚技术有限公司 | Monitoring system and monitoring method |
| CN106998265A (en) * | 2017-03-14 | 2017-08-01 | 中国银联股份有限公司 | A kind of monitoring method and its device |
| CN108270618A (en) * | 2017-12-30 | 2018-07-10 | 杭州华为数字技术有限公司 | Alert the method, apparatus and warning system of judgement |
| CN108829560A (en) * | 2018-06-01 | 2018-11-16 | 平安科技（深圳）有限公司 | Data monitoring method, device, computer equipment and storage medium |
| CN109245966A (en) * | 2018-11-05 | 2019-01-18 | 郑州云海信息技术有限公司 | The monitoring method and device of the service state of cloud platform |
| CN109743191A (en) * | 2018-11-28 | 2019-05-10 | 中通服建设有限公司 | A kind of accurate positioning centralized processing system of equipment alarm, method and device |
| CN110048888A (en) * | 2019-04-16 | 2019-07-23 | 深圳市致宸信息科技有限公司 | A kind of method based on zabbix monitoring alarm, server, equipment and storage medium |
| CN110224858A (en) * | 2019-05-16 | 2019-09-10 | 平安科技（深圳）有限公司 | Alarm method and relevant apparatus based on log |
| CN110247811A (en) * | 2019-07-17 | 2019-09-17 | 深圳市智物联网络有限公司 | A kind of alarm method and relevant apparatus of internet of things equipment |
| US20200028701A1 (en) * | 2018-07-19 | 2020-01-23 | Bank Of Montreal | Systems and methods for alert services |
| WO2020029407A1 (en) * | 2018-08-08 | 2020-02-13 | 平安科技（深圳）有限公司 | Alarm data management method and apparatus, and computer device and storage medium |
| US20200073906A1 (en) * | 2017-06-15 | 2020-03-05 | Beijing Gridsum Technology Co., Ltd. | Method, Device, Storage Medium and Processor for Data Acquisition and Query |
-
2020
- 2020-12-17 CN CN202011503058.XA patent/CN114650218B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102035685A (en) * | 2010-12-20 | 2011-04-27 | 中兴通讯股份有限公司 | Alarm treating method and DPI (Deep Packet Inspection) device |
| CN106998265A (en) * | 2017-03-14 | 2017-08-01 | 中国银联股份有限公司 | A kind of monitoring method and its device |
| CN106961352A (en) * | 2017-03-29 | 2017-07-18 | 努比亚技术有限公司 | Monitoring system and monitoring method |
| US20200073906A1 (en) * | 2017-06-15 | 2020-03-05 | Beijing Gridsum Technology Co., Ltd. | Method, Device, Storage Medium and Processor for Data Acquisition and Query |
| CN108270618A (en) * | 2017-12-30 | 2018-07-10 | 杭州华为数字技术有限公司 | Alert the method, apparatus and warning system of judgement |
| WO2019227689A1 (en) * | 2018-06-01 | 2019-12-05 | 平安科技（深圳）有限公司 | Data monitoring method and apparatus, and computer device and storage medium |
| CN108829560A (en) * | 2018-06-01 | 2018-11-16 | 平安科技（深圳）有限公司 | Data monitoring method, device, computer equipment and storage medium |
| US20200028701A1 (en) * | 2018-07-19 | 2020-01-23 | Bank Of Montreal | Systems and methods for alert services |
| WO2020029407A1 (en) * | 2018-08-08 | 2020-02-13 | 平安科技（深圳）有限公司 | Alarm data management method and apparatus, and computer device and storage medium |
| CN109245966A (en) * | 2018-11-05 | 2019-01-18 | 郑州云海信息技术有限公司 | The monitoring method and device of the service state of cloud platform |
| CN109743191A (en) * | 2018-11-28 | 2019-05-10 | 中通服建设有限公司 | A kind of accurate positioning centralized processing system of equipment alarm, method and device |
| CN110048888A (en) * | 2019-04-16 | 2019-07-23 | 深圳市致宸信息科技有限公司 | A kind of method based on zabbix monitoring alarm, server, equipment and storage medium |
| CN110224858A (en) * | 2019-05-16 | 2019-09-10 | 平安科技（深圳）有限公司 | Alarm method and relevant apparatus based on log |
| CN110247811A (en) * | 2019-07-17 | 2019-09-17 | 深圳市智物联网络有限公司 | A kind of alarm method and relevant apparatus of internet of things equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115834333A (en) * | 2022-11-24 | 2023-03-21 | 苏州睿芯通量科技有限公司 | Multi-type equipment monitoring method and device, electronic equipment and storage medium |
| CN115834333B (en) * | 2022-11-24 | 2023-08-29 | 苏州睿芯通量科技有限公司 | Monitoring method and device for multi-type equipment, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114650218B (en) | 2023-12-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110401662B (en) | Industrial control equipment fingerprint identification method and storage medium | |
| CN109918279B (en) | Electronic device, method for identifying abnormal operation of user based on log data and storage medium | |
| CN108494622A (en) | Monitoring rules configuration method, device and server | |
| CN109543891B (en) | Method and apparatus for establishing capacity prediction model, and computer-readable storage medium | |
| CN110933178B (en) | Method for adjusting node configuration in cluster system and server | |
| CN112395156A (en) | Fault warning method and device, storage medium and electronic equipment | |
| CN114650218B (en) | Data acquisition method, device, system and storage medium | |
| CN107426012B (en) | Fault recovery method and device based on super-fusion architecture | |
| CN111224890A (en) | Traffic classification method and system of cloud platform and related equipment | |
| CN113590178B (en) | API instance management method and device, storage medium and electronic equipment | |
| CN116016653A (en) | Information pushing method and device of blockchain, electronic equipment and storage medium | |
| CN112965735B (en) | Model updating method, device, equipment and computer readable medium | |
| CN112416385A (en) | Acquisition component management method and system | |
| CN114706737B (en) | Crash alarm method, device, system, equipment and readable storage medium | |
| CN113971093A (en) | Message processing method, device, equipment and computer storage medium | |
| CN112583825A (en) | Method and device for detecting abnormality of industrial system | |
| CN113487344B (en) | Communication service prediction method, centralized server, edge service terminal and medium | |
| CN113778800B (en) | Error information processing method, device, system, equipment and storage medium | |
| CN112907221B (en) | Self-service method, device and system | |
| CN114629791B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN112733210B (en) | Equipment identifier obtaining method and device and computer readable storage medium | |
| CN106714122B (en) | Short message transmission virus detection method and device | |
| CN113055412B (en) | Sample collection method, apparatus, system, computer device, and readable storage medium | |
| CN110750418B (en) | Information processing method, electronic equipment and information processing system | |
| CN109683926B (en) | Network component updating method, device, equipment and computer readable storage medium |
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 |