Enable Slowest layers in analytics

Ethan Granger

12 janvier 2017 18:03

In Analytics, If I drill down to TRENDS > GEOCORTEX ESSENTIALS > then to my app, there is a statistic on "Slowest Layers," but it says "No information available." How do I get this data to appear?

0

• 

  Permanently deleted user

  12 janvier 2017 18:33

  Hi Ethan,

   

  That panel is populated from the following collectors:

  1. ArcGIS Catalog probe
  2. ArcGIS log file collector
  3. Essentials Info Collector (on the Essentials server)

  Usually if the panel is not populating, it can indicate that there is an issue with one of these collectors.  You can check the following logs for guidance on that:

  1. C:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs\Analytics.ArcGisCatalogProbe.log
  2. C:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs\Analytics.ArcGisLog.log
  3. C:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs\Analytics.EssentialsInfo.log (on the Essentials server) 

  Another thing you can check is that the URLs you are using to connect to your ArcGIS server in Analytics match the URLs in your Essentials sites.  For example, if you are monitoring webadapter.mydomain.com/arcgis/rest/services but your Essentials sites are using localservername.myinternaldomain.com:6080/arcgis/rest/services, the data that is collected won't match, and will result in the panel (and possibly other panels) being blank.  

   

  I hope this helps!

   

  Thanks,

   

  Danny

  0
• 

  Ethan Granger

  23 janvier 2017 16:53

  I think my problem was the matching URLs. I'm getting data in that table now.  So, follow-up question: I've got some slow vector and raster catalog layers, how to do I make them perform better?

  0
• 

  Permanently deleted user

  23 janvier 2017 17:19

  Hi Ethan,

   

  Glad to hear that it's working!  Now that you know which layers are slow to respond, you will need to go through your ArcGIS server logs and examine the services that host those layers.  From there you can have a look at the Esri KB for possible solutions, or open a support case with them to request assistance.  

   

  The other thing you can do on the Analytics side, is look at the server usage information for the same time range, and see it anything else lines up with the slow layers.  Some common culprits are CPU and memory usage.  

   

  I hope this helps!

   

  Thanks,

   

  Danny

  0

Vous devez vous connecter pour laisser un commentaire.