Dagster integration
Connect Dagster to service workflows so data teams can check runs, rerun jobs, and manage access by request.
What it connects
- Pull run history and status to explain failed or slow jobs in a ticket.
- Retrieve jobs, schedules, and sensors to identify what a request refers to.
- Pull asset health and the asset catalog when someone reports stale data.
- Retrieve users and team membership to confirm who can act in a deployment.
What it automates
- Launch, re-execute, or terminate runs when a data engineer asks through a request.
- Start or stop schedules and sensors during maintenance or incident response.
- Invite users and update team membership as people join or change teams.
- Revoke user or agent tokens when access should end or a token is exposed.
In practice
- A data engineer asks in Slack to rerun a failed job. STLabs finds the run, re-executes it, and replies in the thread with the new status.
- A new analyst needs Dagster access. After manager approval, STLabs invites them and adds them to the right team so they can see their pipelines.
- During an upstream outage, the on-call engineer asks to pause a sensor. STLabs stops it and starts it again when the engineer requests.
- When someone leaves the data team, STLabs revokes their Dagster user tokens during offboarding, so those tokens can no longer reach your deployment.
