System event processing method, operation and maintenance system, device, medium, and program product

Abstract

Embodiments of the present disclosure provide a system event processing method, an operation and maintenance system, a device, a medium, and a program product. The method comprises: an operation and maintenance system compares respective generation times of current time series data and acquired valid time series data; and if the generation time of the current time series data is later than that of the valid time series data, the operation and maintenance system can start engine inspection, i.e., determine whether the current time series data meets a preset threshold condition, and generate a system event reflecting the operation state of an engine to be subjected to operation and maintenance. In the method, when performing operation and maintenance on an engine, the operation and maintenance system uses a condition corresponding to the engine; that is, an operation and maintenance engine has conditions corresponding to respective different engines, so that the universality of the operation and maintenance system can be improved. In addition, by means of time delay comparison, the operation and maintenance system can be further made to start inspection only when receiving new time series data, thereby realizing real-time inspection of engines.

Description

[0001] TECHNICAL FIELD The present disclosure relates to the field of device operation and maintenance technology, and more particularly to a system event processing method, operation and maintenance system, device, medium, and program product. Background In the computer field, an engine can be considered as a packaged combination of code and function libraries, which implements specific functions through invocation. Common engines include computing engines that implement computing functions, storage engines that implement storage functions, and database engines that implement database functions. In the prior art, operation and maintenance systems provide inspection services for engines, monitoring engine performance indicators to perform operation and maintenance on the engines and ensure their normal operation. In practice, different engines have different specific performance indicators, often requiring the use of different operation and maintenance systems. This means that the versatility of the operation and maintenance systems is limited. Based on the above description, improving the versatility of the operation and maintenance systems has become an urgent issue. SUMMARY OF THE INVENTION In view of this, embodiments of the present disclosure provide a system event processing method, operation and maintenance system, device, medium, and program product to improve the versatility of the operation and maintenance systems. In a first aspect, embodiments of the present disclosure provide a system event processing method, comprising: obtaining current time series data reflecting an engine performance indicator value; if the generation time of the current time series data is later than the generation time of previously obtained valid time series data, determining a preset threshold condition corresponding to the engine to be operated; and generating a system event reflecting the operating status of the engine to be operated based on whether the current time series data satisfies the preset threshold condition. In a second aspect, embodiments of the present disclosure provide an operation and maintenance system, comprising: a processing component and an event output component; the processing component is configured to obtain current time series data reflecting an engine performance indicator value; if a transmission delay formed by the difference between the generation time of the current time series data and the acquisition time of the time series data is not greater than a preset delay, determining a preset threshold condition corresponding to the engine to be operated; and generating a processing result based on whether the current time series data satisfies the preset threshold condition; and the event output component is configured to generate a system event reflecting the operating status of the engine to be operated based on the processing result. In a third aspect, an embodiment of the present disclosure provides an electronic device, including: a memory configured to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the system event processing method described in the first aspect. The electronic device may also include a communication interface configured to communicate with other devices or communication systems.In a fourth aspect, embodiments of the present disclosure provide a non-transitory machine-readable storage medium storing executable code. When the executable code is executed by a computing system of an electronic device, the computing system is enabled to implement at least the system event processing method described in the first aspect. In a fifth aspect, embodiments of the present disclosure provide a computer program product. This computer program product includes a computer program or instructions. When executed by a processor, the computer program or instructions cause the processor to implement the system event processing method described in the first aspect. In the system event processing method provided by embodiments of the present disclosure, an operation and maintenance system can obtain current time series data reflecting engine performance indicator values. If the generation time of this current time series data is later than the generation time of previously obtained valid time series data, indicating that this current time series data is the most recently generated time series data for the engine to be operated and maintained, the operation and maintenance system can then initiate an inspection of the engine. The specific process is as follows: The operation and maintenance system determines the preset threshold conditions corresponding to the engine to be maintained and generates a corresponding system event based on whether the current time series data meets these threshold conditions. This system event serves as an inspection result, reflecting whether the engine's operating status is normal or abnormal. In this method, when performing maintenance on an engine, the operation and maintenance system uses the conditions corresponding to that engine. This means that different operation and maintenance engines have their own corresponding conditions, thereby improving the versatility of the operation and maintenance system. Furthermore, by comparing generation times, the operation and maintenance system can only begin engine inspections upon receiving the engine's latest time series data, thus achieving real-time inspection of the engine. Furthermore, the system events generated by real-time inspections can reflect the engine's latest operating status, allowing the provider of the engine to understand the engine's operating status in real time. BRIEF DESCRIPTION OF THE DRAWINGS To more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present disclosure. Those skilled in the art can derive other drawings based on these drawings without inventive effort.Figure 1 is a flowchart of a system event processing method provided by an embodiment of the present disclosure; Figure 2 is a flowchart of another system event processing method provided by an embodiment of the present disclosure; Figure 3 is a schematic diagram illustrating the relationship between events, rules, and conditions provided by an embodiment of the present disclosure; Figure 4 is a structural diagram of an operation and maintenance system provided by an embodiment of the present disclosure; Figure 5 is a structural diagram of another operation and maintenance system provided by an embodiment of the present disclosure; Figure 6 is a schematic diagram illustrating the working process of an operation and maintenance system provided by an embodiment of the present disclosure; Figure 7 is a structural diagram of a system event processing device provided by an embodiment of the present disclosure; and Figure 8 is a structural diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS To further clarify the objectives, technical solutions, and advantages of the embodiments of the present disclosure, the technical solutions in the embodiments of the present disclosure will be described clearly and completely below in conjunction with the accompanying drawings. It should be understood that the described embodiments are only a portion of the embodiments of the present disclosure, and are not intended to be exhaustive. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present disclosure without inventive effort are within the scope of protection of the present disclosure. The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the present disclosure. As used in the embodiments of the present disclosure and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. "A plurality" generally includes at least two, but does not exclude the inclusion of at least one. It should be understood that the term "and / or" as used herein is merely a description of an associative relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " as used herein generally indicates that the associated objects are in an "or" relationship. Depending on the context, the terms "if" and "if" as used herein can be interpreted as "when," "when," "in response to determining," or "in response to identifying." Similarly, the phrase "if determined" or "if (stated condition or event) is identified" may be interpreted as "when determined" or "in response to determining" or "when identifying (stated condition or event)" or "in response to identifying (stated condition or event)", depending on the context.It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, storage, and display) referred to in this disclosure are all information and data authorized by the user or fully authorized by all parties. The collection, use, and processing of the relevant data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse. It should also be noted that the terms "include," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a product or system comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such product or system. Without further limitation, an element defined by the phrase "comprising a..." does not preclude the presence of other identical elements in the product or system comprising the element. Before describing the methods and examples provided in the following embodiments of this disclosure, the following concepts should also be explained: System event: A form used to describe the operating status of an engine. Unlike user events, system events can be automatically generated by the operation and maintenance system without user intervention, and the user may not be aware of the system event's generation. Message: A form of transmitting an event describing the engine's operating status to the user. For example, when a system event generated by the operation and maintenance system reflects an abnormal engine operation, an alarm message may be generated; when a system event reflects normal engine operation, a notification message may also be generated. Based on the above introduction, some embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. The following embodiments and features may be combined unless there is a conflict between the embodiments. Furthermore, the sequence of steps in the following method embodiments is provided as an example and is not a strict limitation. Figure 1 is a flow chart of a system event processing method provided in an embodiment of the present disclosure. This method provided in an embodiment of the present disclosure can be executed by an operation and maintenance system that provides inspection services for the engine. As shown in Figure 1, the method may include the following steps:

