CN117170894A

CN117170894A - Event center management method and device based on real-time calculation

Info

Publication number: CN117170894A
Application number: CN202310945898.9A
Authority: CN
Inventors: 石松坡
Original assignee: Shanghai Shuhe Information Technology Co Ltd
Current assignee: Shanghai Shuhe Information Technology Co Ltd
Priority date: 2023-07-31
Filing date: 2023-07-31
Publication date: 2023-12-05

Abstract

The application relates to an event center management method and device based on real-time calculation, event center management equipment and a storage medium. The method comprises the following steps: receiving an original event output by each message queue; the original event is reported to a corresponding message queue by each event source generating terminal; determining the event type to which the original event belongs according to the type identifier of the original event; wherein the event types include atomic events, derivative events, and complex events; based on an event processing rule database corresponding to a preconfigured event type, carrying out rule query according to an event code of an original event to obtain an event processing rule of the original event; and carrying out data processing on the original event according to the event processing rule to obtain a standardized event. By adopting the method, the flexibility of the event processing rule can be improved.

Description

Event center management method and device based on real-time calculation

Technical Field

The present application relates to the field of computer information technologies, and in particular, to an event center management method and apparatus based on real-time computing, an event center management device, and a storage medium.

Background

With the development of network technology, in the mobile internet era, massive business data are generated every day. Wherein, the real-time data generated when the business object changes in the self business field can be called an event. For example, data whose login state changes when a user logs in may be referred to as a user login event.

However, due to the diversity and complexity of event source generation terminals and events, conventional event management methods suffer from lower flexibility in event processing rules, resulting in lower overall efficiency in event processing for the event center.

Disclosure of Invention

In view of the foregoing, it is desirable to provide an event center management method, apparatus, event center management device, and storage medium based on real-time computation, which can improve the flexibility of event processing rules.

In a first aspect, there is provided a method for event center management based on real-time computing, the method comprising:

receiving an original event output by each message queue; the original event is reported to a corresponding message queue by each event source generating terminal;

determining the event type to which the original event belongs according to the type identifier of the original event; wherein the event types include atomic events, derivative events, and complex events;

Based on an event processing rule database corresponding to a preconfigured event type, carrying out rule query according to an event code of an original event to obtain an event processing rule of the original event;

and carrying out data processing on the original event according to the event processing rule to obtain a standardized event.

In one embodiment, when the event type is an atomic event, the event processing rule database is an atomic event processing rule database and the event processing rule is a data cleansing rule; the method comprises the steps of carrying out data processing on an original event according to an event processing rule to obtain a standardized event, wherein the method comprises the following steps: and carrying out data cleaning treatment on the atomic event according to the data cleaning rule to obtain a standardized event.

In one embodiment, when the event type is a derived event, the event processing rule database is a derived event processing rule database and the event processing rules include data cleansing rules, data filtering rules, and data conversion rules; the method comprises the steps of carrying out data processing on an original event according to an event processing rule to obtain a standardized event, wherein the method comprises the following steps: carrying out data cleaning treatment on the derived events according to the data cleaning rule to obtain the derived events after the data cleaning treatment; carrying out data filtering processing on the derived event after the data cleaning processing according to the data filtering rule to obtain a standardized event; or, carrying out data conversion processing on the derivative event after the data cleaning processing according to the data conversion rule to obtain a standardized event.

In one embodiment, when the event type is a complex event, the event processing rule database is a complex event processing rule database and the event processing rules include data cleansing rules, data filtering rules, data conversion rules, and data aggregation rules; the method comprises the steps of carrying out data processing on an original event according to an event processing rule to obtain a standardized event, wherein the method comprises the following steps: performing data cleaning processing on the complex event according to the data cleaning rule to obtain a complex event after the data cleaning processing; carrying out data filtering processing on the complex event subjected to data cleaning processing according to the data filtering rule to obtain a standardized event to be subjected to data aggregation; or, performing data conversion processing on the complex event subjected to data cleaning processing according to the data conversion rule to obtain a standardized event to be subjected to data aggregation; and carrying out data aggregation processing on the standardized event to be subjected to data aggregation according to the data aggregation rule to obtain the standardized event.

In one embodiment, the event source generating terminal comprises a service platform, a buried point platform and a feature platform; the business original event comprises a business event, a buried point event and a characteristic event; the service event is reported to the corresponding message queue by the service platform; reporting the embedded point event to a corresponding message queue by the embedded point platform; the feature event is reported by the feature platform to the corresponding message queue.

In one embodiment, the method further comprises: and according to the subscription application identification of the original event, matching the target subscription application, and publishing the standardized event to the target subscription application.

