Closed
Bug 1505395
Opened 6 years ago
Closed 6 years ago
Add support for gathering telemetry from other libraries
Categories
(Toolkit :: Telemetry, enhancement, P3)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox65 | --- | affected |
People
(Reporter: Dexter, Assigned: mdroettboom)
References
Details
(Whiteboard: [telemetry:mobilesdk:m5])
Attachments
(1 file)
Other libraries in android-components might want to push their own telemetry to glean, having it take care of the assembly and the delivery of pings.
This bug is about investigating this possibility, kicking off a document to gather the requirements
Reporter | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → mdroettboom
Assignee | ||
Comment 1•6 years ago
|
||
:tlong made a good point elsewhere: Won't the libraries have to either try and initialize, or wait for initialization before they can do anything with Glean? I know that the init function throws an IllegalStateException but is that going to be an issue for a consuming application/library? I know that it can be handled with a try but that seems like a harsh way to indicate that the library is already initialized. Also, what happens if a library tries to initialize with a different configuration?
I would summarize this as: Make sure initialization is as straightforward and fool-proof as possible in light of the new multiple-libraries-using-glean-together world.
Reporter | ||
Updated•6 years ago
|
Whiteboard: [telemetry:mobilesdk:m4] → [telemetry:mobilesdk:m5]
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•6 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•6 years ago
|
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•