[0002] 5101. Obtain current time series data reflecting engine performance index values. The operation and maintenance system may obtain current time series data reflecting engine performance index values. Optionally, the engines operated and maintained by the operation and maintenance system may include multiple types, such as the computing engine, storage engine, and database engine mentioned in the background technology. Different types of engines may also have different deployment forms. For example, a computing engine may be deployed as a virtual host in a physical host, and the computing engine may be deployed as a cloud server (ECS). o Both the storage engine and the database engine can be deployed on a physical host. Furthermore, the computing engine and the database engine can also be referred to as instances within a physical host. The engine to be operated and maintained mentioned in the various embodiments of this disclosure can be any of the aforementioned types of engines. Optionally, since the engine can generate time series data, the engine is also a data source. Optionally, the operation and maintenance system can obtain current time series data from the engine's log or from the engine's data pool using the engine's application programming interface (API). In addition to performance indicator values, current time series data can also include timestamps. Performance indicator values ​​are specific numerical values ​​of performance indicators. Timestamps are the time when the current time series data was generated. Optionally, the engine to be operated and maintained can periodically generate time series data at a time scale of seconds or minutes. Furthermore, for each of the aforementioned engines, the performance indicators generated during operation can include multiple types. Each engine can have common performance indicators, such as CPU usage, memory usage, disk usage, and so on. Each engine may also have unique performance indicators. For example, the unique performance indicators of a database engine may include: response time for data queries, number of database connections, etc.

[0003] 5102. If the generation time of the current time series data is later than the generation time of the valid time series data that has been obtained, determine the preset threshold condition corresponding to the engine to be operated and maintained.

