Closed Bug 1322412 Opened 5 years ago Closed 1 year ago
move crash-stats to .org
Is there a good reason not to choose one over the other and stick to it with redirects? Yak shaving, awaaaay!
Peter has said that Google Analytics does not reflect the accurate crash-stats traffic because many users use crash-stats.mozilla.org, which does not have GA enabled.
Tweaking the summary because it seemed the right thing to do at the time.
Summary: Move crash-stats to .com or .com → Move crash-stats to .com or .org
Concrete points: * Fixing this would "merge" all traffic from both domains in on Google Analytics account * There's a general common "trend" in the organization to use .org for sites/apps. E.g. sql.telemetry.mozilla.org * about:crashes has "crash-stats.mozilla.com" hardcoded * The breakpad URL uses crash-report.mozilla.com so not applicable.
We can change the in browser things, too, though it will take a long time to roll out
We don't use Google Analytics anymore, so all the GA parts of this issue are moot now. Alexis is making changes to about:crashes, so we could take this opportunity to switch those urls from .com to .org. If we do that, our plan should be "we're done with crash-stats.mozilla.com in 2 years" or something similar, but it has to be with conviction. I'm +1 on switching to crash-stats.mozilla.org with conviction. Is there a good reason not to?
+1 The URL in Breakpad can be changed too but it'll take a few years until the .com dies out.
breakpad uses crash-reports.mozilla.com. I think we should spin changing that to a different bug since we can do it independently and it involves a bunch of different non-overlapping work.
Priority: -- → P3
Summary: Move crash-stats to .com or .org → move crash-stats to .org
Assignee: nobody → bpitts
Component: Infra → Operations: Socorro
Product: Socorro → Cloud Services
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.