HK1159892A1 - System and method for monitoring service servers - Google Patents

Abstract

The invention provides a system and a method for monitoring a business server. The method comprises that: every time when executing a business processing method, a business module on the business server transmits business monitoring data to a monitoring acquisition module on the business server, wherein the business monitoring data indicates a business module name and a monitoring point number in a preset format; the monitoring acquisition module generates monitoring information based on at least one piece of received business monitoring data at a preset time interval; the monitoring acquisition module transmits the generated monitoring information to a monitoring server; the monitoring server stores the received monitoring information; and the monitoring server generates hierarchically statistical summary data based on the stored monitoring information according to a statistical time interval.

Description

System and method for monitoring a business server

Technical Field

The present invention relates generally to the field of monitoring, and more particularly, to a system and method for monitoring a traffic server.

Background

With the widespread use of computers, many business systems need to be monitored in enterprises. However, the monitoring system is limited to monitoring hardware systems. In reality, service processing functions or methods need to be monitored.

The existing distributed deployment can not ensure that each service monopolizes one server, and when one service system is deployed on a plurality of systems, the service system is inevitably influenced by other service systems. For example, whether a hardware system or an available state is a possible situation, but a problem arises with a certain business system.

In some cases, hundreds of business systems may need to be monitored, and a business system may have tens of business processing functions or methods. For such a large number of monitoring contents, a good content definition method is required to distinguish the monitoring information of different service systems, service functions, hardware systems, etc.; and provides a data base for the logic simplification of the acquisition, storage, real-time analysis, reporting and alarming of the monitoring data.

Disclosure of Invention

The present invention has been made to solve the above-mentioned disadvantages and problems occurring in the prior art. The system and the method of the invention can simply and conveniently monitor the service function and the service system at the same time, and are mainly embodied in the following points: the requirement of service function monitoring and service system monitoring can be met simultaneously by sampling the service system once; the service model is simple, and a simple, flexible and efficient data basis is provided for monitoring data acquisition and monitoring analysis of a large number of systems and a large number of services; the service logic is simplified, and the development cost is reduced in the aspects of monitoring information acquisition, storage, real-time monitoring, reporting, alarming and the like; the hierarchical relation of the business system can be expressed; the monitoring information of the monitoring system itself can be expressed.

According to an aspect of the present invention, there is provided a method for monitoring a traffic server, comprising: when a service module on a service server executes a service processing method, sending service monitoring data to a monitoring acquisition module on the service server, wherein the service monitoring data indicates a service module name and a monitoring point name in a preset format; generating, by the monitoring acquisition module, monitoring information based on at least one received traffic monitoring data when a predetermined time interval is reached; transmitting the generated monitoring information to a monitoring server; storing, by the monitoring server, the received monitoring information; and generating, by the monitoring server, hierarchical statistical summary data based on the stored monitoring information at statistical time intervals.

In the method, generating, by the monitoring acquisition module, monitoring information based on at least one received traffic monitoring data when a predetermined time interval is reached may include: analyzing the received service monitoring data by the monitoring acquisition module; generating heartbeat information data under the condition that the heartbeat information data corresponding to the service monitoring data does not exist; generating monitoring point information data under the condition that monitoring point information data corresponding to the service monitoring data does not exist; updating the monitoring point information data under the condition that the monitoring point information data corresponding to the service monitoring data exists; and when a preset time interval is reached, generating the monitoring information based on the heartbeat information data and the monitoring point information data.

The statistical time interval may include at least one of hours, days, weeks, months, and years.

The generated monitoring information may include at least one of monitoring point information, call number information, response number information, and response time information.

In the method, generating monitoring information based on the heartbeat information data and the monitoring point information data may include: and when the preset time interval is reached, if the calling frequency information is zero, the monitoring information is not generated.

In the method, the monitoring point information data may be cleared after the generated monitoring information is transmitted to the monitoring server.

According to another aspect, there is provided a system for generating monitoring information, comprising: at least one service server, each of said service servers comprising: a service module, which executes a service processing method; and a monitoring acquisition module that monitors the server, wherein the business module is configured to: whenever a service processing method is executed, sending service monitoring data to the monitoring acquisition module, wherein the service monitoring data indicates a service module name and a monitoring point name in a predetermined format, wherein the monitoring acquisition module is configured to: generating monitoring information based on at least one received traffic monitoring data when a predetermined time interval is reached, and transmitting the generated monitoring information to the monitoring server, wherein the monitoring server is configured to store the received monitoring information and to generate hierarchical statistical summary data based on the stored monitoring information at statistical time intervals.

