1001548 - UI for querying tasks on queue.taskcluster.net

Status: RESOLVED WONTFIX

(Taskcluster :: General, enhancement)

Description

[Jonas Finnemann Jensen (:jonasfj)]

queue.taskcluster.net current has an empty persona protected web UI.

We should implement a simple UI that allows us query tasks by owner, workerType, provisionerId, and state.
This could be useful inspecting which tasks a running and queued.
The UI could also provide options for tweaking how tasks are distributed to workers.

If we decide not to have any UI at all, then we should remove the UI parts of taskcluster-queue.

Comment 1

[Pete Moore [:pmoore][:pete]]

Maybe it would be nice for this to be integrated with https://tools.taskcluster.net/task-inspector/ - a one stop solution for browsing tasks, currently queued or completed? Maybe we could have tick boxes for pending, running, completed etc as part of the search criteria, i.e. something akin to a fully featured search page such as https://bugzilla.mozilla.org/query.cgi?query_format=advanced (but for taskcluster tasks, not bugzilla bugs). What do you think?

Comment 2

[Jonas Finnemann Jensen (:jonasfj)]

1)
This bug was for when queue had UI and was using a database so it was possible.
Now we use azure table storage and queue doesn't have any UI.

2)
We can't query table storage on random keys efficiently.
But we could create secondary indexes for keys like task.owner and task.tags.
But I think this should be a secondary component. And it's already sort of possible with index...
As a tool it might be nice for debugability to have something that could just show tasks arriving, using pulse or something... I'm not sure.

Anyways, I doubt we can just search in azure table storage. It basically amounts to a full table scan, which might work now, but certainly won't continue to scale.

For now, let's use index when we want to find tasks again... And maybe in the future expand index so that task.owner and task.tags are always used for indexing somehow... Exactly how I'm not sure :)

Marking this as won't fix because it's really old and tech for doing this is long gone.
The concept may still be desirable, but we should fix perf issues before we add secondary indexes.

Comment 3

[Pete Moore [:pmoore][:pete]]

Resetting Version and Target Milestone that accidentally got changed...