CN110865921A - Data monitoring method, apparatus, readable storage medium and electronic device - Google Patents

Abstract

The embodiments of the present invention disclose a data monitoring method, an apparatus, a readable storage medium and an electronic device. In this embodiment of the present invention, after acquiring the data to be monitored, the data to be monitored is matched with a predetermined rule to determine the event type of the data to be monitored, and when the data to be monitored satisfies the triggering rule corresponding to the event type, the warning label corresponding to the data to be monitored is determined , and then determine the warning feedback information according to the data to be monitored and the warning label, so as to distribute the warning feedback information to the server corresponding to the data to be monitored. The method of the embodiment of the present invention enables the server to efficiently and accurately monitor the monitoring data automatically, and timely alarm notification when abnormal data occurs, effectively improving the accuracy and timeliness of warning when data is abnormal.

Description

Data monitoring method, apparatus, readable storage medium and electronic device

technical field

The disclosure of the present invention relates to the field of computer technology, in particular to a data monitoring method, device, readable storage medium and electronic device.

Background technique

With the continuous development of computer technology, the functions and types of application software become more and more abundant. When the application software is running, it needs to call the service through the network. At least one invocation of a service by any application software can be regarded as an event. With the increasing number of functions, types and services of application software, how to accurately monitor each event and issue a warning when an event is abnormal is an urgent problem to be solved.

SUMMARY OF THE INVENTION

In view of this, the purpose of the embodiments of the present invention is to provide a data monitoring method, device, readable storage medium and electronic device for accurately monitoring various event data generated during the running of an application, and Issue a warning in a timely manner when the data is abnormal.

In a first aspect, an embodiment of the present invention provides a data monitoring method, the method comprising:

Obtain the data to be monitored by a computer system having at least one processor;

Matching the data to be monitored with a predetermined rule by the computer system to determine the event type of the data to be monitored;

In response to the data to be monitored satisfying the triggering rule corresponding to the event type, the computer system determines the warning label corresponding to the data to be monitored;

determining warning feedback information by the computer system according to the data to be monitored and the warning label;

The computer system distributes the warning feedback information to a server corresponding to the data to be monitored.

Preferably, the obtaining the data to be monitored includes:

The log of the predetermined service is subscribed by the predetermined distributed publish-subscribe messaging system;

The log uploaded to the distributed publish-subscribe messaging system is acquired by a data collector in the data collection layer as the data to be monitored.

Preferably, the matching of the data to be monitored with a predetermined rule, and determining the event type of the data to be monitored includes:

The event router in the event routing layer matches the to-be-monitored data with a predetermined rule to determine the event type of the to-be-monitored data;

The method also includes:

The event router sends the to-be-monitored data to a rule processing node corresponding to the event type.

Preferably, each of the event routers in the event routing layer is managed by a rule manager.

Preferably, the determining of the warning label corresponding to the data to be monitored includes:

The warning label is determined by the rule processing node according to a predetermined warning rule.

Preferably, the distributing the warning feedback information to the server corresponding to the data to be monitored includes:

sending the warning feedback information to a predetermined message queue by the rule processing node in the rule processing layer to store the warning feedback information;

The warning feedback information in the message queue is distributed to the corresponding server by a predetermined distributed publish-subscribe message system.

In a second aspect, an embodiment of the present invention provides a data monitoring device, the device comprising:

A data acquisition unit for acquiring data to be monitored;

a type determination unit, configured to match the data to be monitored with a predetermined rule, and determine the event type of the data to be monitored;

A label determination unit, configured to determine a warning label corresponding to the data to be monitored in response to the data to be monitored satisfying the triggering rule corresponding to the event type;

an information determination unit, configured to determine warning feedback information according to the data to be monitored and the warning label;

An information distribution unit, configured to distribute the warning feedback information to the server corresponding to the data to be monitored.