In the system, the monitor acquisition module is further configured to: analyzing the service monitoring data, and generating heartbeat information data under the condition that heartbeat information data corresponding to the service monitoring data does not exist; generating monitoring point information data under the condition that monitoring point information data corresponding to the service monitoring data does not exist; updating the monitoring point information data in the presence of monitoring point information data corresponding to the traffic monitoring data, and wherein the monitoring acquisition module is further configured to: and when a preset time interval is reached, generating the monitoring information based on the heartbeat information data and the monitoring point information data.

The statistical time interval may include at least one of hours, days, weeks, months, and years.

The generated monitoring information may include at least one of monitoring point information, call number information, response number information, and response time information.

In the system, the monitor acquisition module is further configured to: and when the preset time interval is reached, if the calling frequency information is zero, the monitoring information is not generated.

In the system, the monitor acquisition module is further configured to: and after the generated monitoring information is sent to a monitoring server, clearing the monitoring point information data.

Drawings

The foregoing and other aspects, features and advantages of certain exemplary embodiments of the present invention will become apparent to those skilled in the art from the following description, taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram illustrating a system according to an exemplary embodiment of the present invention;

FIG. 2 is a diagram illustrating access of a monitoring point according to an exemplary embodiment of the present invention;

fig. 3 is a diagram illustrating a cache structure of monitoring point information data according to an exemplary embodiment of the present invention;

fig. 4 is a diagram illustrating a data structure of monitoring information according to an exemplary embodiment of the present invention;

fig. 5 is a diagram illustrating a data structure of monitoring point information stored by a monitoring server according to an exemplary embodiment of the present invention;

fig. 6 is a flowchart illustrating a method of generating heartbeat information data and monitoring point information data according to an exemplary embodiment of the present invention;

fig. 7 is a flowchart illustrating a method of generating monitoring information according to an exemplary embodiment of the present invention; and

fig. 8 is a flowchart illustrating a method of generating statistical summary data according to an exemplary embodiment of the present invention.

Detailed Description

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention. It includes various details to assist understanding, but they should be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

The present invention will be described in detail below with reference to the accompanying drawings.

Fig. 1 is a block diagram illustrating a system according to an exemplary embodiment of the present invention. The system includes business servers 110-1, 110-2 and a monitoring server 140.

Service modules 120-1 and 120-2 are respectively operated on the service servers 110-1 and 110-2. As will be appreciated by those skilled in the art, the service modules 120-1, 120-2 may perform various service processing functions or service processing methods according to actual needs. Although each service server 110-1 or 110-2 is shown in fig. 1 to include only one service module 120-1 or 120-2, it should be understood that each service server 110-1, 110-2 may include two or more service modules.

For the purpose of description, it is assumed that the machine name of the service server 110-1 is WEB1, the name of the service module 120-1 (user module) is jd.user, and the service processing functions that can be executed by the service module 120-1 include a Login method and a GetUser method; the machine name of the service server 110-2 is WEB2, the name of the service module 120-2 (user module) is jd.

When monitoring the above two service processing functions of the user module, two monitoring points are generated on the WEB 1:

(1) name of monitoring point: user.login; machine name: WEB1

(2) Name of monitoring point: jd.user.getuser; machine name: WEB1

Two monitoring points are also generated on WEB 2:

(1) name of monitoring point: user.login; machine name: WEB2

(2) Name of monitoring point: jd.user.getuser; machine name: WEB2

The service servers 110-1 and 110-2 are also respectively operated with monitoring acquisition modules 130-1 and 130-2, which are respectively used for acquiring service monitoring data and generating monitoring information.

Whenever the service module 120-1 (or the service module 120-2) performs a service processing function, it transmits service monitoring data to the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2). When a predetermined time interval is reached, the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) forms monitoring information according to at least one traffic monitoring data received during the predetermined time interval.

For example, upon receiving the traffic monitoring data from the traffic module 120-1 (or the traffic module 120-2), the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) analyzes the traffic monitoring data. According to the analysis, the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) generates heartbeat information data, monitoring point information data, or updates monitoring point information data, and the like. When the predetermined period of time is reached, the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) generates monitoring information and transmits the generated monitoring information to the monitoring server 140.

