Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Load Testing
  • Getting started
    • All guides
    • Creating a test agent
    • Configuring test agent security groups
    • Configuring test target security groups
    • Creating a test with data from a bucket
    • Exporting test reports
    • Collecting user requests using Dispatcher
    • Creating and configuring a regression dashboard
    • Checking regression metrics for exceeded thresholds
    • Saving test artifacts to Object Storage
    • Viewing operations with resources
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes

In this article:

  • Preparing test IDs
  • Checking all charts of a selected test
  • Checking charts on a given dashboard
  • Checking an idividual chart
  1. Step-by-step guides
  2. Checking regression metrics for exceeded thresholds

Checking regression metrics for exceeded thresholds using CLI

Written by
Yandex Cloud
Updated at March 6, 2025
  • Preparing test IDs
  • Checking all charts of a selected test
  • Checking charts on a given dashboard
  • Checking an idividual chart

For each metric (line) on the regression dashboard charts, you can add a threshold value the excess of which should be considered abnormal. In addition to graphical display of areas where thresholds are exceeded, you can get information about regressions using a CLI command.

This page describes the main use cases for the yc loadtesting test check-regression command to check if thresholds are exceeded in regression charts.

Preparing test IDsPreparing test IDs

Get a list of test IDs with the yc loadtesting test list command:

Response example:

+----------------------+---------+--------+---------------------+----------+
|          ID          |  NAME   | LABELS |       CREATED       | FINISHED |
+----------------------+---------+--------+---------------------+----------+
| ff6mmyz7s4t2m4****** | test780 |        | 2024-09-29 09:26:56 |          |
+----------------------+---------+--------+---------------------+----------+

Use the IDs you get to run the check command.

Checking all charts of a selected testChecking all charts of a selected test

If you run the command without any additional parameters, it will check for regression on all the charts in your folder which contain the selected test.

Run this command:

yc loadtesting test check-regression <test_ID>

Example of running the command:

yc loadtesting test check-regression ff6mmyz7s4t2m4******

                     Test:   autotest-pandora-line-uripost (id=ff6mmyz7s4t2m4******)

------------------------------------------------------------------------------------
   Charts checked (count):                                                         3
               Thresholds:                                           2 OK / 1 FAILED


   status   value     threshold        fn                           metric      case                                                    chart        dashboard

--------------------------------------------------------------------------------------------------------------------------------------------------------------
       OK       0    value <= 5   percent   Responses: protocol code (5xx)   overall                       all tests: less than 5% 5xx codes    test-dashboard
       OK     100   value >= 90   percent   Responses: protocol code (200)   overall                      all tests: more than 90% 200 codes    test-dashboard
   FAILED      27   value <= 20       q99                          Latency   overall              Response time: autotest-pandora-line-uripost         autotest
        -      18             -       q98                          Latency   overall              Response time: autotest-pandora-line-uripost         autotest
        -     4.3             -       q75                          Latency   overall              Response time: autotest-pandora-line-uripost         autotest
        -    3.39             -       q50                          Latency   overall              Response time: autotest-pandora-line-uripost         autotest

Checking charts on a given dashboardChecking charts on a given dashboard

If you run the command with the --dashboard-id parameter, it will only check the charts from the dashboard you specify.

You can get the dashboard ID on the page with the list of dashboards (the ID column is hidden by default), or take it from the dashboard page URL.

Run this command:

yc loadtesting test check-regression <test_ID> --dashboard-id <dashboard_ID>

Example of running the command:

yc loadtesting test check-regression ff6mmyz7s4t2m4****** --dashboard-id ff6jqg3mf5xhby******

                     Test:   autotest-pandora-line-uripost (id=ff6mmyz7s4t2m4******)

------------------------------------------------------------------------------------
   Charts checked (count):                                                         2
               Thresholds:                                           2 OK / 0 FAILED


   status   value     threshold        fn                           metric      case                                 chart        dashboard

-------------------------------------------------------------------------------------------------------------------------------------------
       OK       0    value <= 5   percent   Responses: protocol code (5xx)   overall    all tests: less than 5% 5xx codes    test-dashboard
       OK     100   value >= 90   percent   Responses: protocol code (200)   overall   all tests: more than 90% 200 codes    test-dashboard

Checking an idividual chartChecking an idividual chart

If you run the command with the --dashboard-id and --chart-id parameters, it will only check the thresholds on a specific chart.

yc loadtesting test check-regression <test_ID> --dashboard-id <dashboard_ID> --chart-id <chart_ID>

You can get the dashboard ID on the page with the list of dashboards (the ID column is hidden by default), or take it from the dashboard page URL.

To get the chart ID, click next to any of the charts on the dashboard. This will open a separate chart page. You can find the ID is at the top of the page and in its URL.

Example of running the command:

yc loadtesting test check-regression ff6mmyz7s4t2m4****** --dashboard-id ff6jqg3mf5xhby****** --chart-id 57651054-35af-47ea-a5a8-6a1a8dbe4377

                     Test:   autotest-pandora-line-uripost (id=ff6mmyz7s4t2m4******)

------------------------------------------------------------------------------------
   Charts checked (count):                                                         1
               Thresholds:                                           1 OK / 0 FAILED


   status   value    threshold        fn                           metric      case                                chart        dashboard

-----------------------------------------------------------------------------------------------------------------------------------------
       OK       0   value <= 5   percent   Responses: protocol code (5xx)   overall   all tests: less than 5% 5xx codes    test-dashboard

Was the article helpful?

Previous
Creating and configuring a regression dashboard
Next
Saving test artifacts to Object Storage
© 2025 Direct Cursus Technology L.L.C.