In one embodiment, the method further comprises: monitoring statistical indexes of data processing; the statistical indexes comprise event processing data quantity, event processing work quantity, event processing failure quantity and equipment resource occupancy rate; and outputting monitoring alarm information of the statistical index in response to the statistical index being greater than the corresponding index threshold.

In one embodiment, the step of configuring the event handling rules includes: responding to the first configuration operation on the basic information of the event processing rule in the rule configuration interface, and determining the basic information according to the result of the first configuration operation; the basic information comprises event types, event sources, event names, event classifications, event descriptions, event codes, service main keys, research and development responsible persons, service responsible persons and rule input samples; responding to the attribute information of the event processing rule in the rule configuration interface to carry out second configuration operation, and determining the attribute information according to the result of the second configuration operation; the attribute information comprises an attribute field, an attribute name, an attribute data type, an attribute remark, a rule output field and a conversion rule; and generating event processing rules according to the basic information and the attribute information.

In a second aspect, an event center management device based on real-time computation is provided, where the device includes an event receiving module, a type determining module, a rule query module, and a data processing module.

The event receiving module is used for receiving the original event output by each message queue; the original event is reported to a corresponding message queue by each event source generating terminal; the type determining module is used for determining the event type to which the original event belongs according to the type identifier of the original event; wherein the event types include atomic events, derivative events, and complex events; the rule query module is used for carrying out rule query according to the event code of the original event based on the event processing rule database corresponding to the event type to obtain the event processing rule of the original event; the data processing module is used for carrying out data processing on the original event according to the event processing rule to obtain a standardized event.

In a third aspect, an event centre management apparatus is provided, the computer apparatus comprising a memory storing a computer program and a processor implementing the steps of any of the method embodiments described above when the processor executes the computer program.

In a fourth aspect, a computer readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of any of the above-described method embodiments.

The event center management method, the device, the event center management equipment and the storage medium based on real-time calculation receive the original event output by each message queue; the original event is reported to a corresponding message queue by each event source generating terminal; then, determining the event type to which the original event belongs according to the type identifier of the original event; wherein the event types include atomic events, derivative events, and complex events; then, based on an event processing rule database corresponding to the pre-configured event type, carrying out rule query according to the event code of the original event to obtain the event processing rule of the original event; finally, data processing is carried out on the original event according to the event processing rule to obtain a standardized event, so that diversity, flexibility and expansibility of event reporting of the terminal generated by each event source are realized, standardized management of atomic events, derived events and complex events is realized, standardized output of the event is facilitated, access and use of subscribers are facilitated, efficiency of event standardized management is improved, flexibility of the event processing rule is improved, flexible adjustment of resources is carried out on different types of events, and resource waste or resource shortage is avoided.

Drawings

FIG. 1 is a diagram of an application environment for an event center management method based on real-time computing in one embodiment;

FIG. 2 is a first flow diagram of an event center management method based on real-time computing in one embodiment;

FIG. 3 is a flow diagram that illustrates the steps of configuring event handling rules in one embodiment;

FIG. 4 is a first schematic diagram of a rule configuration interface in one specific example;

FIG. 5 is a second schematic diagram of a rule configuration interface in one specific example;

FIG. 6 is a second flow diagram of an event center management method based on real-time computing in one embodiment;

FIG. 7 is a third flow diagram of an event center management method based on real-time computing in one embodiment;

FIG. 8 is a block diagram of an event center management device based on real-time computing in one embodiment;

fig. 9 is an internal structural diagram of an event center management device in one embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

In order that the application may be readily understood, a more complete description of the application will be rendered by reference to the appended drawings. Embodiments of the application are illustrated in the accompanying drawings. This application may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the description of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

It will be understood that the terms first, second, etc. as used herein may be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another element. For example, a first resistance may be referred to as a second resistance, and similarly, a second resistance may be referred to as a first resistance, without departing from the scope of the application. Both the first resistor and the second resistor are resistors, but they are not the same resistor.

It is to be understood that in the following embodiments, "connected" is understood to mean "electrically connected", "communicatively connected", etc., if the connected circuits, modules, units, etc., have electrical or data transfer between them.

As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," and/or the like, specify the presence of stated features, integers, steps, operations, elements, components, or groups thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof.

The event center management method based on real-time computing provided by the application can be applied to an application environment shown in figure 1. Wherein the terminal 102 communicates with the event center management server 104 via a network. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smartphones, tablet computers, and portable wearable devices, and the event center management server 104 may be implemented by a stand-alone server or a server cluster composed of a plurality of servers.