In a third aspect, an embodiment of the present invention provides a computer-readable storage medium on which computer program instructions are stored, wherein, when executed by a processor, the computer program instructions implement any one of the first aspects. method.

In a fourth aspect, an embodiment of the present invention provides an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are The processor described above executes the following steps:

Obtain the data to be monitored;

Matching the data to be monitored with a predetermined rule to determine the event type of the data to be monitored;

In response to the to-be-monitored data satisfying the triggering rule corresponding to the event type, determining a warning label corresponding to the to-be-monitored data;

Determine warning feedback information according to the data to be monitored and the warning label;

Distributing the warning feedback information to the server corresponding to the data to be monitored.

Preferably, the obtaining the data to be monitored includes:

The log of the predetermined service is subscribed by the predetermined distributed publish-subscribe messaging system;

The log uploaded to the distributed publish-subscribe messaging system is acquired by a data collector in the data collection layer as the data to be monitored.

In this embodiment of the present invention, after acquiring the data to be monitored, the data to be monitored is matched with a predetermined rule to determine the event type of the data to be monitored, and when the data to be monitored satisfies the triggering rule corresponding to the event type, a warning label corresponding to the data to be monitored is determined , and then determine the warning feedback information according to the data to be monitored and the warning label, so as to distribute the warning feedback information to the server corresponding to the data to be monitored. The method of the embodiment of the present invention enables the server to efficiently and accurately monitor the monitoring data automatically, and timely alarm notification when abnormal data occurs, effectively improving the accuracy and timeliness of warning when data is abnormal.

Description of drawings

The above and other objects, features and advantages of the present invention will become more apparent from the following description of embodiments of the present invention with reference to the accompanying drawings, in which:

1 is a flowchart of a data monitoring method according to a first embodiment of the present invention;

Fig. 2 is the data flow chart of the data monitoring method of the first embodiment of the present invention;

3 is a schematic diagram of a data monitoring device according to a second embodiment of the present invention;

FIG. 4 is a schematic diagram of an electronic device according to a third embodiment of the present invention.

Detailed ways

The present disclosure is described below based on examples, but the present disclosure is not limited only to these examples. In the following detailed description of the present disclosure, some specific details are described in detail. The present disclosure may be fully understood by those skilled in the art without these detailed descriptions. Well-known methods, procedures, procedures, components and circuits have not been described in detail in order to avoid obscuring the essence of the present disclosure.

Furthermore, those of ordinary skill in the art will appreciate that the drawings provided herein are for illustrative purposes and are not necessarily drawn to scale.

Unless clearly required by the context, words such as "including", "comprising" and the like throughout this application should be construed in an inclusive rather than an exclusive or exhaustive sense; that is, in the sense of "including but not limited to".

In the description of the present disclosure, it should be understood that the terms "first", "second" and the like are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of the present disclosure, unless stated otherwise, "plurality" means two or more.

When the application software is running, it needs to call the service through the network. In the computer world, a "service" is a type of application that runs in the background. Services can generally provide users with different functions locally (that is, devices directly connected to users) or through a network, such as remote uploading/downloading of files by terminals, networking, and the like. At least one invocation of a service by any application software can be regarded as an event. With the increasing number of functions, types and services of application software, it is impossible to effectively monitor all events by manual methods. Therefore, how to accurately monitor each event and issue a warning in time when the event is abnormal is an urgent problem to be solved.

The execution body of the data monitoring method provided by the embodiment of the present invention includes, but is not limited to, a server.

FIG. 1 is a flowchart of a data monitoring method according to a first embodiment of the present invention. As shown in Figure 1, the method of this embodiment includes the following steps:

Step S100, acquiring data to be monitored.

In this embodiment, the data to be monitored is the data related to service invocation recorded during the running of the application software, such as the network transmission speed of the data during transmission through the network, the access frequency or the number of accesses to the predetermined web page, and the like.

