Ownership & accountability · rule dagster-asset-unowned
Dagster assets with no owner
A Metacenta review checks this under the rule Dagster assets name an owner. Everything below applies whether or not you ever commission one.
What this rule checks
This rule flags Dagster assets that declare no owners. When more than half the assets have none, we report it once for the project rather than once per asset.
Why it matters
When the asset fails, Dagster has nobody to route the alert to, and nobody is accountable for its data. The failure waits for whoever looks next.
How to fix it
Name an owner for every Dagster asset. Set owners=["team:…"] on the asset, or on its group so every asset in it inherits.
Before:
@asset(group_name="finance")
def orders(raw_orders):
...
After:
@asset(group_name="finance", owners=["team:finance-data"])
def orders(raw_orders):
...
When it is fine to leave
A project that routes Dagster alerts some other way, such as by code location or a sensor that pages one team, is covered in practice. Tell us, and the finding comes out of your report.
What we need to check it
The Dagster Python files you supply. We read only what they declare (assets, checks, owners), so the finding is medium confidence.