-
Notifications
You must be signed in to change notification settings - Fork 975
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
38 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -33,7 +33,9 @@ Create configuration YAML files in your project for dbt to send notifications ab | |
|
||
## Configure groups | ||
|
||
Add your group configuration in either the `dbt_project.yml` or `groups.yml` file. For example: | ||
Define your groups in any .yml file in your [models directory](/reference/project-configs/model-paths). For example: | ||
|
||
<File name='models/groups.yml'> | ||
|
||
```yml | ||
version: 2 | ||
|
@@ -42,22 +44,26 @@ groups: | |
- name: finance | ||
description: "Models related to the finance department" | ||
owner: | ||
# 'name' or 'email' is required | ||
# Email is required to receive model-level notifications, additional properties are also allowed. | ||
name: "Finance Team" | ||
email: [email protected] | ||
slack: finance-data | ||
favorite_food: donuts | ||
|
||
- name: marketing | ||
description: "Models related to the marketing department" | ||
owner: | ||
name: "Marketing Team" | ||
email: [email protected] | ||
slack: marketing-data | ||
favorite_food: jaffles | ||
``` | ||
## Set up models | ||
</File> | ||
## Attach groups to models | ||
Attach groups to models as you would any other config, in either the `dbt_project.yml` or `<whatever>.yml` files. For example: | ||
|
||
Set up your model configuration in either the `dbt_project.yml` or `groups.yml` file; doing this automatically sets up notifications for tests, too. For example: | ||
<File name='models/marts.yml'> | ||
|
||
```yml | ||
version: 2 | ||
|
@@ -74,6 +80,32 @@ models: | |
group: marketing | ||
``` | ||
</File> | ||
|
||
By assigning groups in the `dbt_project.yml` file, you can capture all models in a subdirectory at once. In the below example, all notifications related to staging models will go to the data engineering group, whereas models in `marts/sales` will be routed to the finance team. | ||
|
||
<File name='dbt_project.yml'> | ||
|
||
```yml | ||
config-version: 2 | ||
name: "jaffle_shop" | ||
[...] | ||
models: | ||
jaffle_shop: | ||
staging: | ||
+group: data_engineering | ||
marts: | ||
sales: | ||
+group: finance | ||
campaigns: | ||
+group: marketing | ||
``` | ||
|
||
</File> | ||
Attaching a group to a model also encompasses its tests, so you will also receive notifications for a model's test failures. | ||
|
||
## Enable access to model notifications | ||
|
||
|