Closed Bug 649432 Opened 9 years ago Closed 9 years ago

Make build channels available in Socorro

Categories

(Socorro :: General, task)

task
Not set

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: kairo, Assigned: laura)

References

Details

Attachments

(1 file)

We ended up selecting a versioning scheme where beta and release can not be told apart by version, so we'll need to get the channel into crash-stats. Bug 649419 is filed on the Breakpad side, we'll need to care to get this information into Socorro once it's coming in from there.
Actually, gavin says in bug 649419 that this actually was already implemented in bug 526623 - if that's true, all that was and is still missing is the Socorro side!

Can someone verify that crash reports coming in actually do have a "ReleaseChannel" annotation that tells us the channel?
(In reply to comment #2)
> Actually, gavin says in bug 649419 that this actually was already implemented
> in bug 526623 - if that's true, all that was and is still missing is the
> Socorro side!
> 
> Can someone verify that crash reports coming in actually do have a
> "ReleaseChannel" annotation that tells us the channel?

I chose some random crash IDs in production and found this in the raw JSON in HBase (which is where the data received by the breakpad HTTP POST is stored):

"ReleaseChannel": "release"
"ReleaseChannel": "beta"
etc.

I don't see this in the processed report.
Depends on: 526623
No longer depends on: 649419
As a further note how we might want to use that code:

From bug 526623 comment #0:
> Doing so would allow us to easily process 100% of crash reports for users
> during the maintenance release beta periods we have. Otherwise, we'll have to
> unthrottle then re-throttle all the time.

Note that the latter is what is happening nowadays...

Also, we'd love to have that field in the CSVs so any experiments we do based on those can easily filter for the channel.
Lars, can you please take the first part of this (getting it into the processed json) and then throw it back to me?
Target Milestone: --- → 1.7.8
So we'll need to add this column to the PG database as well, in some form.
I have checked in a change that makes the processors copy the "ReleaseChannel" from the raw json into the processed json.  This is checked into trunk.
I'll get this into the UI.  Will put this into 1.7.7 branch for a .x release.
Assignee: nobody → laura
Target Milestone: 1.7.8 → 1.7.7
Laura: A question came up in the beta meeting - after this change is made will we able to capture crashes that have already happened with Firefox 5 Beta 1? 

I have already created a 5.0b1 entry in the Socorro UI.
Assignee: laura → nobody
Target Milestone: 1.7.7 → 1.7.8
Those crashes will never show up as 5.0b1, since their version is being sent as 5.0. If we need to display them differently somehow, we'll need to sort out the details first and then file another bug to implement that. This sounds like something that ought to be hashed out at a planning meeting first.
I say we focus on getting all future crash reports in the right place then we can talk about the old data. For now it's probably just QA so in my opinion it would not be catastrophic if we didn't get these reports.

Laura, if we put this into 1.7.7 branch, when would it go out?
The change we're talking about here is just adding the ReleaseChannel information to the UI for an individual crash, but I see the need to get the data sliced by channel.  Adding this one piece of data is something we can ship as a dot release, probably even this week.
  
Sheila or Marcia: can you specify exactly what you want?  Hard to know how long the other stuff is going to take when I'm not sure of the scope yet.
Laura: Right now our most urgent need is to be able to search in the UI for 5.0b1 crash reports (because the version is being sent as 5.0). Would you like me to file a new bug for that?
Marcia: yes please!
Marcia, you could do an advanced search and filter on the buildID of 20110427143820. For the last few releases all the platforms have had the same buildID.

Hopefully there is a bug elsewhere on this, but what Ted says in comment #10 is absolutely right. With several sets of builds reporting with version 5.0, we have to use update channel *and* buildID to tell between them. ie if you want to know how crashy each set of builds on the beta channel is, compared to the previous ones.
This just passes it through to an individual crash report display in the webapp.
Depends on lars' commits in trunk, r3127 and r3128.
Assignee: nobody → laura
Attachment #529989 - Flags: review?(rhelmer)
Also, I had a phone conversation with Marcia and Sheila yesterday about this, outcomes as follows:
- QA will use the advanced search as a temporary measure
- I needed to check if ADUs were available by buildid and apaprently they are. I don't think we have them this way in Socorro (yet).
- Longer term, we'll need to slice by version + buildid  for betas and final releases, and version alone for Aurora and Nightlies.
- The betas and final reports may be easy to pull out with ElasticSearch.

We'll merge this bug to 1.7.7 branch, tag it as 1.7.7.1 and push it out ASAP (today preferably).
Attachment #529989 - Flags: review?(rhelmer) → review+
That should be 1.7.7.2, btw.

Committed to trunk:
Sending        webapp-php/application/libraries/CrashReportDump.php
Sending        webapp-php/application/views/report/index.php
Transmitting file data ..
Committed revision 3137.

Lars, can you merge your changesets above to the release branch please?
http://socorro.googlecode.com/svn/branches/1.7.7/
Make that branches/releases/1.7.7.
my changes are now checked into branches/releases/1.7.7
Committed revision 3138.
(In reply to comment #17)
> - Longer term, we'll need to slice by version + buildid  for betas and final
> releases, and version alone for Aurora and Nightlies.

FWIW, I think it would be useful to slice aurora & nightly by buildid too, so we can easily say <this> nightly is really crashy and this <this later one> is better. Feel free to point me to a more appropriate place to discuss this :-)
Merged changes in revisions 3138, 3139, 3140.

To test, we'll need to submit a few crashes to staging for processing, and then
put the OOIDS in here so QA can look.  Jabba/Rhelmer, can you push some crashes
for us?

Nick: we should spin a tracker bug off for other changes.
QA verified. Both Aurora and Beta channels are being marked as such in the crash reports.

Aurora Channel
https://crash-stats.allizom.org/report/index/3cf4e0b3-9cc1-42e9-b7b1-ab2972110504
Beta Channel:
https://crash-stats.allizom.org/report/index/2910c3a5-3fd9-4201-8a41-5457b2110504
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
(In reply to comment #23)
> QA verified. Both Aurora and Beta channels are being marked as such in the
> crash reports.
> 
> Aurora Channel
> https://crash-stats.allizom.org/report/index/3cf4e0b3-9cc1-42e9-b7b1-ab2972110504
> Beta Channel:
> https://crash-stats.allizom.org/report/index/2910c3a5-3fd9-4201-8a41-5457b2110504

...and "release": https://crash-stats.allizom.org/report/index/80759c44-edeb-48f7-91f0-206892110504
Status: RESOLVED → VERIFIED
Thanks mbrandt/stephend!

Since we're doing Hbase maintenance this evening, we are going to push this live tomorrow morning.
Thanks for the great assist :) What time is this being pushed? I want to be online.
Blocks: 655067
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.