I think developers must build their own back-ends and keep track of
what they do.
While I agree in theory, it is more difficult in practice. A single push server may be
used by several developers across several different app teams, in that case, you will want
some metrics/logging captured at the central point. Any given developer/team may
misbehave quite badly. Our experience with multi-developer services has demonstrated
that customers like having centralized logging/metric capture.
This will be always the more flexible solution.
IMHO you must focus on the core of building a reliable and powerful push send service
(includind the documentation part).
Enviado do meu iPhone
No dia 07/04/2014, às 13:09, Burr Sutter <bsutter(a)redhat.com> escreveu:
>
> On Apr 7, 2014, at 1:17 AM, Matthias Wessendorf <matzew(a)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)
>>
> As a developer, I wish to know if my 3 test devices all registered properly.
> As a developer, I wish to know if the push notification was sent to all 3 test
devices properly (at least delivered to Apple/Google properly)
> As a developer, I would like to know what were my past messages
> As a push administrator, a business unit representative (e.g head of sales, warehouse
manager) is going ask me if a particular message was sent to a particular user (alias) or
user group (aliases or category).
>>
>> This is a nice feature, and would enrich the UPS.
>>
>>
>> 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).
> I can see people wanting to just archive instead of delete those records -
interesting data points would be:
> - any commonality in device type
> - a trend in date/time of removal
> - ratio of added/removed (user opted in vs out)
>
> Is it possible to distinguish between app uninstall vs push notification disable
(where the app remains installed)?
>
>>
>> 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])
> would this be a good proxy for letting me know how often an end-user is using the
app?
>> - 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])
>>
>>
>> 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...
>> [3]
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/...
>> [4]
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/...
>> [5]
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs...
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog:
http://matthiaswessendorf.wordpress.com/
>> sessions:
http://www.slideshare.net/mwessendorf
>> twitter:
http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev