Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Further document custom slack channels #1145

Merged
merged 3 commits into from
Sep 10, 2023
Merged

Further document custom slack channels #1145

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1740631
further comment custom slack channels
JavierLopezT Sep 5, 2023
a7cf89e
Merge branch 'master' into custom-slack-channel-docs
Maayan-s Sep 7, 2023
d42b96e
Merge branch 'master' into custom-slack-channel-docs
Maayan-s Sep 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/guides/alerts-configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,7 +221,9 @@ This way you can ensure your alerts are valuable and avoid alert fatigue.
#### Custom channel

Elementary supports configuring custom Slack channels for models and tests.
By default, Elementary uses the Slack channel that was configured in the Slack integration.
By default, Elementary uses the Slack channel that was configured in the Slack integration. Even if
a custom channel is defined for every test, you must specify a default fallback channel, either using
the CLI or the `config.yml` file.

<CodeGroup>

Expand Down
6 changes: 5 additions & 1 deletion docs/quickstart/send-slack-alerts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,11 @@ Make sure to run the following command after your dbt runs and tests:
edr monitor --slack-token <your_slack_token> --slack-channel-name <slack_channel_to_post_at> --group-by [table | alert]
```

Or just `edr monitor` if you used `config.yml`.
Or just `edr monitor` if you used `config.yml`. Please note that when you specify the --slack-channel-name, it's the
default channel name to which all the alerts will be sent that are not attributed to any custom channel. Therefore,
if you execute several `edr monitor` commands at the same time with different `slack-channel-name` arguments, they can
be sent to the wrong one due to the overlap accessing the backend table of elementary. For avoiding this problem,
[the guide](/guides/alerts-configuration#custom-channel) can be followed.

---

Expand Down