You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Waterfall visualization is actively used for displaying page visualization, build history (see screenshots), and many other use cases.
I propose implementing a similar visualization for the Nomad deploy page.
Use-cases
This would be very useful for deployment understanding and debugging:
Understanding why deployments take so long
Identifying which allocations or clients are the slowest
And more
Attempted Solutions
The alternative is to spend time tediously searching through the UI and logs :(
The text was updated successfully, but these errors were encountered:
Hey @valodzka, this is a cool idea. Point of clarification though, did you mean the job deployments page, or the deployment history on the main job page (which shows task events)?
The deployments page, showing previous deployments of the job
The deployments history, showing task events
If it's the latter, I think this is a great idea. There's also a previous attempt here from about a year ago, at time-based clustering events: #19904 that would serve as prior art.
From my point of view both options would work. Deployments page would be more usefull because it would be possible to analyze not only last deployment but previous too. But in mosts cases I interested about last deployment, so deployments history page would be ok too.
Got it. I think the deployments page is precarious because of garbage collection, so any waterfall there might only be a few items long and with disparate times between. Let me think about how I might apply this to the main job page, though!
Proposal
Waterfall visualization is actively used for displaying page visualization, build history (see screenshots), and many other use cases.
I propose implementing a similar visualization for the Nomad deploy page.
Use-cases
This would be very useful for deployment understanding and debugging:
Attempted Solutions
The alternative is to spend time tediously searching through the UI and logs :(
The text was updated successfully, but these errors were encountered: