Open rkothari19 opened 6 years ago
This is partly dependent on a better panning/zooming implementation in metrics-graphics, but yes.
Note also that "trends" would only be apparent over a longer period of time (days) -- likely something noticed over a shorter period (hours) is just a transient phenomenon, unless it's an absolutely gigantic, sustained spike.
I don't feel like this is a must before turning off awsy, as it is still possible to do basic analysis/comparisons of the rates without it. But we should get to this soon, moving this to the relman_v2 milestone.
Let's move this to the relman_v3 milestone for now, I'd like to close out relman_v2 soon and this isn't trivial to implement. If this is still really important, we can prioritize it.
metrics graphics now has brushing/zooming thanks to @cnwangjie, we just need to expose it in the react library (https://github.com/metricsgraphics/react-metrics-graphics/issues/30) and add the appropriate fields to the detail graphs.
https://missioncontrol.telemetry.mozilla.org/#/release/windows/main_crashes
Since the detail graphs are actually two different visualizations (crash rates vs. khours of usage) I think the appropriate thing to do is to use a series of callbacks to make sure that zooming one graph results in the other being zoomed too. I believe this should be possible with the various callback methods that @cnwangjie implemented.
https://data-missioncontrol.dev.mozaws.net/#/esr/mac/content_crashes - Need ability to click on individual graphs for zoomed in/better viewability of trends