Closed
Bug 1803513
Opened 2 years ago
Closed 2 years ago
`events` ping without events should not be sent
Categories
(Data Platform and Tools :: Glean: SDK, task, P1)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Dexter, Assigned: chutten)
References
Details
Attachments
(1 file)
I noticed this while helping :daisuke (his ping). For context, all we see in that ping is this:
"metrics": {
"uuid": {
"legacy.telemetry.client_id": "--redacted client id--"
}
}
No events. For what is worth, the ping was triggered using about:glean
in Firefox Desktop, but a quick analysis from Jan-Erik identified that this specific issue is on the rise.
Assignee | ||
Comment 1•2 years ago
|
||
This is almost certainly due to bug 1800081 where legacy.telemetry.client_id
was given lifetime: application
.
I agree with the conversation on Matrix that maybe the "events" ping can be special-cased to not be sent unless there are event
metrics.
See Also: → 1800081
Updated•2 years ago
|
Component: Telemetry → Glean: SDK
Priority: -- → P3
Product: Toolkit → Data Platform and Tools
Summary: An increasing number of `events` pings with no events is being sent by Firefox Desktop → `events` ping without events should not be sent
Updated•2 years ago
|
Priority: P3 → --
Updated•2 years ago
|
Assignee: nobody → chutten
Priority: -- → P1
Comment 4•2 years ago
|
||
Assignee | ||
Comment 5•2 years ago
|
||
chutten merged PR #2301: "bug 1803513 - Do not send 'events' ping if there are no events" in 1de4660.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•