search

dagster-io / dagster

An orchestration platform for the development, production, and observation of data assets.
https://dagster.io
Apache License 2.0
10.66k stars 1.32k forks source link

[Overview Page UI] Separate auto-materialize runs from Adhoc materializations #15423

Open dduong1603 opened 11 months ago

dduong1603 commented 11 months ago

What's the use case?

In the Activity Timeline view, all auto-materialize runs are currently grouped into Ad hoc materializations graph. It would be nice to separate these runs from the manual runs

https://dagster.slack.com/archives/C01U954MEER/p1689872292022849

Ideas of implementation

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a đź‘Ť! We factor engagement into prioritization.

dduong1603 commented 9 months ago

Hi, just want to get an update on this or if this needs additional info since it hasn't been tagged with UI/UX tag. thanks!

sryza commented 9 months ago

Hey @dduong1603 - not sure how this slipped through the cracks, but I added it to the UI/UX project so it will get triaged to the right folks.

somiandras commented 2 months ago

Having the same issue with the overview/activity/timeline screen. As we are relying more and more on declarative scheduling with auto-materializations, most of our workload is labelled as “ad hoc materializations” in this summary screen, but these are anything but ad hoc… Maybe there could be some breakdown of manual launches vs. auto-materializations (maybe even by cause/trigger, like cron, upstream, freshness, etc.)