Closed
Bug 1109170
Opened 10 years ago
Closed 8 years ago
Google Analytics for moztrap
Categories
(Mozilla QA Graveyard :: MozTrap, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: peterbe, Assigned: peterbe)
References
Details
Let's add Google Analytics to Moztrap so we can see where the traffic is happening.
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Comment 2•10 years ago
|
||
First part done
https://github.com/mozilla/moztrap/commit/7a6f193f9b3ccda39f34a61c09cf20feca83ef79
Now we just need to the AJAX.
Assignee: nobody → peterbe
Status: NEW → ASSIGNED
I'm a bit ignorant about Google Analytics and the data that you can pull from it.
Does this take in any account on how long someone stays/gets stuck on a page?
The reason I ask is because there are some sporadic events (based on user flow) such as test suite creation that may not necessarily have a lot of traffic, but have performance and usability issues.
The other thought is that for the people that use it a lot they got trained not to use some of the functions because they are way too slow or too buggy. Example : I stopped using the "make shift" import because it was too buggy.
Assignee | ||
Comment 4•10 years ago
|
||
PR https://github.com/mozilla/moztrap/pull/81
cmore, can you check the event strings are good?
Flags: needinfo?(chrismore.bugzilla)
Assignee | ||
Comment 5•10 years ago
|
||
Naoki,
The things we can get:
* URLs that get hit a lot
* AJAX requests that get hit a lot
* How much traffic comes from Asia (might motivate use to set up a CDN for static assets)
I know it is possible but perhaps something we do later, to tell GA to track how long certain pageloads take to load. And perhaps with that we can try to track how long AJAX events take too.
Mass-closing remaining MozTrap bugs as WONTFIX, due to 1) the Mozilla-hosted instance being decommissioned (see https://wiki.mozilla.org/TestEngineering/Testrail), and, for now, 2) the still-up code archived at its GitHub page: https://github.com/mozilla/moztrap (we'll decide what's next for that, in the near future).
See also the history and more-detailed discussion which led us here, at https://groups.google.com/forum/#!topic/mozilla.dev.quality/Sa75hV8Ywvk
(If you'd like, you should be able to filter these notification emails using at least the unique string of "Sa75hV8Ywvk" in the message body.
Thanks!
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•