Client Relay reports now showing

Permanently deleted user

2 mai 2017 15:57

My Client Relay reports are empty

 

I am only getting Application down time report

 

 

My client relay url  http://(servername)/Geocortex/Analytics/ClientRelay seems ok, and I get following xml if I go there:

 

 

 

 

Do I need more time for reports to populate ? Or is there something wrong ?

 

 

0

• 

  Permanently deleted user

  2 mai 2017 16:03

  Hi Muhammad,

   

  Can you check your browser console in the viewer to see if the client relay is firing?  If you are seeing any errors in there, that may give you a clue as to the source of the issue.  

   

  My hunch is that you may not have the client relay URL in your viewer's proxy.config file.  Check section 8.9 of the Analytics admin guide for instructions on configuring that!

   

  Thanks,

   

  Danny

  0
• 

  Permanently deleted user

  2 mai 2017 18:02

  Hi Daniel,

   

  I have checked from browser, client relay seems to be fine. Here is the image:_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000PEaz&feoid=Body&refid=0EM60000000HYMg" _/_img_

   

  Is there any way, I can check from Analytics, which data it recieved and when it recieved from client?

   

  Thanks

  0
• 

  Permanently deleted user

  2 mai 2017 18:19

  Hi Muhammad,

   

  You can check the elastic-search database to see what's being collected, however it's pretty complicated, and we don't have printed instructions for it.  My suggestion would be to contact support so we can help you with that.  

   

  That being said, if the connection from the viewer is working, it may be a correlation issue, between what Analytics is seeing for the viewer URL, and what your users are using.  

   

  You may need to set an alternate URL (using URL Substitution) for Essentials in the configuration page.  Have a look at section 9.5.3 for details on that.  

   

  I hope this helps!

   

  Thanks,

   

  Danny

  0
• 

  Permanently deleted user

  2 mai 2017 18:27

  I forgot to mention that I have made changes in proxy.config file

  0
• 

  Permanently deleted user

  2 mai 2017 19:17

  you might also find some information in the Analytics.ClientRelay.log which can be found in [install drive]:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs.

   

   

  0
• 

  Permanently deleted user

  2 mai 2017 19:37

  I have checked ClientRelay log file, everythings look ok. Here are few last lines:

   

  [2017-05-02 12:15:40,573][INFO ][84  ][Analytics.ClientRelay][Geocortex.Analytics.Collectors.ClientRelay.ClientRelayRequestConsumer.ProcessRequestAsync[TRequest]] Sent request from Client Relay Service to database module.

   

  [2017-05-02 12:24:26,459][INFO ][101 ][Analytics.ClientRelay][Geocortex.Analytics.Collectors.ClientRelay.ClientRelayRequestConsumer.ProcessRequestAsync[TRequest]] Sent request from Client Relay Service to database module.

   

  [2017-05-02 12:37:19,392][INFO ][138 ][Analytics.ClientRelay][Geocortex.Analytics.Collectors.ClientRelay.ClientRelayRequestConsumer.ProcessRequestAsync[TRequest]] Sent request from Client Relay Service to database module.

   

  [2017-05-02 13:33:37,301][INFO ][111 ][Analytics.ClientRelay][Geocortex.Analytics.Collectors.ClientRelay.ClientRelayRequestConsumer.ProcessRequestAsync[TRequest]] Sent request from Client Relay Service to database module.

   

  Muhammad Almas

  0
• 

  Permanently deleted user

  2 mai 2017 19:48

  That looks like it's relaying correctly :)

   

  As I mentioned, I'd suggest checking that the URL you are using to access your viewer matches the discovered URL in Analytics.  Check my previous post in this thread for more details!

   

  Thanks,

   

  Danny

  0
• 

  Permanently deleted user

  2 mai 2017 19:52

   

  I will check that soon Daniel. Seems like it might be the cause. 

   

  Muhammad Almas

   

   

  0
• 

  Permanently deleted user

  2 mai 2017 20:15

  You were right Daniel. Analytics was accessing the Site using internal machine name url, where as I was opening and testing the site usinger external weblink. Now in Essentials Manager, I have changed the launch url. Will Analytics pick it by itself, or I have to refresh some thing to force it?

   

   

  Muhammad Almas

  0
• 

  Permanently deleted user

  2 mai 2017 20:41

  Hi Muhammad,

   

  That's great!  The collector will pick up the change in 24 hours, but you can speed up the process by restarting Geocortex Core on the Essentials server.  

   

  Thanks,

   

  Danny

  0
• 

  Permanently deleted user

  2 mai 2017 21:19

  Thank you very much Daniel.

   

  Everythings seems to be working ok.

   

  Muhammad Almas

  0
• 

  Permanently deleted user

  3 mai 2017 13:49

  Great!  I'm glad that it's working for you now :)

   

  Cheers!

   

  Danny

  0

Vous devez vous connecter pour laisser un commentaire.