Hey Elad,
Thanks for the reply. Regarding 2) - I am simply saying that *including* the vs name as a label (which is already done in vsx.overview would really sell this much more. I hope you will consider it.
I will give the following example with snmp polling, graphing CPU load per VS. I am aware I blocked the names out - but replacing names with, vs_id_0, vs_id_1, vs_id_2 etc. will give me absolutely zero traction with our management and customers.
"Ohh vs_id_19 is high today - Hmm wait - Anyone knows what vs_id_19 is????"
This is basically the same for every usecase for skyline graphs. We need logical names for quick references and visual guidance.
Regards,
Henrik