add another breakdown of running jobs, by current-step

[srulkapara]

Summary

Adding another column for "current step" of each run, and also allows filters - just like the status of Running/Failed/Completed (only with more options) will be very useful.

Once you submit dozens of jobs which will be running for hours, it is very nice to see where they currently stand (that we've passed something that was recently fixed, for instance), and make sure that the pace makes sense and we can estimate how long it will take.

An alternative solution will be a different page entirely, grouping the current steps of running-jobs only showing some kind of graph. I'll take that as well.

Alternatives: None, except for manually querying s3 relevant paths - or opening lots of tabs.
I don't think the aws-UI also has a per-step StepFunctions dashboard either.

The complication i can think of is having lots of steps (but this can be fixed using UI), or higher refresh-rate needed since steps can change more quickly than other fields.

[savingoyal]

That's a great idea. Today, if you want a bird's eye view of any run's state, you can click on a lever button towards the very right of the row you are on which pops open the timeline view.

[obgibson]

Are you thinking of something like this on the Run page?

[obgibson]

and/or this?

[obgibson]

@srulkapara

[srulkapara]

Yes, exactly @obgibson.
Something to consider: should this new current-step filter only be relevant while using specific-flows (so only if the flow-filter is activated it can be applicable?) - or maybe have some kind of super-set options out of the entire possible flows?
Or should the relevant step-values there be Flow1.step1, Flow1.step2?

[obgibson]

What would your use case be for the filter on the home page? If you, as a user, are going to the effort to filter on flows, and then on current step, you may find it easier to just look at the Current Step column. The column will be orderable so you can make the runs with current steps float to the top.

Do we need a filter?

[srulkapara]

My case is a surge of hundreds of jobs submitted where i don't want to click on each, to get a big-picture status, but i want some counts and a quick validation that things are going smooth - so using the step-filter (and count through browser-Search, for instance, as a job-count trick) is useful.

Note: for this purpose (counting runs in each step) i don't need the filter, i can also browser-search the name of the step, so i guess it's not a must.