CN105610648B - A method and server for collecting operation and maintenance monitoring data - Google Patents

Abstract

The invention discloses a method for collecting operation and maintenance monitoring data and a server, belonging to the field of information security. According to the collection interval of each monitoring item in the server configuration file, the server obtains the monitoring items that meet the collection conditions, sends the monitoring information corresponding to the monitoring items that meet the collection conditions to the client, receives the collection results returned by the client, and performs the collection The results are processed. By adopting the technical method of the present invention, the granularity of monitoring is smaller, and the original machine is reduced to a certain resource on the machine that can be monitored. When the machine needs to add monitoring resources, the system program does not need to be modified, just write the corresponding monitoring data collection application and configure it in the system. Improve the stability of the system, and increase the scalability of the system.

Description

A method and server for collecting operation and maintenance monitoring data

technical field

The invention relates to the field of information security, in particular to a method for collecting operation and maintenance monitoring data and a server.

Background technique

In the existing disaster recovery system, the scalability of operation and maintenance monitoring can only be at the machine level, not on the resources on a single machine, and the monitoring resources on each machine are pre-designed. It is not easy to add new monitoring resources on a single machine.

Therefore, if you need to add monitoring resources, you need to provide development support at the system level, which is not conducive to the stability and maintainability of the system.

Contents of the invention

The object of the present invention is to provide a method for collecting operation and maintenance monitoring data and a server in order to solve the problems existing in the prior art.

The technical solution adopted in the present invention is: a method for collecting operation and maintenance monitoring data, comprising:

Step S1: The server judges whether any monitoring item satisfies the collection condition according to the collection interval of each monitoring item in the server configuration file, if yes, executes step S2, otherwise continues to execute step S1;

Step S2: the server sends the monitoring information corresponding to the monitoring items meeting the collection conditions to the client; the client is installed on the monitored machine;

Step S3: the server receives the collection result returned by the client; the collection result is the data collected by the client on the monitored machine according to the received monitoring information;

Step S4: the server processes the collection result, and returns to step S1.

The method also includes: the server obtains an updated server configuration file, and according to the collection interval of each monitoring item in the updated server configuration file, judges whether any monitoring item satisfies the collection condition, and if so, executes the step S2, otherwise continue to execute step S1'.

The step S1 is specifically: the server registers a timing event for each monitoring item according to the collection interval of each monitoring item in the server configuration file, and when it is detected that a timing event is triggered, then there is a monitoring item that meets the acquisition condition, and executes Step S2, otherwise continue to execute step S1.

According to the collection interval of each monitoring item in the server configuration file, register a timing event for each monitoring item, specifically: the server parses all monitoring items from the server configuration file, and according to the quantity of all monitoring items, Create a working process group for each monitoring item, and register timing events for each working process group according to the collection interval of each monitoring item.

The client includes a data collection application, and between the step S2 and the step S3 also includes:

Step d1: the client sends the received monitoring information to the data collection application;

Step d2: the data collection application collects the corresponding data in the client according to the received monitoring information, and sends the collected collection result to the server.

The step S2 specifically includes: when the server configuration file is in a text file format, calling an interface for processing a text file format, and sending monitoring information corresponding to monitoring items meeting collection conditions to the client.

The step S2 specifically includes: when the server configuration file is in the XML file format, calling an interface for processing the XML file format, and sending the monitoring information corresponding to the monitoring items meeting the collection conditions to the client.

Described step S4 specifically comprises:

Step e1: the server judges whether the collection result is abnormal, if yes, execute step e2, otherwise return to step S1;

Step e2: The server judges whether the abnormal collection result needs to be called an alarm according to the monitoring information of the monitoring item, if yes, execute step e3, otherwise return to step S1;

Step e3: The server judges whether the alarm notification is allowed to be sent according to the monitoring information in the monitoring item, if yes, executes step e4, otherwise returns to step S1;

Step e4: The server selects an alarm notification method, sends the alarm information to the administrator, and returns to step S1.

The step S4 is specifically: the server judges according to the server configuration file whether it is necessary to analyze the change trend of the collection result, if yes, save the collection result and return to step S1, otherwise directly return to step S1.

The step S4 specifically includes: the server judges whether log information needs to be recorded according to the collection result, if yes, records the log information, and returns to step S1, otherwise directly returns to step S1.

Before the step S3, the method further includes: the client loads the client configuration file, monitors the connection port with the server according to the configuration parameters in the client configuration file, and waits to receive the monitoring information of the server.

Also include before the step S3:

Step f1: After receiving the monitoring information sent by the server, the client judges whether the server is a device that allows access according to the configuration file of the client, and if so, executes step f2, otherwise continues Waiting to receive monitoring information;

Step f2: The client judges whether the monitoring information is monitoring information that is allowed to be executed according to the client configuration file, and if so, executes step f3, otherwise continues to wait for receiving the monitoring information;

Step f3: the client collects corresponding data according to the received monitoring information, and sends the collected collection result to the server.

The step S2 specifically includes: when the data collection method in the server configuration file acquired by the server is the data collection method of the monitoring agent, sending the monitoring information corresponding to the monitoring items satisfying the collection conditions to the client.

The step S2 and the step S3 are replaced by: when the server obtains the data collection method in the server configuration file as the SNMP agent data collection method, send the monitoring information corresponding to the monitoring items that meet the collection conditions to the SNMP agent , receiving the collection result returned by the SNMP agent, and performing step S4.

The server includes a data collector, and the step S2 is specifically:

Step b1: the server sends the monitoring information corresponding to the monitoring item meeting the collection condition to the data collector;

Step b2: the data collector sends the received monitoring information to the client.

Between the step b1 and the step b2, it also includes: the execution mode of the data acquisition in the monitoring information obtained by the data collector is local execution, and the data collector collects the data collected by the server according to the monitoring information The data in the method is obtained, and the collection result is obtained, and the collection result is sent to the server, and step S4 is executed.

The step b2 specifically includes: when the execution mode of the data acquisition in the monitoring information acquired by the data collector is executed by the client, sending the received monitoring information to the client.

The server includes a data collection application, and the data collector collects data in the server according to the monitoring information, specifically:

Step c1: the data collector sends the monitoring information to the data collection application;

Step c2: the data collection application collects data in the corresponding server according to the received monitoring information;

Step c3: the data collection application sends the collected data in the server to the data collector.

Before the step b2, the method further includes: the data collector judges whether the received monitoring information contains auxiliary information, if yes, displays the auxiliary information, and ends, otherwise, executes step b2.

Between the step S2 and the step S3, it also includes:

Step g1: the client collects corresponding data according to the received monitoring information, and sends the collected collection result to the data collector;

Step g2: The data collector judges whether the collection result is correct according to the checksum in the collection result, if yes, executes step g3, otherwise reports an error, and ends;

Step g3: the data collector sends the collection result to the server.

Between the step S1 and the step S2, it also includes: the server judges whether the data in the client can be collected according to the operating system information in the server configuration file, and if so, executes step S2, Otherwise, report an error and return to step S1.

The judging whether the data in the client can be collected is specifically: the server sends a request to the client to obtain the client operating system information, receives the client operating system information returned by the client, and judges the client operating system information. Whether the operating system information in the server configuration file matches the received client operating system information, if yes, execute step S2, otherwise report an error, and return to step S1.

A server for collecting operation and maintenance monitoring data, including:

The first judging module is used for judging whether any monitoring item satisfies the collection condition according to the collection interval of each monitoring item in the server configuration file;

The first sending module is configured to send the monitoring information corresponding to the monitoring items satisfying the collection conditions to the client when the first judging module judges that there are monitoring items meeting the collection conditions;

The first receiving module is configured to receive the collection result returned by the client;

A processing module, configured to process the collection result received by the first receiving module, and trigger the first judging module.

The server also includes a second judging module;

The second judging module is used to obtain the updated server configuration file, and judge whether any monitoring item satisfies the collection condition according to the collection interval of each monitoring item in the updated server configuration file, and when the judgment is yes, trigger the The first sending module, if the judgment is no, continue to trigger the second judging module.

The first judging module specifically includes a registration unit and a detection unit;

The registration unit is configured to register timing events for each monitoring item according to the collection interval of each monitoring item in the server configuration file;

The detecting unit is configured to detect a timing event, and trigger the first sending module when a timing event trigger is detected.

The registration unit is specifically used to parse and obtain all monitoring items from the server configuration file, create a working process group for each monitoring item according to the number of monitoring items, and create a working process group for each monitoring item according to the collection interval of each monitoring item. Register for timed events.

The first sending module is specifically configured to call an interface for processing a text file format when the server configuration file is in a text file format, and send monitoring information corresponding to monitoring items meeting collection conditions to the client.

The first sending module is specifically configured to call an interface for processing an XML file format when the server configuration file is in an XML file format, and send monitoring information corresponding to monitoring items meeting collection conditions to the client.

The processing module specifically includes: a first judging unit, a second judging unit, a third judging unit and an alarm unit;

The first judging unit is configured to judge whether the collection result received by the receiving module is abnormal, if it is judged to be yes, trigger the second judging unit, and if it is judged to be no, trigger the first judging module;

The second judging unit is used to judge whether the abnormal collection result needs to be called an alarm according to the monitoring information of the monitoring item, if it is judged to be yes, trigger the third judging unit, and if it is judged to be no, trigger the first Judgment module;

The third judging unit is used to judge whether to allow sending an alarm notification according to the monitoring information in the monitoring item, if it is judged to be yes, trigger the alarm unit, and if it is judged to be no, trigger the first judgment module;

The alarm unit is configured to select an alarm notification mode, send alarm information to an administrator, and trigger the first determination module when the third determination unit determines yes.

The server also includes a storage module;

The processing module is specifically used to judge whether it is necessary to analyze the change trend of the collected data according to the server configuration file, if it is judged to be yes, trigger the storage module, and if it is judged to be no, trigger the first judgment module;

The storage module is configured to save the collection result and trigger the first judging module.

The server also includes a logging module;

The processing module is specifically used to judge whether log information needs to be recorded according to the collected data, if it is judged to be yes, trigger the log recording module, and if it is judged to be no, trigger the first judgment module;

The log recording module is configured to record log information and trigger the first judging module.

The first sending module is specifically configured to send the monitoring information corresponding to the monitoring items meeting the collection conditions to the client when the data collection method in the server configuration file is the monitoring agent data collection method.

The first sending module is also used to send the monitoring information corresponding to the monitoring items that meet the collection conditions to the SNMP agent when the data collection method in the server configuration file is obtained as the SNMP data collection method;

The first receiving module is further configured to receive the collection result returned by the SNMP agent, and trigger the processing module.

The server also includes a data collector module;

The data collector module includes a first receiving unit and a first sending unit;

The first sending module is further configured to send the monitoring information corresponding to the monitoring items satisfying the collection conditions to the first receiving unit when the first judging module judges that there are monitoring items meeting the collection conditions;

The first receiving unit is configured to receive the monitoring information sent by the first sending module;

The first sending unit is configured to send the monitoring information received by the first receiving unit to the client.

The data collector module also includes a first collection unit;

The first collecting unit is configured to collect data in the server according to the monitoring information and trigger the first sending unit when the data collection in the monitoring information is executed locally.

The first sending unit is specifically configured to send the monitoring information received by the first receiving unit to the client when the execution mode of acquiring the data in the monitoring information is executed by the client.

The server includes a data acquisition application module;

The data collection application module includes a second receiving unit, a second collecting unit and a second sending unit;

The second receiving unit is configured to receive monitoring information sent by the data collector module;

The second collecting unit is configured to collect data in the corresponding server according to the monitoring information received by the second receiving unit;

The second sending unit is configured to send the data in the server collected by the second collecting unit to the data collector module.

The data collector module also includes a fourth judging unit and a display unit;

The fourth judging unit is configured to judge whether the monitoring information received by the first receiving unit contains auxiliary information, and if it is judged to be yes, trigger the display unit; sending unit;

The display unit is used to display the auxiliary information.

The server also includes a third judging module and an error reporting module;

The third judging module is configured to judge whether the data in the client can be collected according to the operating system information in the server configuration file when the judgment is yes by the first judgment module, and if the judgment is yes, triggering the first sending module, and triggering the error reporting module when the judgment is negative;

The error reporting module is used to report an error and continue to trigger the first judging module.

The third judging module specifically includes a third sending unit, a third receiving unit and a fifth judging unit;

The third sending unit is configured to send to the client a request for acquiring client operating system information;

The third receiving unit is configured to receive the client operating system information returned by the client;

The fifth judging unit is configured to judge whether the operating system information in the server configuration file matches the client operating system information received by the first receiving unit, and trigger the first The sending module triggers the error reporting module when the judgment is negative.

The beneficial effects obtained by the present invention are: adopting the technical method of the present invention, the granularity of monitoring is smaller, and the original machine is reduced to a certain resource on the machine that can be monitored. When the machine needs to add monitoring resources, the system program does not need to be modified, just write the corresponding monitoring data collection application and configure it in the system. Improve the stability of the system, and increase the scalability of the system.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a flowchart of a method for collecting operation and maintenance monitoring data provided by Embodiment 1 of the present invention;

FIG. 2 is a flow chart of a collection method of an operation and maintenance monitoring data system provided in Embodiment 2 of the present invention;

3 is a flow chart of a working method of a monitoring server in an operation and maintenance monitoring data system provided by Embodiment 3 of the present invention;

4 is a flow chart of a working method of a data collector in an operation and maintenance monitoring data system provided in Embodiment 4 of the present invention;

Fig. 5 is a flowchart of a working method of a monitoring client in an operation and maintenance monitoring data system provided by Embodiment 5 of the present invention.

FIG. 6 is a device diagram of a server for collecting operation and maintenance monitoring data according to Embodiment 6 of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Both the server and the client are pre-registered with configuration files, which include configuration parameters for service startup and monitoring configuration files for specified monitoring machines. There can be multiple monitoring configuration files, each monitoring configuration file represents a machine to be monitored, and the client is installed on the machine to be detected. The monitoring configuration file contains the basic information of the machine and multiple monitoring items. Each monitoring item contains multiple monitoring information, including the type of data collected and the attributes of the collected data (such as collection information description, IP address, etc.), among which , the monitoring items and monitoring information can be set by the user, or can be set according to the frequency of data collection by the monitoring server or monitoring client.

In the present invention, as long as resources that can be represented by quantified numbers and can be used to collect quantitative data through programs in a certain way, they can be used as monitoring items. Among them, monitoring items include but are not limited to CPU usage, CPU load, memory Usage, disk usage, network interface traffic, WEB site response time, etc.

Example 1

Embodiment 1 of the present invention provides a method for collecting operation and maintenance monitoring data. In this embodiment, a data collector and a data collection application may be provided in the server, and a data collection application may be provided in the client, as shown in FIG. 1 ,include:

Step S1: The server judges whether any monitoring item satisfies the collection condition according to the collection interval of each monitoring item in the server configuration file, if yes, executes step S2, otherwise continues to execute step S1;

This step is specifically as follows: the server registers timing events for each monitoring item according to the collection interval of each monitoring item in the server configuration file. When a timing event is detected to be triggered, there are monitoring items that meet the collection conditions, and step S2 is executed; otherwise, continue to execute Step S1;

Among them, according to the collection interval of each monitoring item in the server configuration file, register timing events for each monitoring item, specifically: the server parses all monitoring items from the server configuration file, and creates a working process for each monitoring item according to the number of monitoring items Group, according to the collection interval of each monitoring item, register timing events for each working process group.

Step S2: The server sends the monitoring information corresponding to the monitoring items meeting the collection conditions to the client;

Among them, the client is installed on the machine to be monitored;

When the format of the server configuration file is a text file format, call the interface for processing the text file format, and send the monitoring information corresponding to the monitoring items that meet the collection conditions to the client;

When the format of the server configuration file is an XML file format, call the interface for processing the XML file format, and send the monitoring information corresponding to the monitoring items that meet the collection conditions to the client;

This step specifically includes:

When the server obtains the data collection method in the server configuration file as the data collection method of the monitoring agent, it sends the monitoring information corresponding to the monitoring items that meet the collection conditions to the client;

When the server obtains the data collection method in the server configuration file as the SNMP agent data collection method, it sends the monitoring information corresponding to the monitoring items meeting the collection conditions to the SNMP agent, receives the collected data returned by the SNMP agent, and executes step S4.

Step S3: the server receives the collection result returned by the client;

In this embodiment, the collection result is the data collected by the client on the machine to be monitored according to the received monitoring information;

Step S4: the server processes the collection result, and returns to step S1.

In this embodiment, the processing of the collected results by the server includes alarming (including restarting the client, etc.), saving the collected data to analyze changing trends, recording log information, and the like.

In this embodiment, before step S2, it also includes:

Step S1': The server obtains the updated server configuration file, and according to the collection interval of each monitoring item in the updated server configuration file, judges whether any monitoring item satisfies the collection condition, if yes, executes step S2, otherwise proceeds to step S1';

Wherein, the monitoring items in the updated server configuration file are different from the monitoring items in the server configuration file before updating.

Example 2

Embodiment 2 of the present invention provides a working method of an operation and maintenance monitoring data collection system, which is applied to a system including a server and a client, wherein the server includes a monitoring server, a data collector, and a data collection application; the client includes a monitoring client and data collection applications; specifically, the data collector is an application program used by the server to obtain collection results. The data collection application can be deployed in the server or client, and is a plug-in for data collection in the monitoring server or monitoring client. As shown in Figure 2, including:

Step 101: Start the monitoring server, register a timing event for each monitoring item according to the collection interval of each monitoring item in the server configuration file, wait for the trigger of the timing event, and execute step 102 when the trigger of the timing event is received, otherwise continue Wait for the trigger of the timing event;

In this embodiment, the collection duration is preset in each monitoring item of the server configuration file, wherein the collection duration can be set by the user or set by the monitoring server according to the rate of data collection;

Among them, the collection time of each monitoring item in the timing monitoring server configuration file of the timing event of the monitoring server, if the collection interval of a monitoring item reaches the monitoring duration of the monitoring item, the following steps are performed on the monitoring item ;

In this embodiment, the format of the monitoring item can be set by the user, including text file format and XML file format, etc.;

For example, the server configuration file in the text file format is (it should be noted that one or more monitoring items may be included in the server configuration file, and this embodiment uses the server configuration file to include one monitoring item as an example):

For example, a server configuration file in XML file format is:

<service>

<use>generic-service</use>

<host_name>192.168.88.179</host_name>

<service_description>Swap Usage</service_description>

<check_command>check_nrpe! check_swap! 20! 10</check_command>

<active_checks_enabled>1</active_checks_enabled>

<passive_checks_enabled>1</passive_checks_enabled>

<parallelize_check>1</parallelize_check>

<obsess_over_service>1</obsess_over_service>

<check_freshness>0</check_freshness>

<notifications_enabled>1</notifications_enabled>

<event_handler_enabled>1</event_handler_enabled>

<flap_detection_enabled>1</flap_detection_enabled>

<process_perf_data>1</process_perf_data>

<retain_status_information>1</retain_status_information>

<retain_nonstatus_information>1</retain_nonstatus_information>

<is_volatile>0</is_volatile>

<check_period>24x7</check_period>

<max_check_attempts>3</max_check_attempts>

<normal_check_interval>2</normal_check_interval>

<retry_check_interval>2</retry_check_interval>

<contact_groups>admins</contact_groups>

<notification_options>w,u,c,r</notification_options>

<notification_interval>60</notification_interval>

<notification_period>24x7</notification_period>

<register>0</register>

</service>

According to the monitoring information service_description SwapUsage or <service_description>SwapUsage</service_description> in the above two types of server configuration files, the server configuration file is used to check the usage of the swap partition in the machine 192.168.89.179 in the monitoring client, where , according to the monitoring information normal_check_interval2 or <normal_check_interval>2</normal_check_interval> in the above two types of server configuration files, it can be seen that the collection time is 2 minutes;

In this embodiment, after the monitoring server registers the timing event, it records the first time, and when it is monitored that the time interval between the current time and the first time (that is, the collection interval) reaches an integer multiple of the collection time, step 102 is executed;

For example, after the monitoring server registers the timing event, the first time recorded is 2015.09.24 10:39:25, then when the time interval between the current time and the first time is monitored to reach the shortest collection time (2 minutes) among all monitoring items When, that is, when the current time is 2015.09.24 10:41:25, step 102 is executed;

Step 102: the monitoring server judges whether the data on the monitored machine corresponding to the monitoring client can be collected according to the operating system in the server configuration file, if yes, then execute step 103, otherwise continue to wait for the triggering of the timing event;

In this embodiment, this step is specifically:

The monitoring server sends a request to the monitoring client to obtain the client operating system, receives the client operating system information returned by the monitoring client, and judges whether the operating system information in the server configuration file matches the received client operating system information. , then execute step 102, otherwise report an error and continue to wait for the trigger of the timing event;

Further, in this embodiment, if the operating system is not configured in the server configuration file or the operating system is configured to be automatically identified, step 103 is directly executed after step 101 is executed;

Step 103: the monitoring server obtains the data collection method in the server configuration file, if it is the monitoring agent data collection method, then execute step 104, if it is the SNMP agent data collection method, then execute step 115;

