Skip to content

121. Tui-dash widens to orchestration quota and resource view ​

Date: 2026-10-18

Status ​

Accepted.

Context ​

Record 110 kept firstmate out of tui-dash on 2026-10-17. The captain widened the dashboard scope to orchestration on 2026-10-18. The wider scope supersedes the part of 110 that kept firstmate out.

The captain's words ​

also i want tui-dash to be interface with which i can understand quota consumption of my orchestration setup, see how and who consume too much quota AND resource consumption too, i want to see what tasks running right now on which project, i want to see which tasks consumed too much resources, i want to see tasks/jobs schedules

He said this on 2026-10-18 in his ruling on tui-dash.

Decision ​

Tui-dash becomes the interface for quota consumption of the orchestration setup. It shows who consumes too much quota and too many resources. It shows which tasks run right now on which project, which tasks consumed too much and the task schedules.

Evidence ​

Quota consumption of the orchestration setup needs one readable interface. Overconsumers of quota and resources need naming by who and how. Running tasks need their project, heavy tasks need flagging and schedules need viewing.

What was considered and rejected ​

Keeping tui-dash free of firstmate under 110. It lost because the captain widened the scope to orchestration, which supersedes that part of 110.