In one embodiment, as shown in fig. 2, a method for event center management based on real-time computing is provided, and the method is applied to the event center management server 104 in fig. 1 for illustration, and includes the following steps 202 to 208.

Step 202, receiving the original event output by each message queue.

The original event is reported to the corresponding message queue by each event source generating terminal. In particular, event center management server 104 may receive the original event output by each message queue.

In one embodiment, the event source generating terminal comprises a service platform, a buried point platform and a feature platform; the business original events comprise business events, buried point events and characteristic events.

The service event is reported to the corresponding message queue by the service platform; reporting the embedded point event to a corresponding message queue by the embedded point platform; the feature event is reported by the feature platform to the corresponding message queue.

In this embodiment, the event center management server 104 may receive a service event reported by the service platform to a corresponding message queue, and may also receive a buried event reported by the buried platform to a corresponding message queue, and may also receive a feature event reported by the feature platform to a corresponding message queue, thereby reducing difficulty of event access, improving convenience of event access, and realizing diversity, flexibility and expansibility of event reporting of each event source generating terminal.

In one embodiment, the message queues include a KAFKA message queue, an AMQP message queue, an API message queue, a RABBITMQ message queue, and a FLINK message queue.

In one specific example, the message queues include a KAFKA message queue, an AMQP message queue, an API message queue, and a FLINK message queue. The event source generation terminal comprises a buried point system, a characteristic platform and a service system, and the original event comprises a buried point event, a characteristic event and a service event; it can be appreciated that the embedded point system can report the embedded point event to the corresponding pre-configured message queue, and the message queue can output the embedded point event to the event center management server 104, so that the event center management server 104 receives the embedded point event output by the corresponding message queue. The feature platform may report the feature event to a corresponding pre-configured message queue, where the message queue may output the feature event to the event center management server 104, so that the event center management server 104 receives the feature event output by the corresponding message queue. The service system reports the service event to the corresponding pre-configured message queue, and the message queue can output the service event to the event center management server 104, so that the event center management server 104 receives the service event output by the corresponding message queue. The above is merely a specific example, and is flexibly set according to the user's needs in practical applications, and is not limited herein.

Step 204, determining the event type to which the original event belongs according to the type identifier of the original event.

Wherein the type identification of the original event is used for representing the event type to which the original event belongs. The event types to which the original event belongs include atomic events, derivative events, and complex events. Specifically, the atomic event refers to an event which is reported by each event source generating terminal and can output a standardized event only by performing data cleaning processing. The derived event refers to an event which is reported by each event source generating terminal and needs to be subjected to data cleaning processing and data filtering processing and/or data conversion processing. The complex event refers to an event which is reported by each event source generating terminal and needs to be subjected to data cleaning processing, data filtering processing and/or data conversion processing, and data aggregation processing.

Specifically, the event center management server 104 may determine an event type to which the original event belongs according to the type identifier of the original event. In one particular example, the data corresponding to the original event output by the message queue includes a type identification of the original event. Specifically, the type of the original event is identified as 01, and 01 characterizes the original event as an atomic event; the type of the original event is identified as 02, and 02 represents the original event as a derivative event; the type of the original event is identified as 03, and 03 characterizes the original event as a complex event. The above is merely a specific example, and is flexibly set according to the user's needs in practical applications, and is not limited herein.

And 206, based on an event processing rule database corresponding to the pre-configured event type, carrying out rule query according to the event code of the original event to obtain the event processing rule of the original event.

Specifically, the event center management server 104 pre-configures an event processing rule database corresponding to the event type. That is, the event types to which the different original events belong match the corresponding event handling rule database. The event center management server 104 performs rule query according to the event code of the original event based on the event processing rule database corresponding to the pre-configured event type, so as to obtain the event processing rule of the original event.

In one embodiment, as shown in FIG. 3, the step of configuring event handling rules includes steps 301 through 303.

Step 301, in response to performing a first configuration operation on the basic information of the event processing rule in the rule configuration interface, determining the basic information according to the result of the first configuration operation.

The basic information comprises type identification, event sources, event names, event classification, event description, event codes, service main keys, research and development responsible persons, service responsible persons and rule input samples. When the event center management server 104 performs the first configuration operation on the basic information of the event processing rule in the rule configuration interface, the basic information can be determined according to the result of the first configuration operation.

In one specific example, as shown in fig. 4, the rule configuration interface is configured with an input field of an event type, an input field of an event source, an input field of an event name, an input field of an event classification, an input field of an event description, an input field of an event code, an input field of a business key, an input field of a development responsible person, an input field of a business responsible person, and an input field of a rule input sample. Specifically, an input field of the event type is used for inputting the event type in the basic information of the event processing rule; the input field of the event source is used for inputting the event source in the basic information of the event processing rule; the input column of the event name is used for inputting the event name in the basic information of the event processing rule; the input field of the event classification is used for inputting the event classification in the basic information of the event processing rule; the input field of the event description is used for inputting the event description in the basic information of the event processing rule; the input field of the event code is used for inputting the event code in the basic information of the event processing rule; the input column of the business main key is used for inputting the business main key in the basic information of the event processing rule; the input bar of the input bar business main key of the research and development responsible person is used for inputting basic information of the event processing rule; the input field of the business responsible person is used for inputting the business responsible person in the basic information of the event processing rule; the input field of the rule input sample is used for inputting the rule input sample in the basic information of the event processing rule. The above is merely a specific example, and is flexibly set according to the user's needs in practical applications, and is not limited herein.

Step 302, responding to the attribute information of the event processing rule in the rule configuration interface to perform a second configuration operation, and determining the attribute information according to the result of the second configuration operation;

the attribute information comprises an attribute field, an attribute name, an attribute data type, an attribute remark, a rule output field and a conversion rule. When performing the second configuration operation on the attribute information of the event processing rule in the rule configuration interface, the event center management server 104 may determine the attribute information according to the result of the second configuration operation.

In one specific example, as shown in fig. 5, the rule configuration interface is configured with an input field for an attribute field, an input field for an attribute name, an input field for an attribute data type, an input field for an attribute remark, an input field for a rule output field, and an input field for a conversion rule. Specifically, an input field of the attribute field is used for inputting the attribute field in the attribute information of the event processing rule; the input column of the attribute name is used for inputting the attribute name in the attribute information of the event processing rule; the input field of the attribute data type is used for inputting the attribute data type in the attribute information of the event processing rule; the input field of the attribute remarks is used for inputting the attribute remarks in the attribute information of the event processing rule; the input field of the rule output field is used for inputting a rule output field in attribute information of the event processing rule; the input field of the conversion rule is used for inputting the conversion rule in the attribute information of the event processing rule. The above is merely a specific example, and is flexibly set according to the user's needs in practical applications, and is not limited herein.

Step 303, generating event processing rules according to the basic information and the attribute information.

Specifically, the event center management server 104 may generate event processing rules based on the base information determined according to the result of the first configuration operation and the attribute information determined according to the result of the second configuration operation. In addition, the event center management server 104 may store the event processing rules to the corresponding event processing rule database according to event types, and store the event processing rules to the corresponding storage locations in the corresponding event processing rule database according to event codes.

In the embodiment, in response to performing a first configuration operation on basic information of an event processing rule in a rule configuration interface, determining the basic information according to a result of the first configuration operation; then, responding to the attribute information of the event processing rule in the rule configuration interface to carry out second configuration operation, and determining the attribute information according to the result of the second configuration operation; then, according to the basic information and the attribute information, an event processing rule is generated, so that convenience in configuring the event processing rule is improved, and standardized management of the event is facilitated.

And step 208, carrying out data processing on the original event according to the event processing rule to obtain a standardized event.

Specifically, the event center management server 104 processes data of the original event according to the event processing rule obtained by the rule query, so that standardized events can be obtained, thereby not only realizing diversity, flexibility and expansibility of event reporting of each event source generation terminal, but also realizing standardized management of atomic events, derived events and complex events, facilitating standardization of event output, facilitating access and use of subscribers, improving efficiency of event standardized management, improving flexibility of event processing rule, flexibly adjusting resources for different types of events, and avoiding waste or shortage of resources.

In one embodiment, when the event type is an atomic event, the event handling rules database is an atomic event handling rules database and the event handling rules are data cleansing rules.

The method comprises the steps of carrying out data processing on an original event according to an event processing rule to obtain a standardized event, wherein the method comprises the following steps: and carrying out data cleaning treatment on the atomic event according to the data cleaning rule to obtain a standardized event.

Specifically, the atomic event refers to an event which is reported by each event source generating terminal and can output a standardized event only by performing data cleaning processing. The event center management server 104 may perform rule query through the event code of the atomic event based on a preconfigured atomic event processing rule database, so as to obtain the data cleaning rule of the atomic event; and then, carrying out data cleaning processing on the atomic event according to the data cleaning rule to obtain a standardized event.

In this embodiment, when the event type is an atomic event, the event processing rule database is an atomic event processing rule database and the event processing rule is a data cleansing rule; and meanwhile, data cleaning processing is carried out on the atomic events according to the data cleaning rules to obtain standardized events, so that the standardized events are standardized and output through the data cleaning processing on the atomic events, the efficiency of event standardized management is improved, the flexibility of event processing rules is improved, the flexible adjustment of resources is carried out on different types of events, and resource waste or resource shortage is avoided.

In one embodiment, when the event type is a derived event, the event processing rule database is a derived event processing rule database and the event processing rules include data cleansing rules, data filtering rules, and data conversion rules.

The method comprises the steps of carrying out data processing on an original event according to an event processing rule to obtain a standardized event, wherein the method comprises the following steps:

carrying out data cleaning treatment on the derived events according to the data cleaning rule to obtain the derived events after the data cleaning treatment;

carrying out data filtering processing on the derived event after the data cleaning processing according to the data filtering rule to obtain a standardized event; or, carrying out data conversion processing on the derivative event after the data cleaning processing according to the data conversion rule to obtain a standardized event.

Specifically, the derived event refers to an event that is reported by each event source generating terminal and that requires not only data cleansing processing but also data filtering processing and/or data conversion processing. The event center management server 104 may perform rule query through the event code of the derived event based on a preconfigured derived event processing rule database, so as to obtain the data cleaning rule, the data filtering rule and the data conversion rule of the derived event. Then, carrying out data cleaning treatment on the derived events according to the data cleaning rule to obtain derived events after the data cleaning treatment; then, carrying out data filtering processing on the derived event after the data cleaning processing according to the data filtering rule to obtain a standardized event; or, carrying out data conversion processing on the derivative event after the data cleaning processing according to the data conversion rule to obtain a standardized event.

In this embodiment, when the event type is a derivative event, the event processing rule database is a derivative event processing rule database and the event processing rules include a data cleansing rule, a data filtering rule, and a data conversion rule. Meanwhile, carrying out data cleaning treatment on the derived events according to the data cleaning rule to obtain derived events after the data cleaning treatment; then, carrying out data filtering processing on the derived event after the data cleaning processing according to the data filtering rule to obtain a standardized event; or, carrying out data conversion processing on the derived events after the data cleaning processing according to the data conversion rule to obtain standardized events, thereby realizing standardized output of the standardized events through data filtering processing or data conversion processing after the data cleaning processing of the derived events, improving the efficiency of standardized management of the events, improving the flexibility of the event processing rule, flexibly adjusting resources for different types of events, and avoiding waste or shortage of resources.

In one embodiment, when the event type is a complex event, the event processing rule database is a complex event processing rule database and the event processing rules include data cleansing rules, data filtering rules, data conversion rules, and data aggregation rules;

performing data cleaning processing on the complex event according to the data cleaning rule to obtain a complex event after the data cleaning processing;

carrying out data filtering processing on the complex event subjected to data cleaning processing according to the data filtering rule to obtain a standardized event to be subjected to data aggregation; or, performing data conversion processing on the complex event subjected to data cleaning processing according to the data conversion rule to obtain a standardized event to be subjected to data aggregation;

and carrying out data aggregation processing on the standardized event to be subjected to data aggregation according to the data aggregation rule to obtain the standardized event.

Specifically, the complex event refers to an event that is reported by each event source generating terminal and needs to perform not only data cleaning processing but also data filtering processing and/or data conversion processing, and data aggregation processing. The event center management server 104 may perform rule query through the event code of the complex event based on a pre-configured complex event processing rule database, so as to obtain the data cleaning rule, the data filtering rule, the data conversion rule and the data aggregation rule of the complex event. Then, carrying out data cleaning treatment on the complex event according to the data cleaning rule to obtain a complex event after the data cleaning treatment; then, carrying out data filtering processing on the complex event subjected to data cleaning processing according to a data filtering rule to obtain a standardized event to be subjected to data aggregation; or, performing data conversion processing on the complex event subjected to data cleaning processing according to the data conversion rule to obtain a standardized event to be subjected to data aggregation; and finally, carrying out data aggregation processing on the standardized event to be subjected to data aggregation according to the data aggregation rule to obtain the standardized event.

In one particular example, the aggregation process refers to merging or counting data from different event sources. Such as counting the number of times, accumulating the calculation of an event's certain attribute value, or calculating an average of the event's certain attribute values. The specific characterization rules are as follows: wherein a_or_b is used to characterize completion event a+ OR +completion event B; WI N_A_B is used to characterize the time window+completion event A+and +completion event B; the A_WI N_NOT_B is used for representing a completion event A+event window+incompletion+event B; WI N_A_CNT is used for representing the accumulated occurrence times in the event A time window; wi_a_sum is used to characterize the accumulation of certain business attributes of event a within a time window. The above is merely a specific example, and is flexibly set according to the user's needs in practical applications, and is not limited herein.