More specifically, the business monitoring data sent by the business module 120-1 (or the business module 120-2) to the monitoring collection module 130-1 (or the monitoring collection module 130-2) may be in a suitable format to identify the name of the business module and the name of the business processing method being performed (i.e., the monitoring point name). For example, in the above example, when the service module 120-1 executes the service processing method Login, the service monitoring data sent by the service module 120-1 to the monitoring acquisition module 130-1 may include a character string "jd. After receiving the service monitoring data including, for example, the character string "jd.user.login", the monitoring acquisition module 130-1 extracts the service module name "jd.user" and the monitoring point name "jd.user.login" from the service monitoring data. Then, the monitoring acquisition module 130-1 determines whether heartbeat information data corresponding to the service monitoring data exists, for example, whether heartbeat information data named "jd. In the absence of heartbeat information data corresponding to the traffic monitoring data (e.g., named "jd.user"), heartbeat information data corresponding to the traffic monitoring data (e.g., named "jd.user") is established. Then, the monitoring acquisition module 130-1 determines whether there is monitoring point information data corresponding to the service monitoring data, for example, whether there is monitoring point information data named "jd. Establishing monitoring point information data corresponding to the service monitoring data (e.g., named "jd.user.login") in the absence of the monitoring point information data corresponding to the service monitoring data (e.g., named "jd.user.login"); and in the case that there is monitoring point information data corresponding to the service monitoring data (for example, named "jd. When a predetermined time interval is reached, for example, when a preset time period of 1 minute is reached, the monitoring acquisition module 130-1 determines whether the call count information is zero. Under the condition that the information of the calling times is not zero, the monitoring acquisition module 130-1 generates monitoring information according to the heartbeat information data and the monitoring point information data, and sends the generated monitoring information to the monitoring server 140. And if the information of the number of times of calling is zero, the monitoring acquisition module 130-1 does not generate the monitoring information.

After the predetermined time interval is reached, the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) may reset the cached monitoring point information data, for example, may clear the monitoring point information data, regardless of whether the monitoring information is generated. Thus, the monitor acquisition module 130-1 (or the monitor acquisition module 130-2) may start the generation of the monitor information for the next predetermined time interval.

In the example described above, only information on the monitoring point name, the number of calls, the interval time is collected. However, information regarding any other aspect may also be employed as desired. For example, in many cases, it is desirable that the monitoring information includes information on the number of responses and response time.

In the case where the monitoring information is desired to include information on the number of responses and the response time, a time may be recorded at the start of execution of the service processing method and at the end of the service processing method, and then the difference between the two recorded values is the response time. The following problems exist if all response times are recorded: (1) for highly concurrent traffic, the amount of data is very large; (2) the large amount of data transmission can generate additional performance expense for the service system; (3) data transmission of a large amount of services can make the whole network environment bear a great load.

In order to overcome the problems, the invention adopts the following modes: when the service module 120-1 (or the service module 120-2) finishes the service processing method, the service monitoring data is sent to the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2), so that the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) can acquire the response time information. For example, when the service module 120-1 (or the service module 120-2) finishes executing the service processing method Login, the service monitoring data sent by the service module 120-1 (or the service module 120-2) to the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) may include a character string "jd.user.login; end ", although the invention is not limited to the traffic monitoring data format described above. The monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) may take a difference between a time when the execution of the business process method is started and a time when the business process method is ended as the response time, and by incrementing the response time information. Thus, the average response time information can be calculated from the number of responses and the response time information that are buffered. For example, when the predetermined time interval of 1 minute is reached, the number of responses is 100 times, and the total response time is 1 second, the average response time information of 100/1 seconds of 0.01 seconds may be calculated.

As will be appreciated by those skilled in the art, various changes can be made to the above examples. For example, the format of the transmitted traffic monitoring data may be changed as needed, and the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2) may employ an appropriate analysis means according to the format of the received traffic monitoring data.

Fig. 2 is a diagram illustrating access of a monitoring point according to an exemplary embodiment of the present invention. As shown in fig. 2, whenever the service module 120-1 (or the service module 120-2) starts or finishes executing the service processing method, the service module 120-1 (or the service module 120-2) directly calls the monitoring interface, so as to send service monitoring data to the monitoring collection module 130-1 (or the monitoring collection module 130-2). The access mode has strong invasion to a service system and is closely coupled. As will be appreciated by those skilled in the art, the monitoring access mode is not limited to the direct access mode described above, and other access modes may be adopted, for example, the call to the monitoring acquisition module may be injected by using AOP (aspect oriented) technology.

