Migrate Legacy Telemetry Environment `system` fields to Glean metrics
Categories
(Toolkit :: Telemetry, task)
Tracking
()
People
(Reporter: chutten, Assigned: chutten)
References
Details
(Whiteboard: [fog-migration])
Attachments
(1 obsolete file)
This bug is for defining and using Glean metrics to mirror Legacy Telemetry Environment fields in the system
section (but not its subsections, which have their own bugs). The fields and their needs are:
memoryMB - needs migration
virtualMaxMB - needs migration
isWow64 - needs migration
isWowARM64 - needs migration
hasWinPackageId - needs migration
winPackageFamilyName - needs migration
appleModelId - needs migration
" needs migration" means that the field must be either:
- removed (if you know that a field is unused or not useful, or can find an authority who can assert that), or
- have a Glean metric defined for it in an appropriate
metrics.yaml
in an appropriate component in the tree and instrumentation code added inTelemetryEnvironment.sys.mjs
so that it begins reporting data
Remember to update the totals for fields you migrate.
Updated•6 months ago
|
Assignee | ||
Comment 1•4 months ago
|
||
Updated•4 months ago
|
Comment 3•3 months ago
|
||
Backed out for causing xpcshell failures in /test_TelemetryEnvironment_search.js.
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | toolkit/components/telemetry/tests/unit/test_TelemetryEnvironment_search.js | xpcshell return code: 0
Assignee | ||
Comment 4•3 months ago
|
||
Apparently I missed a part where isWow64
is set, whoops. win32-on-win64 doesn't appear to be a build that I can select with try chooser
so I missed it.
Assignee | ||
Updated•3 months ago
|
Updated•3 months ago
|
Description
•