David Roman-Halliday
07/10/2026, 8:33 AMactivity_id, activity_timestamp, activity_source, activity_type, activity_metric_1, activity_metric_2
I want to have a test which checks this table daily for row counts, and identifies if there is a drop off or complete absence for a activity_source , given that different sources will have different usual volumes.hijcss
07/10/2026, 10:44 AMAlvin Rusly
07/13/2026, 5:46 AMFrank Tubbing [Beequip]
07/13/2026, 7:26 AMedr CLI tools already to dbt fusion?Ryan Paul
07/14/2026, 12:48 AMjblecherman
07/14/2026, 5:41 PMEylon Ronen
07/22/2026, 7:32 AMtimestamp_column and we notice that the queries generated by the test filter far far further back than the training period. how can we limit that? we have some large tables and want to make it as efficient as possible
Ideally since the tables are partitioned by the timestamp column we want to only filter on the duration of the test+detectionAlvin Rusly
07/29/2026, 8:55 AMFrank Tubbing [Beequip]
07/30/2026, 11:17 AMBrad Wettig
07/30/2026, 5:48 PMJay Leon
08/05/2026, 10:36 AMJay Leon
08/05/2026, 11:44 AMslack_group_alerts_by in +meta correct, and does it cover model alerts?
On elementary dbt package 0.25.1 with edr 0.25.1 on BigQuery, we setin+meta: {slack_group_alerts_by: table}under bothdbt_project.ymlandmodels:. Manifest confirms 1431/1431 models and 557/557 tests carry it. Two docs pages disagree: the OSS alerts-configuration page namesdata_tests:in YAML meta and says it applies to model and test alerts; another says the key isslack_group_alerts_by, lives in edr'sgroup_alerts_by, and supports test alerts only. Which is correct for 0.25.1, and does grouping apply to model run failures?config.yml
gabriel.maxwell
08/10/2026, 11:06 PMYashwanth THONUKUNURU
08/12/2026, 9:51 AMMatthew Weiner
08/13/2026, 7:12 PMMark van der Meulen
08/20/2026, 11:17 AMdbt state (State adapter: dbt-state v2.29.3 is enabled) while running dbt core 1.12 Elementary 0.25 and edr cli 0.25.0 After implementing dbt state we've experience problems with alerts not being sent. When the alerts_v2 tables is dropped and we run edr monitor it will send the alerts, but will fail to sent alerts the following run. Can you suggest a solution?negordyh
08/21/2026, 4:40 AMjob_name, so we can manage each tenant/game through job-based filters?Paige Fuller
08/27/2026, 9:06 AMDorota Nowicz
09/01/2026, 12:16 PMtest_type value in elementary_test_results table for Volume test? (Elementary volume anomalies tests)Emma Emerton
09/01/2026, 3:03 PMPaula Sielawa
09/02/2026, 10:43 AMHTTPSConnectionPool(host='<http://app.posthog.com|app.posthog.com>', port=443): Max retries exceeded with url: /batch/
This results in multiple retries and delays:
Backing off send_request(...)
Giving up send_request(...) after 4 tries
We would like Elementary to operate completely offline, without attempting any external network connections or telemetry.
Could you please let us know:
1. Is there a supported configuration/environment variable to completely disable PostHog/telemetry?
2. If so, what is the recommended configuration for Elementary CLI 0.25.0?
3. Does disabling telemetry have any impact on Elementary's core functionality or dbt operations?
4. Is there any other outbound network communication that Elementary 0.25.0 may attempt, so that we can ensure the container remains fully offline?
We are also seeing this warning:
You are using incompatible versions between edr (0.25.0) and Elementary's dbt package (0.19.0).
Could you also confirm which Elementary dbt package version is recommended/compatible with edr==0.25.0?
Our requirement is that the container must not make any outbound internet connections, so we would appreciate the recommended configuration for a fully offline/restricted environment.
Thanks!Paula Sielawa
09/09/2026, 10:39 AMedr monitor without sending the alerts directly, but instead get the generated alerts in a structured format (e.g. JSON) so that our wrapper could pick them up and send them through our gateway?Jimmy PANG
09/10/2026, 4:35 PMOndra Paul
09/17/2026, 3:40 PMnegordyh
09/18/2026, 4:02 AMOndra Paul
09/25/2026, 8:36 PMPaula Sielawa
10/09/2026, 11:51 AMedr report getting OOM-killed, looking for ways to reduce its memory footprint
We run edr report (edr 0.26.0, dbt package 0.26.0, Snowflake) inside a container (AWS ECS Fargate). On one of our larger projects the report generation gets OOM-killed — the process exits with Killed (SIGKILL) and we see resource_tracker: ... leaked semaphore objects at shutdown, right after it loads test results.
From the logs, the underlying macro call is:
elementary_cli.get_test_results
days_back: 7, invocations_per_test: 720,
disable_passed_test_metrics: false, skip_test_result_rows: false
We invoke it simply as:
edr report --profiles-dir ... --target-path ... --file-path ...
We understand we can throw more memory at it, but we'd like to reduce what the report loads into memory too. Questions:
1. Are there edr report CLI flags (or config) to control invocations_per_test, days_back, disable_passed_test_metrics, and skip_test_result_rows? 720 invocations/test seems high — is that the default, and can it be lowered?
2. What's the recommended memory for edr report on larger projects?
3. Any guidance on generating the report with a lower memory footprint (pagination/streaming, splitting the window, etc.)?
Thanks a lot — happy to share more logs or config if helpful! 🙏Andy Davies
10/12/2026, 2:27 PMsaul.castro
10/12/2026, 6:17 PMDorota Nowicz
10/14/2026, 11:21 AM