Knowledge BaseMetric InsightsDistribution BurstsConfigure Notification Schedules and Data Collection Triggers Using Controls

Configure Notification Schedules and Data Collection Triggers Using Controls

This article provides some recommendations on how to properly configure runs of Notification Schedules and Data Collection Triggers using controls.

1. What to Remember

Multiple concurrent runs within a Notification Schedule or a Data Collection Trigger are not allowed as they may affect each other and their behavior is difficult to predict. Metric Insights implemented Expiration Period and Abort Run functions to help Power Users and Admins ensure each previous run within a Notification Schedule or a Data Collection Trigger is completed and allow a new run to be started properly.

Learn also how to create and modify Notification Schedules and automate collection of data with Data Collection Triggers.

2. Using Controls for Notification Schedules

2.1. Expiration Period

Expiration Period allows setting a period within which a run is expected to be completed.

In the [Schedule] tab, set: 

  1. Frequency of a run
  2. Time when a run is expected to start

In the [Advanced] tab:

  1. Expiration Period within which a run is expected to be completed

By default, Expiration Period is set to 600 min for Notification Schedule.

If a run frequency is set to be performed once a day, set Expiration Period to less than 23 h and Abort Run to "yes". Alternatevily, try to offload the run to fit the desired Expiration Period (e.g. move a part of the run content to another Notification Schedule).

2.2. Abort Run

Abort Run allows automatically abort all active threads within a run once Expiration Period is completed, so that a current run does not block the following runs.

[Advanced] setting allows to:

  1. Set Abort Run to "yes"
  2. Determine email where to send a notification

By default, Abort Run is set to "yes".

When a run expires and some users are still being processed or remain active while others are in the queue, active jobs are completed and no new jobs are started. As a result, the run is aborted and processed and active users receive their content, while those in the queue do not. The next run starts as scheduled.

3. Using Controls for Data Collection Triggers

All above is also applicable to Data Collection Triggers: Expiration Period and Abort Run functions allow completing active runs of data collection within the period set and start new runs as scheduled.

In [Configuration] tab, set:

  1. Expiration Period
  2. Abort Run to "yes"

By default, Expiration Period is set to 60 min and Abort Run to "yes".