You can create periodic latency tests with the scheduling mechanism. The scheduler is basically a wrapper over Latency Test Plan to make it periodically runnable with the given configurations.

Creating a Scheduler

A new Scheduler needs a Test Plan to wrap it, an Interval to decide the interval time between each run, and optionally Total Run Count to state the maximum number of run counts for the scheduler. If you leave the Total Run Count empty, then the Scheduler runs until you stop it or your balance is out of credit.

Lifecycle of a Scheduler

Once you click the Save button on the New Scheduler form, the scheduler starts to work by considering the Interval time. Unless you stop it, it will run until it reaches the Total Run Count. You can track the run count or disable the scheduler on the Scheduler list as shown in "Figure 1: Scheduler Table"

Analyzing the Result

To should the result of the scheduler, click the "Result" button located on the right side of the Scheduler Table.

The Scheduler Result displays the latency changes of your endpoint over time with city breakdowns.

Last updated