Contact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.

Autostop

Written by
Updated at April 28, 2026

Warning

Starting July 1, 2026, Load Testing will be discontinued. For more information, see Yandex Load Testing shutdown.

Autostop is a plugin configurable during test creation that automatically stops the test depending on pre-defined criteria.

Autostop is used to limit time and resources allocated for testing or define certain events after which further testing is unneeded.

The triggered autostop criterion prematurely stops the test. To determine which criterion stopped the test, criteria are assigned Termination codes, which can be used for automatic evaluation of test results.

autostop section format in the yaml test configuration file:

autostop:
  enabled: true
  package: yandextank.plugins.Autostop
  autostop:
    - <autostop_criterion>(<criterion_parameters>)

Warning

In the configuration file, autostop is a required section; otherwise, the test will not run in new system versions.
In this section, you must specify at least the limit criterion, which is the time limit for the test.
The limit value should be slightly greater than the expected test duration to prevent autostopping the regular flow of the test.

Main criteria

Criterion Description
limit This is a required criterion.
The test will stop after the specified period of time.
Example: limit(1m).
time The test will stop if the average response time exceeds the given value during the specified period.
Examples: time(1s500ms,30s), time(50,15).
Termination code: 21.
http The test will stop if the number of responses with particular HTTP codes exceeds the given absolute or relative values during the specified period. Use xx for all non-zero code values.
Examples: http(404,10,15), http(5xx,10%,1m).
Termination code: 22.
net Similar to http for net codes.
Termination code: 23.
quantile The test will stop if the selected percentile of queries exceeds the given value during the specified period. Available percentiles: 25, 50, 75, 80, 90, 95, 98, 99, 100.
Example: The quantile(95,100ms,10s) criterion stops the test if the 95th percentile exceeds 100 milliseconds for 10 seconds (for 10 seconds, the time to process 5% of queries exceeds 100 milliseconds).
instances The test will stop if the number of testing threads exceeds the given value during the specified period.
Examples: instances(80%,30), instances(50,1m).
Termination code: 24.
steady_cumulative The test will stop if the cumulative percentiles do not change during the specified period.
Example: steady_cumulative(1m).
Termination code: 33.

The main criteria are not averaged, they are assessed every second during the specified period. For example, the autostop=time(50,15) criterion stops the test if the average response time per second exceeds 50 milliseconds during 15 seconds.

Additional criteria

Criterion Description
total_time Similar to time but cumulative for the whole time period (responses that meet the criterion may be non-consecutive but coming during the specified period).
Example: total_time(300ms,70%,3s).
Termination code: 25.
total_http Similar to http but cumulative for the whole time period. See total_time.
Examples: total_http(5xx,10%,10s), total_http(3xx,40%,10s).
Termination code: 26.
total_net Similar to net but cumulative for the whole time period. See total_time.
Examples: total_net(79,10%,10s), total_net(11x,50%,15s).
Termination code: 27.
negative_http Inverted total_http.
The test will stop if the total number of responses with HTTP codes not matching the mask exceeds the given absolute or relative values within the specified period. Use HTTP code 200 to make sure the server responds.
Example: negative_http(2xx,10%,10s).
Termination code: 28.
negative_net Inverted total_net.
The test will stop if the total number of responses with net codes not matching the mask exceeds the given absolute or relative values within the specified period.
Example: negative_net(0,10%,10s).
Termination code: 29.
http_trend The test will stop if the trend for specific HTTP codes remains negative during the specified period. A trend is the sum of the linear function's averaged coefficient, calculated for each pair of points for the last n seconds, and its standard deviation.
Example: http_trend(2xx,10s).
Termination code: 30.

Criteria for specific tags

Except for limit, all other criteria can be applied to a specific URI labeled with a tag, not the whole test.

For example, time(1s,5s,/latest/index/) stops the test if the average response time only from the URL tagged /latest/index/ exceeds 1 second for 5 seconds.

Any specific URI can be tested this way. For example:

autostop:
  enabled: true
  package: yandextank.plugins.Autostop
  autostop:
    - limit(5m)
    - http(4xx, 20%, 15s, case1)
    - http(4xx, 5%, 5s, case2)

Such autostop will stop the test if the number of URI responses tagged case1 with HTTP code 4xx exceeds 20% for 15 seconds, or the number of URI responses tagged case2 with HTTP code 4xx exceeds 5%.

Use cases

Previous
Testing threads
Next
Resource Check