Run Results Checks
Note
The below checks require both manifest.json
and run_results.json
to be present.
check_run_results
check_run_results_max_gigabytes_billed
Each result can have a maximum number of gigabytes billed.
Note
Note that this check only works for the dbt-bigquery
adapter.
Receives:
Name | Type | Description |
---|---|---|
exclude |
Optional[str]
|
Regex pattern to match the resource path. Resource paths that match the pattern will not be checked. |
include |
Optional[str]
|
Regex pattern to match the resource path. Only resource paths that match the pattern will be checked. |
max_gigabytes_billed |
float
|
The maximum gigabytes billed allowed for a node. |
run_result |
DbtBouncerResult
|
The DbtBouncerResult object to check. |
Example(s):
Source code in src/dbt_bouncer/checks/run_results/check_run_results.py
check_run_results_max_execution_time
Each result can take a maximum duration (seconds).
Receives:
Name | Type | Description |
---|---|---|
exclude |
Optional[str]
|
Regex pattern to match the resource path. Resource paths that match the pattern will not be checked. |
include |
Optional[str]
|
Regex pattern to match the resource path. Only resource paths that match the pattern will be checked. |
max_execution_time_seconds |
float
|
The maximum execution time (seconds) allowed for a node. |
run_result |
DbtBouncerResult
|
The DbtBouncerResult object to check. |
Example(s):
run_results_checks:
- name: check_run_results_max_execution_time
include: ^staging # Not a good idea, here for demonstration purposes only
max_execution_time_seconds: 10