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 propose new fields. Don't do anything with new fields - freeze the definition already. We've had a pageviews definition for 6 months, we've had unreliability in Henrik's third-party service for 12, and every time there's a "should we add a new field?" proposal it slows implementing an alternative down. We need that alternative. On 15 June 2015 at 00:57, Yuri Astrakhan <[email protected]> wrote: > X-analytics contains HTTPS=1 for all text hits, but not for other types of > traffic > > On Jun 15, 2015 00:54, "Kevin Leduc" <[email protected]> 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 dimension? >> >> >> On Thu, Jun 11, 2015 at 1:46 PM, Jon Katz <[email protected]> wrote: >>> >>> 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 >>> >>> On Fri, Jun 5, 2015 at 12:28 PM, Dan Andreescu <[email protected]> >>> wrote: >>>> >>>> On Fri, Jun 5, 2015 at 3:09 PM, Oliver Keyes <[email protected]> >>>> 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: >>>>> >>> >>>>> >>> 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? >>>> >>>> >>>> Jon, we chose to not include that information in order to limit the >>>> amount of data that we'd have to deal with. If it gets too large, it won't >>>> fit into PostgreSQL. For the iOS / Android and beta / alpha versions of >>>> the >>>> site we can either: >>>> >>>> * 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. >>>> >>>> _______________________________________________ >>>> Analytics mailing list >>>> [email protected] >>>> https://lists.wikimedia.org/mailman/listinfo/analytics >>>> >>> >>> >>> _______________________________________________ >>> Analytics mailing list >>> [email protected] >>> https://lists.wikimedia.org/mailman/listinfo/analytics >>> >> >> >> _______________________________________________ >> Analytics mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/analytics >> > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics > -- Oliver Keyes Research Analyst Wikimedia Foundation _______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