In this embodiment, SNMP is a network management standard based on the TCP/IP protocol family, a standard protocol for managing network nodes in an IP network, and realizes direct interaction between a monitoring server and a monitored machine.

Step 104: The monitoring server sends the monitoring information corresponding to the monitoring item triggered by the timing event to the data collector;

Step 105: The data collector acquires the execution mode of the data collection in the received monitoring information. If it is executed on the local machine, then execute step 111, and if it is executed on the monitoring client, then execute step 106;

In this embodiment, it is pre-agreed that if there is no check_agent in the execution mode check_command of the data collection in the monitoring information, it will be identified that the data collection is executed locally; if check_agent is used in the collection execution mode check_command in the monitoring information, it will be identified The data collection is performed on the monitoring client;

For example, in the example of step 101, the data collector acquires the monitoring information check_nrpe! from the server configuration file. check_swap! 20! There is no check_agent in 10, which means that the data collection is performed on the local machine, and go to step 111;

Step 106: the data collector sends the monitoring information to the monitoring client;

Step 107: the monitoring client sends the monitoring information to the data collection application;

Step 108: collect the monitoring information received by running the data collection application, collect the data on the monitored machine according to the monitoring information, and obtain the collection result in a preset format;

In this embodiment, preferably, the collection result in the preset format is:

Description of the current state of the monitoring item | Description of the current collection information of the monitoring item = the current collection value of the monitoring item; alarm threshold; fault threshold; the minimum value of the y-axis when outputting the report; the maximum value of the y-axis when outputting the report; description information of the current state of the monitoring item |The current collection information description of the monitoring item=the current collection value of the monitoring item; alarm threshold; fault threshold; the minimum value of the y-axis when outputting the report; the maximum value of the y-axis when outputting the report... (use ";" to separate multiple collection items open);

For example, monitoring information is used to collect memory usage, and the collected collection results are:

Memory Free:/246MB(16%)|percentage＝24;20;10;0;100;

Among them, the current state description information of the monitoring item: Memory Free:/246MB (16%), the current collection information description of the monitoring item: percentage, the current collection value of the monitoring item: 24, the alarm threshold: 20, the failure threshold: 10, and output the report The minimum value of the y-axis when the report is output: 0, and the maximum value of the y-axis when the report is output: 100.

Step 109: the data collection application returns the collection result to the monitoring client;

Step 110: the monitoring client returns the collection result to the data collector, and executes step 114;

Step 111: the data collector sends all monitoring information to the data collection application;

Step 112: collect the monitoring information received by running the data collection application, collect data according to the monitoring information, and obtain the collection result in a preset format;

For example, the configuration information is used to collect the CPU load, and the collected collection results are as follows:

OK-load average: 0.16, 0.12, 0.09 | load1 = 0.160; 15.000; 30.000; 0; load5 = 0.120; 10.000; 25.000; 0; load15 = 0.090;

Among them, the current state description information of the monitoring item: OK-load average: 0.16, 0.12, 0.09, and the collection results include three values:

First:

Description of the current collection information of the monitoring item: load1, the current collection value of the monitoring item: 0.160, the alarm threshold: 15.000, the fault threshold: 30.000, the minimum value of the y-axis when outputting the report: 0, the maximum value of the y-axis when outputting the report: none (no limit)

the second:

Description of the current collection information of the monitoring item: load5, the current collection value of the monitoring item: 0.120, the alarm threshold: 10.000, the fault threshold: 25.000, the minimum value of the y-axis when outputting the report: 0, the maximum value of the y-axis when outputting the report: none (no limit)

The third:

Description of the current collection information of the monitoring item: load15, the current collection value of the monitoring item: 0.090, the alarm threshold: 5.000, the fault threshold: 20.000, the minimum value of the y-axis when outputting the report: 0, the maximum value of the y-axis when outputting the report: none (no limit);

Step 113: the data collection application returns the collection result to the data collector;

Specifically, the data collection application sends the collected data to the data collector through a pipeline.

Step 114: the data collector returns the collection result to the monitoring server, and executes step 118;

Step 115: the monitoring server sends the monitoring information corresponding to the monitoring item triggered by the received timing event to the SNMP agent;

Step 116: The SNMP agent runs the received monitoring information, collects data according to the monitoring information, and obtains a collection result in a preset format;

Step 117: the SNMP agent sends the collection result to the monitoring server, and executes step 118;

Step 118: The monitoring server processes the received collection results, and continues to wait for the trigger of the timing event;

Wherein, the processing of the collection result by the monitoring server is specifically described in Embodiment 3, and will not be repeated here.

Example 3

Embodiment 3 of the present invention provides a working method of a monitoring server in an operation and maintenance monitoring data system, as shown in FIG. 3 , including:

Step 201: start the monitoring server, perform initialization, and read the server configuration file locally from the server;

Among them, initialization includes reading server configuration files and parsing command line parameters, etc.;

Step 202: The monitoring server sends a request to the monitoring client to acquire the client operating system, receives the client operating system information returned by the monitoring client, and determines whether the operating system information in the server configuration file matches the received client operating system information , if yes, execute step 203, otherwise report an error and end;

In this embodiment, if the operating system information is not configured in the server configuration file, step 203 is directly executed after step 201 is executed; or, if the operating system information is configured in the server configuration file, but step 202 is judged as no, it can also be executed Step 203.

Step 203: the monitoring server judges the format of the server configuration file, if it is a text file format, then call the interface for processing the text file format, and perform step 204, if it is an XML file format, then call the interface for processing the XML file format, and perform step 204;

Step 204: the monitoring server parses all monitoring items from the server configuration file, and reads all monitoring items into memory;

Step 205: The monitoring server creates a working process group for each monitoring item according to the quantity of all monitoring items, so as to process the monitoring items in the server configuration file;

In this embodiment, the server configuration file contains the quantity of all monitoring items, which is used to indicate how many work process groups need to be created for data monitoring, such as, the configuration parameter is check_workers=6;

In addition, the number of process groups that the server can create by default is 1.5 multiplied by the number of CPUs, and the default is at least 4.

Step 206: The monitoring server registers timing events for each working process according to the collection interval of each monitoring item;

In this embodiment, the monitoring server registers a timing event for the corresponding working process according to the value of the monitoring information normal_check_interval in the monitoring item (ie, the collection interval of the monitoring item);

For example, if the monitoring information normal_check_interval is 1, set the worker process registration timing event to be executed every 1 minute. If the obtained monitoring information normal_check_interval is 2, set the worker process registration timing event to be executed every 2 minutes.

Step 207: each working process of the monitoring server monitors the corresponding monitoring item, and judges whether a timing event trigger of a certain working process is detected, if yes, then execute step 208, otherwise continue to execute step 207;

Specifically, it is judged whether there is a timing event of a certain working process that reaches an integer multiple of the collection interval of the monitoring item;

For example, if the collection interval of the monitoring item is 1 minute, when the work process corresponding to the monitoring item monitors that a timing event is triggered, data collection will be performed.

Step 208: the monitoring server judges the data collection method, if it is the monitoring agent data collection method, then execute step 209, if it is the SNMP agent data collection method, then execute step 210;

