Matthew Seligson
01/26/2022, 7:03 PMKevin Kho
Matthew Seligson
01/26/2022, 7:12 PMKevin Kho
name
or slug
. We also have tags
if that helps.Kevin Kho
Matthew Seligson
01/26/2022, 7:32 PMAnna Geller
tags
for such use case - imo it’s probably the cleanest approach and it will work nicely in Orion. But even using the task name or slug can be used in your use case. It’s all a matter of combining data from multiple queries. For example, this is how you can get all the versions of a specific flow:
query {
flow(where: { name: { _ilike: "%dask%" } }) {
id
name
version
tasks {
name
id
slug
tags
}
}
}
you can replace the “dask” text with some part of your flow name. And then to get the task run history for that, you would need another query.
But note that storing logs and the history of your flow and task runs over such a long period of time (you want to analyze a period of potentially two years of run history?) would be difficult or at least expensive. For example, Prefect Cloud standard plan has a 2 weeks of log retention.Anna Geller