In this embodiment, when the event type is a complex event, the event processing rule database is a complex event processing rule database and the event processing rules include a data cleansing rule, a data filtering rule, a data conversion rule, and a data aggregation rule; carrying out data cleaning treatment on the complex event according to the data cleaning rule to obtain the complex event after the data cleaning treatment; then, carrying out data filtering processing on the complex event subjected to data cleaning processing according to a data filtering rule to obtain a standardized event to be subjected to data aggregation; or, performing data conversion processing on the complex event subjected to data cleaning processing according to the data conversion rule to obtain a standardized event to be subjected to data aggregation; finally, data aggregation processing is carried out on the standardized events to be subjected to data aggregation according to the data aggregation rules to obtain standardized events, so that the standardized events are standardized and output through data filtering processing or data conversion processing and data aggregation processing after data cleaning processing of complex events, the efficiency of event standardized management is improved, the flexibility of event processing rules is improved, flexible adjustment of resources is carried out on different types of events, and resource waste or resource shortage is avoided.

Based on the above, the event center management method based on real-time computation receives the original event output by each message queue; the original event is reported to a corresponding message queue by each event source generating terminal; then, determining the event type to which the original event belongs according to the type identifier of the original event; wherein the event types include atomic events, derivative events, and complex events; then, based on an event processing rule database corresponding to the pre-configured event type, carrying out rule query according to the event code of the original event to obtain the event processing rule of the original event; finally, data processing is carried out on the original event according to the event processing rule to obtain a standardized event, so that diversity, flexibility and expansibility of event reporting of the terminal generated by each event source are realized, standardized management of atomic events, derived events and complex events is realized, standardized output of the event is facilitated, access and use of subscribers are facilitated, efficiency of event standardized management is improved, flexibility of the event processing rule is improved, flexible adjustment of resources is carried out on different types of events, and resource waste or resource shortage is avoided.

In one embodiment, as shown in fig. 6, the method further includes step 601.

And step 601, according to the subscription application identification of the original event, matching the target subscription application, and publishing the standardized event to the target subscription application.

The event center management server 104 may match the subscription application identifier of the original event to a corresponding target subscription application; and then, publishing the standardized event obtained after the data processing of the original event according to the event processing rule to a target subscription application.

In one particular example, the subscription application identification of the original event may be, but is not limited to, a RoutingKey; at the same time, standardized events can also be published to the target subscription application through the message queue. The message queues may include, but are not limited to, a KAFKA message queue, an AMQP message queue, an API message queue, a RABBITMQ message queue, and a FLINK message queue. The above is merely a specific example, and is flexibly set according to the user's needs in practical applications, and is not limited herein.

In this embodiment, the target subscription application is matched according to the subscription application identifier of the original event, and the standardized event is published to the target subscription application, so that convenience in event standardized output and event publishing efficiency are improved.

In one embodiment, the event center management server 104 may further store a normalized event obtained by processing the data of the original event according to the event processing rule, and store the normalized time in the mysql database or the oss database. Thereby, convenience and efficiency of standardized event storage are improved.

In one embodiment, as shown in fig. 7, the method further includes step 701 and step 702.

Step 701, monitoring a statistical indicator of data processing.

Step 702, outputting the monitoring alarm information of the statistical index in response to the statistical index being greater than the corresponding index threshold.

The statistical indexes comprise event processing data quantity, event processing work quantity, event processing failure quantity and equipment resource occupancy rate. The event center management server 104 may also monitor statistical indicators including event processing data volume, event processing effort volume, event processing failure volume, and device resource occupancy; and then, when the statistical index is larger than the corresponding index threshold, the monitoring alarm information of the statistical index is output, so that the convenience of monitoring the statistical index is improved, and the configuration adjustment of the event center management server 104 is facilitated according to the monitoring alarm information.

In a specific example, the method further includes querying statistical indicators of the data processing. When the device resource occupancy rate is greater than the index threshold value of the device resource occupancy rate, not only the monitoring alarm information of the device resource occupancy rate is output, but also the automatic capacity expansion processing of the event center management server 104 can be performed. The above is merely a specific example, and is flexibly set according to the user's needs in practical applications, and is not limited herein.

In a specific example, the event center management server 104 may query a corresponding event according to a result of an event query operation of the event log management page in response to the event query operation. In addition, the event center management server 104 may also respond to the event reissue operation of the event log management page, and perform event reissue according to the result of the event reissue operation, so as to implement timely completion of the event reissue operation under the condition of time failure or the like.

