Closed
Bug 1381487
Opened 8 years ago
Closed 8 years ago
Verify the impact of the 'new-profile' ping on Release
Categories
(Toolkit :: Telemetry, enhancement, P3)
Toolkit
Telemetry
Tracking
()
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| firefox57 | --- | fix-optional |
People
(Reporter: Dexter, Unassigned)
References
Details
(Whiteboard: [measurement:client])
Once the new-profile ping hits Release (2nd of August, 2017), we need to check:
- what's the volume we're seeing?
- do we have to turn it off?
- should we consider enabling the shutdown pingsender from the first session?
|
Reporter | |
Updated•8 years ago
|
|
||
Comment 1•8 years ago
|
||
Is this something we should track at this point?
status-firefox57:
--- → fix-optional
Flags: needinfo?(alessio.placitelli)
|
|
Reporter | |
Comment 2•8 years ago
|
||
(In reply to Georg Fritzsche [:gfritzsche] from comment #1)
> Is this something we should track at this point?
Nope, this was handed over and we should not do that anymore.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(alessio.placitelli)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•