The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hi all. I’m experimenting with using an asset sensor to trigger a cross-repository pipeline and I’m wondering how I can send alerts (ie, slack) if the sensor itself fails exceptionally. Any ideas how/where to look further?

I don’t believe we yet have any special hooks for this . For now you could start with attempting to handle it in the body of your sensor

I was afraid of that :slightly_smiling_face:

Thinking out loud, it might be good for sensors(/schedules?) to have access to logging (already :thumbsup:’d the open ticket), and, resources or config settings.
Maybe a `$DAGSTER_HOME/user_repository.yaml` to provide the `resource:` config for resources specified by a sensors(/schedule?) `required_resource_keys=` ...?