A rate-limiting mechanism is now available for all internal and external tests. This provides you with greater control over how often a test is performed by the sensors thereby reducing the potential impact on an application.

There are two new options in the test configuration:

Frequency: This option represents the minimum time period between two runs of a test on a sensor. This setting was already available for throughput and web application tests. Now it is extended to all internal and external tests. By default, the value is "fastest" which indicates the test should run every test cycle. Other options are 10 Min, 20 Min, 30 Min, 1 Hour, 2 Hours, 4 Hours, 6 Hours or 12 Hours.

Service Rate Limit: This option specifies the test/service execution rate that all of your sensors should not exceed collectively. Once you input the parameters for the limit and period unit, a calculation is performed on the cloud and gets translated to each sensor’s config to determine the execution rate. The calculation will factor in the configured rate, number of sensors, and number of networks that are configured to run this service. This is a best-effort method to ensure sensors execute the tests for service under the provided limit. By default, the rate limit is off but you can specify a number for the limit and set the period to per minute or per second.

If no rate limit is provided, then the sensor will receive the set frequency.

If frequency and rate limit are both configured, the sensor will receive the largest value which will cause the sensor to test the service less often.

Once configured, you can see the Endpoint Test Frequency and Rate Limit under the About section of the service status page.