Fig. 3 is a diagram illustrating a cache structure of monitoring point information data according to an exemplary embodiment of the present invention. As shown in fig. 3, the cache structure of the monitoring point information data includes: a field key, which is monitoring point information (e.g., including the name of the service module and the name of the service processing method); a field responscount, which is a collection number of response times (i.e., response time information) within a predetermined time interval; a field TotalResponse, which is the total length of the response time within a predetermined time interval (i.e., response time information); and an attribute, Amount, which counts the number of service invocations in a predetermined time interval.

Fig. 4 is a diagram illustrating a data structure of monitoring information according to an exemplary embodiment of the present invention. As shown in fig. 4, in the data structure of the monitoring information, there are included: a field key, which is monitoring point information (e.g., including the name of the service module and the name of the service processing method); a field Server, which is the name of the Server where the monitoring point is located; a field Count, which is a service invocation Count within a predetermined time interval; a field responscount, which is a collection number of response times (i.e., response time information) within a predetermined time interval; and a field ResponseTime which is a response time (i.e., response time information) within a predetermined time interval.

Fig. 5 is a diagram illustrating a data structure of monitoring point information stored by a monitoring server according to an exemplary embodiment of the present invention. As shown in fig. 5, in the data structure of the monitoring information stored by the monitoring server, there are included: an attribute key, which is monitoring point information (including, for example, the name of the service module and the name of the service processing method); the attribute Server is the name of the Server where the monitoring point is located; an attribute Count, which is a service invocation Count within a predetermined time interval; an attribute responscount, which is the number of response time acquisitions within a predetermined time interval; an attribute ResponseTime, which is an average response time over a predetermined time interval; an attribute CreateTime, which is a creation time; an attribute Interval, which is a predetermined time Interval; an ID, which is a self-added database row identification; attribute State, which is a status field provided for the aggregate processing operation.

Fig. 6 is a flowchart illustrating a method of generating heartbeat information data and monitoring point information data according to an exemplary embodiment of the present invention.

As shown in fig. 6, the method begins with the traffic monitoring data being received by the monitoring collection module from the traffic module in step S10. As described above with reference to the traffic module 120-1 (or the traffic module 120-2) of fig. 1, whenever the traffic module 120-1 (or the traffic module 120-2) performs a traffic processing function, it transmits traffic monitoring data in an appropriate format to the monitoring acquisition module 130-1 (or the monitoring acquisition module 130-2). Thus, the monitoring collecting module 130-1 (or the monitoring collecting module 130-2) receives the service monitoring data from the service module 120-1 (or the service module 120-2).

In step S20, the monitoring acquisition module analyzes the received traffic monitoring data.

In step S30, the monitoring acquisition module determines whether there is corresponding heartbeat information data. If it is determined that the corresponding heartbeat information data does not exist, the corresponding heartbeat information data is generated in step S40.

Next, in step S50, it is determined whether or not there is corresponding monitoring point information data. If there is no corresponding monitoring point information data, corresponding monitoring point information data is generated in step S60. The generated monitoring point information may be in the format described with reference to fig. 3. Those skilled in the art will readily appreciate that the generated monitoring point information may be in any suitable format as desired, e.g., may include more fields (or attributes) or fewer fields (or attributes) than fig. 3. On the other hand, if there is corresponding monitoring point information data, the corresponding monitoring point information data is updated in step S70.

Although it is shown in fig. 6 that when it is determined in step S30 that there is no corresponding heartbeat information data, it proceeds to step S50 after generating heartbeat information data to determine whether there is corresponding monitoring point information data. However, in fact, since there is no corresponding monitoring point information data when there is no corresponding heartbeat information data, it is possible to proceed directly to step S60 after generating heartbeat information data in step S40 without going through step S50 to determine whether there is corresponding monitoring point information data.

Since how to receive the traffic monitoring data, analyze the traffic monitoring data, generate the heartbeat information data, and generate or update the monitoring point information data has been described in detail above with reference to fig. 1, the steps S10-S70 will not be described in detail herein.

Fig. 7 is a flowchart illustrating a method of generating monitoring information according to an exemplary embodiment of the present invention.

