Referencing operator instructions in event rules
TWSObjectsMonitor type.
By enabling dynamic data extraction from job and job streams definitions, this feature enhances event-driven workload automation (EDWA) processes, significantly improving event rules flexibility and reusability. This enhancement provides greater speed and efficiency in automation, substantially reducing the number of event rules otherwise required to cover multiple objects.
The feature supports the direct use of information contained within the description and documentation fields of jobs and job streams definitions as variables in EDWA actions. Such operator instructions can include runbook steps, support contacts, and recovery procedures.
TWSObjectsMonitor event actions related to jobs and job streams.
You can choose to retrieve the entire set of instructions or specific, customized
key-value pairs.- Retrieving the entire field content: Retrieve the complete text from the
operator instructions fields, typically used for sending full recovery
procedures:
%{<event>.OpInstr} - Retrieving specific key-value pairs: Extract custom metadata defined
within the object description, for example support
contacts:
%{<event>.OpInstr.<key>}Note: The key-value pair must be present within the description or documentation fields of the job or job stream definition. The syntax requires a key, a separator (either=or:), and a value. For example:support_team=help@wa.it
- Key benefits
-
-
Improved efficiency: Processes become more rapid due to automated, context-aware actions.
-
Rule consolidation: The number of unique event rules required is drastically decreased, as one generic rule can cover multiple events across different jobs and job streams.
-
Enhanced recovery: Provides direct access to operational data and support contacts at the moment an event occurs.
-
For more information, see TWSObjectsMonitor events.