In an optional implementation manner, the server may subscribe to the logs of the predetermined service through a predetermined distributed publish-subscribe message system, and the data fetcher (that is, the data collector) obtains and uploads the logs to the distribution at a predetermined period or according to actual needs. The log of the publish-subscribe messaging system is used as the data to be monitored. It is easy to understand that the cycle length can be set according to actual needs. In this step, the distributed publish-subscribe messaging system can be Kafka.

Kafka is a high-throughput distributed publish-subscribe messaging system with high performance, persistence, multi-copy backup and horizontal expansion. Service call data, etc. are quickly integrated and processed. In the production (product)-consume (consume) mode, Kafka can receive the data (that is, the log of the scheduled service) generated and reported by each application software in the calling service through the productor, and pass the consumer (or consumer groups) (that is, , consumer/group) for processing. When the data fetcher (data collector) in the data collection layer is used as the consumer of Kafka, Kafka will create a consumption request, get the response and other operations to the data fetcher to complete. Therefore, when the application software calls the service during the running process, Kafka can automatically send a data acquisition request to the database storing the logs of the predetermined service through the data fetcher, and collect the data to be monitored.

Optionally, the data to be monitored may also be obtained in other ways, such as directly obtaining the data to be monitored from the database, or obtaining the data to be monitored from the database through a log collection system (eg, flume, etc.), middleware, etc., which is not limited in this embodiment.

It is easy to understand that the number of data to be monitored may be one or multiple.

In step S200, the data to be monitored is matched with a predetermined rule, and the event type of the data to be monitored is determined.

In an optional implementation manner, the server can transmit the data to be monitored from the data collection layer to the event routing layer, and the corresponding event router (event router) in the event routing layer compares the data to be monitored with preset data according to actual needs. It matches the predetermined rules to determine the event type of the data to be monitored. The predetermined rule may be a predetermined field in the data to be monitored, etc., which is not limited in this embodiment. Events can be divided into system events and user events. System events are triggered by the system. For example, every 24 hours, the system date is updated one day backward. User events are operations that can be recognized by controls, such as pressing the OK button, selecting a radio option. button or checkbox, etc. Each data to be monitored is used to describe events related to service invocation. Therefore, key fields in each data to be monitored can be determined by matching predetermined rules, so as to determine the event type of each data to be monitored according to the values corresponding to the key fields. The event type may include load (loading), unload (unloading), abort (abort), select (selection), etc., which is not limited in this embodiment.

For example, if the event described by the data to be monitored is "the loading delay caused by calling service 1 is 200ms", and the predetermined rule includes the "load" field, the event type corresponding to the data to be monitored may be load.

Among them, the event router in the event routing layer can be managed by policy management (rule manager). The amount of data to be monitored varies in different periods. Therefore, in order to efficiently process the data to be monitored when the amount of data to be monitored is large or small, the number of event routers can be managed through policy management. Optionally, policy management can also be used to update the event router, etc.

After determining the event type of the data to be monitored, the server can send the data to be monitored to the worker policy (rule processing node) corresponding to the event type of the data to be monitored by the event router to perform alarm processing on the data to be monitored.

Optionally, the event type of the data to be monitored may not be determined by the event router of the event routing layer, and the server may directly determine the event type of the data to be monitored. It is easy to understand that if the event type of the data to be monitored is not determined by the eventrouter of the event routing layer, it is not necessary to send the data to be monitored to the worker policy corresponding to the event type.

Step S300, determining a warning label corresponding to the data to be monitored.

Specifically, the server may determine a warning label corresponding to the data to be monitored when the data to be monitored satisfies the triggering rule corresponding to the event type. The triggering rules can be determined according to actual needs. For example, when the event type is load, the corresponding triggering rule may be that the loading delay exceeds a predetermined threshold, the trend of loading delay is decreasing, etc.; when the event type is select, the corresponding triggering rule may be that the selection frequency exceeds a predetermined threshold, adjacent The year-on-year ratio (ie, the year-on-year to the ring ratio) of the selected frequency in the cycle exceeds a predetermined threshold and the like.

