To edit an existing custom monitoring schedule:
-
On the
Projects page (), click the project for which you want to edit an existing custom monitor schedule.
-
On the
Monitors tab (), click the clock button in the
Schedule column that corresponds to the monitor you want to re-schedule.
-
On the
Configure Schedule page, specify a
From time (month, day, year, hour, minute, second, AM/PM) when the project's monitors should begin to run.
-
Specify the
Interval (day, hour, minute) at which the project's monitors should execute.
Note: When monitors are comprised of multiple transactions, transactions are executed in quick succession. Individual transactions
can't be scheduled independently within monitors. Ensure that the execution interval you select provides adequate time for
the monitor's transactions to execute (for example, a monitor that requires 90 seconds to complete its transactions, can not
be executed at 60 second intervals).
-
Specify how long the project's monitors are to
Run (forever, a specific number of times, or until a specific date.
-
In the
Run From list, select at least one location from which the project's monitors are to be executed. Note that monitors can be run simultaneously
from multiple locations. Use the
Ctrl key to select multiple locations.
-
Select a
Cascaded Delay. This setting avoids that a monitor is started simultaneously across all locations to avoid workload peaks on the system
under test. Example: Setting the cascaded delay to 5 seconds for a monitor that is scheduled to run at 5:00 AM results in
the monitor to run on the first location at 5:00:00 AM, on the second location at 5:00:05, and on the third location at 5:00:10.
Note: If the duration of the cascaded runs exceeds the execution interval, the skipped monitor execution will not be executed.
-
From the
Concurrent Runs list, specify the number of monitors that are concurrently started on the scheduled locations. This setting limits the number
of monitors that are concurrently started on the scheduled locations to the configured value. Example: If a monitor is scheduled
on 100 locations and
Concurrent Runs is set to 10, the first schedule interval executes the monitor on locations 1-10, the second interval on locations 11-20,
and so on.
Note: The underlying round-robin principle does not always arrange the locations into the same groups, depending on if the number
of locations can be divided through the number of concurrent runs. Example: for 13 locations and 5 concurrent runs, the monitor
will execute on locations 1,2,3,4,5 - 6,7,8,9,10 - 11,12,13,1,2 - 3,4,5,6,7, and so on.
-
Click
Save to return to the
Monitors tab. Alternatively, you may advance to the
Configure Schedule Exclusion page to add exclusions or to the
Configure Definite Run page to configure definite runs. See
Schedule Exclusions and
Definite Runs for detailed information.