Closed Bug 956060 Opened 11 years ago Closed 11 years ago

Fix missing raw Thunderbird telemetry data

Categories

(Webtools Graveyard :: Telemetry Server, defect)

Product:
Webtools Graveyard
Component:
Telemetry Server
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mreid, Assigned: mreid)

References

Details

Find out why Thunderbird data is missing for the usual channels and fix it.
Assignee: nobody → mreid
I checked a sample of ~250,000 incoming records and didn't see any sign of submissions from Thunderbird. From reading the source, it looks like it should be submitting the same way as Firefox et al, so time to install Thunderbird and see what's up.
Please try latest nightly - there's a switch that probably should have been enabled a while ago that we've only just enabled again. The latest mac & linux builds should have it.
There are a few records coming in for the latest Nightly (from build 20140102030202), and I've confirmed that the data is making its way to long-term storage. I also confirmed the following from a release build (Thunderbird 24.2.0) on my own machine: 1. Forcing a "test-ping" submission to a local webserver works as expected. 2. Forcing a test submission direct to one of the web heads out in the world works as expected. 3. Forcing a test submission to the AWS Load balancer (incoming.telemetry.mozilla.org) works as expected. 4. Forcing a test submission to data.mozilla.com (which should relay over to incoming.telemetry.m.o at the ZLB level) does NOT work. There may be a Zeus rule that skips these test submissions, but I'm still verifying that theory.
#4 is an unrelated problem and will be fixed by bug 956137. A test ping to data.mozilla.com works as expected with the temporary work around currently in place for that bug. So we should be in good shape data-wise as long as Thunderbird is submitting it should be.
Depends on: 956137
Data is being saved for recent nightly builds - I still don't see any incoming data for the release channel, but per Comment 2 it seems like that's a problem on the client and not with the server/storage end.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.