In this embodiment, statistical indicators of data processing are monitored; and then, in response to the statistical index being greater than the corresponding index threshold, the monitoring alarm information of the statistical index is output, so that the convenience of monitoring the statistical index is improved, and the configuration adjustment of the event center management server 104 is facilitated according to the monitoring alarm information.

It should be understood that, although the steps in the flowcharts of fig. 2, 3, 6, and 7 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps of fig. 2, 3, 6 and 7 may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or stages are performed necessarily occur in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

In a second aspect, as shown in fig. 8, there is provided an event center management apparatus based on real-time computation, the apparatus including an event receiving module 810, a type determining module 820, a rule inquiring module 830, and a data processing module 840.

The event receiving module 810 is configured to receive an original event output by each message queue; the original event is reported to a corresponding message queue by each event source generating terminal; the type determining module 820 is configured to determine an event type to which the original event belongs according to the type identifier of the original event; wherein the event types include atomic events, derivative events, and complex events; the rule query module 830 is configured to perform rule query according to an event code of an original event based on an event processing rule database corresponding to the event type, so as to obtain an event processing rule of the original event; the data processing module 840 is configured to perform data processing on the original event according to the event processing rule, so as to obtain a standardized event.

In one embodiment, when the event type is an atomic event, the event processing rule database is an atomic event processing rule database and the event processing rule is a data cleansing rule; wherein the data processing module 840 includes a first processing unit.

The first processing unit is used for carrying out data cleaning processing on the atomic event according to the data cleaning rule to obtain a standardized event.

In one embodiment, when the event type is a derived event, the event processing rule database is a derived event processing rule database and the event processing rules include data cleansing rules, data filtering rules, and data conversion rules; wherein the data processing module 840 includes a second processing unit.

The second processing unit is used for carrying out data cleaning processing on the derived events according to the data cleaning rules to obtain the derived events after the data cleaning processing; the second processing unit is used for carrying out data filtering processing on the derived event after the data cleaning processing according to the data filtering rule to obtain a standardized event; or, carrying out data conversion processing on the derivative event after the data cleaning processing according to the data conversion rule to obtain a standardized event.

In one embodiment, when the event type is a complex event, the event processing rule database is a complex event processing rule database and the event processing rules include data cleansing rules, data filtering rules, data conversion rules, and data aggregation rules; wherein the data processing module 840 includes a third processing unit.

The third processing unit is used for carrying out data cleaning processing on the complex event according to the data cleaning rule to obtain the complex event after the data cleaning processing; the third processing unit is used for carrying out data filtering processing on the complex event after the data cleaning processing according to the data filtering rule to obtain a standardized event to be subjected to data aggregation; or, performing data conversion processing on the complex event subjected to data cleaning processing according to the data conversion rule to obtain a standardized event to be subjected to data aggregation; and the third processing unit is used for carrying out data aggregation processing on the standardized event to be subjected to data aggregation according to the data aggregation rule to obtain the standardized event.

In one embodiment, the apparatus further includes an event publishing module.

The event publishing module is used for matching the target subscription application according to the subscription application identification of the original event and publishing the standardized event to the target subscription application.

In one embodiment, the apparatus further includes a monitoring alarm module.

The monitoring alarm module is used for monitoring statistical indexes of data processing; the statistical indexes comprise event processing data quantity, event processing work quantity, event processing failure quantity and equipment resource occupancy rate; the monitoring alarm module is used for responding to the statistics index being larger than the corresponding index threshold value and outputting monitoring alarm information of the statistics index.

In one embodiment, the apparatus further includes a rule configuration module.

The rule configuration module is used for responding to the basic information of the event processing rule in the rule configuration interface to carry out a first configuration operation, and determining the basic information according to the result of the first configuration operation; the basic information comprises event types, event sources, event names, event classifications, event descriptions, event codes, service main keys, research and development responsible persons, service responsible persons and rule input samples; the rule configuration module is used for responding to the attribute information of the event processing rule in the rule configuration interface to carry out second configuration operation, and determining the attribute information according to the result of the second configuration operation; the attribute information comprises an attribute field, an attribute name, an attribute data type, an attribute remark, a rule output field and a conversion rule; the rule configuration module is used for generating event processing rules according to the basic information and the attribute information.

