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.

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

[docs] add note about alert behavior with RetryPolicy #26794

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
7 changes: 6 additions & 1 deletion docs/content/dagster-plus/managing-deployments/alerts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,12 @@ Alert policies are configured on a **per-deployment basis**. This means, for exa
Triggers on:
<ul>
<li>
<strong>Asset materializations</strong> - Failure or success
<strong>Asset materializations</strong> - Failure or success.{" "}
<strong>Note:</strong> if using a{" "}
<a href="/concepts/assets/software-defined-assets#retrying-failed-assets">
RetryPolicy
</a>
, an alert will only be sent after all retries complete.
</li>
<li>
<a href="/concepts/assets/asset-checks">
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,13 @@ If desired, add **tags** in the format `{key}:{value}` to filter the runs that w
You can set up alerts to notify you when an asset materialization attempt fails.

By default, these alerts will target all assets in the deployment, but they can be scoped to a specific asset or group of assets.

:::note

If using a RetryPolicy, an alert will only be sent after all retries complete.

:::

<Tabs groupId="ui_or_cli">
<TabItem value='ui' label='In the UI'>
1. In the Dagster UI, click **Deployment**.
Expand Down
Loading