Step 209: The monitoring server sends the monitoring information corresponding to the monitoring item corresponding to the working process to the data collector, receives the collection result returned by the data collector, and executes step 211;

Step 210: The monitoring server sends the monitoring information corresponding to the monitoring item corresponding to the working process to the SNMP agent, receives the collection result returned by the SNMP agent, and executes step 211;

Step 211: the monitoring server judges whether the received collection result is abnormal, if so, execute step 212, otherwise execute step 215;

In this embodiment, the monitoring server judges whether the current collection value in the received collection result is less than the alarm threshold or the failure threshold, if yes, the received collection result is abnormal, otherwise the received collection result is normal;

For example, the collection result is:

Memory Free:/246MB(16%)|percentage=24; 20; 10; 0; 100; among them, the current collection value is 24, which is greater than the fault threshold of 10, and greater than the alarm threshold of 20, so the collection result is normal;

If the collection result received is:

Memory Free:/246MB(16%)|percentage18;20;10;0;100; Among them, the current collection value is 18, which is less than the alarm threshold value of 20 and greater than the fault threshold value of 10, so the collection result is abnormal;

Step 212: The monitoring server judges whether the abnormal collection result needs to be called an alarm according to the monitoring information of the monitored item, if yes, execute step 213, otherwise execute step 215;

In this embodiment, the monitoring server judges whether an abnormal collection result requires an alarm according to the value of the monitoring information notifications_enabled in the monitoring item. If the value of the monitoring information notifications_enabled is 1, an alarm is required. If the value of the monitoring information notifications_enabled is When 0, no alarm is required;

Step 213: The monitoring server judges whether to allow sending an alarm notification according to the monitoring information of the monitoring item in the server configuration file, if yes, then execute step 214, otherwise execute step 215;

In this embodiment, the monitoring server determines whether to allow sending an alarm notification according to the value of the monitoring information notification_period in the monitoring item;

For example, if the value of the monitoring information notification_period in the monitoring item is 24x7, it means that the alarm notification can be sent 7*24 hours, and the value of the monitoring information can be set by the user whether or not an alarm is required and when an alarm is required.

Step 214: the monitoring server selects an alarm notification method, sends the alarm information to the administrator, and executes step 215;

Among them, the alarm notification method can be voice alarm or email notification alarm, etc., which can be set by the user according to the needs.

Step 215: The monitoring server stores the corresponding collection results in the server database, and returns to step 207.

This embodiment also includes: the user interface regularly (preferably 1 minute) reads the collection result from the monitoring server database, and displays the read collection result on the interface;

In this embodiment, step 211 to step 215 can be replaced by: the server judges according to the server configuration file whether it is necessary to analyze the change trend of the collection result, if yes, save the collection result and return to step 207, otherwise directly return to step 207;

For example, when the value of save_result of the monitoring information of the monitoring item in the server configuration file is 1, it means that the change trend of the collection result needs to be analyzed and the collection result needs to be saved. If the value of save_result is 0, it means that the change trend of the collection result does not need to be analyzed. Save the collection result.

In addition, steps 211 to 215 can also be replaced by: the server judges whether log information needs to be recorded according to the collection result, if yes, records the log information, and returns to step 207, otherwise directly returns to step 207;

Specifically, the server judges whether the collection result is abnormal, and if so, records the log information, otherwise does not record the log information;

For example, the monitoring information is to collect the CPU usage rate. When the CPU usage rate in the collection result exceeds the preset alarm threshold, record the information that the CPU usage rate exceeds the threshold value of the monitored machine at the current time point.

Example 4

Embodiment 4 of the present invention provides a working method of a data collector in an operation and maintenance monitoring data system, as shown in FIG. 4 , including:

In this embodiment, preferably, the monitoring server sends the monitoring information to the data collector in the form of a command line, and the data collector performs the following operations after receiving the monitoring information:

Step 301: The data collector parses the received monitoring information in the form of a command line, and judges whether the command line parameters are wrong, and if so, sends an error message to the monitoring server, and ends, otherwise executes step 302;

Step 302: The data collector judges whether the monitoring information contains auxiliary information, if yes, displays the auxiliary information, returns the displayed response to the monitoring server, and ends, otherwise executes step 303;

In this embodiment, when the obtained command line parameters include auxiliary information such as help information and version information of the data collector, it is a command for displaying auxiliary information;

Step 303: the data collector assembles the data packet according to the monitoring information, and obtains the monitoring client specified in the monitoring information;

In this embodiment, the assembled data package contains the version number, package type, data collection command information and the checksum obtained by calculating the above data through a verification algorithm (such as crc32 algorithm, etc.), wherein the package type includes request package type and response packet type;

Step 304: the data collector sends the data packet to a designated monitoring client;

Step 305: the data collector receives the collection result returned by the monitoring client;

In this embodiment, the collection result includes the version number, the packet type, the collected data information and the checksum obtained by calculating the above data through a verification algorithm (such as crc32 algorithm, etc.), wherein the packet type includes the request packet type and Response packet type;

Step 306: the data collector judges whether the collection result is correct, if yes, then executes step 307, otherwise sends an error message to the monitoring server, and ends;

In this embodiment, the data collector obtains the checksum from the collection result, judges whether the checksum in the collection result is the same as the checksum of the data packet sent, and judges whether the version number in the collection result is the same as the version number in the data packet. Whether the number is the same, judge whether the packet type in the collection result is the same as the packet type in the data packet, if they are the same, the collection result is correct, otherwise the collection result is wrong;

Step 307: the data collector sends the collection result to the monitoring server.

Example 5

Embodiment 5 of the present invention provides a working method for monitoring a client in an operation and maintenance monitoring data system, as shown in FIG. 5 , including:

Step 401: the monitoring client loads the client configuration file, and monitors the connection port of the monitoring server according to the configuration parameters in the client configuration file;

For example, the configuration parameters in the client configuration file are:

log_facility=daemon

server_port=5666

allowed_hosts=127.0.0.1,192.168.88.179,192.168.88.189

dont_blame_nrpe=0

The monitoring items in the client configuration file are:

Among them, server_port=5666 in the configuration parameters of the client configuration file is the connection port between the monitoring client and the monitoring server.

Step 402: the monitoring client waits to receive the collection command sent by the monitoring server;

Step 403: When the monitoring client receives the acquisition command, according to the client configuration file, it is judged whether the monitoring server that sends the command is a device that allows access, if yes, then perform step 404, otherwise return an error message to the monitoring server, Return to step 402;

In this embodiment, it is judged whether the IP address of the monitoring server in the collection command is included in the IP address corresponding to the configuration parameter allowed_hosts value in the client configuration file, if yes, the monitoring server sending the command is a device that allows access, Otherwise, the monitoring server of this command is not a device that is allowed to be accessed;

For example, the configuration parameter allowed_hosts in the client configuration file is 127.0.0.1, 192.168.88.179, 192.168.88.189, and the IP address of the monitoring server obtained from the collection command is 192.168.88.179, so the server is allowed to access the Client's device.

Step 404: The monitoring client parses the received collection command, obtains the monitoring information to be collected, and judges whether the monitoring information is monitoring information that is allowed to be executed, and if so, executes step 405, otherwise returns an error message to the monitoring server, Return to step 402;

