Analytics reports afster instance name change

Permanently deleted user

22 février 2019 08:14

We had Analytics 1.4.2.up and running. It was collecting data from two Geocortex Essentials 4.8.2. clusters (an internal cluster/instance and an external cluster/instance) --> Agents were installed on the clustered servers. This week we have done an upgrade to Geocortex Essentials 4.10.2 and also changes the istance name! We got the Essentials Cluster all up and running fine with the new instance name. However, Analytics still looks at the old instance names and therefore it does not collect data any more.

 

How can we teach Analytics to start collection data from the new instance name? We have tried to restart the Geocortex core of Analytics, but that did not work.

 

Thanks for your replies / ideas.

0

• 

  Gareth Evans

  14 mars 2019 18:24

  Hi Vincent

   

  Have you uninstalled/reinstalled the Analytics Agent on the Essentials machines?  I suspect that would be all you need to do to get your new entries in Analytics going.

   

  -Gareth / Latitude Support

  0
• 

  Gareth Evans

  14 mars 2019 18:45

  After conferring with coworkers, it appears this instance change should not have affected Analytics.  The idea of the Agent is that it is able to identify an instance and report it to Analytics.  We might want to take a look at your Analytics agent logs on the Essentials machines at C:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs named Analytics.ResourceCollector.xxx.log and see if we see any errors.  

   

  I'd also recommend you open a support case by emailing us support@latitudegeo.com and we can delve further.

  0

Vous devez vous connecter pour laisser un commentaire.