Deployments are listed in a giant table. The two date/time-related columns, Activity and Schedules, are not helpful when trying to find periods in our infrastructure's workload where other jobs can be slotted in. I have to maintain a separate calendar where I replicate the recurrence rules, but this frequently gets outdated as jobs are added or adjusted. It would be great if there was an easy way to see where deployments are concentrated on the calendar.
Describe the proposed behavior
Include a recurrence calendar on the deployments page. The calendar should have adjustable period views (day, week, month, maybe year?). When looking at the weekly recurrence view, there's an overlay of daily and weekly deployment schedules. When looking at the monthly calendar, then overlay daily, weekly and monthly.
The user can toggle between recurrence view, which doesn't care about the date, and calendar view, which maps everything onto a true calendar.
Awesome to have features:
Allow filter by work pool
Allow filter by tag
Use historical runtime duration for flow run duration. Or make visualization duration an optional field in deployments?
Duration boxes are semi-transparent so more overlap darkens that span on the calendar
Example Use
Some of my flows depend on non-scaling infrastructure. Deployments have to be temporally dispersed to prevent overwhelming or crashing this infrastructure, especially during work hours. Whenever I must add a new deployment, I can easily find a span that won't cause issues.
I'm working on a project that requires me to reserve or plan infrastructure use. I want to see which dates I can squeeze my release into without interrupting normal operations.
phensley-oe
commented
1 week ago
Describe the current behavior
Deployments are listed in a giant table. The two date/time-related columns, Activity and Schedules, are not helpful when trying to find periods in our infrastructure's workload where other jobs can be slotted in. I have to maintain a separate calendar where I replicate the recurrence rules, but this frequently gets outdated as jobs are added or adjusted. It would be great if there was an easy way to see where deployments are concentrated on the calendar.
Describe the proposed behavior
Include a recurrence calendar on the deployments page. The calendar should have adjustable period views (day, week, month, maybe year?). When looking at the weekly recurrence view, there's an overlay of daily and weekly deployment schedules. When looking at the monthly calendar, then overlay daily, weekly and monthly.
The user can toggle between recurrence view, which doesn't care about the date, and calendar view, which maps everything onto a true calendar.
Awesome to have features:
Example Use
Some of my flows depend on non-scaling infrastructure. Deployments have to be temporally dispersed to prevent overwhelming or crashing this infrastructure, especially during work hours. Whenever I must add a new deployment, I can easily find a span that won't cause issues.
I'm working on a project that requires me to reserve or plan infrastructure use. I want to see which dates I can squeeze my release into without interrupting normal operations.
Additional context
No response