Here is a list of flags and vars for Elementary Data that are mentioned in the provided knowledge sources, along with short descriptions. The list is not exhaustive, as the knowledge sources themselves note that a definitive, centralized list is not yet available in the official documentation [[ELE-129 Github Issue](https://github.com/elementary-data/elementary/issues/525)], but these are the ones explicitly referenced: | Type | Name | Description | |-------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | flag | require_explicit_package_overrides_for_builtin_materializations | Allows packages (like Elementary) to override dbt's built-in materializations. Required for Elementary to collect samples and failed row counts for dbt tests (dbt 1.8+). | | flag | mute_ensure_materialization_override | Mutes the warning about the above flag. | | flag | --project-dir | Path to the directory with your

dbt_project.yml

. Default is the working directory. | | flag | --profiles-dir / -p | Path to the directory with your

profiles.yml

. Default is

HOME_DIR/.dbt

. | | flag | --config-dir / -c | Path to the directory with your

config.yml

. Default is

HOME_DIR/.edr

. | | flag | --target-path | Path for output files (logs, reports). Default is

./edr_target

. | | flag | --profile-target / -t | Select a specific target for Elementary. | | flag | --project-profile-target | Select a specific target for your dbt project. | | flag | --select | Filter alerts/report using a selector (e.g., by tag, owner, model, status, resource type). | | flag | --slack-webhook / -s | Slack webhook URL for sending alerts/reports. | | flag | --slack-token / -st | Slack token for sending alerts/reports. | | flag | --slack-channel-name / -ch | Slack channel name to send the file to. | | flag | --full-refresh-dbt-package / -f | Force full refresh of all incremental models in the edr dbt package. | | flag | --days-back / -d | Limit how far back Elementary collects dbt and Elementary results for alerts/reports. | | flag | --file-path | Local file path to save Elementary’s report. | | flag | --file-name | Remote file name for the report (Slack, S3, GCS). | | flag | --s3-endpoint-url | Endpoint of the S3 bucket for

send-report

with S3-compatible storage. | | flag | --timezone / -tz | Timezone for calculating alert times. | | flag | --dbt-quoting / -q | Control dbt quoting for the internal dbt package (e.g., all, none, identifier, schema, etc.). | | flag | --disable-samples | Disable sampling of data in reports/alerts (useful for sensitive/PII data). | | flag | --project-name | Custom project name for the report. | | flag | --env | Indicate if running in dev or prod environment (affects report labeling). | | flag | --suppression-interval | Suppress similar alerts for a given number of hours. Default is 0 (no suppression). | | flag | --override-dbt-project-config | Override alert configuration from dbt project (e.g., for testing, send all alerts to a single channel). | | flag | --filters | Filter alerts by tags, owner, model, status, or resource type. Can be used multiple times. | | flag | --group-by | Group alerts by table. | | flag | --group-alerts-threshold | Minimum alert threshold before grouping notifications into a summary alert. | | var | disable_run_results | Disables uploading of run results. Useful for large projects or development environments. | | var | disable_tests_results | Disables uploading of test results. Useful for large projects or development environments. | | var | disable_dbt_artifacts_autoupload | Disables automatic upload of dbt artifacts. | | var | disable_dbt_invocation_autoupload | Disables automatic upload of dbt invocation data. | | var | enable_elementary | Controls whether Elementary is enabled (can be set based on target type, e.g., disable for 'fabric'). | | var | tuva_schema_prefix | Used to customize schema naming for Elementary models. | | var | enable_input_layer_testing | Used in custom logic to enable/disable input layer testing (example from user config). | | var | mute_ensure_materialization_override | Mutes the warning about the materialization override flag (see above). | Note: - Many CLI flags can also be set in

config.yml

or as environment variables (e.g.,

EDR_<COMMAND>_<OPTION>=<VALUE>

) [[CLI Options](https://docs.elementary-data.com/oss/cli-commands#cli-options)]. - Some variables are referenced in Slack and GitHub issues but are not yet fully documented in the official docs [[ELE-129 Github Issue](https://github.com/elementary-data/elementary/issues/525)], [[Slack Feedback](https://slack.com/archives/C02CTC89LAX/p1672946756861029)]. - For the most up-to-date and complete list, running

edr monitor --help

or

edr report --help

is recommended [[Slack Q&A](https://slack.com/archives/C02CTC89LAX/p1674837405340689)]. If you need details on a specific flag or var, let me know!

@kapa.ai columns_upload_strategy: none

The variable

columns_upload_strategy: none

can be set in your

dbt_project.yml

to disable the upload or processing of column metadata by Elementary. This is particularly useful if updating or collecting column information (such as in the

dbt_columns

model) is too resource-intensive or causes issues in your environment (e.g., exceeding query length limits in Athena, or high memory usage). Setting this variable to

none

should prevent Elementary from running the column collection logic. However, in some cases, users have reported that even after setting this variable, the

dbt_columns

model may still run, especially during certain types of deploys or package updates. In those cases, it is recommended to also explicitly exclude the model using the

--exclude dbt_columns

flag in your dbt run command to ensure it does not execute [[Slack thread: Athena query length](https://slack.com/archives/C02CTC89LAX/p1741597159468009)], [[Slack thread: Memory usage](https://slack.com/archives/C02CTC89LAX/p1740143298724479)]. Summary: -

columns_upload_strategy: none

disables column metadata collection/upload in Elementary. - If issues persist, also use

--exclude dbt_columns

in your dbt run command.