<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On May 14, 2014, at 4:46 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 13, 2014 at 10:23 PM, Jay Balunas <span dir="ltr"><<a href="mailto:jbalunas@redhat.com" target="_blank">jbalunas@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Wanted to chime in here. The overall goal of the metrics/stats imo, is around letting developers/administrators know what is happening with the server. Messages in/out, registrations, etc.... This will also help new developers see activity and do some basic debugging if devices fail to register or messages fail to send. </div>
<div><br></div><div>Maybe in the future we'll get into more analytics, resource usage type stuff but for Mobile Push 1.0 I think this is overkill. For example I would not expect us to store this data over 30 days or so, and have viewing options like "last hour", "last 24 hours", "yesterday", "last 7 days", etc...</div>
</div></blockquote><div><br></div><div>yeah - a simple history of messages sent</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><div>Building on what Matthias posted below, here are some breakdowns of stats we could/should track:</div><div><br></div><div>Registration:</div><div>-- Device registered with [x,y,z] metadata</div>
<div>-- Device removed with [x,y,z] metadata </div></div></blockquote><div><br></div><div>let's focus on message sent stats for now</div></div></div></div></blockquote><div><br></div><div>Makes sense as a first pass. We're already logging this to file anyway iirc.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;">
<div style="word-wrap:break-word"><div><br></div><div>Messages:</div><div>-- Push request <timestamp-id> received from [ip] with [x,y,z] metadata</div><div>-- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD GCM, etc...]</div>
<div>-- Push request <timestamp-id> had foo errors : details</div></div></blockquote><div><br></div><div>Yes, these are nice items for the details once you click on a push message in that 'history table view' (e.g. IP address, full criteria, error details, etc).</div></div></div></div></blockquote><div><br></div><div>I thinking this would be the the data collected, what and how to show it would be part of the whole discussion.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><br></div><div><div style="font-family:arial,sans-serif;font-size:13px">The table itself could be really simple:</div></div><div style="font-family:arial,sans-serif;font-size:13px"><div>* time of sending</div><div>* content/payload of the message</div>
<div>* could be sent out to (e.g. a status icon *green/red*)<br></div><div><br></div><div>Once a user clicks an entry, we would display more details</div></div></div></div></div></blockquote><div><br></div><div>+1</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><div>These would all have app and variant info as part of the metadata so they can filtered/broken down as needed.</div><div><br></div><div>This should give us a great base for all kinds of table and chart views.</div>
<div>-- Registrations over time for the server, specific app, specific variant</div><div>-- Messages over time for the server, specific app, specific variant</div><div>-- Table of the above if feasible :-)</div></div></blockquote>
<div><br></div><div><br></div><div>yeah, all that is good - but IMO more a dashboard </div></div></div></div></blockquote><div><br></div><div>I thought that was basically what we were going for - sort of a simple dashboard type page? With the table you describe above and maybe a chart of messages sent over time or something like that? </div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>(e.g. over time we could also show how often an app has been launched (per variant) - and with some work on the registration SDKs, we could (not 1.0) show how often an app has been opened by a push </div></div></div></div></blockquote><div><br></div><div>Very cool ideas for sure :-)</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>Obviously we may need to scale down as needed, and discuss more, but this is what I was thinking about.</div>
<div><br></div><div>Thoughts?</div><div><div class="h5"><div><br></div><br><div><div>On May 13, 2014, at 4:47 AM, Hylke Bons <<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>> wrote:</div><br><blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hello,<br>
<br>
Depending on the use case, it may even deserve its own spot in the
sidebar. Like already mentioned on the thread, it's better to keep
the number of items there fixed. We may have have several entry
points to the logs, and an overview of some statistics can be
useful as a landing page before going into "Applications".<br>
<br>
Let's step back for a moment before looking at the UI: What are we
trying to solve by providing a log?<br>
<br>
- Let administrators know everything is going well? (or, that
there was a problem?)<br>
- Looking at resources used? Bandwidth, costs?<br>
- App adoption/growth numbers over time? How well is my app doing?<br>
<br>
I'm not sure about the technical possibilities. Thoughts?<br>
<br>
Thanks,<br>
<br>
Hylke<br>
<br>
<br>
<br>
On 07/05/2014 10:54, Matthias Wessendorf wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi,</div>
<div><br>
</div>
<div>as discussed , we need some sort of 'stats' around push,
like:</div>
<div>* time of sending</div>
<div>* receivers (e.g. categories, alias ?)</div>
<div>* content/payload of the message</div>
<div>* could be sent out to APNs/GCM</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>But, where, or how to add this ? </div>
<div>My current thought is:<br>
</div>
</div>
<div><br>
</div>
<div>When a user did select an "Application", he enters the
"Application Details Page" (see [1]), now here, on the sidebar
(see [2]) he would see the "Notifications" icon.</div>
<div><br>
</div>
<div>Clicking on that "Notifications" icon, would give you a
new page, that contains the "Send Notifications..." button
(currently located in [1]), and a table of all the push
messages that were sent out for the _current_ selected
Application.</div>
<div><br>
</div>
<div>Any thoughts ? </div>
<div><br>
</div>
<div>-Matthias</div>
<div><br>
</div>
<div>[1] <a href="https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png" target="_blank">https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png</a></div>
<div>[2] <a href="https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png" target="_blank">https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png</a></div>
<div><br>
</div>
<div><br>
</div>
-- <br>
Matthias Wessendorf <br>
<br>
blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div><br></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></body></html>