By adding aggregators, you can define various functions that can be applied to events in an event strategy rule. For example, you can sum property values from incoming events for trend detection, such as detecting the number of dropped calls, certain transactions, or aggregated purchases conducted with a credit card.
Note: To use aggregators in an event strategy, a Window shape must be placed and configured before the Aggregate shape.
Note: As a best practice, add only one count. Multiple count functions consume processing power unnecessarily as only the last count value is evaluated.
In the Source field, specify a property that is available in the data flow.
Note: By default, all properties defined in the event strategy class are made available through a streamed data set. This makes properties of the event strategy class available to the Real-time Data stream shape. Depending on how the event strategy is constructed, additional properties can be available in the list of the aggregate source field. Additional properties can include:
Note: The Source field is not available for the Count function.
Note: The name allows for creating a dynamic property that exists only in the context of the event strategy. The dynamic property contains the result of the aggregation function. Aggregator names within an event strategy must be unique.
Optional: Repeat these steps to add another aggregator.