Add an "app_id" field to the common information
Categories
(Toolkit :: Telemetry, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | affected |
People
(Reporter: Dexter, Assigned: Dexter)
References
Details
(Whiteboard: [telemetry:mobilesdk:m3])
Attachments
(3 files)
|
Assignee | |
Updated•6 years ago
|
|
|
Assignee | |
Updated•6 years ago
|
|
|
Assignee | |
Comment 1•6 years ago
|
||
|
||
Comment 2•6 years ago
|
||
|
|
||
Comment 3•6 years ago
|
||
In the discussion here, it was determined that the app id name must not contain any periods in order to work with the backend infrastructure. We probably should submit a PR to android-components to enforce this. I think it's reasonable to use the app store id, replacing all . with - as a default, and then validate any name that the application gives to glean explicitly.
|
||
Comment 4•6 years ago
|
||
Idle thought: Do we know whether or not we'll ever want to transform the name back? If so a different escaping scheme may be warranted to avoid something like:
org.mozilla.my-glean-app -> org-mozilla-my-glean-app -> org.mozilla.my.glean.app
|
|
Assignee | |
Comment 5•6 years ago
|
||
(In reply to Chris H-C :chutten from comment #4)
Idle thought: Do we know whether or not we'll ever want to transform the name back? If so a different escaping scheme may be warranted to avoid something like:
org.mozilla.my-glean-app -> org-mozilla-my-glean-app -> org.mozilla.my.glean.app
I didn't hear any requirement about this, so I'm assuming no. I guess that if we care that much about id/names, we can add that as a specific field to the baseline/ping_info
|
|
Assignee | |
Comment 6•6 years ago
|
||
|
|
Assignee | |
Comment 7•6 years ago
|
||
Everything was merged. Closing this.
Description
•