As shown in fig. 7, the method begins with a determination at step S10 as to whether a predetermined time interval has been reached. If it is determined in step S10 that the predetermined time interval has been reached, it is determined in step S20 whether there is traffic heartbeat data. On the other hand, when it is judged in step S10 that the predetermined time interval has not been reached, the waiting is continued. If it is judged in step S20 that the call count information is not zero, monitoring information is generated based on the monitoring point information data in step S30. Then, the buffered monitor point information data is reset in step S40, and the monitor point information data may be cleared, for example. In step S50, the generated monitoring information is transmitted to the monitoring server. The generated monitoring information may be in the format described with reference to fig. 4. Those skilled in the art will readily appreciate that the generated monitoring information may be in any suitable format as desired, e.g., may include more fields (or attributes) or fewer fields (or attributes) than fig. 4. On the other hand, if it is judged in step S20 that the call count information is zero, it indicates that the traffic processing method is not executed and the monitoring point information data is not generated in this period, and thus it is not necessary to generate the monitoring information, and the generation of the monitoring information for the next predetermined time interval is started.

Further, in step S20, it may be alternatively determined that both the call count information and the response count information are zero.

The monitoring server may store the received monitoring information, for example in the format described with reference to fig. 5. Those skilled in the art will readily appreciate that the monitoring server may store the received monitoring information in any suitable format as desired, e.g., may include more attributes or fewer attributes than fig. 5.

FIG. 8 is a flowchart illustrating a method of generating statistical summaries according to an exemplary embodiment of the invention.

Since the monitoring information stored in the monitoring server is collected at relatively small time intervals (e.g., 1 minute), there is a great problem in efficiency if analysis is performed based on the monitoring information. Therefore, the invention adopts a step-by-step statistical summary mode. Specifically, the present invention aggregates the stored monitoring information using a plurality of different statistical time intervals. For example, the plurality of different statistical time intervals may include hours, days, weeks, months, years.

As shown in fig. 8, it is determined in step S10 whether a predetermined statistical time interval is reached (by a hierarchical statistics totaling module (not shown) of the monitoring server). When it is judged in step S10 that the predetermined statistical time interval has been reached, the type of statistical time interval is determined in step S20. When the type of the statistical time interval is the first type, a first level statistical summary is generated from the stored monitoring information in step S30. And when the type of the statistical time interval is Nth (where N ≧ 2), a Nth level of statistical summary is generated in step S40 based on the Nth-1 level of statistical summary and/or based in part on the N-2 level of statistical summary.

For example, a plurality of statistical time intervals including hour, day, week, month and year are taken as an example, the hour is the 1 st type statistical time interval, and the day, week, month and year are the 2 nd, 3 rd, 4 th and 5 th type statistical time intervals, respectively. When the full time (for example, 2011 4/10/8) is reached, that is, when the statistical time interval is of the first type, a first-level statistical summary is generated from the stored monitoring information for a time period from 2011 4/10/7 to 2011 4/10/8. When the time reaches the full time (for example, when the time reaches 24 days 4 and 10 months in 2011), namely the statistical time interval is of a first type, generating a first-level statistical summary of which the time period is 23 days 4 and 10 months in 2011-24 days 4 and 10 months in 2011 according to the stored monitoring information; at this time, the statistical time interval is also of a second type (i.e., days), so a second-level statistical summary is generated from 24 first-level statistical summaries at a time period of 2011 year 4 month 10 day 1 to 2011 year 4 month 10 day 24; the statistical time interval is also of a third type (i.e., week) at this time, so a third level of statistical summary is generated from 7 second level statistical summaries with a time period of 2011 4 months 4 days-2011 4 months 10 days. As another example, when 24 days 4-30 of 2011 is reached, in addition to generating statistical summaries for the first (hours) and second (days), a fourth (month) summary is generated from 3 third-level (weeks) summaries from 4 months 4-24 days 2011 and 9 second-level (days) summaries from 4 months 1-3 days 2011 and 25-30 days 2011 over a period of time.

Of course, the various statistical time intervals described above are merely exemplary and may include, for example, half an hour, 6 hours, 12 hours, day, 10 days, 20 days, month, quarter, year, etc.

Further, the Nth level of summary, the Nth-1 level of statistical summary or stored monitoring information may be deleted when generating the Nth level of summary. Of course, the lower level statistical summaries or stored monitoring information may be deleted at other appropriate times as desired.

Based on the above processing, the efficiency of statistical analysis can be greatly improved, and the need for storage space can be reduced.

The monitoring information according to the invention comprises heartbeat information data and monitoring point information data, wherein the heartbeat information data can be used for determining the states of the system and the service in real time, and the monitoring point information data can be used for analyzing the historical state of the service.

