The problem with bugs is that ...the later you find them the harder they bite your ass. I won't talk about bugs because you don't talk bad about the dead :p
Telemetry Dashboards measure how Firefox behaves on desktop and mobile in real world use.This application provides the aggregate view of the data collected.
One can hit http://telemetry.mozilla.org/ in three ways:
- request for default page (no cookie set)
- request with cookie set (cookie expiration 3 days)
- request for specific state (aka url encoding a particular state)
The page itself has two states:
Single filter (when you look for a "one at a time version plot") you get histogram/table plots and summary details.
By adding multiple filters on your plot you switch from one mode to another. If you want to get back into single mode state you just have to remove all the filters you added.
There are two ways you can use the filters:
You want all the measures to be in sync with the first filter. Whatever change made in your first filter will be propagated to the ones below. If the ones below don't have data for this particular measure they will be set to a default measure.
Use the unlock button to compare between different measures.
The filters can get very long. In some cases it doesn't make sense to show the full state because we only have one measure across multiple versions in the locked state. That's why we show the title of the measure and the details for it and simplify the legend by making it show only the versions.
In the case of mixed filters (aka unlocked state) we show only the part of the filter that fits one line, for more information you can look in the tooltip.
When you add another filter we instantiate a new selector but we don't make a request. Requests are done only if we don't have that data in the cache.
Url and TinyUrl
All the page state: filters, lock/unlock, selector state (percentiles), table/histogram are preserved in the url. This way the state gets saved for a return with state or cookie session.
The end... :)