[0004] S103: Based on whether the current time series data meets a preset threshold condition, a system event reflecting the operating status of the engine to be operated and maintained is generated. After obtaining the current time series data, the operation and maintenance system may optionally directly store the current time series data. Alternatively, the time series data may be stored in a storage component deployed in the operation and maintenance system. However, considering the limited storage space and data validity, a time window may be preset. Alternatively, the operation and maintenance system may further determine whether the current time series data is valid using this preset time window. If the generation time of the current time series data falls within the preset time window, indicating that the current time series data is valid, the current time series data may be stored in the storage component. Optionally, the generation time of the time series data may be described by a timestamp. The validity of the data may also be understood in conjunction with the following: the preset time window may be a time period set by an engine provider (hereinafter referred to as the provider) that reflects the engine's operating status that the provider wishes to focus on. Time series data generated within this time period may be considered valid data that the provider wishes to focus on. For example, the length of the preset time window can be 10 minutes. In this case, the storage component stores valid time series data generated within 10 minutes. Furthermore, this preset time window may be independent of the time when the operation and maintenance system receives the current time series data. For example, the preset time window can be the peak usage period of the engine, such as 12:00 PM to 2:00 PM on January 30, 2024. In this case, the time series data generation time can be 12:00 PM to 2:00 PM on January 29, 2024. After storing the current time series data, the operation and maintenance system can further determine whether to initiate inspection logic for the operation and maintenance engine based on this current time series data. In one case, if the generation time of the current time series data is later than the generation time of the already acquired valid data, indicating that the current time series data is the latest time series data generated by the engine to be operated and maintained, the operation and maintenance system can then begin executing the inspection logic for the engine to be operated and maintained. Specifically, the system first determines the preset threshold conditions corresponding to the engine to be operated and maintained, then determines whether the current time series data meets the preset threshold conditions, and generates a corresponding system event based on the determination result. More specifically, if the current time series data meets the preset threshold conditions, a system event is generated reflecting an abnormal operating status of the engine to be operated and maintained; if the current time series data does not meet the preset threshold conditions, a system event is generated reflecting a normal operating status of the engine to be operated and maintained. The generation times of the current time series data and the valid time series data both fall within this preset time window, making them both valid. Furthermore, the operation and maintenance system can be pre-configured with preset threshold conditions applicable to different types of engines, which can be collectively referred to as alternative preset conditions.Threshold conditions can be customized by the user, and after setting, the set threshold conditions can be added, deleted, modified, and so on. Optionally, the preset threshold conditions can include conditional expressions. For example, if the CPU usage of the engine to be operated and maintained in the current time series data is 85%, the conditional expression is: CPU usage > 80%, where CPU usage is the CPU usage. In this case, because the CPU usage in the current time series data satisfies the conditional expression, the operation and maintenance system can generate a system event reflecting an abnormal operating status of the engine to be operated and maintained. Furthermore, the reason why generation time comparison can be used to determine whether the current time series data is the most recently generated data by the engine to be operated and maintained can be understood with the following example: Assuming that the current time series data was generated at 12:06, and the valid time series data already stored in the storage component may have been generated at 12:05, 12:04, or 12:03, it is clear that the current time series data generated at 12:06 is also the most recently generated time series data by the engine to be operated and maintained, compared to the already stored time series data. Optionally, steps S101 and S102 in this embodiment can be performed by a processing component in the operation and maintenance system; step S103 can be performed by an event output component in the operation and maintenance system. In this embodiment, the operation and maintenance system can obtain current time series data reflecting engine performance indicators. If the generation time of this current time series data is later than the generation time of previously obtained valid time series data, indicating that this current time series data is the most recently generated time series data for the engine to be operated and maintained, the operation and maintenance system can then begin inspecting the engine, specifically determining the preset threshold conditions corresponding to the engine to be operated and maintained, and further determining whether the current time series data meets these preset threshold conditions. Ultimately, a corresponding system event is generated based on the determination result. In the above method, when operating and maintaining an engine, the operation and maintenance system uses the conditions corresponding to that engine. This means that different conditions within the operation and maintenance engine are uniquely matched to each other, thereby improving the versatility of the operation and maintenance system. Furthermore, by comparing generation times, the operation and maintenance system can only begin engine inspections upon receiving the engine's most recently generated time series data, thus achieving real-time inspection of the engine. Furthermore, the system events generated by real-time inspections can reflect the engine's latest operating status, enabling the provider of the engine to be maintained to understand the engine's operating status in real time. Furthermore, the technical effects achieved by the various system event processing methods provided herein can also be understood in conjunction with the following: In practice, the operation and maintenance system typically performs regular inspections of the engines to be maintained. When regularly inspecting multiple engines required by the operation and maintenance system, it is necessary to simultaneously obtain all time series data generated by all engines and test their operating status.This obviously increases the workload of the operation and maintenance system. However, the method provided in this aspect enables real-time inspection of each engine. Since each engine can generate time series data at different times, the operation and maintenance system can perform inspections of different engines at different times, thereby reducing its workload. Furthermore, after generating a system event, the operation and maintenance system can optionally convert the system event into a message that can be directly displayed to the provider, so that the provider can promptly understand the engine's operating status. As will be readily understood, when a system event indicates an abnormal engine operating status, the operation and maintenance system can generate an alert message. When a system event indicates normal engine operating status, the operation and maintenance system can generate a notification message. Compared to alert messages, notification messages are less of a concern to the provider. Therefore, to alleviate the problem of providers being frequently disturbed by notification messages, reduce the frequency of message generation, and reduce the message generation pressure on the operation and maintenance system, after generating a system event using the methods provided in the above and following embodiments of this disclosure, the operation and maintenance system can optionally refer to historical system events to determine whether to generate a message. Historical system events can be generated based on historical time series data, which is generated before the current time series data. Specifically, if the historical system events indicate that the operating status of the engine to be operated is normal, and the system events generated based on the current time series data indicate that the operating status of the engine to be operated is abnormal, the operation and maintenance system can determine that the operating status of the engine to be operated has changed from normal to abnormal, and further generate an alarm message describing the abnormality of the engine to be operated. This situation also requires the attention of the provider. If the historical system events indicate that the operating status of the engine to be operated is abnormal, and the system events generated based on the current time series data indicate that the operating status of the engine to be operated is normal, the operation and maintenance system can determine that the operating status of the engine to be operated has recovered from abnormal to normal, and further generate a notification message describing the abnormal termination of the engine to be operated. In this embodiment, the introduction of historical system events allows the operation and maintenance system to generate corresponding messages only when the operating status of the engine to be operated changes, thereby alleviating the problem of frequent notification messages interrupting the provider. In addition, in this embodiment, the event management component in the operation and maintenance system can determine whether the running state of the engine to be operated and maintained has changed, and then the event output component in the operation and maintenance system generates a corresponding message.Based on the embodiment shown in FIG1 , there is another scenario for the generation time comparison performed by the processing component in the operation and maintenance system: the generation time of the current time series data is earlier than the generation time of the already acquired valid time series data. In this case, it indicates that the current time series data is not the latest time series data generated by the engine to be operated and maintained. Therefore, the operation and maintenance system may not execute the inspection logic for this engine to be operated and maintained, but instead continue to acquire time series data generated by the engine to be operated and maintained after the current time series data. The reason why generation time comparison can determine whether the current time series data is the latest data generated by the engine to be operated and maintained can also be understood in conjunction with the following: Continuing with the example in step S102, assuming that the generation time of the current time series data is 12:06, and among the valid time series data acquired by the operation and maintenance system, there is already a time series data generated at 12:07, then the time series data acquired by the operation and maintenance system at 12:06 is clearly not the latest time series data generated by the engine, and the time series data generated at 12:06 can be considered late data. The time series data generated at 12:07 is the most recent time series data generated by the engine and acquired by the operation and maintenance system. At this point, if the operation and maintenance system continues to execute the inspection logic shown in steps S102 and S103 on this late data, the system event generated by the operation and maintenance system clearly does not reflect the latest operating status of the engine under operation and maintenance. The message generated based on this system event may cause interference to the provider. This interference can be understood with the following example: Continuing with the above example, the operation and maintenance system can generate a system event reflecting an abnormality in the engine under operation and maintenance based on the time series data generated at 12:06. The operation and maintenance system can also generate an alarm message based on this system event. The operation and maintenance system can also generate a system event based on the time series data generated at 12:07. This event reflects that the engine under operation and maintenance is operating normally. This system event can also generate a notification message. This situation indicates that the operating status of the engine under operation and maintenance undergoes a transition from abnormal to normal. This transition may be due to network jitter or abnormal and sudden changes in the collected time series data. However, since the engine under maintenance has returned to normal, notifying the provider of the previous exception (i.e., an expired exception) of the engine under maintenance via an alert message would actually cause interference to the provider, forcing them to perform unnecessary operations on the engine. However, using the method provided by the embodiment shown in FIG1 , the maintenance system executes the inspection logic only after receiving the latest time series data generated by the engine. This ensures that the provider receives notifications reflecting the current operating status of the engine under maintenance and prevents the provider from performing operations on expired exceptions generated by the engine.To improve the processing efficiency of time series data, a streaming computing engine can optionally be deployed in the operation and maintenance system. The streaming computing engine can stream-acquire and process the time series data generated by the engine to be operated and maintained. Streaming computing engines can include Flink, Storm, Kafka Streams, and others. In this embodiment, acquiring time series data with the streaming computing engine can reduce the processing latency of time series data. As shown in the embodiment illustrated in FIG1 , the current time series data generated by the engine to be operated and maintained can be stored in a storage component provided by the operation and maintenance system. Of course, time series data generated by different engines operated by the operation and maintenance system at different times can all be stored in the storage component provided by the operation and maintenance system. Optionally, this storage component can be specifically implemented as a cache. The operation and maintenance system can then store the current time series data in the cache using its own first interface. For cache-based time series data storage, if the cache is full before storing the current time series data generated by the engine to be operated and maintained, the operation and maintenance system can optionally delete the time series data with the oldest generation time in the cache before writing the current time series data into the cache. Alternatively, the cache used to store time series data can be specifically implemented as a ring buffer. Time series data in the ring buffer can be stored in order of generation time. If the cache is full before storing the current time series data, the time series data at the end of the queue with the oldest generation time is deleted. In this embodiment, storing time series data in the cache can increase the speed of time series data acquisition. Setting a time window can enable timely clearing of old time series data, ensuring that the cache only stores time series data with relatively recent generation times, thereby reducing the space occupied by old time series data in the limited cache. Under normal circumstances, time series data generated by the engine to be operated and maintained can be acquired by the operation and maintenance system in order of generation time. However, for various practical reasons, the order in which time series data is received and generated may differ, which is the case with late data mentioned in the above embodiment. To ensure that time series data in the cache is stored in the order of generation time, each storage location in the cache is optionally timestamped. The timestamp added to each storage location describes the generation time of the time series data. The operation and maintenance system can then write the current time series data to a target location in the cache based on its generation time. The timestamp added to the target location is the same as the generation time of the current time series data.For example, the preset time window can be 12:01 ~ 12:10, and the cache is divided into 10 storage locations for storing 10 time series data generated by the operation and maintenance engine between 12:01 and 12:10. The timestamps added to the storage locations in the ring buffer are 12:01 and 12:10 respectively. oTime series data generated at 12:06 can be stored at the target location with a timestamp of 12:06. In this embodiment, even if the operation and maintenance system cannot retrieve time series data in order according to generation time, adding timestamps to the storage locations in the cache can ensure that the time series data is stored in order. Also considering the limited cache size, the operation and maintenance system can optionally periodically clear the data in the cache. In one case, as described in the embodiment shown in FIG1 , the engine to be operated and maintained can be represented as an instance deployed on a physical host. When an instance is deleted, it will no longer generate time series data. The operation and maintenance system can delete all time series data from the cache originating from this instance. The specific implementation process of this case is as follows: When the preset clearing time arrives, the operation and maintenance system can obtain the generation time of time series data generated by different engines in the cache. If the time interval between the generation time of the most recently generated time series data of an instance and the preset clearing time is greater than a preset value, the operation and maintenance system can assume that the instance has been deleted as a whole and delete all time series data from the cache originating from this instance. In another scenario, as described in the embodiment shown in FIG1 , the time series data generated by any engine can include multiple performance indicators, each corresponding to a performance indicator value. The performance indicators corresponding to the time series data generated by different engines can be preconfigured. The specific configuration process can be found in the description of the relevant embodiments below. In practice, when the provider modifies the original performance indicator corresponding to the time series data, the operation and maintenance system can delete the time series data corresponding to the original performance indicator from the cache. The specific implementation process for this scenario is as follows: When a preset cleanup time arrives, the operation and maintenance system can obtain the generation time of the time series data generated by different engines in the cache and the performance indicator corresponding to the time series data. If the time interval between the generation time of the most recently generated time series data of an engine and the preset cleanup time is greater than a preset value, and the performance indicators corresponding to the most recently generated time series data and the time series data already stored in the cache are different, the operation and maintenance system can determine that a performance indicator modification has occurred and can delete the time series data generated by the engine in the cache that corresponds to the original performance indicator. The periodic cleanup of time series data mentioned in this embodiment can be achieved using a cleanup component in the operation and maintenance system. Furthermore, in this embodiment, regular cleanup can be performed to delete time series data generated by deleted or modified engines from the cache, thereby reducing cache usage by old time series data. As described in the embodiment shown in FIG1 , the operation and maintenance system can primarily determine the operating status of the engine to be operated and maintained using a conditional expression in a preset threshold condition.Optionally, a conditional expression may include a relational expression, which may involve a performance indicator, such as the aforementioned CPU usage > 80%. A conditional expression may also involve multiple performance indicators simultaneously, such as rows_read_ps + rows_write_ps > 10000. Here, rows_read_ps represents the number of rows read per second, and rows_write_ps represents the number of rows written per second. A conditional expression may also include multiple relational expressions, and logical operations may exist between these multiple relational expressions. Such a conditional expression may involve multiple performance indicators, such as CPU usage > 80% AND memory usage > 70%. Here, "memory usage" represents memory usage, and "AND" represents a logical operation relationship. Optionally, the logical operations between multiple relational expressions may include AND and OR. The relational operators in any relational expression may include equal, not equal, greater than, less than, greater than or equal to, less than or equal to, and so on. Any relational expression may also include arithmetic operators, such as +, -, *, and / , which are unary arithmetic operators, as well as binary arithmetic operators. In practice, the operating status of an engine can be determined using at least one performance metric of primary interest to the provider. For example, performance metrics such as memory usage and CPU usage can be used to generate corresponding system events. Furthermore, given the varying engine types and application scenarios, different providers may prioritize different performance metrics. Using the aforementioned complex and rich conditional expressions can address the diverse performance metrics of different providers, enriching the use cases for engine inspections. Compared to implementing engine operation and maintenance solely through simple threshold comparisons, in this embodiment, the operation and maintenance system can flexibly support diverse and complex conditional expressions, thereby meeting the operation and maintenance requirements of different providers for different types of engines in different scenarios. As discussed in the aforementioned embodiments, the operation and maintenance system can execute corresponding inspection logic to generate system events each time it receives the latest time series data generated by the engine to be operated and maintained. To improve the reliability of system event generation, the preset threshold condition, in addition to including the conditional expression, may optionally include a restriction condition. For example, the time series data generated within a preset duration must meet the conditional expression a preset number of times. The preset threshold condition may also include the following conditions: the time series data generated within a preset duration must meet the conditional expression a preset number of times, and the time series data meeting the conditional expression is generated continuously. Optionally, the preset duration may be less than or equal to the length of the preset time window.The process of generating a system event using a preset threshold condition containing a conditional expression and a restriction condition can be described as follows: For example, assuming the preset time window is 11:57^12:06, the preset duration is 8 minutes, the preset number of times is 5, and the engine to be operated and maintained generates one time series data every minute. Continuing with the example in the above embodiment, the time series data generated by the engine to be operated and maintained at 12:06 is the current time series data, and this data is the most recently generated time series data by the engine to be operated and maintained. The operation and maintenance system can then further count the number of time series data that meet the conditional expression among the eight time series data generated within the eight minutes from 11:59^12:06. If five of the eight time series data satisfy the conditional expression, this indicates that the time series data satisfying the conditional expression is not an emergency. Therefore, the current time series data generated by the maintenance engine at 12:06 can be considered to meet the preset threshold. At this point, the maintenance system can further generate a system event reflecting the abnormal engine operating status. This system event can also be presented to the provider in the form of an alarm message. It should be noted that this solution does not limit the relationship between the preset duration and the length of the preset time window mentioned in the above embodiment. In practice, the time series data generated by the maintenance engine may contain sudden changes, that is, glitches. Glitches obviously cannot accurately reflect the performance indicators of the maintenance engine. By introducing a constraint described by a preset number of times and a preset duration in the preset threshold condition, the maintenance system only generates a system event when multiple time series data satisfy the conditional expression. The provider will not receive an alarm message generated based on glitches. Optionally, since different performance indicators generate glitches at different frequencies, the preset number of times and the preset duration in the preset threshold condition can also be customized. Specifically, for performance indicators with a high glitch frequency, such as CPU usage, the preset number of times and the preset duration can be set to a larger value, as sudden changes in such performance indicators have a smaller impact on the normal operation of the engine. For performance indicators with a low glitch frequency, such as memory usage, the preset number of times and the preset duration can be set to a smaller value, as sudden changes in such performance indicators have a greater impact on the normal operation of the engine. In this embodiment, by enriching the preset threshold conditions, namely adding a constraint consisting of two parameters, namely, the preset duration and the preset number of times, the issue of the operation and maintenance system generating system events and alarm messages based on sudden changes in time series data can be addressed, thereby improving the reliability of inspection results. In practice, the operation and maintenance system can also provide inspection services for different types of engines. To ensure the accuracy of inspection results, the method provided in the embodiment shown in FIG. 2 can be used.FIG2 is a flow chart of another system event processing method provided by an embodiment of the present disclosure. As shown in FIG2 , the method may include the following steps:

