Results

The results page displays all information applicable to the results of a specific test.

You can access the results for a specific test by clicking on the “View results” button in your Dashboard for the respective test id.

Notes: While the test is still running, the graphs will update automatically near real time (at 4 second intervals), but will not be 100% accurate. However, as soon as the test finishes, the graphs WILL be completely 100% accurate.

Permissions

Member role vs API call

View raw results

View summary

View graphs

Download Failures CSV

Download Detailed Stats

Reader

True

True

True

True

True

Editor

True

True

True

True

True

Admin

True

True

True

True

True

AdminWithBilling

True

True

True

True

True

Owner

True

True

True

True

True

NOTE: If the test is public, then anyone can view the results (including non-authenticated persons).

Raw results

Web

Includes a per-region (as well as “overall”) raw data for each path in your workflow with the details about the success/failure statistics of that workflow step.

API call

The API call is:

curl -s \
    -d '{
        "test_id": "some_test_id",
        "team_id": "my-team",
        "results_region": "overall",
        "results_path": "/",
        "results_method": "GET",
        "results_type": "success",
        "min_timestamp": "1000000000",
        "max_timestamp": "2000000000"
        }' \
    -H "X-Api-Key: my_api_key" \
    -X POST \
    https://app.rungutan.com/v1/api/raw-results/get | jq . -r

{
    "Results": [
        {
            "avg": 144,
            "max": 119,
            "min": 80,
            "path": "/",
            "result_timestamp": "1603882572",
            "rps": 40,
            "sum": 5775,
            "team_id": "my-team",
            "region": "overall",
            "method": "GET",
            "test_id": "some_test_id"
        },

        [...]

        {
            "avg": 41,
            "max": 46,
            "min": 22,
            "path": "/",
            "result_timestamp": "1603882602",
            "rps": 167,
            "sum": 6888,
            "team_id": "my-team",
            "region": "overall",
            "method": "GET",
            "test_id": "some_test_id"
        }
    ],
    "ResultsMetadata": {
        "team_id": "my-team",
        "test_id": "some_test_id",
        "results_region": "overall",
        "results_path": "/",
        "results_method": "GET",
        "results_type": "success",
        "min_timestamp": "1000000000",
        "max_timestamp": "2000000000"
    }
}

CLI

Get them for the overall region:

$ rungutan raw_results get --test_id some_test_id --results_type success --results_region overall --results_path "/" --results_method GET --min_timestamp 1000000000 --max_timestamp 2000000000
{
    "Results": [
        {
            "avg": 144,
            "max": 119,
            "min": 80,
            "path": "/",
            "result_timestamp": "1603882572",
            "rps": 40,
            "sum": 5775,
            "team_id": "my-team",
            "region": "overall",
            "method": "GET",
            "test_id": "some_test_id"
        },

        [...]

        {
            "avg": 41,
            "max": 46,
            "min": 22,
            "path": "/",
            "result_timestamp": "1603882602",
            "rps": 167,
            "sum": 6888,
            "team_id": "my-team",
            "region": "overall",
            "method": "GET",
            "test_id": "some_test_id"
        }
    ],
    "ResultsMetadata": {
        "team_id": "my-team",
        "test_id": "some_test_id",
        "results_region": "overall",
        "results_path": "/",
        "results_method": "GET",
        "results_type": "success",
        "min_timestamp": "1000000000",
        "max_timestamp": "2000000000"
    }
}

Test summary

Web

Includes a per-region summary for each path in your workflow with the details about the success/failure statistics of that workflow step.

API call

The API call is:

curl -s \
    -d '{
        "test_id": "some_test_id",
        "team_id": "my-team"
        }' \
    -H "X-Api-Key: my_api_key" \
    -X POST \
    https://app.rungutan.com/v1/api/summary-results/get | jq . -r

{
  "Results": {
    "us-east-1": {
        "region": "us-east-1",
        "failures": [],
        "public_ips": [
            "18.232.137.175"
        ],
        "requests": [
            {
                "Method": "GET",
                "Path": "/",
                "num_requests": 874,
                "min_response_time": 9,
                "median_response_time": 16,
                "avg_response_time": 21,
                "max_response_time": 246,
                "response_time_percentiles": {
                    "55": 17,
                    "65": 20,
                    "75": 24,
                    "85": 29,
                    "95": 42
                },
                "total_rps": 29,
                "total_rpm": 1740,
                "Region": "us-east-1"
            }
        ]}
  },
  "ResultsMetadata": {
    "team_id": "my-team",
    "test_id": "some_test_id"
  }
}

CLI

Get them for the overall region:

$ rungutan results get --test_id 61c8bc4b-e1b1-4fb5-bb24-d860bf79e460 --results_region overall
{
    "Results": {
        "region": "overall",
        "failures": [],
        "public_ips": [
            "107.20.40.171"
        ],
        "requests": [
            {
                "Method": "GET",
                "Path": "/",
                "num_requests": 4,
                "min_response_time": 21,
                "median_response_time": 22,
                "avg_response_time": 56,
                "max_response_time": 149,
                "response_time_percentiles": {
                    "55": 31,
                    "65": 31,
                    "75": 150,
                    "85": 150,
                    "95": 150
                },
                "total_rps": 1,
                "total_rpm": 60
            }
        ]
    },
    "ResultsMetadata": {
        "team_id": "rungutan",
        "test_id": "61c8bc4b-e1b1-4fb5-bb24-d860bf79e460"
    }
}

Or for any other region and extract the public ips

$ rungutan results get --test_id 61c8bc4b-e1b1-4fb5-bb24-d860bf79e460 --results_region us-east-1 | jq -r .Results.public_ips
[
  "107.20.40.171"
]

Test failures

Web

Includes an overall summary for each path in your workflow with the details about the failure of each workflow step including all error messages that came up.

API call

The API call is:

curl -s \
    -d '{
        "test_id": "some_test_id",
        "team_id": "my-team"
        }' \
    -H "X-Api-Key: my_api_key" \
    -X POST \
    https://app.rungutan.com/v1/api/summary-results/failure-csv | jq . -r

{
    "Url": "https://link-to-download-csv",
    "ResultsMetadata": {
        "team_id": "my-team",
        "test_id": "some_test_id"
    }
}

Test detailed stats

Web

Includes a “sample” of all your requests to better get an overview about response content/length/time.

The sample rate is basically 1 response / second.

API call

The API call is:

curl -s \
    -d '{
        "test_id": "some_test_id",
        "team_id": "my-team"
        }' \
    -H "X-Api-Key: my_api_key" \
    -X POST \
    https://app.rungutan.com/v1/api/summary-results/detailed-stats-csv | jq . -r

{
    "Url": "https://link-to-download-csv",
    "ResultsMetadata": {
        "team_id": "my-team",
        "test_id": "some_test_id"
    }
}

Test progress

Web

Displays the status of the test and provides the possibility of switching the current region of the graphs that are shown.

If test is still running, also provides the possibility to cancel it.

Test graphs

Web

Displays 5 graphs for each workflow step defined in your test scenario.

These graphs are:

  • Requests per second = The amount of requests that have been done at each second for that specific region

  • Average response time = The average response time at 1-second intervals

  • Minimum response time = The minimum response time at 1-second intervals

  • Maximum response time = The maximum response time at 1-second intervals

  • Percentile response time = The percentile-based response time