HI Team,
We are developing Management plugin where we considering the latency for monitoring component is 10 Milliseconds.
But later on the Possible case was found as below :
Possible case : The vROps cluster deployed on India Region (network ) and Rack deployed in Austin Region (network ).
The latency of RACK from vROps is >= 250 milliseconds. And this latency is two high as we are considering the connection within 10 milliseconds.(for Management pack)
Is there any way to reduce latency from vROps to the monitoring component. In the scenarios can vROps Remote Collector is the solution to reduce latency ?
Please suggest on this.
Note : Developing using vROps SDK 7.0
Thanks,
Mithun
Hi,
Even for remote collectors the latency is to high;
Network latency for remote collectors | < 200 ms |
Is a 2nd vROPs deployment in Rack an option?
No, we don't have option to deploy vrops in same rack also need latency below 10 Ms.
Is there any solution for this
No not really because you are looking in the wrong place. You've got a network problem, hard to fix that with some sort of vROPs setup.
My advice, try getting a better network link.
Hi KabirAli82,
I read the VMware KB article
Network latency for remote collectors | < 200 ms |
I have query here ,
Is above time is for remote collector node to vRops node .
Or the above time for collector node to monitoring compoment?
Thanks,
Mithun
It is from remote collector to the analytics cluster.
A remote collector node reduce bandwidth across data centers and does not store data or processing any analytics functions.
Consider above scenario and the management pack limitation as 10 ms latency .
I want to monitor 4 component in one vrops so all are with the Different geo-locatio and the connected via WAN.
In above case will configure 4 different remote controller with component and in same location will help to reduce latency?
can you please suggest best practice handle this scenario while developing management pack