Action pooling is a possibility that allows to limit the number of actions performed as a result of observation monitoring definitions. In many cases it is not wanted that the creation or modification of observations repeatedly triggers the execution of observation monitoring actions in a short time period. E.g. if you create an observation monitoring definition whose conditions match if a numeric property of the observation exceeds some defined interval and which will send a message whenever that condition matches, it might happen, that your mailbox is filled with hundreds or thousands of messages in a short time. With action pooling you can prevent this situation.

Action pooling is configured by a single setting the pooling time span. If an action shall be triggered but the last triggering of the same action (in the same observation monitoring definition) is not longer ago than the configured pooling time span the action will not be triggered again.

Action pooling is defined for each action in an observation monitoring definition. Example: You may define an observation monitoring action that creates a new alarm each time it is called (pooling time span = 0) or but sends out a maximum of one message per hour.