KG
09/22/2024, 9:02 PMMarvin
09/22/2024, 9:02 PM"match": {
"prefect.resource.id": "prefect.flow-run.*",
"prefect.resource.name": ["cute-*", "radical-*"]
},
"match_related": {}
Source
2. Prefect 3.x: Use event triggers to filter flow run events by name. This can be set up by defining custom triggers in your automation settings.
Example from docs:
"match": {
"prefect.resource.id": "prefect.flow-run.*",
"prefect.resource.name": ["cute-*", "radical-*"]
},
"match_related": {}
Source
To perform searches or set up these filters effectively, refer to the respective documentation links provided for detailed steps and additional configurations.Marvin
09/22/2024, 9:02 PM"match": {
"prefect.resource.id": "prefect.flow-run.*",
"prefect.resource.name": ["ochre-skua"]
},
"match_related": {}
This type of configuration can be part of an automation setup in Prefect Cloud.
For programmatic access, consider querying the Prefect API directly for more flexibility. Prefect provides a GraphQL API, and you might write a query to retrieve specific flow runs by their name.
For further assistance, it’s best to refer to the Prefect Cloud documentation or reach out to the Prefect community for specific implementation examples.
Helpful links:
- Prefect 2.x Docs
- Prefect 3.x DocsKG
09/22/2024, 9:02 PMKG
09/23/2024, 4:11 PM