From 8dbb316ea743de50931b3286adaa870cf740468b Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Wed, 27 Nov 2024 16:58:25 +0000 Subject: [PATCH 01/26] remove beta --- website/docs/docs/dbt-versions/release-notes.md | 3 +++ website/docs/docs/deploy/model-notifications.md | 8 -------- website/docs/docs/deploy/monitor-jobs.md | 2 +- 3 files changed, 4 insertions(+), 9 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes.md b/website/docs/docs/dbt-versions/release-notes.md index 55116db68ba..17fd3add960 100644 --- a/website/docs/docs/dbt-versions/release-notes.md +++ b/website/docs/docs/dbt-versions/release-notes.md @@ -18,6 +18,9 @@ Release notes are grouped by month for both multi-tenant and virtual private clo \* The official release date for this new format of release notes is May 15th, 2024. Historical release notes for prior dates may not reflect all available features released earlier this year or their tenancy availability. +## December 2024 +- **New**: [Model notifications](/docs/deploy/model-notifications) is now generally available in dbt Cloud. These notifications alert model owners through email about any issues encountered by models and tests as soon as they occur while running a job. + ## November 2024 - **Fix**: Job environment variable overrides in credentials are now respected for Exports. Previously, they were ignored. - **Behavior change**: If you use a custom microbatch macro, set a [`require_batched_execution_for_custom_microbatch_strategy` behavior flag](/reference/global-configs/behavior-changes#custom-microbatch-strategy) in your `dbt_project.yml` to enable batched execution. If you don't have a custom microbatch macro, you don't need to set this flag as dbt will handle microbatching automatically for any model using the [microbatch strategy](/docs/build/incremental-microbatch#how-microbatch-compares-to-other-incremental-strategies). diff --git a/website/docs/docs/deploy/model-notifications.md b/website/docs/docs/deploy/model-notifications.md index a6d4c467f0b..f444f258120 100644 --- a/website/docs/docs/deploy/model-notifications.md +++ b/website/docs/docs/deploy/model-notifications.md @@ -3,8 +3,6 @@ title: "Model notifications" description: "While a job is running, receive email notifications in real time about any issues with your models and tests. " --- -# Model notifications - Set up dbt to notify the appropriate model owners through email about issues as soon as they occur, while the job is still running. Model owners can specify which statuses to receive notifications about: - `Success` and `Fails` for models @@ -12,12 +10,6 @@ Set up dbt to notify the appropriate model owners through email about issues as With model-level notifications, model owners can be the first ones to know about issues before anyone else (like the stakeholders). -:::info Beta feature - -This feature is currently available in [beta](/docs/dbt-versions/product-lifecycles#dbt-cloud) to a limited group of users and is gradually being rolled out. If you're in the beta, please contact the Support team at support@getdbt.com for assistance or questions. - -::: - To be timely and keep the number of notifications to a reasonable amount when multiple models or tests trigger them, dbt observes the following guidelines when notifying the owners: - Send a notification to each unique owner/email during a job run about any models (with status of failure/success) or tests (with status of warning/failure/success). Each owner receives only one notification, the initial one. diff --git a/website/docs/docs/deploy/monitor-jobs.md b/website/docs/docs/deploy/monitor-jobs.md index 1cbba23161e..40298f0cdbe 100644 --- a/website/docs/docs/deploy/monitor-jobs.md +++ b/website/docs/docs/deploy/monitor-jobs.md @@ -13,7 +13,7 @@ This portion of our documentation will go over dbt Cloud's various capabilities - [Run visibility](/docs/deploy/run-visibility) — View your run history to help identify where improvements can be made to scheduled jobs. - [Retry jobs](/docs/deploy/retry-jobs) — Rerun your errored jobs from start or the failure point. - [Job notifications](/docs/deploy/job-notifications) — Receive email or Slack notifications when a job run succeeds, encounters warnings, fails, or is canceled. -- [Model notifications](/docs/deploy/model-notifications) — Receive email notifications about any issues encountered by your models and tests as soon as they occur while running a job. +- [Model notifications](/docs/deploy/model-notifications) — Receive email notifications about any issues encountered by your models and tests as soon as they occur while running a job. - [Webhooks](/docs/deploy/webhooks) — Use webhooks to send events about your dbt jobs' statuses to other systems. - [Leverage artifacts](/docs/deploy/artifacts) — dbt Cloud generates and saves artifacts for your project, which it uses to power features like creating docs for your project and reporting freshness of your sources. - [Source freshness](/docs/deploy/source-freshness) — Monitor data governance by enabling snapshots to capture the freshness of your data sources. From 94308115f74b5bb972bf6a6f19b7df1e903a0481 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 4 Dec 2024 09:43:53 +0000 Subject: [PATCH 02/26] Update website/docs/docs/dbt-versions/release-notes.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/dbt-versions/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes.md b/website/docs/docs/dbt-versions/release-notes.md index 91f0655cffd..06f77320cd2 100644 --- a/website/docs/docs/dbt-versions/release-notes.md +++ b/website/docs/docs/dbt-versions/release-notes.md @@ -19,7 +19,7 @@ Release notes are grouped by month for both multi-tenant and virtual private clo \* The official release date for this new format of release notes is May 15th, 2024. Historical release notes for prior dates may not reflect all available features released earlier this year or their tenancy availability. ## December 2024 -- **New**: [Model notifications](/docs/deploy/model-notifications) is now generally available in dbt Cloud. These notifications alert model owners through email about any issues encountered by models and tests as soon as they occur while running a job. +- **New**: [Model notifications](/docs/deploy/model-notifications) are now generally available in dbt Cloud. These notifications alert model owners through email about any issues encountered by models and tests as soon as they occur while running a job. ## November 2024 - **Bug**: Identified and fixed an error with Semantic Layer queries that take longer than 10 minutes to complete. From 789bf65f17125a8db22279f53672ceef7d61fbff Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 5 Dec 2024 13:35:51 +0000 Subject: [PATCH 03/26] add callout for collections synching this pr turns the existing content about the once a day sync into a callout and adds info on how to trigger a manual sync per [slack thread](https://dbt-labs.slack.com/archives/C06GJRK27PF/p1733359577763749) and user confusion. --- .../cloud-integrations/configure-auto-exposures.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index 5500e02067e..1d3cc4d0ba8 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -61,9 +61,15 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve 4. Select the collections you want to include for auto exposures. - dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). -5. Click **Save**. + + :::info Syncing collections + dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). + + To manually trigger a sync and update collections (including additions or deletions), go to **Collections**, click **Edit**, make your selections or deselections, and then click **Save**. + ::: + +6. Click **Save**. dbt Cloud imports everything in the collection(s) and you can continue to view them in Explorer. For more information on how to view and use auto-exposures, refer to [View auto-exposures from dbt Explorer](/docs/collaborate/auto-exposures) page. From 8964b5fa5a250824542f6ead423ef8c7a19589df Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 5 Dec 2024 13:41:14 +0000 Subject: [PATCH 04/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md --- website/docs/docs/cloud-integrations/configure-auto-exposures.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index 1d3cc4d0ba8..1d85546b85e 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -63,6 +63,7 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve +#### Synch collections :::info Syncing collections dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). From 77bbb6e080c5dff0f9dd3a9374f7092a2400cc50 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 5 Dec 2024 13:41:27 +0000 Subject: [PATCH 05/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md --- .../docs/docs/cloud-integrations/configure-auto-exposures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index 1d85546b85e..15a40573865 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -64,7 +64,7 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve #### Synch collections - :::info Syncing collections + :::info dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). To manually trigger a sync and update collections (including additions or deletions), go to **Collections**, click **Edit**, make your selections or deselections, and then click **Save**. From b7ddf2372badd44e6e5f732f71eb2134520e3043 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 5 Dec 2024 13:42:14 +0000 Subject: [PATCH 06/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md --- .../docs/docs/cloud-integrations/configure-auto-exposures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index 15a40573865..8c7ea932766 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -63,7 +63,7 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve -#### Synch collections +#### Sync collections :::info dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). From 82d32a06f5250654badb2190e3f5887c77501539 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 5 Dec 2024 13:56:16 +0000 Subject: [PATCH 07/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md --- website/docs/docs/cloud-integrations/configure-auto-exposures.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index 8c7ea932766..f9033d98444 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -63,7 +63,6 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve -#### Sync collections :::info dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). From 73829dd236aff5771b8e8b1a6a4accdc563cc5a9 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 5 Dec 2024 13:56:39 +0000 Subject: [PATCH 08/26] Update configure-auto-exposures.md --- .../cloud-integrations/configure-auto-exposures.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index f9033d98444..833631ebdea 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -63,11 +63,12 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve - :::info - dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). - - To manually trigger a sync and update collections (including additions or deletions), go to **Collections**, click **Edit**, make your selections or deselections, and then click **Save**. - ::: + #### Sync collections + :::info + dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). + + To manually trigger a sync and update collections (including additions or deletions), go to **Collections**, click **Edit**, make your selections or deselections, and then click **Save**. + ::: 6. Click **Save**. From 1f0bd5040c333a87288b820906cfd084b9b5862e Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 5 Dec 2024 14:01:16 +0000 Subject: [PATCH 09/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md --- .../docs/docs/cloud-integrations/configure-auto-exposures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index 833631ebdea..b0f6d8a2f54 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -67,7 +67,7 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve :::info dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). - To manually trigger a sync and update collections (including additions or deletions), go to **Collections**, click **Edit**, make your selections or deselections, and then click **Save**. + To manually trigger a sync and update collections (including additions or deletions), go to **Collections**, click **Edit**, make your checkbox selections or deselections, and then click **Save**. You should see the updates in Explorer. ::: 6. Click **Save**. From a8a9c1170f3ed5292fe08601d73bc61ee1ac82cb Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Dec 2024 10:04:18 +0000 Subject: [PATCH 10/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md Co-authored-by: Joel Labes --- .../docs/docs/cloud-integrations/configure-auto-exposures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index b0f6d8a2f54..be375d9f76d 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -67,7 +67,7 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve :::info dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). - To manually trigger a sync and update collections (including additions or deletions), go to **Collections**, click **Edit**, make your checkbox selections or deselections, and then click **Save**. You should see the updates in Explorer. + A sync will also begin immediately when the list of selected collections is modified, to capture any newly-selected workbooks and remove those which are no longer relevant. ::: 6. Click **Save**. From ae71d185cf18da4b0805dfe6a25ec6633bb3f217 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Dec 2024 10:04:57 +0000 Subject: [PATCH 11/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md --- website/docs/docs/cloud-integrations/configure-auto-exposures.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index be375d9f76d..c157e3b140a 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -63,7 +63,6 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve - #### Sync collections :::info dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). From 1a341d0f3e232a9d1a0a834a84dbf71e781b966e Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Fri, 6 Dec 2024 11:36:45 +0000 Subject: [PATCH 12/26] multiple emails not supported --- website/docs/docs/deploy/model-notifications.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/docs/docs/deploy/model-notifications.md b/website/docs/docs/deploy/model-notifications.md index 9f96237d995..8b290130d1b 100644 --- a/website/docs/docs/deploy/model-notifications.md +++ b/website/docs/docs/deploy/model-notifications.md @@ -22,10 +22,11 @@ Create configuration YAML files in your project for dbt to send notifications ab - Your dbt Cloud administrator has [enabled the appropriate account setting](#enable-access-to-model-notifications) for you. - Your environment(s) must be on a [release track](/docs/dbt-versions/cloud-release-tracks) instead of a legacy dbt Core version. - ## Configure groups -Define your groups in any .yml file in your [models directory](/reference/project-configs/model-paths). For example: +Define your groups in any `.yml` file in your [models directory](/reference/project-configs/model-paths). Each group must have a single email address specified — multiple email fields or lists aren't supported. + +The following example shows how to define groups in a `groups.yml` file. @@ -108,6 +109,6 @@ Provide dbt Cloud account members the ability to configure and receive alerts ab To use model-level notifications, your dbt Cloud account must have access to the feature. Ask your dbt Cloud administrator to enable this feature for account members by following these steps: 1. Navigate to **Notification settings** from your profile name in the sidebar (lower left-hand side). -1. From **Email notications**, enable the setting **Enable group/owner notifications on models** under the **Model notifications** section. Then, specify which statuses to receive notifications about (Success, Warning, and/or Fails). +1. From **Email notifications**, enable the setting **Enable group/owner notifications on models** under the **Model notifications** section. Then, specify which statuses to receive notifications about (Success, Warning, and/or Fails). From 44dbdb9a36fb789ee03e1078c4c92bef66cf3752 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Dec 2024 17:42:34 +0000 Subject: [PATCH 13/26] Update model-notifications.md rephrase and clarify per Rakesh's feedback --- website/docs/docs/deploy/model-notifications.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/docs/deploy/model-notifications.md b/website/docs/docs/deploy/model-notifications.md index 8b290130d1b..e07722dd029 100644 --- a/website/docs/docs/deploy/model-notifications.md +++ b/website/docs/docs/deploy/model-notifications.md @@ -12,9 +12,9 @@ With model-level notifications, model owners can be the first ones to know about To be timely and keep the number of notifications to a reasonable amount when multiple models or tests trigger them, dbt observes the following guidelines when notifying the owners: -- Send a notification to each unique owner/email during a job run about any models (with status of failure/success) or tests (with status of warning/failure/success). Each owner receives only one notification, the initial one. -- Don't send any notifications about subsequent models or tests while a dbt job is still running. -- At the end of a job run, each owner receives a notification, for each of the statuses they specified to be notified about, with a list of models and tests that have that status. +- Each owner/user who subscribes to notifications for one or more statuses (like failure, success, warning) will receive only _one_ email notification at the end of the job run. +- The email includes a consolidated list of all models or tests that match the statuses the user subscribed to, instead of sending separate emails for each status. +- Notifications about subsequent models or tests aren't sent while a dbt job is still running. Users are only notified once the job has fully completed. Create configuration YAML files in your project for dbt to send notifications about the status of your models and tests. From 429d182f51fec46c472174dc438063dae1f9d244 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Dec 2024 17:54:00 +0000 Subject: [PATCH 14/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md --- .../docs/docs/cloud-integrations/configure-auto-exposures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index c157e3b140a..84493dd811d 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -66,7 +66,7 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve :::info dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). - A sync will also begin immediately when the list of selected collections is modified, to capture any newly-selected workbooks and remove those which are no longer relevant. + dbt Cloud immediately starts a sync when you update the selected collections list, capturing new workbooks and removing irrelevant ones. ::: 6. Click **Save**. From ae3a774e112a183fa78c651ca06b28fc5a09fa4a Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Fri, 6 Dec 2024 18:03:16 +0000 Subject: [PATCH 15/26] add fields --- website/docs/docs/build/conversion-metrics.md | 5 ++++- website/docs/docs/build/simple.md | 8 +++++++- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/build/conversion-metrics.md b/website/docs/docs/build/conversion-metrics.md index 97809a13a76..2d227f4a703 100644 --- a/website/docs/docs/build/conversion-metrics.md +++ b/website/docs/docs/build/conversion-metrics.md @@ -34,6 +34,7 @@ Note that we use the double colon (::) to indicate whether a parameter is nested | `base_measure:name` | The base conversion event measure. | Required | String | | `base_measure:fill_nulls_with` | Set the value in your metric definition instead of null (such as zero). | Optional | String | | `base_measure:join_to_timespine` | Boolean that indicates if the aggregated measure should be joined to the time spine table to fill in missing dates. Default `false`. | Optional | Boolean | +| `base_measure:filter` | Optional `filter` used to apply to the base measure. | Optional | String | | `conversion_measure` | A list of conversion measure inputs. | Required | Dict | | `conversion_measure:name` | The base conversion event measure.| Required | String | | `conversion_measure:fill_nulls_with` | Set the value in your metric definition instead of null (such as zero). | Optional | String | @@ -61,6 +62,7 @@ metrics: name: The name of the measure # Required fill_nulls_with: Set the value in your metric definition instead of null (such as zero) # Optional join_to_timespine: true/false # Boolean that indicates if the aggregated measure should be joined to the time spine table to fill in missing dates. Default `false`. # Optional + filter: The filter used to apply to the base measure. # Optional conversion_measure: name: The name of the measure # Required fill_nulls_with: Set the value in your metric definition instead of null (such as zero) # Optional @@ -105,12 +107,13 @@ Next, define a conversion metric as follows: - name: visit_to_buy_conversion_rate_7d description: "Conversion rate from visiting to transaction in 7 days" type: conversion - label: Visit to Buy Conversion Rate (7-day window) + label: Visit to buy conversion rate (7-day window) type_params: conversion_type_params: base_measure: name: visits fill_nulls_with: 0 + filter: {{ Dimension('visits__referrer_id') }} = 'facebook' conversion_measure: name: sellers entity: user diff --git a/website/docs/docs/build/simple.md b/website/docs/docs/build/simple.md index 872a4d34fa8..d84ab7735fc 100644 --- a/website/docs/docs/build/simple.md +++ b/website/docs/docs/build/simple.md @@ -24,6 +24,8 @@ Note that we use the double colon (::) to indicate whether a parameter is nested | `type_params` | The type parameters of the metric. | Required | Dict | | `measure` | A list of measure inputs. | Required | List | | `measure:name` | The measure you're referencing. | Required | String | +| `measure:alias` | Optional [`alias`](/reference/resource-configs/alias) used to rename the measure. | Optional | String | +| `measure:filter` | Optional `filter` used to apply to the measure. | Optional | String | | `measure:fill_nulls_with` | Set the value in your metric definition instead of null (such as zero). | Optional | String | | `measure:join_to_timespine` | Indicates if the aggregated measure should be joined to the time spine table to fill in missing dates. Default `false`. | Optional | Boolean | @@ -38,6 +40,8 @@ metrics: type_params: # Required measure: name: The name of your measure # Required + alias: The alias used to rename the measure. # Optional + filter: The filter used to apply to the measure. # Optional fill_nulls_with: Set value instead of null (such as zero) # Optional join_to_timespine: true/false # Boolean that indicates if the aggregated measure should be joined to the time spine table to fill in missing dates. # Optional @@ -65,9 +69,11 @@ If you've already defined the measure using the `create_metric: true` parameter, name: customers # The measure you are creating a proxy of. fill_nulls_with: 0 join_to_timespine: true + alias: customer_count + filter: {{ Dimension('customer__customer_total') }} >+ 20 - name: large_orders description: "Order with order values over 20." - type: SIMPLE + type: simple label: Large orders type_params: measure: From 4520091f9460d36b1144f39b9f6ed120f856bd33 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Dec 2024 18:08:16 +0000 Subject: [PATCH 16/26] Update website/docs/docs/build/simple.md --- website/docs/docs/build/simple.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/build/simple.md b/website/docs/docs/build/simple.md index d84ab7735fc..b2a65d2668e 100644 --- a/website/docs/docs/build/simple.md +++ b/website/docs/docs/build/simple.md @@ -70,7 +70,7 @@ If you've already defined the measure using the `create_metric: true` parameter, fill_nulls_with: 0 join_to_timespine: true alias: customer_count - filter: {{ Dimension('customer__customer_total') }} >+ 20 + filter: {{ Dimension('customer__customer_total') }} >= 20 - name: large_orders description: "Order with order values over 20." type: simple From 91b7ab669fa801cf6af27d432917449a0e8f220b Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Dec 2024 18:23:14 +0000 Subject: [PATCH 17/26] Update model-notifications.md --- website/docs/docs/deploy/model-notifications.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/model-notifications.md b/website/docs/docs/deploy/model-notifications.md index e07722dd029..9eb9751be3f 100644 --- a/website/docs/docs/deploy/model-notifications.md +++ b/website/docs/docs/deploy/model-notifications.md @@ -12,9 +12,10 @@ With model-level notifications, model owners can be the first ones to know about To be timely and keep the number of notifications to a reasonable amount when multiple models or tests trigger them, dbt observes the following guidelines when notifying the owners: +- Send a notification to each unique owner/email during a job run about any models (with status of failure/success) or tests (with status of warning/failure/success). Each owner receives only one notification, the initial one. +- Don't send any notifications about subsequent models or tests while a dbt job is still running. - Each owner/user who subscribes to notifications for one or more statuses (like failure, success, warning) will receive only _one_ email notification at the end of the job run. - The email includes a consolidated list of all models or tests that match the statuses the user subscribed to, instead of sending separate emails for each status. -- Notifications about subsequent models or tests aren't sent while a dbt job is still running. Users are only notified once the job has fully completed. Create configuration YAML files in your project for dbt to send notifications about the status of your models and tests. From 5a9202355d5c31e07445174b17942a53136d9bef Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Dec 2024 18:48:35 +0000 Subject: [PATCH 18/26] Update simple.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/build/simple.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/build/simple.md b/website/docs/docs/build/simple.md index b2a65d2668e..31475e5b01e 100644 --- a/website/docs/docs/build/simple.md +++ b/website/docs/docs/build/simple.md @@ -40,7 +40,7 @@ metrics: type_params: # Required measure: name: The name of your measure # Required - alias: The alias used to rename the measure. # Optional + alias: The alias applied to the measure. # Optional filter: The filter used to apply to the measure. # Optional fill_nulls_with: Set value instead of null (such as zero) # Optional join_to_timespine: true/false # Boolean that indicates if the aggregated measure should be joined to the time spine table to fill in missing dates. # Optional From 0243800ae5bf3a615b5c835cc12d462eeb99821f Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Dec 2024 18:48:47 +0000 Subject: [PATCH 19/26] Update simple.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/build/simple.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/build/simple.md b/website/docs/docs/build/simple.md index 31475e5b01e..5e485353282 100644 --- a/website/docs/docs/build/simple.md +++ b/website/docs/docs/build/simple.md @@ -41,7 +41,7 @@ metrics: measure: name: The name of your measure # Required alias: The alias applied to the measure. # Optional - filter: The filter used to apply to the measure. # Optional + filter: The filter applied to the measure. # Optional fill_nulls_with: Set value instead of null (such as zero) # Optional join_to_timespine: true/false # Boolean that indicates if the aggregated measure should be joined to the time spine table to fill in missing dates. # Optional From 46a907a0b4503210bd9b46e1fd1b067c238f643a Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 9 Dec 2024 09:55:48 +0000 Subject: [PATCH 20/26] Update website/docs/docs/build/simple.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/build/simple.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/build/simple.md b/website/docs/docs/build/simple.md index 5e485353282..9b20a952ae6 100644 --- a/website/docs/docs/build/simple.md +++ b/website/docs/docs/build/simple.md @@ -24,7 +24,7 @@ Note that we use the double colon (::) to indicate whether a parameter is nested | `type_params` | The type parameters of the metric. | Required | Dict | | `measure` | A list of measure inputs. | Required | List | | `measure:name` | The measure you're referencing. | Required | String | -| `measure:alias` | Optional [`alias`](/reference/resource-configs/alias) used to rename the measure. | Optional | String | +| `measure:alias` | Optional [`alias`](/reference/resource-configs/alias) to rename the measure. | Optional | String | | `measure:filter` | Optional `filter` used to apply to the measure. | Optional | String | | `measure:fill_nulls_with` | Set the value in your metric definition instead of null (such as zero). | Optional | String | | `measure:join_to_timespine` | Indicates if the aggregated measure should be joined to the time spine table to fill in missing dates. Default `false`. | Optional | Boolean | From 8f6cd6a265a94d4419cb707afc344e1ca5a00cde Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 9 Dec 2024 09:55:55 +0000 Subject: [PATCH 21/26] Update website/docs/docs/build/simple.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/docs/docs/build/simple.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/build/simple.md b/website/docs/docs/build/simple.md index 9b20a952ae6..2deb718d780 100644 --- a/website/docs/docs/build/simple.md +++ b/website/docs/docs/build/simple.md @@ -25,7 +25,7 @@ Note that we use the double colon (::) to indicate whether a parameter is nested | `measure` | A list of measure inputs. | Required | List | | `measure:name` | The measure you're referencing. | Required | String | | `measure:alias` | Optional [`alias`](/reference/resource-configs/alias) to rename the measure. | Optional | String | -| `measure:filter` | Optional `filter` used to apply to the measure. | Optional | String | +| `measure:filter` | Optional `filter` applied to the measure. | Optional | String | | `measure:fill_nulls_with` | Set the value in your metric definition instead of null (such as zero). | Optional | String | | `measure:join_to_timespine` | Indicates if the aggregated measure should be joined to the time spine table to fill in missing dates. Default `false`. | Optional | Boolean | From 480d203f5e4f281254c13eeb1c9634d08a923ac6 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 9 Dec 2024 09:56:21 +0000 Subject: [PATCH 22/26] Update website/docs/docs/cloud-integrations/configure-auto-exposures.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- .../docs/docs/cloud-integrations/configure-auto-exposures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index 84493dd811d..dd9afcb4ade 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -64,7 +64,7 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve :::info - dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next automatic sync (usually once per day). + dbt Cloud automatically imports and syncs any workbook within the selected collections. New additions to the collections will be added to the lineage in dbt Cloud during the next sync (automatically once per day). dbt Cloud immediately starts a sync when you update the selected collections list, capturing new workbooks and removing irrelevant ones. ::: From 9f4330ec823480ac5e99dff0fd29f60ae35e661b Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 9 Dec 2024 10:01:45 +0000 Subject: [PATCH 23/26] Update configure-auto-exposures.md --- .../docs/docs/cloud-integrations/configure-auto-exposures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud-integrations/configure-auto-exposures.md b/website/docs/docs/cloud-integrations/configure-auto-exposures.md index dd9afcb4ade..2bb09573221 100644 --- a/website/docs/docs/cloud-integrations/configure-auto-exposures.md +++ b/website/docs/docs/cloud-integrations/configure-auto-exposures.md @@ -69,7 +69,7 @@ To set up [personal access tokens (PATs)](https://help.tableau.com/current/serve dbt Cloud immediately starts a sync when you update the selected collections list, capturing new workbooks and removing irrelevant ones. ::: -6. Click **Save**. +5. Click **Save**. dbt Cloud imports everything in the collection(s) and you can continue to view them in Explorer. For more information on how to view and use auto-exposures, refer to [View auto-exposures from dbt Explorer](/docs/collaborate/auto-exposures) page. From edb54bc828f718afc26623973ad441775c9a67c9 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Mon, 9 Dec 2024 16:33:06 -0500 Subject: [PATCH 24/26] GA v1.9 in docs (#6626) ## What are you changing in this pull request and why? Updates docs for v1.9 GA ## Checklist - [ ] I have reviewed the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [ ] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and/or [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content) guidelines. - [ ] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch." - [ ] The content in this PR requires a dbt release note, so I added one to the [release notes page](https://docs.getdbt.com/docs/dbt-versions/dbt-cloud-release-notes). --- website/dbt-versions.js | 1 + website/snippets/core-versions-table.md | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/website/dbt-versions.js b/website/dbt-versions.js index 13ce565d354..3e59b926b80 100644 --- a/website/dbt-versions.js +++ b/website/dbt-versions.js @@ -20,6 +20,7 @@ exports.versions = [ }, { version: "1.9", + EOLDate: "2025-12-08", }, { version: "1.8", diff --git a/website/snippets/core-versions-table.md b/website/snippets/core-versions-table.md index 899c3dddc28..0d82ab35573 100644 --- a/website/snippets/core-versions-table.md +++ b/website/snippets/core-versions-table.md @@ -2,8 +2,8 @@ | dbt Core | Initial release | Support level and end date | |:-------------------------------------------------------------:|:---------------:|:-------------------------------------:| -| [**v1.9**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.9) | Release candidate | TBA | -| [**v1.8**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.8) | May 9 2024 | Active Support — May 8, 2025| +| [**v1.9**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.9) | Dec 9, 2024 | Active Support — Dec 8, 2025| +| [**v1.8**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.8) | May 9, 2024 | Active Support — May 8, 2025| | [**v1.7**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.7) | Nov 2, 2023 |
**dbt Core and dbt Cloud Developer & Team customers:** End of Life
**dbt Cloud Enterprise customers:** Critical Support until further notice 1
| | [**v1.6**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.6) | Jul 31, 2023 | End of Life ⚠️ | | [**v1.5**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.5) | Apr 27, 2023 | End of Life ⚠️ | From e7c0fed37043d16272003bee939e82600c095be5 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Mon, 9 Dec 2024 19:56:53 -0500 Subject: [PATCH 25/26] Fixing syntax (#6627) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## What are you changing in this pull request and why? Closes https://github.com/dbt-labs/docs.getdbt.com/issues/5394 ## Checklist - [ ] I have reviewed the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [ ] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and/or [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content) guidelines. - [ ] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch." - [ ] The content in this PR requires a dbt release note, so I added one to the [release notes page](https://docs.getdbt.com/docs/dbt-versions/dbt-cloud-release-notes). --- 🚀 Deployment available! Here are the direct links to the updated files: - https://docs-getdbt-com-git-indirect-dbt-labs.vercel.app/reference/global-configs/indirect-selection --- website/docs/reference/global-configs/indirect-selection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/global-configs/indirect-selection.md b/website/docs/reference/global-configs/indirect-selection.md index 729176a1ff4..03048b57119 100644 --- a/website/docs/reference/global-configs/indirect-selection.md +++ b/website/docs/reference/global-configs/indirect-selection.md @@ -6,7 +6,7 @@ sidebar: "Indirect selection" import IndirSelect from '/snippets/_indirect-selection-definitions.md'; -Use the `--indirect_selection` flag to `dbt test` or `dbt build` to configure which tests to run for the nodes you specify. You can set this as a CLI flag or an environment variable. In dbt Core, you can also configure user configurations in [YAML selectors](/reference/node-selection/yaml-selectors) or in the `flags:` block of `dbt_project.yml`, which sets project-level flags. +Use the `--indirect-selection` flag to `dbt test` or `dbt build` to configure which tests to run for the nodes you specify. You can set this as a CLI flag or an environment variable. In dbt Core, you can also configure user configurations in [YAML selectors](/reference/node-selection/yaml-selectors) or in the `flags:` block of `dbt_project.yml`, which sets project-level flags. When all flags are set, the order of precedence is as follows. Refer to [About global configs](/reference/global-configs/about-global-configs) for more details: From e8e71fc182b3fe5171c5c95167f236741d0bb476 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 10 Dec 2024 09:24:55 +0000 Subject: [PATCH 26/26] Update model-notifications.md --- website/docs/docs/deploy/model-notifications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/model-notifications.md b/website/docs/docs/deploy/model-notifications.md index 9eb9751be3f..24bbc2295c6 100644 --- a/website/docs/docs/deploy/model-notifications.md +++ b/website/docs/docs/deploy/model-notifications.md @@ -13,7 +13,7 @@ With model-level notifications, model owners can be the first ones to know about To be timely and keep the number of notifications to a reasonable amount when multiple models or tests trigger them, dbt observes the following guidelines when notifying the owners: - Send a notification to each unique owner/email during a job run about any models (with status of failure/success) or tests (with status of warning/failure/success). Each owner receives only one notification, the initial one. -- Don't send any notifications about subsequent models or tests while a dbt job is still running. +- No notifications sent about subsequent models or tests while a dbt job is still running. - Each owner/user who subscribes to notifications for one or more statuses (like failure, success, warning) will receive only _one_ email notification at the end of the job run. - The email includes a consolidated list of all models or tests that match the statuses the user subscribed to, instead of sending separate emails for each status.