CN106992903B - Data acquisition system and method based on network equipment - Google Patents
Data acquisition system and method based on network equipment Download PDFInfo
- Publication number
- CN106992903B CN106992903B CN201710199399.4A CN201710199399A CN106992903B CN 106992903 B CN106992903 B CN 106992903B CN 201710199399 A CN201710199399 A CN 201710199399A CN 106992903 B CN106992903 B CN 106992903B
- Authority
- CN
- China
- Prior art keywords
- engine
- data
- monitoring
- acquisition
- command
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 22
- 238000012544 monitoring process Methods 0.000 claims abstract description 106
- 238000009434 installation Methods 0.000 claims abstract description 12
- 238000012545 processing Methods 0.000 claims description 12
- 238000012423 maintenance Methods 0.000 claims description 2
- 238000013480 data collection Methods 0.000 claims 3
- 238000011897 real-time detection Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 10
- 238000011161 development Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- 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/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- 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/08—Configuration management of networks or network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
Abstract
The invention provides a data acquisition system and method based on network equipment, the system includes gathering engine and rule engine; the acquisition engine comprises an acquisition controller, a timing scheduling frame, a message service interface, a command control plug-in, an equipment discovery plug-in, an equipment acquisition plug-in and a rule engine; when the acquisition system is started, automatically loading a timing frame, and starting a plug-in by the timing frame to acquire equipment data after the specified time is reached; the acquisition controller is used for receiving a system monitoring control command; after the equipment acquisition plug-ins are installed, the acquisition controller sequentially starts the equipment acquisition plug-ins according to the installation sequence, and distributes scheduling operation and data report for the equipment acquisition plug-ins in the starting process; and after the equipment acquisition plug-in is started, equipment data is acquired according to the corresponding monitoring protocol tool of the previously distributed scheduling operation, and the data is reported to the rule engine through the message service interface. The application of the method realizes real-time detection, flexible deployment across regions and hot deployment of monitoring agents.
Description
Technical Field
The invention belongs to the field of data acquisition, and particularly relates to a data acquisition system and method based on network equipment.
Background
With the continuous deepening of information application, the dependence degree of enterprises on information systems becomes more compact. The failure of any application device can have a great impact on the normal operation of the service. Therefore, the data of configuration, operation, performance and the like of network resources (such as firewalls, switches, routers, hosts, middleware, databases and the like) are collected, and a basis is provided for effectively judging the operation condition of the equipment. However, similar tools are available in the market in a manner of operating in an integrated manner with the system using a thread pool.
Based on J2EE and NET as basic technical platform, the self development technology adopts SNMP, SSH, PING, JDBC and other protocols to collect, display and manage the running state and configuration information of network equipment, host, database and middleware.
Disclosure of Invention
In view of this, the present invention provides a data acquisition system and method based on network devices.
The invention adopts the following technical scheme: a data acquisition system based on network equipment comprises an acquisition engine and a rule engine; the acquisition engine comprises an acquisition controller, a timing frame, a message service interface, a command control plug-in, an equipment discovery plug-in and an equipment acquisition plug-in; when the acquisition system is started, automatically loading a timing frame, and starting a plug-in by the timing frame to acquire equipment data after the specified time is reached; the acquisition controller is used for receiving a system monitoring control command; after the equipment acquisition plug-ins are installed, the acquisition controller sequentially starts the equipment acquisition plug-ins according to the installation sequence, and distributes scheduling operation and data report for the equipment acquisition plug-ins in the starting process; and after the equipment acquisition plug-in is started, equipment data is acquired according to the corresponding monitoring protocol tool of the previously distributed scheduling operation, and the data is reported to the rule engine through the message service interface.
Furthermore, the system also comprises a monitoring engine for monitoring and processing the collected data.
Preferably, the monitoring engine operation framework uses an Apache Felix framework, the main controller receives a system console command to perform the operations of installing, starting, stopping and unloading the monitoring engine, and the monitoring engine is started and then a tool service provides a timed protocol operation and message data processing operation interface to complete a monitoring task.
The invention also provides a data acquisition method based on the network equipment, which comprises the following steps: s1: when the collector is started, the timing frame is automatically loaded, and after the specified time is reached, the timing frame starts the plug-in to collect the equipment data; s2: when the device collects the plug-in to collect the basic index, firstly judging whether the collected basic index is performance data, if the basic index is the performance data, directly collecting the performance data, storing the performance data into a memory, and entering S4; if the base indicator is not the performance indicator, executing S3; s3: collecting data about the index and comparing the data with information in the embedded database; if the value in the database is empty or the data in the database is inconsistent, storing the index data into the memory, updating the information in the database, and finally transmitting the basic index data to the rule engine; s4: the rule engine processes the basic index data according to the relevant strategies, reports the processed data to the upper-level MQ through the message service interface, and the monitoring engine monitors the data.
Further, the monitoring of the data by the monitoring engine in S4 includes the following steps: s41: when the monitoring engine is started, sending starting information to the message server, wherein the starting information comprises monitoring agent ID, installation position and built-in acquisition agent information; s42: the system console receives the monitoring engine starting information through the monitoring message service queue; s43: the system console stores the starting information of the monitoring engine in a database engine running information table; s44: the system console reads the monitoring engine information; s45: the system console issues a monitoring engine synchronization command; s46: an engine controller in the monitoring engine receives an engine synchronization command and judges whether the command information is own command information or not through an engine ID in the broadcast command; s47: after the monitoring engine confirms the command information, downloading a monitoring agent related to the engine to a system console in an HTTP request mode; s48: and the monitoring engine controller decompresses, installs and starts the monitoring agent downloaded to the engine installation catalog, and starts to execute the monitoring task.
Further, the rule engine in S3 performs the following processing: s31: the rule engine starts and loads an index alarm threshold rule; s32: the monitoring engine reports the monitoring data, and the rule engine receives the monitoring data; processing the monitoring data according to an application rule prestored by a rule engine; storing the index and the alarm data into a memory queue; s33: the rule engine pushes the alarm information to a voice message queue and a topology message queue; s34: the rule engine memory updates and stores the indexes and the alarm information to a cache and stores the indexes and the alarm information to a database; s35: reading real-time indexes and alarm information by a system console; or the system console reads the historical index and the alarm information according to the requirement; s36: the voice alarm terminal receives and broadcasts the alarm information; and the topology shows the received alarm information.
Furthermore, when the collection engine is started for the first time, the main program needs to be manually started through a script command.
Further, the method also comprises the step of S5: and after the command is completed, the command which is successfully deployed is sent to the fixed queue of the fixed MQ.
Compared with the prior art, the technical scheme of the invention realizes real-time detection, cross-region flexible deployment and monitoring agent hot deployment on network equipment, namely application.
Drawings
FIG. 1 is a schematic block diagram of the main structure of an acquisition engine.
Fig. 2 is a schematic diagram of a monitoring engine.
FIG. 3 is a schematic diagram of the main flow.
Fig. 4 is a schematic view of a monitoring engine monitoring process.
FIG. 5 is a schematic diagram of a rules engine alarm flow.
FIG. 6 is a collection engine collection flow diagram.
Detailed Description
The invention is further explained below with reference to the figures and the specific embodiments.
A data acquisition system based on network equipment comprises an acquisition engine and a rule engine; the acquisition engine comprises an acquisition controller, a timing frame, a message service interface, a command control plug-in, an equipment discovery plug-in and an equipment acquisition plug-in; when the acquisition system is started, automatically loading a timing frame, and starting a plug-in by the timing frame to acquire equipment data after the specified time is reached; the acquisition controller is used for receiving a system monitoring control command; after the equipment acquisition plug-ins are installed, the acquisition controller sequentially starts the equipment acquisition plug-ins according to the installation sequence, and distributes scheduling operation and data report for the equipment acquisition plug-ins in the starting process; and after the equipment acquisition plug-in is started, equipment data is acquired according to the corresponding monitoring protocol tool of the previously distributed scheduling operation, and the data is reported to the rule engine through the message service interface.
The acquisition controller is used for receiving a system monitoring control command and receiving an execution monitoring command sent by the system, and the controller can apply for an equipment acquisition plug-in to the system according to the command description and automatically download and install the equipment acquisition plug-in. And when receiving the monitoring stopping command, the controller can stop the specified monitoring task and unload the equipment acquisition plug-in according to the required command.
The working process of the collector is as follows:
(1) and installing the acquisition agent to a network to which each monitored device belongs, and configuring an acquisition message interface to be capable of connecting message service.
(2) The acquisition controller is used for receiving a system monitoring control command and receiving an execution monitoring command sent by the system, and the controller can apply for an equipment acquisition plug-in to the system according to the command description and automatically download and install the acquisition plug-in. And when receiving the monitoring stopping command, the controller can stop the specified monitoring task and unload the equipment acquisition plug-in according to the required command.
(3) After the equipment acquisition plug-ins are installed, the controller sequentially starts the equipment acquisition plug-ins according to the installation sequence, and distributes scheduling operation and data reporting message interface service to the acquisition plug-ins in the starting process.
(4) After the equipment acquisition plug-in is started, equipment data can be acquired according to the corresponding monitoring protocol tool of the previously distributed scheduling operation, and the data is reported to the rule engine through the message service interface to carry out index alarm data.
Furthermore, the system also comprises a monitoring engine for monitoring and processing the collected data.
Preferably, the monitoring engine operation framework uses an Apache Felix framework, the main controller receives a console command to perform the operations of installing, starting, stopping and unloading the monitoring engine, and the monitoring engine is started and then a tool service provides a timed protocol operation and message data processing operation interface to complete a monitoring task. The structure schematic diagram is shown in figure 2.
The acquisition engine adopts an Open Service Gateway Initiative (OSGI) development platform, and can flexibly acquire an extended framework based on the OSGI, and the OSGI platform standardizes an execution environment and can dynamically install, Open, close, update and uninstall the monitoring agent. Flexible deployment and data transmission are realized.
The invention also provides a data acquisition method based on the network equipment, which comprises the following steps: s1: when the collector is started, the timing frame is automatically loaded, and after the specified time is reached, the timing frame starts the plug-in to collect the equipment data; s2: when the device collects the basic indexes, firstly judging whether the collected basic indexes are performance data, if the basic indexes are the performance data, directly collecting the performance data, storing the performance data into a memory, and entering S4; if the base indicator is not the performance indicator, executing S3; s3: collecting data of the equipment about the index and comparing the data with information in the embedded database; if the value in the database is empty or the data in the database is inconsistent, storing the index data into the memory, updating the information in the database, and finally transmitting the basic index data to the rule engine; s4: the rule engine processes the basic index data according to the relevant strategies, reports the processed data to the upper-level MQ through the message service interface, and the monitoring engine monitors the data. The specific flow diagram is shown in fig. 3.
Further, the monitoring of the data by the monitoring engine in S4 includes the following steps: s41: when the monitoring engine is started, sending starting information to the message server, wherein the starting information comprises an acquisition agent ID, an installation position and built-in acquisition agent information; s42: the system console receives the monitoring engine starting information through the monitoring message service queue; s43: the system console stores the engine starting information in a database engine operation information table; s44: the system console reads the monitoring engine information; s45: the system console issues a monitoring agent synchronization command; s46: an engine controller in the monitoring engine receives an engine synchronization command and judges whether the command information is own command information or not through an engine ID in the broadcast command; s47: after the monitoring engine confirms the command information, downloading a monitoring agent related to the engine to a system console in an HTTP request mode; s48: and the monitoring engine controller decompresses, installs and starts the monitoring agent downloaded to the engine installation catalog, and starts to execute the monitoring task. See figure 4 for a schematic flow diagram.
Further, the rule engine in S3 performs the following processing: s31: the rule engine starts and loads an index alarm threshold rule; s32: the monitoring engine reports the monitoring data, and the rule engine receives the monitoring data; processing monitoring data by using application rules stored in advance by a rule engine; storing the index and the alarm data into a memory queue; s33: the rule engine pushes the alarm information to a voice message queue and a topology message queue; s34: the rule engine memory updates and stores the indexes and the alarm information to a cache and stores the indexes and the alarm information to a database; s35: reading real-time indexes and alarm information by a system console; or the system console reads the historical index and the alarm information according to the requirement; s36: the voice alarm terminal receives and broadcasts the alarm information; and the topology shows the received alarm information. See figure 5 for a schematic flow diagram.
Furthermore, when the collection engine is started for the first time, the main program needs to be manually started through a script command.
Further, the method also comprises the step of S5: and after the command is completed, the command which is successfully deployed is sent to the fixed queue of the fixed MQ.
See fig. 6 for a process diagram of a specific acquisition engine. The acquisition engine is placed on an application server of a certain network segment, and the main program is manually started through a script command when the acquisition engine is started for the first time, so that the acquisition engine does not need to be manually operated later.
After completing a series of maintenance work, the management console sends a command to the collection agent through the message queue, wherein the command includes the name and parameters of the command. For example, an install monitor template command, the collection agent is not running a collection instance after the first startup. The method can monitor the fixed theme of the fixed MQ, and after the instruction for installing the monitoring template corresponding to the ID is obtained, the parameters in the instruction can be converted into a template bundle and deployed into the file of the user. And after the deployment is completed, a command of successful deployment is sent to the fixed queue of the fixed MQ. And then, according to the parameter frequency in the deployed monitoring template, starting a scheduling program with different frequencies, connecting specific resources according to the resource information in the monitoring template to acquire the parameter information, and sending the information to a fixed queue of the fixed MQ for finishing.
The above are preferred embodiments of the present invention, and all changes made according to the technical scheme of the present invention, which produce functional effects that do not exceed the scope of the technical scheme of the present invention, belong to the protection scope of the present invention.
Claims (4)
1. A data acquisition system based on network equipment is characterized in that: comprises an acquisition engine and a rule engine; the acquisition engine comprises an acquisition controller, a timing frame, a message service interface, a command control plug-in, an equipment discovery plug-in and an equipment acquisition plug-in; when the acquisition system is started, automatically loading a timing frame, and starting a plug-in by the timing frame to acquire equipment data after the specified time is reached; the acquisition controller is used for receiving a system monitoring control command; after the equipment acquisition plug-ins are installed, the acquisition controller sequentially starts the equipment acquisition plug-ins according to the installation sequence, and distributes scheduling operation and data report for the equipment acquisition plug-ins in the starting process; after the equipment acquisition plug-in is started, equipment data is acquired according to the corresponding monitoring protocol tool of the previously distributed scheduling operation, and the data is reported to the rule engine through the message service interface;
the data acquisition system also comprises a monitoring engine for monitoring and processing the acquired data;
the monitoring engine operation framework uses an Apache Felix framework, the main controller receives a system console command to carry out the installation, start-stop and unloading operations of the monitoring engine, and a tool service provides a timed protocol operation and message data processing operation interface to complete a monitoring task after the monitoring engine is started;
the data acquisition system executes a data acquisition method based on network equipment, and comprises the following steps:
s1: when the collector is started, the timing frame is automatically loaded, and after the specified time is reached, the timing frame starts the plug-in to collect the equipment data;
s2: when the device collects the plug-in to collect the basic index, firstly judging whether the collected basic index is performance data, if the basic index is the performance data, directly collecting the performance data, storing the performance data into a memory, and entering S4; if the base indicator is not the performance indicator, executing S3;
s3: collecting data about the index and comparing the data with information in the embedded database; if the value in the database is empty or the data in the database is inconsistent, storing the index data into the memory, updating the information in the database, and finally transmitting the basic index data to the rule engine;
s4: the rule engine processes the basic index data according to the relevant strategies, reports the processed data to the upper-level MQ through the message service interface, and the monitoring engine monitors the data;
further comprising step S5: after the system is maintained by the system control console, sending a command to the acquisition engine through the MQ, and after the command is completed, sending a command which is successfully deployed to the fixed queue of the fixed MQ;
the monitoring of the data by the monitoring engine in the S4 includes the following steps:
s41: when the monitoring engine is started, sending starting information to the message server, wherein the starting information comprises monitoring agent ID, installation position and built-in acquisition agent information;
s42: the system console receives the monitoring engine starting information through the monitoring message service queue;
s43: the system console stores the starting information of the monitoring engine in a database engine running information table;
s44: the system console reads the monitoring engine information;
s45: the system console issues a monitoring engine synchronization command;
s46: an engine controller in the monitoring engine receives an engine synchronization command and judges whether the command information is own command information or not through an engine ID in the broadcast command;
s47: after the monitoring engine confirms the command information, downloading a monitoring agent related to the engine to a system console in an HTTP request mode;
s48: the monitoring engine controller decompresses, installs and starts the monitoring agent downloaded to the engine installation directory, and starts to execute the monitoring task;
the system control console can send a monitoring template installing command to the acquisition agent through the message queue after maintenance work is finished, the acquisition agent monitors the fixed theme of the fixed MQ after being started for the first time, and after the monitoring template installing command corresponding to the ID is obtained, parameters in the command are converted into a template bundle and are deployed into a file of the acquisition agent; after deployment is completed, a command of successful deployment is sent to the fixed queue of the fixed MQ, and after step S5, according to the parameter frequency in the deployed monitoring template, a scheduling program with different frequencies is started, according to the resource information in the monitoring template, the specific resource is connected to obtain the parameter information, and the information is integrated and sent to the fixed queue of the fixed MQ.
2. The network device-based data collection system of claim 1, wherein: the collection engine is an OSGI container.
3. The network device-based data collection system of claim 1, wherein: the rule engine in S3 performs the following processing:
s31: the rule engine starts and loads an index alarm threshold rule;
s32: the monitoring engine reports the monitoring data, and the rule engine receives the monitoring data; processing the monitoring data according to an application rule prestored by a rule engine; storing the index and the alarm data into a memory queue;
s33: the rule engine pushes the alarm information to a voice message queue and a topology message queue;
s34: the rule engine memory updates and stores the indexes and the alarm information to a cache and stores the indexes and the alarm information to a database;
s35: reading real-time indexes and alarm information by a system console; or the system console reads the historical index and the alarm information according to the requirement;
s36: the voice alarm terminal receives and broadcasts the alarm information; and the topology shows the received alarm information.
4. The network device-based data collection system of claim 1, wherein: when the collection engine is started for the first time, the main program needs to be manually started through a script command.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710199399.4A CN106992903B (en) | 2017-03-30 | 2017-03-30 | Data acquisition system and method based on network equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710199399.4A CN106992903B (en) | 2017-03-30 | 2017-03-30 | Data acquisition system and method based on network equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106992903A CN106992903A (en) | 2017-07-28 |
| CN106992903B true CN106992903B (en) | 2020-07-10 |
Family
ID=59412288
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710199399.4A Active CN106992903B (en) | 2017-03-30 | 2017-03-30 | Data acquisition system and method based on network equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106992903B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107864056A (en) * | 2017-11-04 | 2018-03-30 | 公安部第三研究所 | A kind of distributed event acquisition probe, distributed event high speed acquisition system and method |
| CN109756585B (en) * | 2017-11-08 | 2022-02-22 | 中国电信股份有限公司 | Method and control device for identifying position of new network access equipment |
| CN107911467B (en) * | 2017-11-29 | 2020-09-29 | 浪潮云信息技术股份公司 | Service operation management system and method for scripted operation |
| CN111447170B (en) * | 2019-01-17 | 2023-05-30 | 北京京东尚科信息技术有限公司 | Data processing method and system, computer system and computer readable medium |
| CN110048883B (en) * | 2019-04-03 | 2022-06-07 | 国网福建省电力有限公司 | Method for realizing comprehensive network management based on micro-service cloud architecture |
| CN110261701B (en) * | 2019-06-27 | 2021-08-13 | 西安西拓电气股份有限公司 | Configuration method, device and system of power equipment |
| CN110708351A (en) * | 2019-08-30 | 2020-01-17 | 深圳鸿智云创科技有限公司 | Data transmission method |
| CN110955717A (en) * | 2019-11-19 | 2020-04-03 | 深圳市航通智能技术有限公司 | Visual dynamic display method and system based on big data |
| CN111984505B (en) * | 2020-08-21 | 2023-06-16 | 豪越科技有限公司 | Fortune dimension data acquisition device and acquisition method |
| CN112291999A (en) * | 2020-10-20 | 2021-01-29 | 浙江省电子信息产品检验研究院 | Network equipment data acquisition system and method |
| CN113722256A (en) * | 2021-09-02 | 2021-11-30 | 江苏斯菲尔电气股份有限公司 | Communication manager function type control system and method based on plug-in |
| CN114244678B (en) * | 2021-12-15 | 2024-03-12 | 浪潮通信信息系统有限公司 | Multi-protocol alarm equipment access method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102739802A (en) * | 2012-07-06 | 2012-10-17 | 广东电网公司汕头供电局 | Service application-oriented IT contralized operation and maintenance analyzing system |
| CN103309674A (en) * | 2013-06-25 | 2013-09-18 | 深圳中兴网信科技有限公司 | Software architecture system |
| CN103888287A (en) * | 2013-12-18 | 2014-06-25 | 北京首都国际机场股份有限公司 | Information system integrated operation and maintenance monitoring service early warning platform and realization method thereof |
| CN104331780A (en) * | 2014-11-21 | 2015-02-04 | 国家电网公司 | Monitoring system for business process |
| CN104731580A (en) * | 2015-01-12 | 2015-06-24 | 上海新炬网络信息技术有限公司 | Automation operation and maintenance system based on Karaf and ActiveMQ and implement method thereof |
| CN106411609A (en) * | 2016-11-08 | 2017-02-15 | 上海新炬网络信息技术有限公司 | IT software and hardware running state monitoring system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8601318B2 (en) * | 2007-10-26 | 2013-12-03 | International Business Machines Corporation | Method, apparatus and computer program product for rule-based directed problem resolution for servers with scalable proactive monitoring |
-
2017
- 2017-03-30 CN CN201710199399.4A patent/CN106992903B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102739802A (en) * | 2012-07-06 | 2012-10-17 | 广东电网公司汕头供电局 | Service application-oriented IT contralized operation and maintenance analyzing system |
| CN103309674A (en) * | 2013-06-25 | 2013-09-18 | 深圳中兴网信科技有限公司 | Software architecture system |
| CN103888287A (en) * | 2013-12-18 | 2014-06-25 | 北京首都国际机场股份有限公司 | Information system integrated operation and maintenance monitoring service early warning platform and realization method thereof |
| CN104331780A (en) * | 2014-11-21 | 2015-02-04 | 国家电网公司 | Monitoring system for business process |
| CN104731580A (en) * | 2015-01-12 | 2015-06-24 | 上海新炬网络信息技术有限公司 | Automation operation and maintenance system based on Karaf and ActiveMQ and implement method thereof |
| CN106411609A (en) * | 2016-11-08 | 2017-02-15 | 上海新炬网络信息技术有限公司 | IT software and hardware running state monitoring system |
Non-Patent Citations (2)
| Title |
|---|
| Java规则引擎工作原理及其应用;rise51;《http://blog.csdn.net/rise51/article/details/51587900》;20160605;全文 * |
| 以代理为中心的OSGi构建资源监控方法;林洪武等;《计算机科学与探索》;20110131;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106992903A (en) | 2017-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106992903B (en) | Data acquisition system and method based on network equipment | |
| US8191061B2 (en) | Method for managing internal software of terminal through device management server | |
| CA2488044C (en) | System and method for synchronizing the configuration of distributed network management applications | |
| CN109451021B (en) | Internet of things edge side multi-heterogeneous network access system and method | |
| CN101631053B (en) | EAPS ring-network topology monitoring method and system | |
| CN107357571B (en) | Maintenance method and system for equipment component program | |
| CN111786893B (en) | method and device for synchronizing software versions of wireless routers in mesh networking | |
| WO2007048340A1 (en) | Method and device for obtaining software usage frequency and upgrading software in device management | |
| CN101502144A (en) | Element management system in wireless communication network | |
| CN101317381A (en) | Ability management object maintenance, ability management method, system and terminal | |
| CN103019757A (en) | Method, device and system for synchronizing software among multiple clients | |
| CN107483297B (en) | Active monitoring system and method for quality of service carried on embedded equipment | |
| US10970060B2 (en) | IoT endpoint metrics | |
| CN112968789A (en) | Data acquisition method and device, computer equipment and computer readable medium | |
| CN103139245A (en) | Method and device for updating network elements | |
| CN103517300A (en) | Self-discovery method, device and system of distributed base station | |
| CN101507152A (en) | Expandable element management system in wireless communication network | |
| EP2137614A1 (en) | On-line configuration management system and method | |
| KR20060125474A (en) | System and method for setting configuration-value inthereof | |
| CN115357308A (en) | Docker-based edge Internet of things proxy device, system and application method | |
| CN111324365A (en) | Method and equipment for upgrading super-converged system | |
| CN112579398A (en) | Monitoring deployment method and device | |
| CN112527346A (en) | Software upgrading method and device, storage medium and electronic device | |
| CN109039781B (en) | Network equipment fault diagnosis method, execution node, server and system | |
| CN115811457A (en) | Integrated data acquisition method for multi-source data fusion |
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 |