It should be noted that the above describes separately apparatus and method embodiments of the invention, but details described for one embodiment may also be applied to another embodiment.

While the principles of the invention have been described in connection with specific embodiments thereof, it is to be understood that all or any of the steps or elements of the method and system of the invention may be implemented in software, hardware, firmware or any combination thereof, as would be understood by one of ordinary skill in the art after reading the description of the invention, using their basic programming skills.

Thus, the objects of the invention may also be achieved by running a software module or a set of software modules on any computing device. The computing device may be a general purpose device as is well known. The object of the invention is thus also achieved solely by providing a program product comprising program code for implementing the method or the apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is to be understood that the storage medium may be any known storage medium or any storage medium developed in the future.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

A computer program (also known as a program, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code).

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (12)

1. A method for monitoring a traffic server, comprising:

when a service module on a service server executes a service processing method, sending service monitoring data to a monitoring acquisition module on the service server, wherein the service monitoring data indicates a service module name and a monitoring point name in a preset format;

generating, by the monitoring acquisition module, monitoring information based on at least one received traffic monitoring data when a predetermined time interval is reached;

transmitting the generated monitoring information to a monitoring server;

storing, by the monitoring server, the received monitoring information; and

generating, by the monitoring server, hierarchical statistical summary data based on the stored monitoring information at statistical time intervals.

2. The method of claim 1, wherein generating, by the monitoring acquisition module, monitoring information based on at least one received traffic monitoring data upon reaching a predetermined time interval comprises:

analyzing the received service monitoring data by the monitoring acquisition module;

generating heartbeat information data under the condition that the heartbeat information data corresponding to the service monitoring data does not exist;

generating monitoring point information data under the condition that monitoring point information data corresponding to the service monitoring data does not exist;

updating the monitoring point information data under the condition that the monitoring point information data corresponding to the service monitoring data exists;

and when a preset time interval is reached, generating the monitoring information based on the heartbeat information data and the monitoring point information data.

3. The method of claim 1, wherein the statistical time interval comprises at least one of hours, days, weeks, months, years.

4. The method of claim 1, wherein the generated monitoring information includes at least one of monitoring point information, call number information, response number information, and response time information.

5. The method of claim 2, wherein generating the monitoring information based on the heartbeat information data and the monitoring point information data comprises:

and when the preset time interval is reached, if the calling frequency information is zero, the monitoring information is not generated.

6. The method of claim 2, wherein the monitoring point information data is cleared after the generated monitoring information is transmitted to the monitoring server.

7. A system for generating monitoring information, comprising:

at least one service server, each of said service servers comprising:

a service module, which executes a service processing method; and

a monitoring and collecting module is used for monitoring and collecting the data,

the monitoring server is used for monitoring the operation of the server,

wherein the traffic module is configured to: transmitting service monitoring data to the monitoring acquisition module whenever a service processing method is executed, wherein the service monitoring data indicates a service module name and a monitoring point name in a predetermined format,

wherein the monitoring acquisition module is configured to: generating monitoring information based on at least one received traffic monitoring data when a predetermined time interval is reached, and transmitting the generated monitoring information to the monitoring server,

wherein the monitoring server is configured to store the received monitoring information and to generate hierarchical statistical summary data based on the stored monitoring information at statistical time intervals.

8. The system of claim 7, wherein the first and second sensors are arranged in a single package,

wherein the monitoring acquisition module is further configured to: analyzing the service monitoring data, and generating heartbeat information data under the condition that heartbeat information data corresponding to the service monitoring data does not exist; generating monitoring point information data under the condition that monitoring point information data corresponding to the service monitoring data does not exist; updating the monitoring point information data in the presence of monitoring point information data corresponding to the service monitoring data, an

Wherein the monitoring acquisition module is further configured to: and when a preset time interval is reached, generating the monitoring information based on the heartbeat information data and the monitoring point information data.

9. The system of claim 7, wherein the statistical time interval comprises at least one of hours, days, weeks, months, years.

10. The system of claim 7, wherein the generated monitoring information includes at least one of monitoring point information, call number information, response number information, and response time information.

11. The system of claim 10, wherein the monitor acquisition module is further configured to:

and when the preset time interval is reached, if the calling frequency information is zero, the monitoring information is not generated.

12. The system of claim 8, wherein the monitor acquisition module is further configured to: and after the generated monitoring information is sent to a monitoring server, clearing the monitoring point information data.