Can anyone share a pattern they use for including stack traces in failure hooks? I currently use a

failure_hook

on all my pipelines that looks like this:

@failure_hook(required_resource_keys={"slack"})
def slack_message_on_failure(context: HookContext):
    message = f"*ALERT*: Dagster failed while running pipeline `{context.pipeline.pipeline_name}` at solid `{context.solid.name}`.\nCheck out the logs at <https://dagster.ioby.network/instance/runs/{context.run_id}>"
    context.resources.slack.chat_postMessage(channel="product-alerts", text=message, icon_emoji=':scream_cat:', username='Uh-oh Cat')

Hi @Brian Abelson we internally are using the similar pattern as you do here, i.e. linking to the logs in Dagit. As mentioned in #3576, the system-provided

slack_on_failure

and

slack_on_success

takes

dagit_base_url

, the underlying logic of which is exactly the pattern you are using. see details in source code

thank you so much! this is great context @yuhan. i'll follow along on the issue