Analytics - Geocortex Application - collecting data from Viewers that is accessed from a dns adress (load ballancer)
I have two Essentials server (seperate, not clustered) I have configured the Viewers with Client Relay info and updated the proxy.config,. The agent on both servers is running fine, and reports Essentials info as they should. But there is no data reported into the Essentials Application from the Viewers, when using the dns adress. Our servers has the same Application is identical and serves as a failover for each other - the traffic to these servers is handle by an load ballancer and forwards traffic due to load on to each Essentials server.
How to configure agents/traffic to collect reports into Analytics when dns adress is forwarded from a load ballancer (or is the traffic stopped in a FW somewhere? )
-
Hi Morten
It sounds like you may need to configure URL Substitution. You'll want to add the load balancer URL that you access your Viewer at to your Essentials instance.
If that doesn't work out, please open a support case by emailing us at support@latitudegeo.com.
Thanks
Gareth0 -
Hi and thx - I have finally worked out the understanding of some behavior i saw after adding the URL Substitution on both serves. Reports was only written to one of the servers registered in Analytics. I did some testing and and I have now verified that both servers reports usage correctly, but only writes to one of them in Analytics - the first that was registeres with URL Substitution.
I believe this occurs since my servers is separate - not clustered, but share the load balancer adress. This makes it a bit hard to discover issues on wich server. But I least we have verified that we get correct data on all applications from both servers. I will send an email to support aswell just to register the issue to verify if this is a bug or not supported use case.
0 -
Hi Morten
Please do send that email off to support, we'll treat this as a potential bug. It sounds like the client relay data is getting sent for viewers from both servers but is only being presented for one resource. We'll confirm this in the support case.
Thanks
Gareth0 -
Done :) 0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
4 commentaires