This question is locked. New answers and comments are not allowed.
I have a C# application and trying to configure Analytics to log application activity.
When application is instantiated, I call the Start methods and it begins logging. Before application instance dies, I call the Stop method and after that receive all the activity.
My problem is that I'd like to force Analytics to send statistics more often to the server. By default, SynchronizeAutomatically is set to true and StorageSaveInternal is set to 1 minute. However, I noticed that no data is send to server until I call the Stop method.
I tried to decrease StorageSaveInternal to 15 seconds, still no effect.
Also, tried to disable automatic synchronization and to use ForceSync method, but even then I received data only on Stop method call.
All traffic has been monitored by both Fiddler and through logging (created new trace monitor).
I guess that I missed some configuration step, please help.
When application is instantiated, I call the Start methods and it begins logging. Before application instance dies, I call the Stop method and after that receive all the activity.
My problem is that I'd like to force Analytics to send statistics more often to the server. By default, SynchronizeAutomatically is set to true and StorageSaveInternal is set to 1 minute. However, I noticed that no data is send to server until I call the Stop method.
I tried to decrease StorageSaveInternal to 15 seconds, still no effect.
Also, tried to disable automatic synchronization and to use ForceSync method, but even then I received data only on Stop method call.
All traffic has been monitored by both Fiddler and through logging (created new trace monitor).
I guess that I missed some configuration step, please help.
2 Answers, 1 is accepted
0
Accepted
Hi Sasa,
At present you can't control the submission time any further than this, I'm afraid. This behavior is detailed here: http://docs.telerik.com/platform/analytics/integration/data-lifecycle/introduction#when-is-data-saved-and-sent
As it is, calling ForceSync() no more often that every 10 minutes is the most control you'll have.
The reason for this controlled submission is to save bandwidth and processing power.
Could I ask what your reason is for wanting to submit data more often? It's mostly something developers wish to do and mostly when initially integrating with Analytics, because they (we, I should say as I'm a dev too) are excited about seeing data arriving and being displayed. But once data starts coming in from a large number of real users then it actually becomes less important to see and analyze every bit as soon as it arrives and you become more focused on the accumulated, big picture.
To verify that data is arriving at all if you're without Fiddler, you can also take a look at the Live report: http://docs.telerik.com/platform/analytics/client/reports/live
Regards,
Richard Flamsholt
Telerik
At present you can't control the submission time any further than this, I'm afraid. This behavior is detailed here: http://docs.telerik.com/platform/analytics/integration/data-lifecycle/introduction#when-is-data-saved-and-sent
As it is, calling ForceSync() no more often that every 10 minutes is the most control you'll have.
The reason for this controlled submission is to save bandwidth and processing power.
Could I ask what your reason is for wanting to submit data more often? It's mostly something developers wish to do and mostly when initially integrating with Analytics, because they (we, I should say as I'm a dev too) are excited about seeing data arriving and being displayed. But once data starts coming in from a large number of real users then it actually becomes less important to see and analyze every bit as soon as it arrives and you become more focused on the accumulated, big picture.
To verify that data is arriving at all if you're without Fiddler, you can also take a look at the Live report: http://docs.telerik.com/platform/analytics/client/reports/live
Regards,
Richard Flamsholt
Telerik
EQATEC Application Analytics is now Telerik Analytics. For more information on the new name, plus what's new in Telerik Analytics, please, check out the Analytics Service Announcement.
0
Sasa
Top achievements
Rank 1
Rank 1
answered on 25 Sep 2014, 09:15 AM
Hi Richard,
I misunderstood the purpose of StorageSaveInterval property and missed the fact that interrupted session statistics will be send next time user establish a connection.
Thanks for the answer.
I misunderstood the purpose of StorageSaveInterval property and missed the fact that interrupted session statistics will be send next time user establish a connection.
Thanks for the answer.