New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archived Workflow Search and Views #2321
Labels
type/feature
Feature request
Milestone
Comments
I think we should probably treat this as an EPIC and break it up into about 5 smaller items. |
alexec
changed the title
Workflow History Search and Views
Epic: Workflow History Search and Views
Feb 28, 2020
Note that it would also be useful to be able to find/filter by label. |
This should be via the UI. |
Just for archived workflows. |
alexec
changed the title
Epic: Workflow History Search and Views
Archived Workflow Search and Views
Mar 12, 2020
This was referenced Mar 13, 2020
Broken up into smaller issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Have the ability to search in the workflow history, for specific queries such as:
Motivation
ML workflows for training, batch inference etc. run on multiple triggers - timed (schedule) trigger, event trigger (arrival of a file, completion of another workflow, etc.). These workflows run 24x7, in an unattended manner.
Teams have a need to look back at the history of workflow runs for various reasons, such as:
Proposal
There should be a location in the Argo UI for previous workflow executions. This page should allow for various search capabilities within the list of prior workflows.
Clicking into a particular workflow should show a read-only view of the workflow with all the details that would normally be visible if the workflow was currently in progress. From here, a user can either clone the workflow, re-run the same workflow etc.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: