Will Lachance

Closely related to the discussion in #215. I feel like there is a higher level requirement (essentially "what is happening right now?") which we need to think about here.

Sure thing, I hesitated because I felt like the implicit requirement stated here might just be a duplicate of #215. I want to be careful about adding too much information...

I'm not sure if you can extrapolate a trend by comparing the last 24 hours versus the entire release. It could be a useful point of comparison, but it also...

See also #318. We should definitely do something here, ideally I'd like some kind of general solution that applies across the different channel types. The need to know (in general)...

We only show data for the last 3 specific releases in mission control currently: https://github.com/mozilla/missioncontrol/blob/c67a03078c02a2eb481438c99922c4d9b2103436/missioncontrol/etl/measuresummary.py#L159 If you think it would be useful to have more data, feel free to morph...

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...

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...

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...

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...

See also #150, which is more or less the same issue. Let's see if this goes away when we fix that, leaving open for now though.