- All files viewed with the media viewer are recorded by the client requesting the /beacon/media?duration=X&uri=Y URL at some point  – as Nuria points out in that thread, requests to /beacon/... are already filtered and a canned response is sent immediately by Varnish .
- Requesting a URL with the X-Analytics header  set to "preview". In this context, we'd make a HEAD request to the URL of the page with the header set.
IMO #1 is preferable from the operations and performance perspectives as the response is always served from the edge and includes very few headers, whereas the request in #2 may be served by the application servers if the user is logged in (or in the mobile site's beta cohort). However, the requests in #2 are already
We're currently considering recording page interactions when previews are open for longer than 1000 ms. We estimate that this would increase overall web requests by 0.3% .
Are there other ways of recording this information? We're fairly confident that #1 seems like the best choice here but it's referred to as the "virtual file view hack". Is this really the case? Moreover, should we request a distinct URL, e.g. /beacon/preview?duration=X&uri=Y, or should we consolidate the URLs as both represent the same thing essentially?
IRC (Freenode): phuedx