In an optional implementation manner, the warning label of the data to be monitored may be determined according to a predetermined warning rule through the worker policy of the rule processing layer. The worker policy is a type of worker node, and in this embodiment, it can be used to determine the triggering rule and the alarming rule for the data to be monitored. When the data to be monitored satisfies the triggering rule corresponding to the event type, it usually means that there is a problem with the performance of the corresponding application software. Therefore, the worker policy can be used to determine the rules of the data to be monitored, so as to determine the performance of the application software corresponding to the data to be monitored.

The alarm rules can be set according to actual needs, for example, including the alarm notification label, the silent switch identifier of the server corresponding to the data to be monitored, and so on. When the data to be monitored is abnormal, the alarm notification label can be used to notify the abnormal type of the data to be monitored, etc.; the silent switch flag is divided into two cases. Alarm notification, when it is marked as closed, the abnormal data can not be notified of alarm, and the server will automatically handle the abnormality. For example, the event described by the data to be monitored is "The loading delay caused by calling service 1 is 200ms", the corresponding event type is load, the trigger rule corresponding to load includes that the loading delay exceeds 100ms, and the alarm rule is that the silent switch is marked as ON and the alarm notification The label is the alarm notification label with abnormal loading. The data to be monitored satisfies the triggering rule corresponding to the load, and the warning label can be determined as the silent switch flag-on, and the alarm notification label-loading abnormality. It is easy to understand that for data to be monitored of different event types, the corresponding alarm rules may also be different.

Optionally, the warning label corresponding to the data to be monitored may be determined without using the worker policy of the rule processing layer, and the server may directly determine the warning label corresponding to the data to be monitored.

In step S400, the warning feedback information is determined according to the data to be monitored and the warning label.

Optionally, when the data to be monitored is abnormal, the server may determine the data to be monitored and the corresponding warning label used to represent the abnormality of the data to be monitored as warning feedback information; when there is no abnormality in the data to be monitored, the server may The data to be monitored and the corresponding warning label used to indicate that the data to be monitored is not abnormal are determined as warning feedback information.

Optionally, the server may also determine the data to be monitored and the corresponding warning label used to represent the abnormality of the data to be monitored as the warning feedback information only when the data to be monitored is abnormal.

It is easy to understand that when there is at least one abnormal data to be monitored and/or no abnormal data to be monitored, the server can respectively determine each data to be monitored and the corresponding warning label as warning feedback information.

Step S500: Distribute the warning feedback information to the server corresponding to the data to be monitored.

In an optional implementation manner, the worker policy in the rule processing layer can send the warning feedback information to a predetermined message queue to store the warning feedback information, and the message queue is sent to the message queue through a predetermined distributed publish-subscribe message system. The warning feedback information in is distributed to the corresponding server. In this step, the distributed publish-subscribe message system can also be Kafka.

In the publish-subscribe mode, Kafka can regard each worker policy in the rule processing layer as a publisher, and receive and store each message published by the worker policy through different message queues (in this embodiment, That is, the warning feedback information), and each message is distributed to the subscribers who subscribe to each message queue (in this embodiment, that is, the server corresponding to the data to be monitored). Optionally, the server corresponding to the data to be monitored may be determined according to the event type of the data to be monitored.

Optionally, other message distribution systems can also be used, such as the information distribution management system recorded in "Chen Jie. Information Distribution Management System Based on Content Distribution. Software Development and Evaluation, Volume 34, September 2008". information is distributed.

In this embodiment, a framework having a three-layer structure of a data collection layer, an event routing layer, and a rule processing layer may be Storm. Storm has low latency, distribution, scalability and high fault tolerance. Through the setting of each node, it can automatically monitor the monitoring data efficiently and accurately, and timely alarm notification when data is abnormal. Optionally, the frame having the above three-layer structure may also be another frame, which is not limited in this embodiment.

In this embodiment, after acquiring the data to be monitored, the data to be monitored is matched with a predetermined rule to determine the event type of the data to be monitored, and when the data to be monitored satisfies the triggering rule corresponding to the event type, a warning label corresponding to the data to be monitored is determined, Further, the warning feedback information is determined according to the data to be monitored and the warning label, so that the warning feedback information is distributed to the server corresponding to the data to be monitored. The method of this embodiment enables the server to efficiently and accurately perform automatic monitoring on the monitoring data, and timely alarm and notify when the data is abnormal, which effectively improves the accuracy and timeliness of the warning when the data is abnormal.

FIG. 2 is a data flow chart of the data monitoring method according to the first embodiment of the present invention. As shown in FIG. 2 , in conjunction with FIG. 1 , the data flow in this embodiment is as follows:

Step S100, acquiring data to be monitored.

The monitored application software includes application software 1-application software j (j≧1 and is an integer), and application software 1 is taken as an example here. After the application software 1 invokes a service, it will report the data generated by invoking the service. The server receives the reported data as the data to be monitored through the data collector of the data collection layer (that is, the data collector 11 ) as the consumer of Kafka.

In step S200, the data to be monitored is matched with a predetermined rule, and the event type of the data to be monitored is determined.

The data collector 11 transmits the data to be monitored uploaded by the application software 1 to the event routing layer, and the event router 2m (m ≥ 1 and an integer) of the event routing layer matches the data to be monitored with the predetermined rules, thereby determining the data to be monitored. event type.

Further, after determining the event type of the data to be monitored, the event router 2m sends the data to be monitored to the rule processing layer, and the rule processing node corresponding to the event type (ie, the rule processing node 32 ) receives the data to be monitored.

Step S300, determining a warning label corresponding to the data to be monitored.

The rule processing node 31 - the rule processing node 3k (k≧1 and an integer) in the rule processing layer are used for judging the trigger rule and the alarm rule for the data to be monitored. When the data to be monitored uploaded by the application software 1 satisfies the triggering rule corresponding to the event type, the rule processing node 32 determines the warning label corresponding to the data to be monitored according to the alarm rule.

In step S400, the warning feedback information is determined according to the data to be monitored and the warning label.

Step S500: Distribute the warning feedback information to the server corresponding to the data to be monitored.

The server can send the warning feedback information to the predetermined message queue through the worker policy in the rule processing layer to store the warning feedback information, and distribute the warning feedback information in the message queue to the subscribers through the predetermined distributed publish-subscribe message system. The subscriber of the message queue, that is, the server corresponding to the data to be monitored.

FIG. 3 is a schematic diagram of a data monitoring device according to a second embodiment of the present invention. As shown in FIG. 3 , the apparatus of this embodiment includes a data acquisition unit 301 , a type determination unit 302 , a label determination unit 303 , an information determination unit 304 , and an information distribution unit 305 .

The data acquisition unit 301 is used for acquiring data to be monitored. The type determining unit 302 is configured to match the data to be monitored with a predetermined rule, and determine the event type of the data to be monitored. The label determining unit 303 is configured to determine a warning label corresponding to the data to be monitored in response to the data to be monitored satisfying the triggering rule corresponding to the event type. The information determining unit 304 is configured to determine warning feedback information according to the data to be monitored and the warning label. The information distribution unit 305 is configured to distribute the warning feedback information to the server corresponding to the data to be monitored.

In this embodiment, after acquiring the data to be monitored, the data to be monitored is matched with a predetermined rule to determine the event type of the data to be monitored, and when the data to be monitored satisfies the triggering rule corresponding to the event type, a warning label corresponding to the data to be monitored is determined, Further, the warning feedback information is determined according to the data to be monitored and the warning label, so that the warning feedback information is distributed to the server corresponding to the data to be monitored. The device of this embodiment enables the server to efficiently and accurately monitor the monitoring data automatically, and timely alarm notification when abnormal data occurs, effectively improving the accuracy and timeliness of warning when data is abnormal.

