Hi Naganarasimha G R,
Thanks for your comments,
There will be some common queue metrics across the labels, wont it get repeated across for each label if a queue is mapped to multiple labels?
Some common fields may get repeated (like absolute max capacity, etc.). I think repeat some of them is not a very big issue to me. I think we can show queue-label-metrics + queue-common-metrics for each queue-label
IIUC most of the queue Metrics might not be specific to a label, like Capacity, Absolute max capacity, Max apps, Max AM's per user etc... . Correct me if my understanding on this is wrong.
Yes, they're, but there're more parameters / metrics in queues for both label/queue, different labels under same queue can have different user-limit/capacity/maximum-capacity/max-am-resource, etc.). We also need to show them to users if possible
Apart from the label specific queue metrics like (label capacity, label abs capacity,used) are there any new Label specific queue metrics you have in your mind ?
I think above can answer your question.
would it be better to list like
If we have this view,
1) How you show label-specific metrics?
2) What's the "used-resource" in queue level means (used-resource make more sense when it's per-label).
3) How to check "label-wise" resource usage for parent queues.
Also if required we can have seperate page (/in the labels page/append at the end of CS page) like
I think my proposal is still a little more clear, we need to show label-wise metrics to user. And with that, user can clear understand resource usage for each partition (just check each label's usage. Also parent's label-wise usage can show as well.