Export metrics
In a test report directory, the export subdirectory contains files that can be imported to InfluxDB or Prometheus for building custom graphs.
Export to InfluxDB
The export/influxDbData.txt file contains aggregate test data in the line protocol format for InfluxDB. When imported, it created the following measurements.
| Measurement |
Tags |
|
launch_status
|
One tag per each possible test status: failed, broken, passed, skipped, unknown.
Each value represents the number of tests with the status.
|
|
launch_time
|
duration — the time it took to run all tests.
min_duration — the duration of the fastest test run.
max_duration — the duration of the slowest test run.
sum_duration — all durations, combined.
The values for duration and sum_duration may differ significantly if your test framework runs test in parallel or spends significant time preparing for each test.
|
|
launch_problems
|
One tag per each non-empty defect category.
Each category's name is converted to lowercase, and the spaces are replaced with underscores, for example: test_defects, product_defects.
Each value represents the number of tests in the category.
|
|
launch_retries
|
retries — the number of unique test runs.
run — the number of test runs that were retries of other test runs.
|
Export to Prometheus
The export/prometheusData.txt file contains aggregate test data in the text-based format format for Prometheus. When imported, it created the following metrics.
| Prefix |
Metrics |
|
launch_status_*
|
One metric per each possible test status:
launch_status_failed,
launch_status_broken,
launch_status_passed,
launch_status_skipped,
launch_status_unknown.
Each value represents the number of tests with the status.
|
|
launch_time_*
|
launch_time_duration — the time it took to run all tests.
launch_time_min_duration — the duration of the fastest test run.
launch_time_max_duration — the duration of the slowest test run.
launch_time_sum_duration — all durations, combined.
The values for launch_time_duration and launch_time_sum_duration may differ significantly if your test framework runs test in parallel or spends significant time preparing for each test.
|
|
launch_problems_*
|
One metric per each non-empty defect category.
Each category's name is converted to lowercase, the spaces are replaced with underscores, and the prefix is added, for example: launch_problems_test_defects, launch_problems_product_defects.
Each value represents the number of tests in the category.
|
|
launch_retries_*
|
launch_retries_retries — the number of unique test runs.
launch_retries_run — the number of test runs that were retries of other test runs.
|