FIG. 4 is a schematic diagram of an electronic device according to a third embodiment of the present invention. As shown in FIG. 4 , the electronic device: includes at least one processor 401 ; and a memory 402 that is communicatively connected to the at least one processor 401 ; Receive and send data under the control of the memory 402; wherein, the memory 402 stores instructions that can be executed by at least one processor 401, and the instructions are executed by at least one processor 401 to achieve:

Obtain the data to be monitored;

Matching the data to be monitored with a predetermined rule to determine the event type of the data to be monitored;

In response to the to-be-monitored data satisfying the triggering rule corresponding to the event type, determining a warning label corresponding to the to-be-monitored data;

Determine warning feedback information according to the data to be monitored and the warning label;

Distributing the warning feedback information to the server corresponding to the data to be monitored.

Further, the obtaining the data to be monitored includes:

The log of the predetermined service is subscribed by the predetermined distributed publish-subscribe messaging system;

The log uploaded to the distributed publish-subscribe messaging system is acquired by a data collector in the data collection layer as the data to be monitored.

Further, the matching of the data to be monitored with a predetermined rule, and determining the event type of the data to be monitored includes:

The event router in the event routing layer matches the to-be-monitored data with a predetermined rule to determine the event type of the to-be-monitored data;

The electronic device is also used to perform the following steps:

The event router sends the to-be-monitored data to a rule processing node corresponding to the event type.

Further, each of the event routers in the event routing layer is managed by a rule manager.

Further, the determining of the warning label corresponding to the data to be monitored includes:

The warning label is determined by the rule processing node according to a predetermined warning rule.

Further, the distributing the warning feedback information to the server corresponding to the data to be monitored includes:

sending the warning feedback information to a predetermined message queue by the rule processing node in the rule processing layer to store the warning feedback information;

The warning feedback information in the message queue is distributed to the corresponding server by a predetermined distributed publish-subscribe message system.

Specifically, the electronic device includes: one or more processors 401 and a memory 402, and one processor 401 is taken as an example in FIG. 4 . The processor 401 and the memory 402 may be connected through a bus or in other ways, and the connection through a bus is taken as an example in FIG. 4 . As a non-volatile computer-readable storage medium, the memory 402 can be used to store non-volatile software programs, non-volatile computer-executable programs and modules. The processor 401 executes various functional applications and data processing of the device by running the non-volatile software programs, instructions and modules stored in the memory 402, that is, the above-mentioned data monitoring method is implemented.

The memory 402 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function; the storage data area may store an option list and the like. Additionally, memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 402 may optionally include memory located remotely relative to processor 401, which may be connected to external devices via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

One or more modules are stored in the memory 402, and when executed by one or more processors 401, perform the data monitoring method in any of the above method embodiments.

The above product can execute the methods provided by the embodiments of the present application, and have functional modules and beneficial effects corresponding to the execution methods. For technical details not described in detail in the present embodiments, reference may be made to the methods provided by the embodiments of the present application.

In this embodiment, after acquiring the data to be monitored, the data to be monitored is matched with a predetermined rule to determine the event type of the data to be monitored, and when the data to be monitored satisfies the triggering rule corresponding to the event type, a warning label corresponding to the data to be monitored is determined, Further, the warning feedback information is determined according to the data to be monitored and the warning label, so that the warning feedback information is distributed to the server corresponding to the data to be monitored. This embodiment enables the server to efficiently and accurately perform automatic monitoring on the monitoring data, and timely alarm notification when abnormal data occurs, effectively improving the accuracy and timeliness of warning when data is abnormal.

