Closed
Bug 916891
Opened 11 years ago
Closed 11 years ago
Enhance telemetry server stats graph
Categories
(Webtools Graveyard :: Telemetry Server, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mreid, Assigned: trink)
References
Details
Attachments
(1 file)
102.88 KB,
image/png
|
Details |
The attached screenshot of the current server stats graph was loaded from this URL: http://ec2-54-245-195-188.us-west-2.compute.amazonaws.com:4352/TelemetryFilter.RequestStatistics.html I'd like to add a few more things. If any of them are already available at a different URL, please point me in the right direction. Things to add: 1. Total throughput in bytes/sec (or per min) 2. Success count broken down by update channel 3. Longer views of the data, including "last week", "last month", "last year". For #2, the update channel can be extracted from the request URL (at least for requests we care about). A correct telemetry submission URL takes the form: ^/submit/telemetry/id/reason/appName/appUpdateChannel/appVersion/appBuildID$ Ideally, we'd bucket the channel the same way as in the data storage, namely [release, beta, aurora, nightly, other].
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → mtrinkala
Reporter | ||
Comment 1•11 years ago
|
||
(In reply to Mark Reid [:mreid] from comment #0) > ^/submit/telemetry/id/reason/appName/appUpdateChannel/appVersion/appBuildID$ Sorry, my bad - I have these in the wrong order. The official source of truth is: http://mxr.mozilla.org/mozilla-central/source/toolkit/components/telemetry/TelemetryPing.js#668 appVersion and appUpdateChannel should be swapped: ^/submit/telemetry/id/reason/appName/appVersion/appUpdateChannel/appBuildID$
Assignee | ||
Comment 2•11 years ago
|
||
The new plugins are up, please review http://ec2-54-245-195-188.us-west-2.compute.amazonaws.com:4352/TelemetryChannel.html We shouldn't really be storing this duration of data in the real time monitoring system (at the lower resolution it uses the same amount of memory as the daily view but it still feels wrong ;) ) http://ec2-54-245-195-188.us-west-2.compute.amazonaws.com:4352/TelemetryChannel60Days.html
Comment 3•11 years ago
|
||
This currently displays y values like 'requests' and 'total size', but doesn't make x axis clear. We should have some JS calculate per second values for the tooltip and clearly display the x dimension(in the tooltip too?).
Assignee | ||
Comment 4•11 years ago
|
||
This is not configurable in the default Heka view, however the raw data can be consumed and presented in anyway the telemetry dashboard sees fit.
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•11 years ago
|
||
Please add the plugin for the 60-day graphs (TelemetryChannel60Days) to the telemetry-server repo.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 6•11 years ago
|
||
Merged the PR that adds the 60-day graphs: https://github.com/mreid-moz/telemetry-server/pull/9
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•