For specific limitations on the event center management device based on real-time computation, reference may be made to the above limitation on the event center management method based on real-time computation, and detailed description thereof will be omitted. The modules in the event center management device based on real-time computing may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, an event center management device is provided, which may be a server, and an internal structure thereof may be as shown in fig. 9. The event center management device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the event center management appliance is configured to provide computing and control capabilities. The memory of the event center management device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the event center management device is used for storing data of an event processing rule database corresponding to the event type. The network interface of the event center management device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements an event center management method based on real-time computing.

It will be appreciated by those skilled in the art that the structure shown in fig. 9 is merely a block diagram of a portion of the structure associated with the present inventive arrangements and is not limiting of the event center management device to which the present inventive arrangements are applied, and that a particular event center management device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchi nk) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.

Claims

1. An event center management method based on real-time computing, the method comprising:

receiving an original event output by each message queue; the original event is reported to the corresponding message queue by each event source generating terminal;

determining the event type of the original event according to the type identifier of the original event; wherein the event types include atomic events, derivative events, and complex events;

Based on a pre-configured event processing rule database corresponding to the event type, performing rule query according to the event code of the original event to obtain the event processing rule of the original event;

2. The method of claim 1, wherein when the event type is an atomic event, the event processing rule database is an atomic event processing rule database and the event processing rule is a data cleansing rule;

the data processing is performed on the original event according to the event processing rule to obtain a standardized event, which comprises the following steps:

and carrying out data cleaning processing on the atomic event according to the data cleaning rule to obtain the standardized event.

3. The method of claim 1, wherein when the event type is a derived event, the event processing rule database is a derived event processing rule database and the event processing rules include data cleansing rules, data filtering rules, and data conversion rules;

Performing data cleaning processing on the derived events according to the data cleaning rules to obtain the derived events after the data cleaning processing;

performing data filtering processing on the derivative event after the data cleaning processing according to the data filtering rule to obtain the standardized event; or, performing data conversion processing on the derivative event after the data cleaning processing according to the data conversion rule to obtain the standardized event.

4. The method of claim 1, wherein when the event type is a complex event, the event processing rule database is a complex event processing rule database and the event processing rules include data cleansing rules, data filtering rules, data conversion rules, and data aggregation rules;

performing data cleaning processing on the complex event according to the data cleaning rule to obtain the complex event after the data cleaning processing;

carrying out data filtering processing on the complex event after the data cleaning processing according to the data filtering rule to obtain a standardized event to be subjected to data aggregation; or, performing data conversion processing on the complex event after the data cleaning processing according to the data conversion rule to obtain the standardized event to be subjected to data aggregation;

5. The method according to any one of claims 1 to 4, wherein the event source generating terminal includes a service platform, a buried point platform, and a feature platform; the business original event comprises a business event, a buried point event and a characteristic event; the business event is reported to the corresponding message queue by the business platform; reporting the embedded point event to the corresponding message queue by the embedded point platform; and the feature event is reported to the corresponding message queue by the feature platform.

6. The method according to any one of claims 1 to 4, further comprising:

and according to the subscription application identification of the original event, matching a target subscription application, and publishing the standardized event to the target subscription application.

7. The method according to any one of claims 1 to 4, further comprising:

monitoring a statistical index of the data processing; the statistical indexes comprise event processing data quantity, event processing work quantity, event processing failure quantity and equipment resource occupancy rate;

And outputting monitoring alarm information of the statistical index in response to the statistical index being larger than a corresponding index threshold.

8. The method according to any one of claims 1 to 4, wherein the step of configuring the event handling rules comprises:

responding to a first configuration operation on basic information of the event processing rule in a rule configuration interface, and determining the basic information according to a result of the first configuration operation; the basic information comprises the type identifier, event sources, event names, event classification, event description, event codes, service main keys, research and development responsible persons, service responsible persons and rule input samples;

responding to second configuration operation on the attribute information of the event processing rule in the rule configuration interface, and determining the attribute information according to the result of the second configuration operation; the attribute information comprises an attribute field, an attribute name, an attribute data type, an attribute remark, a rule output field and a conversion rule;

and generating the event processing rule according to the basic information and the attribute information.

9. An event center management apparatus based on real-time computing, the apparatus comprising:

The event receiving module is used for receiving the original event output by each message queue; the original event is reported to the corresponding message queue by each event source generating terminal;

the type determining module is used for determining the event type of the original event according to the type identifier of the original event; wherein the event types include atomic events, derivative events, and complex events;

the rule query module is used for carrying out rule query according to the event code of the original event based on the event processing rule database corresponding to the event type to obtain the event processing rule of the original event;

and the data processing module is used for carrying out data processing on the original event according to the event processing rule to obtain a standardized event.

10. An event centre management apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method of any of claims 1 to 8 when the computer program is executed by the processor.

11. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 8.