In this embodiment, it is judged whether the obtained monitoring information can be found in the configuration file of the client, if yes, the monitoring information is the monitoring information that is allowed to be executed, otherwise, the monitoring information is not the monitoring information that is allowed to be executed.

Step 405: the monitoring client sends the monitoring information to be collected to the data collection application;

For example, the monitoring information received by the client is used to collect the CPU usage, and the data collection application uses the top command to obtain the CPU usage. For example, the obtained CPU usage is:

Cpu(s): 2.9% us, 33.3% sy, 16.2% ni, 44.8% id, 2.9% wa, 0.0% hi, 0.0% si.

For example, the monitoring information received by the client is used to obtain the memory usage, and the data collection application obtains the memory usage through the free command. For example, the obtained memory usage is:

total used free shared buffers cached Mem: 775708 741808 33900 0 79948 268824

Step 406: The monitoring client judges whether the collection result returned by the data collection application is received within the preset time, if yes, then execute step 407, otherwise set the collection result as timeout, and execute step 407;

Preferably, the preset time is 10s.

Step 407: the monitoring client returns the collection result to the monitoring server.

Example 6

Embodiment 6 of the present invention provides a server for collecting operation and maintenance monitoring data, as shown in FIG. 6 , including:

The first judging module 601 is used for judging whether any monitoring item satisfies the collection condition according to the collection interval of each monitoring item in the server configuration file;

The first sending module 602 is configured to send the monitoring information corresponding to the monitoring items that meet the collection conditions to the client when the first judging module 601 judges that there are monitoring items that meet the collection conditions;

The first receiving module 603 is configured to receive the collection result returned by the client;

The processing module 604 is configured to process the collection result received by the first receiving module 603 and trigger the first judging module 601 .

In this embodiment, the server further includes a second judging module;

The second judging module is used to obtain the updated server configuration file, and judge whether any monitoring item satisfies the collection condition according to the collection interval of each monitoring item in the updated server configuration file, and when it is judged to be yes, trigger the first sending module 602 , when the judgment is no, continue to trigger the second judging module.

Specifically, the first judging module 601 specifically includes a registration unit and a detection unit;

The registration unit is used to register timing events for each monitoring item according to the collection interval of each monitoring item in the server configuration file;

The detection unit is configured to detect a timing event, and trigger the first sending module 602 when a timing event trigger is detected.

Among them, the registration unit is specifically used to parse all monitoring items from the server configuration file, create a working process group for each monitoring item according to the number of monitoring items, and register a timing for each working process group according to the collection interval of each monitoring item. event.

Further, the first sending module 602 is specifically configured to call the interface for processing the text file format when the server configuration file is in the text file format, and send the monitoring information corresponding to the monitoring items meeting the collection conditions to the client.

Furthermore, the first sending module 602 is specifically configured to call an interface for processing the XML file format when the server configuration file is in the XML file format, and send the monitoring information corresponding to the monitoring items meeting the collection conditions to the client.

Wherein, the processing module 604 specifically includes: a first judging unit, a second judging unit, a third judging unit, an alarm unit and a storage unit;

The first judging unit is used to judge whether the collection result received by the receiving module is abnormal, and when it is judged to be yes, trigger the second judging unit, and when it is judged to be no, trigger the first judging module 601;

The second judging unit is used to judge whether the abnormal collection result needs to be called an alarm according to the monitoring information of the monitoring item, and when it is judged to be yes, trigger the third judging unit, and when it is judged to be no, trigger the first judging module 601;

The third judging unit is used to judge whether the alarm notification is allowed to be sent according to the monitoring information in the monitoring item, when it is judged to be yes, trigger the alarm unit, and when it is judged to be no, trigger the first judging module 601;

The alarm unit is configured to select an alarm notification mode, send the alarm information to the administrator, and trigger the first determination module 601 when the third determination unit determines yes.

In this embodiment, the server further includes a storage module;

The processing module 604 is specifically used to judge whether it is necessary to analyze the change trend of the collected data according to the server configuration file, if it is judged to be yes, trigger the storage module, and when it is judged to be no, trigger the first judgment module 601;

The storage module is used to save the collection result and trigger the first judging module 601 .

In this embodiment, the server also includes a logging module;

The processing module 604 is specifically used to judge whether log information needs to be recorded according to the collected data, if it is judged to be yes, trigger the log recording module, and when it is judged to be no, trigger the first judging module 601;

The log recording module is configured to record log information and trigger the first judging module 601 .

Wherein, the first sending module 602 is specifically configured to send the monitoring information corresponding to the monitoring items meeting the collection conditions to the client when the data collection method in the acquisition server configuration file is the monitoring agent data collection method.

Further, the first sending module 602 is also used to send the monitoring information corresponding to the monitoring items that meet the collection conditions to the SNMP agent when the data collection method in the acquisition server configuration file is the SNMP data collection method;

The first receiving module 603 is further configured to receive the collected data returned by the SNMP agent, and trigger the processing module 604 .

In this embodiment, the server also includes a data collector module;

The data collector module includes a first receiving unit and a first sending unit;

The first sending module 602 is also used to send the monitoring information corresponding to the monitoring items that meet the collection conditions to the first receiving unit when the first judging module 601 judges that there are monitoring items that meet the collection conditions;

The first receiving unit is configured to receive the monitoring information sent by the first sending module;

The first sending unit is configured to send the monitoring information received by the first receiving unit to the client.

Wherein, the data collector module also includes a first collection unit;

The first collection unit is configured to collect data in the server according to the monitoring information and trigger the first sending unit when the execution mode of the data collection in the monitoring information acquisition is local execution.

Further, the first sending unit is specifically configured to send the monitoring information received by the first receiving unit to the client when the data collection in acquiring the monitoring information is performed by the client.

In this embodiment, the server includes a data acquisition application module;

The data collection application module includes a second receiving unit, a second collecting unit and a second sending unit;

The second receiving unit is used to receive the monitoring information sent by the data collector;

The second collecting unit is used to collect the data in the corresponding server according to the monitoring information received by the second receiving unit;

The second sending unit is configured to send the data in the server collected by the second collecting unit to the data collector module.

Wherein, the data collector module also includes a fourth judging unit and a display unit;

The fourth judging unit is used to judge whether the monitoring information received by the first receiving unit contains auxiliary information, if it is judged to be yes, trigger the display unit, and if it is judged to be no, trigger the first sending unit;

The display unit is used for displaying auxiliary information.

In this embodiment, the server further includes a third judging module and an error reporting module;

The third judging module is used to judge whether the data in the client can be collected according to the operating system information in the server configuration file when the first judging module 601 judges yes, and trigger the first sending module 602 when judging yes, When the judgment is no, trigger the error reporting module;

The error reporting module is used to report an error and continue to trigger the first judging module 601 .

Wherein, the third judging module specifically includes a third sending unit, a third receiving unit and a fifth judging unit;

The third sending unit is configured to send to the client a request for acquiring client operating system information;

A third receiving unit, configured to receive client operating system information returned by the client;

The fifth judging unit is used to judge whether the operating system information in the server configuration file matches the client operating system information received by the third receiving unit, and trigger the first sending module 602 when it is judged to be yes, and trigger Error reporting module.

