I'd like for the console to be more usable and relevant to quarks application
developers. I'm also hoping by asking for feedback and ideas for improvements
someone may decide they would like to make a contribution to the console.
Here are some thoughts I had, and I'd love it if folks could comment on these
about whether they seem worthwhile, or if you have thoughts of your own about
what could make the console better. If anyone has an in-depth use case they
could describe that would also help illustrate things that could be added or
improved that would really be helpful.
1. Display oplet aliases (application assigned names) instead of the 'OP_X' in
the topology graph
2. Alternately, remove the 'OP_X' and just assign the index value in the graph
'0', '1', etc
3. If a topology has counter metrics on all oplets (i.e, DevelopmentProvider is
used) either a) remove all oplets from the graph or b) make the counter ops
look less significant or 'grey' them out from the graph.
4. In 'static flow' mode disable the refresh. If the oplets are stacked on top
of each other you can drag them, but when the refresh timer expires, they snap
back.
5. Add the ability to plot multiple oplets at the same time as line charts -
currently line charts are only supported for a metrics that are only on one
oplet
6. Add the ability to view the metrics chart as a separate window - similar to
the 'View all oplet properties' window?
7.Ability to zoom in on one region of the graph to better understand the
topology. either zoom in to the existing graph, but a new graph containing the
contents below it, or again, have a separate window with the zoomed in content.
8. In 'Tuple count' view remove the colors on the edges, instead color the
vertices corresponding to the tuple count, and add stream tags to this view on
the edges
9. Add a new view, similar to Tuple count, but if rate meters are applied
enable a new option called 'Flow rates' that would display the metric counters
present.
Cheers,
Susan
