Customizable Event Processing for Infrastructure Platforms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing event handling solutions for computing infrastructure events lack flexibility and customization, often failing to perform time-sensitive actions within specified time periods due to pre-defined, fixed action orders across multiple infrastructure platforms.
Innovation Solution
The implementation of a customizable event processing system that allows third-party providers to define custom actions, change the order of pre-defined default actions, and prioritize actions based on policy data, ensuring time-sensitive actions are performed within allotted time frames across different infrastructure platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If pre-defined fixed management actions are performed for infrastructure events, then system simplicity and ease of operation are improved, but adaptability and ability to perform time-sensitive custom actions deteriorate
Solution Approach 1:
The event processing system is segmented into modular components: event subscriptions, event notifications, processing definitions, and action implementations. Third-party systems can subscribe to specific event types and define custom processing definitions that segment the overall event handling into manageable, customizable units. This allows selective customization without affecting the entire system.
Solution Approach 2:
The system transitions from static pre-defined actions to dynamic customizable processing definitions. Third-party systems can dynamically define custom actions, modify processing definitions, and adjust event handling behavior based on specific requirements. The system supports runtime configuration of event processing through configurable parameters and customizable action sequences.
2Device complexity
If a single fixed order of actions is applied across all infrastructure platforms, then system complexity is reduced, but the ability to perform time-sensitive actions within specified time periods deteriorates
Solution Approach 1:
The action order is made dynamic through processing definitions that specify customizable sequences for different event types and platforms. Third-party systems can define different action orders based on time-sensitivity requirements, platform-specific constraints, and business logic. The system executes actions according to the dynamically determined order rather than a fixed universal sequence.
Solution Approach 2:
Different action orders and processing definitions are applied locally to different infrastructure platforms and event types based on their specific requirements. Time-sensitive events receive prioritized handling with customized action sequences, while less critical events follow standard procedures. This local customization optimizes response time for critical operations without unnecessarily complicating the entire system.
3Adaptability or versatility
If third-party customization of event processing is allowed, then adaptability and customization capability are improved, but device complexity and implementation difficulty increase
Solution Approach 1:
The system provides universal event processing capabilities that work across multiple infrastructure platforms through a common interface. The processing definition framework serves multiple purposes: it handles standard events, supports third-party customizations, and enables time-sensitive actions. This multi-functionality reduces the need for separate customization mechanisms while maintaining high adaptability.
Solution Approach 2:
The processing definition acts as an intermediary layer between event notifications and action implementations. Third-party systems define custom processing definitions that mediate between the event source and the execution engine, abstracting the complexity of customization. This intermediary framework simplifies implementation by providing a standardized structure for customization while enabling sophisticated event handling.
4Ease of operation
If pre-defined management actions are executed without customization, then ease of operation is maintained, but productivity and time efficiency for critical actions deteriorate
Solution Approach 1:
Third-party systems can define processing definitions and custom actions in advance, preparing the event processing pipeline before events occur. Time-sensitive actions are pre-configured with prioritized orders and necessary parameters, enabling immediate execution when events are triggered. This preliminary configuration maintains ease of operation while significantly improving response time and productivity for critical actions.
Data Source
AI summary
A processing device receives a request to include a custom action in a processing definition. The custom action is to be performed in response to an occurrence of an infrastructure event in a third party infrastructure platform. The processing device selects the processing definition that specifies a default action to be performed in response to the occurrence of the infrastructure event. The default action being defined by an infrastructure management platform managing the third party infrastructure platform. The processing device receives, from the third party infrastructure platform, user input defining the custom action relative to the default action in the processing definition and changes the processing definition to include the custom action relative to the default action.