-
Notifications
You must be signed in to change notification settings - Fork 670
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
[Feature] [UI] Execution Details should show System Metadata, to ease debugging #371
Closed
1 of 13 tasks
Comments
kumare3
added
enhancement
New feature or request
ui
Admin console user interface
untriaged
This issues has not yet been looked at by the Maintainers
labels
Jun 28, 2020
schottra
removed
the
untriaged
This issues has not yet been looked at by the Maintainers
label
Jul 1, 2020
This is implemented by flyteorg/flyteconsole#78 |
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 6, 2022
Signed-off-by: Babis Kiosidis <[email protected]> Co-authored-by: Babis Kiosidis <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 6, 2022
* Make default RawOutputDataConfig overridable Signed-off-by: Kevin Su <[email protected]> * Fixed tests Signed-off-by: Kevin Su <[email protected]> * update single task execution Signed-off-by: Kevin Su <[email protected]> * Updated tests Signed-off-by: Kevin Su <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
Signed-off-by: Kevin Su <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
…g#371) Signed-off-by: Eugene Jahn <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
## [0.51.1](http://github.com/lyft/flyteconsole/compare/v0.51.0...v0.51.1) (2022-04-12) ### Bug Fixes * dimensionality per data type blob and be disabled in UI ([flyteorg#371](http://github.com/lyft/flyteconsole/issues/371)) ([dc38ae3](http://github.com/lyft/flyteconsole/commit/dc38ae39ceecce24f9a65f4c02f364d8ab05728d))
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 9, 2023
Signed-off-by: Babis Kiosidis <[email protected]> Co-authored-by: Babis Kiosidis <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 21, 2023
* Make default RawOutputDataConfig overridable Signed-off-by: Kevin Su <[email protected]> * Fixed tests Signed-off-by: Kevin Su <[email protected]> * update single task execution Signed-off-by: Kevin Su <[email protected]> * Updated tests Signed-off-by: Kevin Su <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation: Why do you think this is important?
With multi-cluster support, Flyte schedules many workflows across multiple different clusters. When a user has a problem with a workflow (bug, or errors) the first step for the on-call is to find the cluster where the Workflow ended up. This needs access to the database and querying the execution table.
It would be preferable to show the System Execution metadata on the Details page. This is available in the FlyteAdmin API's already https://github.com/lyft/flyteidl/blob/master/protos/flyteidl/admin/execution.proto#L150
Goal: What should the final outcome look like, ideally?
The console should show the cluster information (an in the future other system metadata) on the Details page.
Describe alternatives you've considered
CLI, but this needs setup and re-write information in the CLI. Users usually share UI links.
Flyte component
Additional context
NA
Is this a blocker for you to adopt Flyte
NA
The text was updated successfully, but these errors were encountered: