No AGS Server stats collected by Analytics
Hi, I have 2 ArcGIS Server sites set up in front of a load balancer. The Analytics Agent are installed on these 2 servers. I have also installed Analytics Agent on 2 separate Geocortes serverx, and Analytics Hub Server on a different server.
I have configured logging to verbose for both ArcGIS servers. In Analytics I have set up ArcGIS Server using Windows Authentication, and set the logging path using UNC path to the log file, specifying the FQDN. The settings are saved successfully.
However no stats are being collected by Analytics. Also I cannot see the logs being collected in the Core log directory C:\program files\Latitude Geographics\Geocortex Core\Data\Logs
Has anyone come across this issue? I am using Analytics 1.2, ArcGIS Server 10.3.1 and Essentials 4.6.3
I have also tried setting the log path simply as D:\arcgisserver\logs\, but it didn't work either.
0
-
Hi Ravin,
It sounds like you may be configuring the server in the Analytics configuration page, as well as using remote monitoring (via the agent). I would suggest deleting the configured server from the configuration page, and restarting the Geocortex Core service on all 3 servers (the hub, and the 2 ArcGIS servers), and see if there is any change.
Thanks!
Danny0 -
Hi Danny,
Please see my configuration attached. ST2W3417 is the Hub server. ST2W3423, ST2W3424 are the agents where ArcGIS Server is installed. arcgisenterprisepreprod is the load balancer name. I have tried configuring using the server names and LB names. By "deleting the configured server from the configuration page", do you mean deleting ST2W3423 and ST2W3424 under ArcGIS Servers ->Default ? On the configuration page, I only have the option to save changes, but not delete the server.
_img_ alt="AnalyticsConfig" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrQ2&feoid=Body&refid=0EM60000000Ujcd" _/_img_0 -
Hi Ravin,
If you are not seeing the option to delete the servers from your configuration page, I'd suggest opening a support case, as it sounds like you may have encountered a bug. We would need to review your configuration files to figure out the state your server is in.
Thanks,
Danny0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
3 commentaires