The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto, any changes or variations that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention Replacement should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (36)

1. a kind of acquisition method of O&M monitoring data characterized by comprising

Step S1: it is full to judge whether there is monitored item according to the acquisition interval of monitored item each in server profile for server Otherwise sufficient acquisition condition continues to execute step S1 if so, thening follow the steps S2；It include clothes in the server profile The configuration parameter of starting of being engaged in and the monitoring configuration file of specified monitoring machine, monitoring configuration file have multiple, each monitoring Configuration file represents a machine of monitoring；The essential information in configuration file comprising machine and multiple monitored item are monitored, often It include multiple monitoring informations in a monitored item；Monitored item and monitoring information are by user's sets itself, or according to monitoring server Or the frequency of monitor client acquisition data is set；Monitored item includes CPU usage, cpu load, memory usage, magnetic Disk utilization rate, network interface flow, the website WEB response time；

Step S2: the corresponding monitoring information of the monitored item for meeting the acquisition condition is sent to client by the server；Institute Client is stated to be mounted on monitored machine；

Step S3: the server receives the collection result that the client returns；The collection result is by the client According to the monitoring information received on the monitored machine collected data；

Step S4: the server handles the collection result, return step S1；

The server includes data collector, the step S2 specifically:

Step b1: the corresponding monitoring information of the monitored item for meeting the acquisition condition is sent to the data and adopted by the server Storage；

Step b2: the monitoring information received is sent to the client by the data collector；

The step S4 include: the server alarmed according to the collection result, save analysis of data collected variation become Gesture, record log information；

Include: before the step S2

Step S1 ': the server obtains updated server profile, configures text according to the updated server The acquisition interval of each monitored item in part, judges whether there is monitored item and meets acquisition condition, if so, S2 is thened follow the steps, Otherwise step S1 ' is continued to execute.

2. the method according to claim 1, wherein the step S1 specifically: the server is according to The acquisition interval of each monitored item in server profile, for each monitored item register timed events, when detected timing When event triggers, then there is monitored item to meet acquisition condition, executes step S2, otherwise continue to execute step S1.

3. according to the method described in claim 2, it is characterized in that, described according to monitoring each in the server profile The acquisition interval of item registers timed events for each monitored item, specifically: the server is from the server profile Parsing obtains all monitored item, according to the quantity of all monitored item, progress of work group is created for each monitored item, according to each prison The acquisition interval of item is controlled, registers timed events for each progress of work group.

4. the method according to claim 1, wherein the client includes data acquisition applications, then the step Between the rapid S2 and step S3 further include:

Step d1: the monitoring information received is sent to the data acquisition applications by the client；

Step d2: the data acquisition applications are according to the number in the corresponding client of the monitoring information acquisition received According to the collection result collected is sent to the server.

5. the method according to claim 1, wherein the step S2 specifically: when the server configures text When the format of part is text file format, the interface of processing text file format is called, the monitored item pair of acquisition condition will be met The monitoring information answered is sent to the client.

6. the method according to claim 1, wherein the step S2 specifically: when the server configures text When the format of part is XML file format, the interface of processing XML file format is called, the monitored item for meeting acquisition condition is corresponding Monitoring information be sent to the client.

7. the method according to claim 1, wherein the step S4 is specifically included:

Step e1: whether the server judges the collection result abnormal, if so, thening follow the steps e2, otherwise returns to step Rapid S1；

Step e2: the server judges whether abnormal collection result needs to alarm according to the monitoring information of the monitored item, If so, then follow the steps e3, otherwise return step S1；

Step e3: the server determines whether transmission alert notice according to the monitoring information in the monitored item, if It is to then follow the steps e4, otherwise return step S1；

Step e4: the server selects alert notice mode, and warning message is sent to administrator, return step S1.

8. the method according to claim 1, wherein the step S4 specifically: the server is according to Server profile judges whether to need to analyze the variation tendency of the collection result, if it is, by the collection result It saves, return step S1, otherwise direct return step S1.

9. the method according to claim 1, wherein the step S4 specifically: the server is according to Collection result judges whether to need record log information, if it is, record log information, return step S1, are otherwise directly returned Return step S1.

10. the method according to claim 1, wherein

Before the step S3 further include: the client loads client configuration file, according to the client configuration file In configuration parameter, monitor with the connectivity port of the server, wait the monitoring information of the server to be received.

11. according to the method described in claim 10, it is characterized in that,

Before the step S3 further include:

Step f1: it after the client receives the monitoring information that the server is sent, is configured according to the client File judges whether the server is that the equipment accessed is allowed otherwise to continue waiting for receiving if so, thening follow the steps f2 Monitoring information；

Step f2: the client judges whether the monitoring information is to allow to execute according to the client configuration file Otherwise monitoring information continues waiting for receiving monitoring information if so, thening follow the steps f3；

Step f3: the client is according to the corresponding data of the monitoring information acquisition received, the acquisition that will be collected As a result it is sent to the server.

12. the method according to claim 1, wherein the step S2 specifically: when the server obtains institute When to state acquisition data mode in server profile be that monitoring agent acquires data mode, the monitoring of acquisition condition will be met The corresponding monitoring information of item is sent to client.

13. the method according to claim 1, wherein the step S2 and step S3 replacement are as follows: when described Server obtain the acquisition data mode in the server profile be SNMP agent acquire data mode when, satisfaction is adopted The corresponding monitoring information of the monitored item of collection condition is sent to SNMP agent, receives the collection result that the SNMP agent returns, holds Row step S4.

14. the method according to claim 1, wherein between the step b1 and the step b2 further include: institute Stating data collector and obtaining the executive mode of the data acquisition in the monitoring information is the machine execution, the data collector root According to the data in server described in the monitoring information acquisition, collection result is obtained, the collection result is sent to the clothes Business device, executes step S4.

15. the method according to claim 1, wherein the step b2 specifically: when the data collector obtains When the executive mode for taking the data in the monitoring information to acquire is client executing, the monitoring information received is sent To the client.

16. according to the method for claim 14, which is characterized in that the server includes data acquisition applications, then described Data of the data collector in the server according to the monitoring information acquisition, specifically:

Step c1: the monitoring information is sent to the data acquisition applications by the data collector；

Step c2: the data acquisition applications are according to the data in the corresponding server of the monitoring information acquisition received；

Step c3: the data in the collected server are sent to the data collector by the data acquisition applications.

17. the method according to claim 1, wherein before the step b2 further include: the data collector Judge, if it is, showing the auxiliary information, to terminate, otherwise hold whether comprising auxiliary information in the monitoring information received Row step b2.

18. the method according to claim 1, wherein between the step S2 and the step S3, further includes:

Step g1: the client is according to the corresponding data of the monitoring information acquisition received, the acquisition that will be collected As a result it is sent to the data collector；

Step g2: the data collector according in the collection result verification and, judge whether the collection result correct, If so, thening follow the steps g3, otherwise report an error, terminates；

Step g3: the collection result is sent to the server by the data collector.

19. the method according to claim 1, wherein

Between the step S1 and the step S2, further includes: the server is according to the behaviour in the server profile Make system information, judges whether that the data in the client can be acquired, if so, thening follow the steps S2, otherwise report an error, return Return step S1.

