703018 - Get topcrashes and reports for nightly-* development branches

Status: RESOLVED FIXED

(Socorro :: General, task, P1)

Description

[Robert Kaiser]

We tend to have longer-term development branches with "nightly-*" release channels for which we'll want to have topcrash and crash rate information for investigating specifics of them and for comparing to the standard "nightly" channel.

Right now, we are counting all nightly* versions together, but when this is being solved, we should do separate reports for each of those.

At the moment, this concerns nightly-ux, nightly-jaegermonkey, nightly-ash, nightly-elm and for Fennec nightly-birch. Even if the latter will go away once it's merged to mozilla-central (hopefully soon), this will come up again and again with other branches in the future, so we should have this in the middle to long term.

Comment 1

[Robert Kaiser]

With B2G, the request also comes up to be able to get separate reports for release-* vendor channels where needed.

Comment 2

[Robert Kaiser]

(In reply to Robert Kaiser (:[e-mail]) from comment #1)
> With B2G, the request also comes up to be able to get separate reports for
> release-* vendor channels where needed.

For that case, I'm adding this to the B2G crash report tracker - if we end up doing that case in a different bug, let's move the dependency there.

Comment 3

[Laura Thomson :laura]

Adrian: can we do this with ElasticSearch?

Comment 4

[[DEACTIVATED] Adrian Gaudebert]

Last time I tried, I came to the conclusion that doing topcrashes with elasticsearch was a bad idea. We might want to think about it again, I know some important features were added to ES that could be useful in this case. 

This is going to take a long time though, there is nothing like topcrashes in Socorro right now.

Comment 5

[Robert Kaiser]

(In reply to Adrian Gaudebert [:adrian] from comment #4)
> This is going to take a long time though, there is nothing like topcrashes
> in Socorro right now.

Not sure what you mean, as the search interfaces right now gives us a topcrash-style output, and that's all we're looking for here.

Comment 6

[[DEACTIVATED] Adrian Gaudebert]

(In reply to Robert Kaiser (:[e-mail]) from comment #5)
> (In reply to Adrian Gaudebert [:adrian] from comment #4)
> > This is going to take a long time though, there is nothing like topcrashes
> > in Socorro right now.
> 
> Not sure what you mean, as the search interfaces right now gives us a
> topcrash-style output, and that's all we're looking for here.

As far as I remember (which means not very far as it was a long time ago), search and topcrashes are very different algorithms. But I might be wrong. I'll take this as a priority after AutomaticEmails and ES indexing.

Comment 7

[Robert Kaiser]

(In reply to Adrian Gaudebert [:adrian] from comment #6)
> As far as I remember (which means not very far as it was a long time ago),
> search and topcrashes are very different algorithms.

They might be generated a lot differently, but they end up matching very largely, just that the topcrash report is easier on the server due to being a matview (but then, search has the upside of giving more current information with flexible criteria). We expect that for the time being, Firefox OS will be a small enough data set that views like what we want here or in bug 832362 will not be too straining on the server side when just being offered via search.

Comment 8

[[DEACTIVATED] Adrian Gaudebert]

This is now possible with supersearch. For example: https://crash-stats.mozilla.com/search/?product=Firefox&release_channel=nightly&release_channel=ux&_facets=signature&_facets=release_channel

The "Crash Reports" tab shows all individual reports, the "Signature facet" tab shows top signatures.