[0005] 5201. Obtain current time series data reflecting engine performance indicator values. The current time series data includes metadata describing at least one attribute information of the engine to be operated. The specific implementation process for obtaining time series data can be found in the detailed description of the relevant steps in the embodiment shown in FIG1 and will not be repeated here. Optionally, the time series data may include metadata in addition to the performance indicator value and timestamp. This metadata is used to describe at least one attribute information of the engine to be operated. The metadata may specifically include first data describing the name of each attribute information item and second data describing the specific content of each attribute information item. Engine attribute information may include the engine name, type, model, master / slave information, deployment address, etc. Optionally, unlike performance indicator values, which are expressed as numerical values, metadata may be expressed as character strings.

[0006] 5202. Obtain preset data filtering rules corresponding to the engine to be operated and maintained. The preset data filtering rules include metadata describing engine attribute information.

[0007] At step 5203, if the metadata included in the current time series data is identical to the metadata included in the data filtering rule, the magnitude relationship between the generation time of the current time series data and the already acquired valid time series data is determined. In each of the above embodiments, it is assumed that the current time series data is generated by the engine to be operated and maintained. However, in practice, time series data generated by different engines can be stored in the same storage space of the operation and maintenance system, such as a cache. The current time series data acquired by the operation and maintenance system may also originate from another engine. In this case, to ensure the accuracy of inspections of the engine to be operated and maintained, the operation and maintenance system may further acquire a preset data filtering rule corresponding to the engine to be operated and maintained. This rule may include metadata describing engine attribute information and an operator. Based on this operator, the operation and maintenance system may determine whether the metadata included in the preset data filtering rule and the metadata included in the current time series data are identical. If they are identical, it indicates that the current time series data acquired by the operation and maintenance system was generated by the engine to be operated and maintained. The operation and maintenance system may then further generate a time comparison. Furthermore, in this embodiment, the generation times of the valid time series data and the current time series data are within a preset time window indicating data validity. As can be seen, by using the preset data filtering rules, the source of the current time series data acquired by the operation and maintenance system and subsequently used in the inspection logic can be verified, thereby reducing the situation where the inspection logic is executed using the time series data generated by one engine to obtain the inspection results of another engine. Optionally, the operation and maintenance system can obtain this preset data filtering rule via a second interface. The operators in the preset data filtering rule may include IN or NOT I No, and step S202 can be specifically performed by a filtering component in the operation and maintenance system.

[0008] At step 5204, if the generation time of the current time series data is later than the generation time of the valid time series data, a preset threshold condition corresponding to the engine to be operated and maintained is obtained. Optionally, the operation and maintenance system can obtain the preset threshold condition corresponding to the engine to be operated and maintained via its second interface. Optionally, the correspondence between the engine to be operated and the threshold condition, as well as the correspondence between the engine to be operated and the data filtering rules, can be preconfigured. The specific configuration process can be found in the relevant description below.

[0009] S205: Based on whether the current time series data meets the preset threshold conditions, a system event reflecting the operating status of the engine to be operated and maintained is generated. The specific implementation process of steps S204 and S205 can be found in the detailed description of the relevant steps in the embodiment shown in FIG1 and will not be repeated here. In this embodiment, before executing the inspection logic on the engine to be operated and maintained, the operation and maintenance system may also perform data filtering to ensure that the current time series data used in executing the inspection logic is generated by the engine to be operated and maintained, thereby ensuring the accuracy of the inspection results. Optionally, before completing the system event processing methods provided in the above embodiments, a related configuration process may be performed. This configuration process may be performed by a configuration component in the operation and maintenance system. Specifically, the configuration component may create the first and second interfaces described above in the operation and maintenance system. Simultaneously, the configuration component may also create an event collection. Each event in the event collection may be associated with an engine, the provider of the engine, the preset threshold conditions corresponding to the engine, and the data filtering rules corresponding to the engine. The process of creating an event collection can also be considered as the process of establishing associations between events and various content. The associations between events and various content can also be understood in conjunction with FIG3. For example, any event in an event collection can be associated with a database engine provided by provider 1. The preset threshold conditions for this database engine include: CPU usage > 80%, preset duration 8 minutes, and preset number of times 5. This event reflects the time series data generated by the database engine within 8 minutes, including 5 instances of CPU usage exceeding 80%. Therefore, the operation and maintenance system needs to output a system event: "Database engine CPU usage exceeds 80%." The events in the event collection can be configured by the provider based on their needs, and the provider can also be considered the event source. Furthermore, because the content reflected by the event is related to the provider's needs, the relationship between the provider and the event can be one-to-many, and the relationship between the engine and the event can also be one-to-many. For example, the events corresponding to database engine 1 provided by provider 1 can include the aforementioned "database engine CPU usage exceeds 80%," "database engine memory usage exceeds 70%," "database engine CPU usage exceeds 80% and database engine memory usage exceeds 70%," and so on. Based on the created event set, once the operation and maintenance system obtains the current time series data, it can retrieve the preset threshold conditions and data filtering rules corresponding to the engine based on the engine name described in the metadata of the time series data. During the configuration phase, the provider can independently enter the preset threshold conditions corresponding to different engines.Optionally, the operation and maintenance system can also verify the conditions entered by the provider. Specifically, in practice, different types of engines can generate their own unique performance indicators. For example, database engines can generate performance indicators such as data query response time and the number of database connections, while compute engines and storage engines do not have such performance indicators. Therefore, the operation and maintenance system can determine whether the preset threshold conditions entered by the provider are correct by determining whether the performance indicators included in the conditional expression of the preset threshold conditions correspond to the engine type. If so, indicating that the preset threshold conditions entered by the provider are correct, an event can be further created to ultimately obtain an event set. In this embodiment, by pre-configuring the interface and event set through the configuration component, the operation and maintenance system can implement operation and maintenance for different types of engines. The specific content of the system event processing methods provided in the above embodiments can also be understood in conjunction with the following examples and Figure 6. Assume that the engine to be operated and maintained is a database engine provided by Provider 1. The engine generates time series data with a period of one minute, and the metadata of the time series data generated by the database engine may include engine type, engine name, engine version number, user name, and other content. The type of the database engine can be represented by "db_redis" as a unique identifier, which can be recorded as "engine=db_redis"; the engine name can be represented by "instName" as a unique identifier, which can be recorded as "instName=id123"; the engine version number can be represented by "version" as a unique identifier, which can be recorded as "versions"; the user name can be represented by "userid" as a unique identifier, which can be recorded as "userld=111". Assuming that the database engine generates a time series data item at 12:06, the metadata of the time series data can include engine=db_redis, insName=id123, and userid=111. oThe performance indicator values ​​included in the time series data may be: CPU usage = 85%, memory usage = 75%, and data query response time = 10ms. The time series data containing the performance indicator values ​​and metadata can be stored in the operation and maintenance system's cache via the first interface of the operation and maintenance system. Furthermore, before this time series data is stored in the cache, the cache already stores time series data generated by the database engine between 12:00 and 12:05. Furthermore, the operation and maintenance system's filtering component can retrieve the time series data generated at 12:06 from the cache. Thereafter, the filtering component can further retrieve the data filtering rule corresponding to the database engine via the second interface. The filtering component can determine that both the metadata in the rule and the metadata in the time series data include "engine=db_red is" and "userId=111". Therefore, the time series data generated at 12:06 and received by the operation and maintenance system was generated by the database engine when user 111 was using the database engine. This time series data can be processed in subsequent logic. Furthermore, the processing component in the operation and maintenance system can also compare generation times. Since the generation time of this time series data is later than the generation time of other time series data in the cache, the time series data generated at 12:06 can be considered the latest time series data generated by the database engine. The processing component can further obtain the preset threshold condition corresponding to the database engine through the second interface. The relational expression in this condition can be "CPU usage > 80% & memory usage > 70% & Response Time > 7ms", with a preset duration of 8 minutes and a preset number of times of 5. The time series data generated at 12:06 clearly satisfies the above relational expression. Furthermore, the operation and maintenance data can be statistically analyzed to determine that 6 of the 8 time series data generated by the database engine between 11:59 and 12:06 satisfy the above relational expression. At this point, the processing component may determine that the time series data generated at 12:06 meets the preset threshold condition. The event output component in the operation and maintenance system can then generate a system event reflecting a database engine anomaly. This event is "CPU usage greater than 80%, memory usage greater than 70%, and response time greater than 7ms." Furthermore, the operation and maintenance system can optionally directly generate an alarm message, or determine whether to generate an alarm message based on historical system events. This alarm message can also be "CPU usage greater than 80%, memory usage greater than 70%, and response time greater than 7ms." Optionally, the time series data in the cache can also be cleared. The specific process can be found in the above description.In addition, for details not described in this embodiment, please refer to the descriptions in the above embodiments and will not be repeated here. The working process of the operation and maintenance system has been described above from a methodological perspective. The following will further describe the operation and maintenance system from a structural perspective. Figure 4 is a schematic diagram of the structure of an operation and maintenance system provided by an embodiment of the present disclosure. As shown in Figure 4, the operation and maintenance system may include a processing component and an event output component. The processing component may first obtain current time series data reflecting engine performance indicator values. If the generation time of the current time series data is later than the generation time of the already obtained valid time series data, the processing component begins executing inspection logic, namely, determining the preset threshold conditions corresponding to the engine to be operated and maintained. Ultimately, based on whether the current time series data meets the preset threshold conditions, a corresponding processing result is generated. The generation times of the current time series data and the valid time series data are each within a preset time window reflecting data validity. Based on the processing result, the event output component may generate a system event reflecting the operating status of the engine to be operated and maintained. More specifically, if the current time series data meets the preset threshold conditions, the event output component can generate a system event reflecting an abnormal operating status of the engine to be maintained; if the current time series data does not meet the preset threshold conditions, the event output component can generate a system event reflecting normal operating status of the engine to be maintained. In this embodiment, the processing component first obtains the current time series data reflecting the engine's performance indicator value, and then further determines whether to initiate an engine inspection based on the generation time of this current time series data. If the generation time of the current time series data is later than the generation time of the already obtained valid time series data, the operation and maintenance system can initiate an engine inspection. This involves determining the preset threshold conditions corresponding to the engine to be maintained from the candidate preset conditions, and further obtaining a processing result reflecting whether the current time series data meets the preset threshold conditions. Finally, the event output component in the operation and maintenance system can generate a corresponding system event based on the processing result. In the above method, when operating an engine, the operation and maintenance system uses the conditions corresponding to that engine. This means that different conditions within the operation and maintenance engine are individually corresponding to different engines, thereby improving the versatility of the operation and maintenance system. Furthermore, by comparing transmission delays, the operation and maintenance system can begin engine inspections only upon receiving the engine's latest time series data, thus achieving real-time inspection of the engine. Furthermore, the system events generated by real-time inspections can reflect the engine's latest operating status, enabling the provider of the engine to be maintained to understand the engine's operating status in real time. For details not described in detail in this embodiment and the technical effects achieved, please refer to the relevant descriptions of the aforementioned embodiments and will not be elaborated upon here. Figure 5 is a schematic diagram of the structure of another operation and maintenance system provided in an embodiment of the present disclosure.As shown in Figure 5 , based on the embodiment shown in Figure 4 , the operation and maintenance system may further include: a storage component configured to store time series data generated by various engines requiring operation and maintenance by the operation and maintenance system, including the engine to be operated and maintained. Optionally, the storage component may be implemented as a cache. To ensure the accuracy of the operation and maintenance system's engine inspections, the operation and maintenance system may further include a filtering component. This filtering component is used to determine whether the metadata contained in the current time series data and the preset data filtering rules corresponding to the engine to be operated and maintained are identical. If they are identical, it indicates that the current time series data obtained by the operation and maintenance system was generated by the engine to be operated and maintained, and the operation and maintenance system may further execute subsequent logic. The specific working process of the filtering component can be found in the relevant description of the embodiment shown in Figure 2 and will not be repeated here. In this embodiment, the processing component can also use the filtering component to filter time series data before executing the inspection logic on the pending operation and maintenance engine. Specifically, the processing component verifies the source of the current time series data acquired by the operation and maintenance system and subsequently used in the inspection logic execution to confirm that the current time series data used when executing the inspection logic was generated by the pending operation and maintenance engine, thereby ensuring the accuracy of the inspection results. Optionally, the operation and maintenance system can also include an event management component and a message output component. The event management component can obtain historical system events generated based on historical time series data and further combine these historical system events with system events generated based on current time series data to determine the operating status of the pending operation and maintenance engine. The historical time series data is generated before the current time series data. Specifically, if the historical system events indicate that the operating status of the pending operation and maintenance engine is normal, and the system events generated based on the current time series data indicate that the operating status of the pending operation and maintenance engine is abnormal, the event management component can determine that the pending operation and maintenance engine has begun to experience an abnormality, i.e., the operating status of the pending operation and maintenance engine has changed from normal to abnormal. At this point, the message output component can generate an alarm message describing the abnormality of the pending operation and maintenance engine. This situation also requires the attention of the provider. If historical system events indicate an abnormal operating status of the engine to be maintained, and system events generated based on current time series data indicate a normal operating status, the event management component can determine that the abnormality of the engine to be maintained has been recovered, meaning that the operating status of the engine to be maintained has changed from abnormal to normal. At this point, the message output component can generate a notification message describing the abnormal termination of the engine to be maintained. In this embodiment, by introducing historical system events, the event management component in the operation and maintenance system can determine whether the operating status of the engine to be maintained has changed. The message output component can only generate corresponding messages when the operating status of the engine to be maintained has changed, thereby alleviating the problem of frequent notification message interruptions to the provider. It can also reduce the frequency of message generation, alleviating the message generation pressure on the operation and maintenance system.Optionally, the operation and maintenance system may further include a configuration component. This component creates a first interface for storing current time series data and a second interface for obtaining preset data filtering rules and preset threshold conditions. This component may also create a system event set, wherein each system event in the system event set is associated with an engine, an engine provider, a preset threshold condition, and a preset data filtering rule. In this embodiment, pre-configuration enables the operation and maintenance system to implement real-time inspections of different types of engines. Furthermore, for details not described in detail in this embodiment and the technical effects that can be achieved, please refer to the relevant descriptions of the above embodiments and will not be repeated here. The operation of the above-mentioned method and system embodiments can also be understood in conjunction with FIG6 . The system event processing devices of one or more embodiments of the present disclosure will be described in detail below. Those skilled in the art will appreciate that these system event processing devices can be constructed using commercially available hardware components configured according to the steps taught in this solution. FIG7 is a schematic structural diagram of a system event processing device provided in an embodiment of the present disclosure. As shown in FIG7 , the device may include an acquisition component 11 configured to acquire current time series data reflecting engine performance indicator values. The determination component 12 is configured to determine a preset threshold condition corresponding to the engine to be operated and maintained if the generation time of the current time series data is later than the generation time of the already acquired valid time series data. The event generation component 13 is configured to generate a system event reflecting the operating status of the engine to be operated and maintained based on whether the current time series data meets the preset threshold condition. Optionally, the event generation component 13 is configured to generate a system event reflecting an abnormal operating status of the engine to be operated and maintained if the current time series data meets the preset threshold condition; otherwise, it is configured to generate a system event reflecting a normal operating status of the engine to be operated and maintained. Optionally, the acquisition component 11 is configured to wait for acquisition of time series data generated after the current time series data if the generation time of the current time series data is earlier than the generation time of the valid time series data. Optionally, the apparatus further includes a storage component 14 configured to store the valid time series data and the current time series data in a cache of the operation and maintenance system. The acquisition component 11 is configured to utilize a stream computing engine deployed in the operation and maintenance system to acquire the current time series data from the cache. Optionally, the storage component 14 is configured to write the current time series data to a target location in the cache based on the generation time of the current time series data, and to add a timestamp to the target location, where the timestamp is the same as the generation time of the current time series data. Optionally, the current time series data includes metadata describing at least one attribute information of the engine.The acquisition component 11 is further configured to acquire preset data filtering rules corresponding to the engine to be operated and maintained, the preset data filtering rules including metadata describing attribute information of the engine to be operated and maintained; and if the metadata contained in the current time series data is the same as the metadata contained in the data filtering rules, then the preset threshold conditions corresponding to the engine to be operated and maintained are acquired. Optionally, the acquisition component 11 is further configured to acquire the preset data filtering rules and the preset threshold conditions corresponding to the engine to be operated and maintained. Optionally, the apparatus further includes: a creation component 15 configured to create a first interface and a second interface in the operation and maintenance system, the first interface being used to store the valid time series data and the current time series data in the operation and maintenance system's cache, and the second interface being used to acquire the preset data filtering rules and the preset threshold conditions corresponding to the engine to be operated and maintained; and to create a system event set, wherein each system event in the system event set is respectively associated with an engine, a provider of the engine, the preset threshold conditions corresponding to the engine, and the preset data filtering rules. Optionally, the creation component 15 is configured to obtain a preset threshold condition input by the provider of the engine, the preset threshold condition including a conditional expression and the number of times that time series data generated within a preset time period satisfies the conditional expression reaching a preset number of times; and if the performance indicator included in the conditional expression in the input preset threshold condition corresponds to the type of the engine to be operated, then the system event set is created. Optionally, the apparatus further includes a message generation component 16. The acquisition component 11 is further configured to obtain historical system events generated based on historical time series data. The message generation component 16 is configured to generate an alarm message describing the abnormality of the engine to be operated if the historical system events indicate that the operating status of the engine to be operated is normal, and the system events generated based on the current time series data indicate that the operating status of the engine to be operated is abnormal; and to generate a notification message describing the abnormal termination of the engine to be operated if the historical system events indicate that the operating status of the engine to be operated is abnormal, and the system events generated based on the current time series data indicate that the operating status of the engine to be operated is normal. The apparatus shown in FIG7 can execute the methods of the embodiments shown in FIG1 through FIG3 . For portions not described in detail in this embodiment, reference can be made to the relevant descriptions of the embodiments shown in FIG1 through FIG3 . The execution process and technical effects of this technical solution are described in the embodiments shown in FIG1 through FIG3 , and will not be further elaborated here. In one possible design, the system event processing methods provided in the above embodiments can be applied in an electronic device. As shown in FIG8 , the electronic device may include a processor 31 and a memory 32.The memory 32 is configured to store a program that supports the electronic device in executing the system event processing method provided in the embodiments shown in Figures 1 to 3 , and the processor 31 is configured to execute the program stored in the memory 32. The program includes one or more computer instructions. When executed by the first processor 31, the one or more computer instructions can implement the following steps: obtaining current time series data reflecting engine performance indicator values; if the generation time of the current time series data is later than the generation time of the already obtained valid time series data, determining a preset threshold condition corresponding to the engine to be operated and maintained from among the candidate preset conditions; and generating a system event reflecting the operating status of the engine to be operated and maintained based on whether the current time series data meets the preset threshold condition. Optionally, the processor 31 is further configured to execute all or part of the steps in the embodiments shown in Figures 1 to 3 . The electronic device may also include a communication interface 33 configured to enable the electronic device to communicate with other devices or communication systems. In addition, embodiments of the present disclosure provide a computer storage medium configured to store computer software instructions for use in the electronic device described above, including a program for executing the system event handling method illustrated in Figures 1 to 3 . Furthermore, embodiments of the present disclosure provide a computer program product. This computer program product includes a computer program or instructions. When executed by a processor, the computer program or instructions enable the processor to implement the steps or functions of the system event handling method illustrated in Figures 1 to 3 . Finally, it should be noted that the above embodiments are intended only to illustrate the technical solutions of the present disclosure and are not intended to limit them. Although the present disclosure has been described in detail with reference to the aforementioned embodiments, persons skilled in the art will understand that modifications may be made to the technical solutions described in the aforementioned embodiments, or that some of the technical features therein may be replaced by equivalents. However, such modifications or replacements do not deviate from the essence of the corresponding technical solutions within the spirit and scope of the technical solutions of the various embodiments of the present disclosure. Industrial Applicability: The solution provided by the embodiments of this disclosure can be applied to the operation and maintenance of a pair of engines. When operating an engine, the operation and maintenance system uses the conditions specific to that engine. This means that different engine-specific conditions exist within the operation and maintenance system, thereby improving the versatility of the system. Furthermore, by comparing generation times, the operation and maintenance system can only begin engine inspections upon receiving the most recently generated time series data from an engine, thus achieving real-time inspection of the engine. Furthermore, the system events generated by real-time inspections can reflect the engine's latest operating status, enabling the provider of the engine to be operated and maintained to understand the engine's operating status in real time.

