What's the use case?
Dagster+ alert policies (we use Slack) currently render a fixed message template with no way to control which fields are shown or how they're prioritized. The only content-related option exposed today is policy_options.include_description_in_notification. For teams routing alerts to shared channels (e.g. #dagster-alerts), this creates two recurring problems:
- The asset/job name isn't visually prominent in the message — it's harder that it should be to see which asset failed when scanning the alert channel channel, especially when several alerts land close together.
- Failure notifications always include the full stack trace inline. This makes messages long and noisy in Slack, duplicates information already available in the Dagster+ UI (which is one click away via the run link), and makes it harder to scan multiple alerts at a glance.
Being able to control message composition would let teams tune alerts for readability in the channels/tools they actually use, without having to abandon native alert policies in favor of hand-rolled sensors just to control formatting.
Ideas of implementation
Extend policy_options with additional toggles, e.g. include_stack_trace_in_notification and similar per-field flags for other verbose sections.
Alternatively, support a configurable message template (e.g. a Jinja-style string or ordered list of fields) per alert policy, so teams can choose which fields appear and in what order — similar to how some other Dagster+ features (e.g. asset descriptions) already support Markdown.
Additional information
I'd love for asset alert messages to always include the asset name as the lead line / bolded header of the message, regardless of other content.
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
What's the use case?
Dagster+ alert policies (we use Slack) currently render a fixed message template with no way to control which fields are shown or how they're prioritized. The only content-related option exposed today is policy_options.include_description_in_notification. For teams routing alerts to shared channels (e.g. #dagster-alerts), this creates two recurring problems:
Being able to control message composition would let teams tune alerts for readability in the channels/tools they actually use, without having to abandon native alert policies in favor of hand-rolled sensors just to control formatting.
Ideas of implementation
Extend
policy_optionswith additional toggles, e.g.include_stack_trace_in_notificationand similar per-field flags for other verbose sections.Alternatively, support a configurable message template (e.g. a Jinja-style string or ordered list of fields) per alert policy, so teams can choose which fields appear and in what order — similar to how some other Dagster+ features (e.g. asset descriptions) already support Markdown.
Additional information
I'd love for asset alert messages to always include the asset name as the lead line / bolded header of the message, regardless of other content.
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.