The fourth embodiment of the present invention relates to a non-volatile storage medium for storing a computer-readable program, and the computer-readable program is used for a computer to execute some or all of the above method embodiments.

That is, those skilled in the art can understand that all or part of the steps in the method for implementing the above embodiments can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium and includes several instructions to make a device ( It may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

The embodiment of the present invention discloses A1, a data monitoring method, the method includes:

Obtain the data to be monitored by a computer system having at least one processor;

Matching the data to be monitored with a predetermined rule by the computer system to determine the event type of the data to be monitored;

In response to the data to be monitored satisfying the triggering rule corresponding to the event type, the computer system determines the warning label corresponding to the data to be monitored;

determining warning feedback information by the computer system according to the data to be monitored and the warning label;

The computer system distributes the warning feedback information to a server corresponding to the data to be monitored.

A2. In the method according to A1, the obtaining the data to be monitored includes:

The log of the predetermined service is subscribed by the predetermined distributed publish-subscribe messaging system;

The log uploaded to the distributed publish-subscribe messaging system is acquired by a data collector in the data collection layer as the data to be monitored.

A3. In the method according to A1, the matching of the data to be monitored with a predetermined rule, and determining the event type of the data to be monitored includes:

The event router in the event routing layer matches the to-be-monitored data with a predetermined rule to determine the event type of the to-be-monitored data;

The method also includes:

The event router sends the to-be-monitored data to a rule processing node corresponding to the event type.

A4. In the method according to A3, each of the event routers in the event routing layer is managed by a rule manager.

A5. In the method according to A3, the determining the warning label corresponding to the data to be monitored includes:

The warning label is determined by the rule processing node according to a predetermined warning rule.

A6. In the method according to A1, the distributing the warning feedback information to the server corresponding to the data to be monitored includes:

sending the warning feedback information to a predetermined message queue by the rule processing node in the rule processing layer to store the warning feedback information;

The warning feedback information in the message queue is distributed to the corresponding server by a predetermined distributed publish-subscribe message system.

The embodiment of the present invention also discloses B1, a data monitoring device, the device includes:

A data acquisition unit for acquiring data to be monitored;

a type determination unit, configured to match the data to be monitored with a predetermined rule, and determine the event type of the data to be monitored;

A label determination unit, configured to determine a warning label corresponding to the data to be monitored in response to the data to be monitored satisfying the triggering rule corresponding to the event type;

an information determination unit, configured to determine warning feedback information according to the data to be monitored and the warning label;

An information distribution unit, configured to distribute the warning feedback information to the server corresponding to the data to be monitored.

The embodiment of the present invention also discloses C1, a computer-readable storage medium on which computer program instructions are stored, wherein the computer program instructions implement the method according to any one of A1-A6 when executed by a processor .

The embodiment of the present invention also discloses D1, an electronic device including a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are The processor performs the following steps:

Obtain the data to be monitored;

Matching the data to be monitored with a predetermined rule to determine the event type of the data to be monitored;

In response to the to-be-monitored data satisfying the triggering rule corresponding to the event type, determining a warning label corresponding to the to-be-monitored data;

Determine warning feedback information according to the data to be monitored and the warning label;

Distributing the warning feedback information to the server corresponding to the data to be monitored.

D2. In the electronic device according to D1, the acquiring the data to be monitored includes:

The log of the predetermined service is subscribed by the predetermined distributed publish-subscribe messaging system;

The log uploaded to the distributed publish-subscribe messaging system is acquired by a data collector in the data collection layer as the data to be monitored.

D3. In the electronic device according to D1, the matching of the data to be monitored with a predetermined rule, and determining the event type of the data to be monitored includes:

The event router in the event routing layer matches the to-be-monitored data with a predetermined rule to determine the event type of the to-be-monitored data;

The electronic device is also used to perform the following steps:

The event router sends the to-be-monitored data to a rule processing node corresponding to the event type.

D4. In the electronic device according to D3, each event router in the event routing layer is managed by a rule manager.

D5. In the electronic device according to D3, the determining of the warning label corresponding to the data to be monitored includes:

The warning label is determined by the rule processing node according to a predetermined warning rule.

D6. In the electronic device according to D1, the distributing the warning feedback information to the server corresponding to the data to be monitored includes:

sending the warning feedback information to a predetermined message queue by the rule processing node in the rule processing layer to store the warning feedback information;

The warning feedback information in the message queue is distributed to the corresponding server by a predetermined distributed publish-subscribe message system.

Those of ordinary skill in the art can understand that the above-mentioned embodiments are specific embodiments for realizing the present invention, and in practical applications, various changes can be made in form and details without departing from the spirit and the spirit of the present invention. scope.

Claims (10)

1. a data monitoring method, is characterized in that, described method comprises: Obtain the data to be monitored by a computer system having at least one processor; Matching the data to be monitored with a predetermined rule by the computer system to determine the event type of the data to be monitored; In response to the data to be monitored satisfying the triggering rule corresponding to the event type, the computer system determines the warning label corresponding to the data to be monitored; determining warning feedback information by the computer system according to the data to be monitored and the warning label; The computer system distributes the warning feedback information to a server corresponding to the data to be monitored. 2. The method according to claim 1, wherein the acquiring the data to be monitored comprises: The log of the predetermined service is subscribed by the predetermined distributed publish-subscribe messaging system; The log uploaded to the distributed publish-subscribe messaging system is acquired by a data collector in the data collection layer as the data to be monitored. 3. The method according to claim 1, wherein the matching the data to be monitored with a predetermined rule, and determining the event type of the data to be monitored comprises: The event router in the event routing layer matches the to-be-monitored data with a predetermined rule to determine the event type of the to-be-monitored data; The method also includes: The event router sends the to-be-monitored data to a rule processing node corresponding to the event type. 4. The method according to claim 3, wherein each of the event routers in the event routing layer is managed by a rule manager. 5. The method according to claim 3, wherein the determining the warning label corresponding to the data to be monitored comprises: The warning label is determined by the rule processing node according to a predetermined warning rule. 6. The method according to claim 1, wherein the distributing the warning feedback information to the server corresponding to the data to be monitored comprises: sending the warning feedback information to a predetermined message queue by the rule processing node in the rule processing layer to store the warning feedback information; The warning feedback information in the message queue is distributed to the corresponding server by a predetermined distributed publish-subscribe message system. 7. A data monitoring device, wherein the device comprises: A data acquisition unit for acquiring data to be monitored; a type determination unit, configured to match the data to be monitored with a predetermined rule, and determine the event type of the data to be monitored; A label determination unit, configured to determine a warning label corresponding to the data to be monitored in response to the data to be monitored satisfying the triggering rule corresponding to the event type; an information determination unit, configured to determine warning feedback information according to the data to be monitored and the warning label; An information distribution unit, configured to distribute the warning feedback information to the server corresponding to the data to be monitored. 8. A computer-readable storage medium on which computer program instructions are stored, wherein the computer program instructions, when executed by a processor, implement the method according to any one of claims 1-6. 9. An electronic device comprising a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to achieve Follow the steps below: Obtain the data to be monitored; Matching the data to be monitored with a predetermined rule to determine the event type of the data to be monitored; In response to the to-be-monitored data satisfying the triggering rule corresponding to the event type, determining a warning label corresponding to the to-be-monitored data; Determine warning feedback information according to the data to be monitored and the warning label; Distributing the warning feedback information to the server corresponding to the data to be monitored. 10. The electronic device according to claim 9, wherein the acquiring the data to be monitored comprises: The log of the predetermined service is subscribed by the predetermined distributed publish-subscribe messaging system; The log uploaded to the distributed publish-subscribe messaging system is acquired by a data collector in the data collection layer as the data to be monitored.

Images