Re: [Analytics] Pageview API Status update

2015-06-25 Thread Dan Andreescu
Two quick updates: What Oliver said resonates with us, we are doing everything possible to focus and keep the project moving instead of satisfying all possible requirements at launch. We have been working our goals (not yet finalized) to include "Pageview API by September". There is quite a bit

Re: [Analytics] Pageview API Status update

2015-06-15 Thread Oliver Keyes
Well, that's not the case; https=1 was added for the apps, and so hit both mobile and text varnishes. Since all pageviews go through the text or mobile sources, all pageviews note (implicitly or explicitly) their https status. In regards to the initial suggestion; no. Don't add new fields. Don't p

Re: [Analytics] Pageview API Status update

2015-06-14 Thread Yuri Astrakhan
X-analytics contains HTTPS=1 for all text hits, but not for other types of traffic On Jun 15, 2015 00:54, "Kevin Leduc" wrote: > In light of the recent switch to use HTTPS, what about adding http/https > information. Maybe it can be added to the 'access_method' rather than > adding a new dimensi

Re: [Analytics] Pageview API Status update

2015-06-14 Thread Kevin Leduc
In light of the recent switch to use HTTPS, what about adding http/https information. Maybe it can be added to the 'access_method' rather than adding a new dimension? On Thu, Jun 11, 2015 at 1:46 PM, Jon Katz wrote: > Hi Dan, > Sorry for the late response to this-- > > ** Make a new cube that

Re: [Analytics] Pageview API Status update

2015-06-11 Thread Jon Katz
Hi Dan, Sorry for the late response to this-- ** Make a new cube that examines site versions and client information* ** Just use the private data as we're already doing, but aggregate it hourly or daily as needed, to make analysis much faster.* How can I help add/keep this to/on your roadmap? -J

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Dan Andreescu
On Fri, Jun 5, 2015 at 3:09 PM, Oliver Keyes wrote: > If we can't share it with the public then it seems like it shouldn't > be part of a proposal for an API. > Right, to clarify, this proposal is for a public data set and API. > >>> Thanks Dan, and apologies if these are naive questions: > >>

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Oliver Keyes
If we can't share it with the public then it seems like it shouldn't be part of a proposal for an API. On 5 June 2015 at 14:56, Yuri Astrakhan wrote: > Yep, the Zero tag would be very useful. Also, something zero team found > highly useful are: via (proxy value in x-analytics), https vs http, zer

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Yuri Astrakhan
Yep, the Zero tag would be very useful. Also, something zero team found highly useful are: via (proxy value in x-analytics), https vs http, zero sub domain vs m subdomain. On Jun 5, 2015 14:51, "Kevin Leduc" wrote: > I came across another potential requirement from the WP Zero team: > add the x-a

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Kevin Leduc
I came across another potential requirement from the WP Zero team: add the x-analytics['zero'] to the dimensions. This would allow the zero team to get pageviews per partner carrier. Our partners are interested in this data, however, they don't want to share it with anyone as it is competitive da

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Jon Katz
Thanks Dan, and apologies if these are naive questions: For mobile web can we also see beta v. stable? This is important for tracking prototypes, which is one of the core product uses for this data. For apps can we see ios v android? On Fri, Jun 5, 2015 at 8:39 AM, Oliver Keyes wrote: > On

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Oliver Keyes
On 5 June 2015 at 10:38, Dan Andreescu wrote: >> Gotcha. Reading that proposal it appears to be a proposal for a >> methodology that will enable future proposals; where are the future >> proposals? > > > Well, so the geo cube has to guess a bit at who would find it useful in the > future. > >> >>

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Dan Andreescu
> > Gotcha. Reading that proposal it appears to be a proposal for a > methodology that will enable future proposals; where are the future > proposals? Well, so the geo cube has to guess a bit at who would find it useful in the future. > It also says "in many countries, disease monitoring must b

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Oliver Keyes
Gotcha. Reading that proposal it appears to be a proposal for a methodology that will enable future proposals; where are the future proposals? It also says "in many countries, disease monitoring must be carried out at the state or metro-area level" - which countries have to be metro-level? Who are

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Dan Andreescu
> > My only thought is that "city" makes me uncomfortable. Did we track > down a precise use case for that in the end? Yes, the Los Alamos National Lab folks' proposal: https://meta.wikimedia.org/wiki/Research:Geo-aggregation_of_Wikipedia_pageviews We talked to them yesterday and it seems the ti

Re: [Analytics] Pageview API Status update

2015-06-05 Thread Oliver Keyes
My only thought is that "city" makes me uncomfortable. Did we track down a precise use case for that in the end? On 5 June 2015 at 09:25, Dan Andreescu wrote: > I just posted a comment on the famous task: > https://phabricator.wikimedia.org/T44259#1341010 :) > > Here it is for those who would rat

[Analytics] Pageview API Status update

2015-06-05 Thread Dan Andreescu
I just posted a comment on the famous task: https://phabricator.wikimedia.org/T44259#1341010 :) Here it is for those who would rather discuss on this list: We have finished analyzing the intermediate hourly aggregate with all the columns that we think are interesting. The data is too large to q