Claims

Claims 1. A system event processing method, comprising: Get the current time series data reflecting the engine performance index value; If the generation time of the current time series data is later than the generation time of the valid time series data that has been obtained, determining a preset threshold condition corresponding to the engine to be operated and maintained; A system event reflecting the operating status of the engine to be operated and maintained is generated according to whether the current time series data meets the preset threshold condition.

2. The method according to claim 1, wherein: The generating of a system event corresponding to the engine to be operated and maintained based on whether the current time series data satisfies the threshold condition includes: if the current time series data satisfies the preset threshold condition, generating a system event reflecting that the operating status of the engine to be operated and maintained is abnormal; otherwise, generating a system event reflecting that the operating status of the engine to be operated and maintained is normal.

3. The method according to claim 1, wherein: The method further includes: if the generation time of the current time series data is earlier than the generation time of the valid time series data, acquiring time series data generated after the current time series data.

4. The method according to claim 1, wherein: The method further includes: storing the valid time series data and the current time series data in a cache of the operation and maintenance system; and obtaining the current time series data reflecting the engine performance indicator value, including: obtaining the current time series data from the cache using a streaming computing engine deployed in the operation and maintenance system.

5. The method according to claim 4, wherein: The storing the current time series data into the cache of the operation and maintenance system includes: writing the current time series data to a target location in the cache according to the generation time of the current time series data, and adding a timestamp to the target location, where the timestamp is the same as the generation time of the current time series data.

6. The method according to claim 1, wherein: The current time series data includes metadata for describing at least one attribute information of the engine; After obtaining the current time series data reflecting the engine performance index value, the method further includes: obtaining a preset data filtering rule corresponding to the engine to be operated and maintained, the preset data filtering rule including metadata describing attribute information of the operation and maintenance engine; If the metadata included in the current time series data is the same as the metadata included in the data filtering rule, the preset threshold condition corresponding to the engine to be operated and maintained is obtained.

7. The method according to claim 6, wherein: The method further includes: acquiring the preset data filtering rule and the preset threshold condition corresponding to the engine to be operated and maintained.

8. The method according to claim 6, wherein: The method further includes: creating a system event set, wherein any system event in the system event set is associated with an engine, provision of the engine, a preset threshold condition corresponding to the engine, and a preset data filtering rule.

9. The method according to claim 8, wherein: The creating of the system event set includes: Obtain a preset threshold condition input by the provider of the engine, where the preset threshold condition includes a conditional expression and the number of times that the time series data generated within a preset time period satisfies the conditional expression reaches a preset number of times; if the performance indicator included in the conditional expression in the input preset threshold condition corresponds to the type of the engine to be operated and maintained, create the system event set.

10. The method according to claim 1, wherein: The method also includes: obtaining historical system events generated according to historical time series data; if the historical system events reflect that the operating status of the engine to be operated is normal, and the system events generated according to the current time series data reflect that the operating status of the engine to be operated is abnormal, then generating a notification message describing the abnormal occurrence of the engine to be operated; if the historical system events reflect that the operating status of the engine to be operated is abnormal, and the system events generated according to the current time series data reflect that the operating status of the engine to be operated is normal, then generating a notification message describing the abnormal end of the engine to be operated.

11. An operation and maintenance system, comprising: Processing components and event output components; The processing component is configured to obtain current time series data reflecting engine performance indicator values; If the generation time of the current time series data is later than the generation time of the valid time series data that has been obtained, determining a preset value condition corresponding to the engine to be operated and maintained; Generate a processing result according to whether the current time series data meets the preset threshold condition; The event output component is configured to generate a system event reflecting the running status of the engine to be operated and maintained according to the processing result.

12. The system according to claim 11, wherein: The system further includes: a storage component configured to store the current time series data.

13. The system according to claim 11, wherein: The current time series data and the preset data rules corresponding to the engine to be operated and maintained contain metadata for describing at least one attribute information of the engine; the system also includes: a filtering component, configured to determine whether the metadata contained in the current time series data and the preset data filtering rules corresponding to the engine to be operated and maintained are the same; if the metadata contained in the current time series data and the data filtering rules corresponding to the engine to be operated and maintained are the same, then the preset threshold condition corresponding to the engine to be operated and maintained is taken.

14. The system according to claim 13, wherein: The system also includes: a configuration component configured to create a first interface for storing the current time series data and a second interface for obtaining the preset data filtering rules; create a system event set, and any system event in the system event set is associated with an engine, an engine provider, a threshold condition, and a preset data filtering rule.

15. The system according to claim 11, wherein: The system further includes an event management component and a message output component; the event management component is configured to store historical system events generated based on historical time series data; if the historical system events reflect that the operating status of the engine to be operated and maintained is normal, and the system events generated based on the current time series data reflect that the operating status of the engine to be operated and maintained is abnormal, then it is determined that an abnormality has occurred in the engine to be operated and maintained; If the historical system events reflect that the operation status of the engine to be maintained is abnormal, and the current time series data is generated If the system event reflects that the operating status of the engine to be operated and maintained is normal, it is determined that the engine to be operated and maintained has recovered abnormally; the message output component is configured to generate an alarm message describing the abnormal occurrence of the engine to be operated and maintained, or generate a notification message describing the abnormal end of the engine to be operated and maintained.

16. An electronic device, comprising: A memory and a computing system; wherein the memory stores executable code, and when the executable code is executed by the computing system, the computing system executes the system event processing method according to any one of claims 1 to 10.

17. A non-transitory machine-readable storage medium having executable code stored thereon, wherein when the executable code is executed by a computing system of an electronic device, the computing system is caused to execute the system event processing method according to any one of claims 1 to 10.

18. A computer program product, comprising a computer program or instructions, which, when executed by a processor, enables the processor to implement the steps of the system event processing method according to any one of claims 1 to 10.

Images