Input error - output discard - possible display

From GEANT2-JRA1 Wiki

1 One tab, selection of one or more metrics for data retrieval
2 One tab per metric
3 One tab, selection of one or more metrics for data retrieval and display

Below, you can find crude drawing aiming at explaining what could be done starting from perfsonarUI. We will ask PERT members and MDM members to orde the best solution to implement and weight it against its easiness to implement.

Name, ordered list of prefered solution. (feel free to add additional proposals)

you:
- What you like in [1,2,3] and your additional suggestions
- your ordered list of preference.
NS:
- In 3, I like the fact that we can add and remove metrics in the bottom window.
- Preference: 3, 1
AH:
- In 3, I like the possibility to see metrics in the same window which may be related (e.g. how high utilization leads to output drops)
- Also in 3, I see no need to have the possibility to hide some parts of the window. On the other hand, the metrics which are currently selected should be clearly indicated (with checkboxes)
- The implementation of option 2 might lead to a duplication of code and we may end up with a lot of tabs in the end
- The implementation of 3 may be done in phases where we have a view similar to 1 in the beginning which is then extended to 3
ST:
- I don't like 2 because it multiplies tabs. One tab per functionality (all metrics here are SNMP counters under Interface) is more clear.
- In 3 I would see a checkbox with a list of available metrics which one can turn On/Off to see them displayed. And a legend of colours. Because for this kind of metrics (util, errors, discards) one always has in/out and it is difficult to show them on one graph with one axis you may consider a graph with positive and negativ Y axis for in and out values.
- In 1 you can't se any correlation between metrics (if there is some)
- Preference: 3

MG (Internet2):
- In general I don't like 2, it clutters the amount of tabs at the top, especially if more metrics will be added later. Also it will make things harder to maintain if the project has to be split up. In addition it seems that being able to see the data together is important. Perhaps areas of high utilization trigger errors.
- 3 is very appealing although it's starting to get to the point where the amount of information on the one tab is intimidating. The ability to hide some of the windows to make room for information you actually care about is nice. I find that it can be especially difficult to look at information in pS-UI on a low-resolution computer. As far as graphing for this suggestion goes I think it might need some work. I do think that having two Y axis might be necessary considering the difference in scale of the data being graphed but it seems that whether or not errors/discards are happening at a given time is more important than how many bytes are involved.
- The downside about 1 is that the metrics can't be graphed at the same time which is useful.
- Preference: 3, 1

JZ:
- I agree with AH, ST, and MG on the summary of number 2, having the multiple tabs looks too busy and there would be lots of code duplication.
- I agree with ST, MG on number 1 about the ability to display multiple related items on the same graph. This would be very useful for NOC alarm like functions.
- I agree with MG but disagree with AH on the need to hide items. I have a small laptop screen and pS-UI starts very large so I can never fit everything in desktop. Hiding certain functions would be much more user friendly.
- ST's suggestion about checkboxes and legends is very good.
- Preference: 3 (with modifications)

[edit]