"The virtual hostname is there only as a convienece option to customers. Note that the virtual hostname and VIP are both only used for incomming traffic to Orion. This is typically end-users accessing the Orion web interface. If you don't need a solution for redirecting incomming web requests to the active member of the pool, then this is not something you need to worry about"
The details with respect to Web Traffic is 100% clear, To understand further , In our environment we have SAM agents( Agent initiated ) & these agents traffic are incoming requests to Orion platform, So definitely i need to have a solution (Default DNS update by HA or custom Load balance solution) to direct these traffic to active member, or does the agent have any intelligence to identify itself, which is the active member of the pool (without any above mentioned option).
And to add, incase of agent with Server initiated communication , i assume we will able to achieve continuous monitoring, without traffic re-direct option like "Default DNS update by HA or custom Load balance solution".
kindly help to validate my understanding, Please