20. according to the method for claim 19, which is characterized in that described to judge whether to acquire in the client Data, specifically: the server sends the request for obtaining client operating system information to the client, receives the visitor Client operating system information that family end returns, judges operation system information in the server profile and receives Whether the client operating system information matches, if so, thening follow the steps S2, otherwise reports an error, return step S1.

21. a kind of server of O&M monitoring data collection characterized by comprising

First judgment module judges whether there is monitoring for the acquisition interval according to monitored item each in server profile Item meets acquisition condition；It include the configuration parameter and specified monitoring machine that service starts in the server profile Configuration file is monitored, monitoring configuration file has multiple a, machine of each monitoring configuration file representative monitoring；Monitoring configuration text Essential information and multiple monitored item in part comprising machine include multiple monitoring informations in each monitored item；Monitored item and prison Information is controlled by user's sets itself, or is set according to the frequency of monitoring server or monitor client acquisition data；Prison Control item include CPU usage, cpu load, memory usage, disk utilization rate, network interface flow, the website WEB response when Between；

First sending module, for when the first judgment module judgement there is monitored item to meet acquisition condition when, will be described in satisfaction The corresponding monitoring information of the monitored item of acquisition condition is sent to client；

First receiving module, the collection result returned for receiving the client；

Processing module, the collection result for receiving to first receiving module are handled, triggering described first Judgment module；

The processing module is specifically used for being alarmed according to the collection result, saves analysis of data collected variation tendency, note Record log information；

The server further includes data collector module and the second judgment module；

The data collector module includes the first receiving unit and the first transmission unit；

First sending module is also used to expire when the first judgment module, which judges, has monitored item to meet acquisition condition The corresponding monitoring information of monitored item of the foot acquisition condition is sent to first receiving unit；

First receiving unit, the monitoring information sent for receiving first sending module；

First transmission unit, the monitoring information for receiving first receiving unit are sent to the client End；

Second judgment module is configured for obtaining updated server profile according to server after the update The acquisition interval of each monitored item in file, judges whether there is monitored item and meets acquisition condition, when being judged as YES, described in triggering First sending module when being judged as NO, continues to trigger second judgment module.

22. server according to claim 21, which is characterized in that it is single to specifically include registration for the first judgment module Member and detection unit；

The registering unit is each monitoring for the acquisition interval according to monitored item each in the server profile Item registration timed events；

The detection unit, when having detected timed events triggering, triggers described first and sends mould for detecting timed events Block.

23. server according to claim 22, which is characterized in that the registering unit is specifically used for from the service Parsing obtains all monitored item in device configuration file, according to the quantity of monitored item, creates progress of work group, root for each monitored item According to the acquisition interval of each monitored item, timed events are registered for each progress of work group.

24. server according to claim 21, which is characterized in that first sending module is specifically used for when described When the format of server profile is text file format, the interface of processing text file format is called, pick-up slip will be met The corresponding monitoring information of the monitored item of part is sent to the client.

25. server according to claim 21, which is characterized in that first sending module is specifically used for when described When the format of server profile is XML file format, the interface of processing XML file format is called, acquisition condition will be met The corresponding monitoring information of monitored item be sent to the client.

26. server according to claim 21, which is characterized in that the processing module specifically includes: the first judgement is single Member, second judgment unit, third judging unit and alarm unit；

First judging unit, for judging whether the collection result that the receiving module receives is abnormal, is judged as When being, the second judgment unit is triggered, when being judged as NO, triggers the first judgment module；

The second judgment unit judges whether abnormal collection result needs for the monitoring information according to the monitored item Alarm, when being judged as YES, triggers the third judging unit, when being judged as NO, triggers the first judgment module；

The third judging unit sends alert notice for determining whether according to the monitoring information in the monitored item, When being judged as YES, the alarm unit is triggered, when being judged as NO, triggers the first judgment module；

The alarm unit, for alert notice mode being selected, by warning message when the third judging unit is judged as YES It is sent to administrator, triggers the first judgment module.

27. server according to claim 21, which is characterized in that the server further includes memory module；

The processing module, specifically for being judged whether to need to analyze the acquisition data according to the server profile Variation tendency when being judged as YES, triggers the memory module, when being judged as NO, triggers the first judgment module；

The memory module triggers the first judgment module for saving the collection result.

28. server according to claim 21, which is characterized in that the server further includes record log module；

The processing module, specifically for judging whether to need record log information according to the acquisition data, when being judged as YES, The record log module is triggered, when being judged as NO, triggers the first judgment module；

The record log module is used for record log information, triggers the first judgment module.

29. server according to claim 21, which is characterized in that

First sending module, specifically for being monitoring generation when obtaining the acquisition data mode in the server profile When reason acquisition data mode, the corresponding monitoring information of the monitored item for meeting the acquisition condition is sent to client.

30. server according to claim 21, which is characterized in that first sending module is also used to when acquisition institute When to state acquisition data mode in server profile be that SNMP mode acquires data mode, the monitoring of acquisition condition will be met The corresponding monitoring information of item is sent to SNMP agent；

First receiving module is also used to receive the collection result that the SNMP agent returns, triggers the processing module.

31. server according to claim 21, which is characterized in that the data collector module further includes the first acquisition Unit；

First acquisition unit, for being the machine execution when the executive mode for obtaining the data acquisition in the monitoring information When, according to the data in server described in the monitoring information acquisition, trigger first transmission unit.

32. server according to claim 21, which is characterized in that first transmission unit is specifically used for when acquisition When the executive mode of data acquisition in the monitoring information is client executing, institute that first receiving unit is received It states monitoring information and is sent to the client.

33. server according to claim 31, which is characterized in that the server includes data acquisition applications module；

The data acquisition applications module includes the second receiving unit, the second acquisition unit and the second transmission unit；

Second receiving unit, the monitoring information sent for receiving the data collector module；

Second acquisition unit, the corresponding clothes of the monitoring information acquisition for being received according to second receiving unit The data being engaged in device；

Second transmission unit, for the data in the collected server of second acquisition unit to be sent to institute State data collector module.

34. server according to claim 21, which is characterized in that the data collector module further includes the 4th judgement Unit and display unit；

4th judging unit, for whether judging in the monitoring information that first receiving unit receives comprising auxiliary Supplementary information when being judged as YES, triggers the display unit, when being judged as NO, triggers first transmission unit；

The display unit, for showing the auxiliary information.

35. server according to claim 21, which is characterized in that the server further includes third judgment module and report Mismatch block；

The third judgment module, for when the first judgment module is judged as YES, according to the server profile In operation system information, judge whether that the data in the client can be acquired, when being judged as YES, trigger it is described first hair Module is sent, when being judged as NO, report an error module described in triggering；

The module that reports an error continues to trigger the first judgment module for reporting an error.

36. server according to claim 35, which is characterized in that the third judgment module specifically includes third transmission Unit, third receiving unit and the 5th judging unit；

The third transmission unit, for sending the request for obtaining client operating system information to the client；

The third receiving unit, the client operating system information returned for receiving the client；

5th judging unit, for judging that the operation system information in the server profile and the third receive Whether the client operating system information that unit receives matches, and when being judged as YES, triggers first sending module, sentences Break when being no, report an error module described in triggering.