[aerogear-dev] [UnifiedPush Server] Analytics / Metrics

Sebastien Blanc scm.blanc at gmail.com
Mon Apr 7 02:25:59 EDT 2014


Sounds good !
Some comments inline


On Mon, Apr 7, 2014 at 7:17 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello,
>
> for a first round of collection some more data around the usage of the
> push server (aka analytics/metrics), I'd propose we keep it very simple.
>
> Overall, I see one major area of interest:
> *metrics around push messages being sent:
> - time of sending (using timezone of the server?)
> - group of receivers (e.g. everyone or the provided cirterias(e.g. alias,
> categories,...))
> - payload (the entire payload, including custom keys - not only alert,
> sound, badge etc)
>
+ Response / Status of the submitted message I suppose (response status to
the "sender" and info it's has been dispatched to the 3rd Push network) ?
It would also be nice to see who has initiated the send request : cURL,
backend app or Compose Message Page ? Not sure how to do this but could be
useful IMO.

>
>
> This is a nice feature, and would enrich the UPS.
>

For sure. But how will someone access these metrics ? Is the plan to have
some kind of metric/usage page (with charts etc ...) on the console and/or
just raw data in the form of json/xml/txt ?

>
>
> However, I can see also some interest around device specific metrics:
>
> Today we obivously store all the registered devices, but we also remove
> them from the database table if needed (to not send messages to phones that
> would no longer receive them anyways).
>
> Something that would be interesting as well, might be the following data:
> - how often was an app has reached the push server  (note: every time the
> app starts, the metadata of the server is being updated (see [2])
> - number of device-tokens / registrationIDs that have been removed, when
> receiving errors from Apple/Google (see [3] or [4])
> - number of devices, that were activly removed using our APIs (supported
> only on Android/SimplePush due to Apple policy, see [5])
>
Yes, that is a tricky one even going beyond the scope of metrics. For
instance with Android there is no way to unregister when you desinstall the
app.

>
>
> While the initial focus should be around the message related metrics,
> capturing some device data is nice too.
>
>
> Any thoughts ?
>
> -Matthias
>
>
> PS: Oh, for the longer run(...), I'd also like to see metrics like "was
> mobile app opened due to a push notification". BUT that also requires some
> more work/reseach on the client Push SDKs. But seriously, this is not a
> priority for the next few months!
>
>
>
>
> [1] https://issues.jboss.org/browse/AGPUSH-116
> [2]
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L98-L112
> [3]
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L87-L94
> [4]
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/GCMPushNotificationSender.java#L93-L94
> [5]
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L117-L119
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140407/d26e2d8a/attachment-0001.html 


More information about the aerogear-dev mailing list