CloudFront was serving stale data, it's fixed now. Give it another try?
On Tuesday, July 7, 2015 at 3:06:45 PM UTC-4, Boris Zbarsky wrote:
> On 7/7/15 2:26 PM, Vladan Djeric wrote:
> > Let us know if you find bugs, notice missing functionality, or if anything
> > is ambiguous or counter-intuitive.
*The stale file issues are fixed, please try out the new dashes!*
https://telemetry.mozilla.org/
CloudFront was serving stale data and we needed to invalidate its caches
(and give it enough time to complete the invalidations).
On Tue, Jul 7, 2015 at 3:15 PM, Vladan Djeric wrote:
> It looks lik
It looks like there is some kind of bug with propagating the changes to the
(static) dashboard files in S3, somehow causing the old dash to be shown at
telemetry.mozilla.org for some users. Others are reporting dashes that
don't load.
Apologies for the (very embarassing) technical difficulties. I'l
On 7/7/15 2:26 PM, Vladan Djeric wrote:
Let us know if you find bugs, notice missing functionality, or if anything
is ambiguous or counter-intuitive.
When I first load https://telemetry.mozilla.org/ it says, in the console:
ReferenceError: CustomSelector is not defined dashboard.js:674:5
an
We noticed a lot of Mozillians struggle to use the Telemetry dashboards
effectively. It can be difficult to interpret the graphs & numbers, hard to
find or filter the data, and there is a risk of making the wrong
conclusions. The dashboards needed an overhaul.
Anthony Zhang, our summer intern, has
5 matches
Mail list logo
