This section is aimed at collecting common issues users have to provide quick debug solutions.
I run `edr report` and get an empty report
dbt deps
. Make sure to execute dbt run --select elementary
for the package tables to be created.
elementary_test_results
exists and has data
dbt run --select elementary
for the package tables to be created.
dbt test
since deploying the package and creating the models?
dbt_project.yml
file that overrides the package config. Remove it, and run dbt run --select elementary --full-refresh
to recreate the tables. After that run dbt test
again and check if there is data.
pip show elementary-data
to detect your version, and validate that it is the latest one. If not, run
pip install elementary-data --upgrade
.
edr report -u true
HOME_DIR/.dbt/profiles.yml
. If saved elsewhere, make sure to run dbt run and dbt test with —profiles-dir <profiles.yml path>
elementary
<your_dbt_project_schema>_elementary
/site-packages/monitor/dbt_project/logs/dbt.log
You can find the full path of the package location using
pip show elementary-data
.Error: `cannot insert into a view`
dbt_project.yml
file, under the key materialization
.Error: `command not found: edr` on macOS
edr
, it places the executable in a location that is not under the default PATH
which is the environment variable that is used for executable lookups. Here’s an example of the warning you might receive upon running python3 -m pip install elementary-data
.edr
is not found by default upon installation.
There are multiple ways to solve this.~/.zshrc
) and append Python’s library path.Error: `command not found: edr` on Windows
Successfully installed elementary-data
but get a command not found
error, it is probably because of a missing path in your environment variables.Look for a warning in your terminal saying:
Warning: the script edr.exe is installed in '<path>' which is not on PATH
This is the path that needs to be added to your windows env vars, run:edr
again.Error: No such command 'monitor'
WARNING - Installed package 'elementary' is overriding the built-in materialization 'XXX'
require_explicit_package_overrides_for_builtin_materializations
to false
as required in the dbt package installation guide.I changed the training period but the results are the same
training_period
.
If you change it after executing elementary tests, you will need to run a full refresh to the metrics collected. This will make the next tests collect data for the new training_period
timeframe.
The steps are:training_period
in your dbt_project.yml
. dbt run --select data_monitoring_metrics --full-refresh
.edr report --days-back 45
Error when trying to run parallel dbt jobs
dbt_artifacts
tables in the Elementary schema, data is deleted and reinserted. Running parallel jobs through an orchestrator can lead to errors, as multiple jobs may attempt to modify the same tables simultaneously.
To prevent this, you should:For scheduled updates to dbt_artifacts
(e.g., a daily job), run:Elementary on-run-end hooks are taking a long time
dbt_columns
table in the Elementary schema can take a while to update, especially for large projects. This table is only used by Elementary Cloud, so if you’re not relying on it (or want to speed up your runs), you can disable it safely without affecting any other functionality.To skip updating this table, add the following to your dbt_project.yml:My problem is not listed here