countly-sdk-cocoa
countly-sdk-cocoa copied to clipboard
benoitsan
Default update interval of 120 seconds is too long for the 'Online Users' tracking in Countly
I noticed that the 'Online Users' widget on the cloud.count.ly dashboard would rise when one of my client applications using this SDK was started, but would drop back down after about a minute and a half, even though the application was still running. Seems the server requires a more regular heartbeat than 120 seconds. I dialed it back to 60 seconds and it seems to work ok.
An online user is expired if we don't receive any request for the user for 60 seconds. Countly iOS SDK sends a request every 30 seconds. We can discuss this further if anyone thinks 60 seconds should be increased.
I am integrating Count.ly into a long-lived Mac app, and I find 60 second intervals for session keep-a-live to be too frequent. I don't need such fine granularity for session counting. In fact, something around 30 minutes would probably be sufficient, as the app is expected to be very long-lived (utility accessed from menu bar, very rarely closed).
In particular, I don't want my users complaining that the app "calls home" every 60 seconds, just for analytics.
Ideally, I would like session length to be configurable per app in Count.ly Cloud. Is there an official channel for feature requests, such as this?
Cheers, Chris
Yeah, I was about to say, a configuration per-app would be the way to go.
Cheers
Sean
On 3 Aug 2013, at 7:59 pm, Chris Miles [email protected] wrote:
I am integrating Count.ly into a long-lived Mac app, and I find 60 second intervals for session keep-a-live to be too frequent. I don't need such fine granularity for session counting. In fact, something around 30 minutes would probably be sufficient, as the app is expected to be very long-lived (utility accessed from menu bar, very rarely closed).
In particular, I don't want my users complaining that the app "calls home" every 60 seconds, just for analytics.
Ideally, I would like session length to be configurable per app in Count.ly Cloud. Is there an official channel for feature requests, such as this?
Cheers, Chris
— Reply to this email directly or view it on GitHub.
I sent my concern about the duration API on the countly forum (http://support.count.ly/discussions/questions/198-api-implementation). Basically, as @chrismiles, I didn't like the idea to send a heart bit request every 30 seconds. It sounds awkward to me because I consider Countly as a developer tool, not an essential service for the end user, and I don't want to abuse of it concerning the requests made in the background. That's also why I added 2 parameters in the SDK: 1 parameter to adjust the frequency, 1 parameter to enable/disable the tracking. Also about the duration, as I said, sending a "end session" signal on OS X is not easy because there is no background task on OS X when you quit an app.
