Closed
Bug 1587838
Opened 6 years ago
Closed 5 years ago
Add an expiry to custom pings
Categories
(Data Platform and Tools :: Glean: SDK, defect, P3)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: janerik, Unassigned)
References
Details
(Whiteboard: [telemetry:glean-rs:backlog])
We might want custom pings to have an explicit expiry just the same as metrics do.
This is mentioned in the docs:
In addition to these parameters, pings also support the parameters related to data review and expiration defined in common metric parameters: [...]
but was never implemented.
| Reporter | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:backlog]
Comment 2•5 years ago
|
||
I'd say we should carefully discuss this before implementing this. See bug 1548129.
"""
The concept of "disabled" or "expired" pings might have other implications and open up other bugs. For example, what if we collect more than 500 events on a disabled ping. Would they ever be cleared, or just fill up disk indefinitely?
"""
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•