Closed
Bug 1331005
Opened 7 years ago
Closed 7 years ago
get_pings_properties doesn't work for filtering GPU process histograms
Categories
(Data Platform and Tools :: General, defect, P1)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gw280, Assigned: gw280)
References
Details
Attachments
(1 file, 1 obsolete file)
e.g. GPU_PROCESS_INTIIALIZATION_TIME_MS. I think GPU stuff needs to be handled here: https://github.com/mozilla/python_moztelemetry/blob/master/moztelemetry/spark.py#L251, like: children += [_get_ping_property(child, path, histograms_url, additional_histograms) \ for child in cursor.get("gpu", {})]
Assignee | ||
Updated•7 years ago
|
Blocks: e10s-gpu-win
Updated•7 years ago
|
Component: Telemetry → Metrics: Pipeline
Product: Toolkit → Cloud Services
Assignee | ||
Comment 1•7 years ago
|
||
For now it works if you do: histograms = get_pings_properties(pings, "payload/processes/gpu/histograms/GPU_PROCESS_INITIALIZATION_TIME_MS")
Assignee | ||
Comment 2•7 years ago
|
||
This patch should work. The only thing I'd want to question is whether we'd want to aggregate the content and gpu histograms under HISTOGRAM_children or have separate HISTOGRAM_content and HISTOGRAM_gpu containers.
Comment 3•7 years ago
|
||
Updated•7 years ago
|
Attachment #8827565 -
Attachment is obsolete: true
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → gwright
Updated•7 years ago
|
Priority: -- → P1
Updated•7 years ago
|
Whiteboard: [fce-active]
Updated•7 years ago
|
Component: Metrics: Pipeline → Telemetry APIs for Analysis
Product: Cloud Services → Data Platform and Tools
Updated•7 years ago
|
Whiteboard: [fce-active]
Comment 4•7 years ago
|
||
Mauro, it looks like the PR here has been merged, can we close this bug?
Flags: needinfo?(mdoglio)
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(mdoglio)
Resolution: --- → FIXED
Comment 5•7 years ago
|
||
Please reopen if this bug needs more work.
Updated•2 years ago
|
Component: Telemetry APIs for Analysis → General
You need to log in
before you can comment on or make changes to this bug.
Description
•