Closed Bug 399869 Opened 18 years ago Closed 17 years ago

Demonstrate a working metrics extension

Categories

(Toolkit Graveyard :: Data Collection/Metrics, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: alex, Unassigned)

References

()

Details

bug 393881 proposes a fix for updating the metrics extension to trunk. Once in trunk, we need to confirm that the extension works. To accomplish this, a simple backend will need to be implemented. The most basic purpose of the backend is to provide a config to the extension. Upon initialization of the extension, it will ping the server for a config. An example config from the server is given here: http://mxr.mozilla.org/seamonkey/source/extensions/metrics/src/nsMetricsConfig.cpp#128 A server response of 200, along with a valid config, should be enough to get the extension to start collecting information. Full details of the server/extension interaction can be found here: http://mxr.mozilla.org/seamonkey/source/extensions/metrics/src/nsMetricsService.cpp#667 Once it is working, a call to about:metrics should display what has been collected since it was last uploaded. Example output from about:metrics is a good enough demonstration that it works as expected.
I got it to work! The config I used can be found here: http://polvi.net/~polvi/metrics/ To test, add "ac_add_options --enable-extensions=metrics" to your mozconfig, then after it is built, change the "metrics.upload.uri" pref to that polvi.net url, and finally set the metrics.upload.enable pref to "true". I built with a MOZILLA_1_9a8_RELEASE client.mk... it does not, however, work with M8 downloaded from an ftp mirror. Debugging output is showing assertion errors parsing the config, not sure what is up. From about:metrics : <log version="2" clientid="bQYUeSd3XK8zJxRT4Y+8EA=="> − <profile time="1192656598" session="8"> <cpu arch="x86"/> <os version="8.10.1" name="Darwin"/> <install installdate="1192579200" default="true" buildid="2007101711"/> − <extensions> <extension extensionid="uNC/2/DnFvZumtt5pS3lyA==" version="1.9a8"/> </extensions> − <plugins> <plugin filename="bvWog2Dc136UMPLRRI8KPw==" name="kEynWHadwOx2MjcAVqH/fg=="/> <plugin filename="9CJqaKyFudrPV3T3C4fLYQ==" name="5TdsXcFyg4G+LskE6g6EJA=="/> <plugin filename="gBJjAI/CnGE/TprJW6oqrw==" name="2x6X/43GhfEjcF3ilVqpcg=="/> <plugin filename="9j2N8julsDY5lYP9hD8AuQ==" name="nfGm7uk2q0xBpC3X5CA95A=="/> <plugin filename="bJWrgIKqSJIuivoSwU6mRQ==" name="+E00XUow3cubD9l6AE4Dkg=="/> <plugin filename="BtOsPZr5RzgVmUFYLc24pQ==" name="84Dey2U5UFajBYWVs62MnA=="/> <plugin filename="y0AINhD7Z3ubsu2sNC+qhQ==" name="l6JHR+3K7GRvMs+hSWWp1w=="/> </plugins> <display ysize="900" xsize="1440" screens="2"/> − <bookmarks> <bookmarklocation foldercount="4" itemcount="6" separatorcount="2" livemarkcount="1" name="full-tree"/> <bookmarklocation foldercount="2" itemcount="1" separatorcount="2" livemarkcount="0" name="root"/> <bookmarklocation foldercount="0" itemcount="1" separatorcount="0" livemarkcount="1" name="toolbar"/> </bookmarks> </profile> <uielement targetidhash="x3sZiMpvdX+CG64ivccpTg==" action="command" window="1" time="1192656603" session="8"/> <window action="create" windowid="3" parent="1" time="1192656603" session="8"/> <document memresident="59105280" origin="typed" action="load" window="3" loadtime="160" docid="0" memtotal="1960747008" time="1192656603" session="8"/> </log> ... here is some more output of what happens when I click reload a bunch of times on the about:metrics window: <log version="2" clientid="/luV/uU1UTMaMDLdtOw6uw=="> <document memresident="70008832" origin="reload" action="load" window="3" loadtime="63" docid="100" memtotal="1983287296" time="1192658581" session="0"/> <document memresident="70045696" origin="reload" action="load" window="3" loadtime="52" docid="101" memtotal="1983287296" time="1192658582" session="0"/> <document memresident="70860800" action="destroy" window="3" docid="99" memtotal="1984077824" time="1192658583" session="0"/> <document memresident="70860800" action="destroy" window="3" docid="100" memtotal="1984077824" time="1192658583" session="0"/> <document memresident="70074368" origin="reload" action="load" window="3" loadtime="63" docid="102" memtotal="1983287296" time="1192658583" session="0"/> <document memresident="70086656" origin="reload" action="load" window="3" loadtime="61" docid="103" memtotal="1983287296" time="1192658585" session="0"/> <document memresident="70873088" action="destroy" window="3" docid="102" memtotal="1984077824" time="1192658585" session="0"/> <document memresident="70873088" action="destroy" window="3" docid="101" memtotal="1984077824" time="1192658585" session="0"/> <document memresident="70090752" origin="reload" action="load" window="3" loadtime="72" docid="104" memtotal="1983287296" time="1192658586" session="0"/> </log>
btw, I'm not resolving this because it is not yet working with nightlies...
Here is what some uicommand data looks like: <log version="2" clientid="/luV/uU1UTMaMDLdtOw6uw=="> <uielement targetidhash="sXsjfiH1XCNLtYRKWGBFIg==" action="command" window="0" time="1193781701" session="1"/> <uielement targetidhash="sXsjfiH1XCNLtYRKWGBFIg==" action="command" window="0" time="1193781701" session="1"/> <uielement targetidhash="sXsjfiH1XCNLtYRKWGBFIg==" action="command" window="0" time="1193781764" session="1"/> <uielement targetidhash="sXsjfiH1XCNLtYRKWGBFIg==" action="command" window="0" time="1193781767" session="1"/> <uielement targetidhash="9SZovgxhLNvCve0WXSRvlg==" action="command" window="0" time="1193781768" session="1"/> <uielement targetidhash="x3sZiMpvdX+CG64ivccpTg==" action="command" window="0" time="1193782957" session="2"/> <uielement targetidhash="fgKIKfJEiGq5arJfJCcOSQ==" action="command" window="0" time="1193782961" session="2"/> <uielement targetidhash="fgKIKfJEiGq5arJfJCcOSQ==" action="command" window="0" time="1193782962" session="2"/> </log>
Fixed? Its on AMO now.
OS: Mac OS X → All
Hardware: PC → All
Version: unspecified → Trunk
(In reply to comment #4) > Fixed? Its on AMO now. > Woot, yep!
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.