689086 - integrate webtrends with bugzilla.mozilla.org

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Extensions, enhancement)

Description

[:glob ✱]

is there a facility which provides a breakdown on the web traffic bmo is serving?

i'm after information like visitor counts, browser information, .. all the usual data which most web server log analyzers generate.

eg. the sort of reports which piwik generates.

Comment 1

[:glob ✱]

in my intranet travels i stumbled across webtrends, which may be suitable.
i'm waiting for a webtrends account so i can evaluate it.

Comment 2

[David Lawrence [:dkl]]

(In reply to Byron Jones ‹:glob› from comment #1)
> in my intranet travels i stumbled across webtrends, which may be suitable.
> i'm waiting for a webtrends account so i can evaluate it.

Link to creating a new account for myself as well?

dkl

Comment 3

[:glob ✱]

webtrends is definitely what i had in mind, morphing bug.

Comment 4

[Daniel Einspanjer [:dre] [:deinspanjer]]

piwik uses JS or image tagging which is the same as what Webtrends supplies.  In order to get webtrends integrated, changes would have to be made to the bugzilla webapp templates.

Metrics maintains a small instance of awstats which provides simple weblog only based metrics.  It does include visitor, session, entry/exit, and browser info.  Would you like to explore that rather than going the route of webtrends integration?

Comment 5

[:glob ✱]

(In reply to Daniel Einspanjer :dre [:deinspanjer] from comment #4)
> piwik uses JS or image tagging which is the same as what Webtrends supplies.
> In order to get webtrends integrated, changes would have to be made to the
> bugzilla webapp templates.

yup, that's what this bug is now about :)  i've generated sample code for another site and it looks trivial to deploy.

> Metrics maintains a small instance of awstats which provides simple weblog
> only based metrics.  It does include visitor, session, entry/exit, and
> browser info.  Would you like to explore that rather than going the route of
> webtrends integration?

thanks... the preference at this stage is to use webtrends; let's consider awstats a fallback :)

Comment 6

[Daniel Einspanjer [:dre] [:deinspanjer]]

Attachment: Pentaho Data Integration script to map names from AMO hosted add-ons

Can only be run with PDI.  Here just for safe keeping

Comment 7

[Daniel Einspanjer [:dre] [:deinspanjer]]

Comment on attachment 570758 [details]
Pentaho Data Integration script to map names from AMO hosted add-ons

D'oh!  Attached to the wrong bug.  Please disregard.

Comment 8

[:glob ✱]

bmo has been added to webtrends \o/

we need to add the tracking code to the footer.  the sample code provided (bug 698329 comment 2) doesn't use https to deliver the script, which triggers 'mixed content' warnings in firefox (ensure security.warn_viewing_mixed is enabled).  unfortunately the certification on mozcom-cdn isn't valid for our domain so we can't simply use https.

the simple fix is to keep a local mirror of the script and serve it from bmo.

Comment 9

[:glob ✱]

Attachment: patch v1

this adds webtrends as per dkl's original patch, with the following differences:
  - the webtrends javascript is being served from bmo rather than cdn
  - enable webtrends on the production site only

in order to keep our mirror up to date, i've scheduled a simple notification script on my dev box (http://glob.pastebin.mozilla.org/1377786).

Comment 10

[David Lawrence [:dkl]]

Comment on attachment 573096 [details] [diff] [review]
patch v1

Review of attachment 573096 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks for catching the errors with my previous commit. This looks better and works as expected. r=dkl

Comment 11

[:glob ✱]

Committing to: bzr+ssh://[e-mail]/bmo/4.0/
added extensions/BMO/template/en/default/hook/global/footer-end.html.tmpl
added extensions/BMO/web/js/webtrends.js
Committed revision 7935.

Comment 12

[Dave Miller [:justdave]]

This got cleared with infrasec/privacy, right?  Anything that provides additional tracking of users needs to get cleared before it's deployed.

Comment 13

[:glob ✱]

(In reply to Dave Miller [:justdave] from comment #12)
> This got cleared with infrasec/privacy, right?  Anything that provides
> additional tracking of users needs to get cleared before it's deployed.

no; you're the first person to make me aware of this requirement.  i'll follow this up.

Comment 14

[:glob ✱]

backed out:

Committing to: bzr+ssh://[e-mail]/bmo/4.0/
deleted extensions/BMO/template/en/default/hook/global/footer-end.html.tmpl
Committed revision 7937.

i have emailed the privacy team.

mcoates has said there's no need for a security review for this:
<glob> mcoates, i didn't think a sec review was required as we're not adding any code that isn't already in use (it's just the standard webtrends javascript thing)
(discussion snipped)
<mcoates> glob: you are correct. just touch base with privacy

Comment 15

[Tom Lowenthal]

No privacy concerns with this. Since bugzilla uses the Mozilla privacy policy, there's no privacy blocker here.

Comment 16

[David Lawrence [:dkl]]

Cool So I assume glob can put this back in now then and we can go live with this feature.

dkl

Comment 17

[:glob ✱]

thanks tom :)

Committing to: bzr+ssh://[e-mail]/bmo/4.0/
added extensions/BMO/template/en/default/hook/global/footer-end.html.tmpl
Committed revision 7956.