Enable new Glean App `viu.politica`
Categories
(Data Platform and Tools :: Glean Platform, task, P1)
Tracking
(Not tracked)
People
(Reporter: chico, Assigned: Dexter)
Details
Attachments
(1 file, 1 obsolete file)
To be filled by the requester
Application ID*: "viu.politica.prod" and "viu.politica.dev"
Application Canonical Name: Viu Politica
Description: This is a "spin-off" of the Mozilla YouTube RegretsReporter extension. We are building an opt-in browser extension where users can anonymously tag videos related to the 2022 Brazilian Elections.
Data-review response link: https://bugzilla.mozilla.org/show_bug.cgi?id=1783726
Repository URL: https://github.com/evoluchico/viu-politica
Locations of metrics.yaml
files (can be many):
- source/telemetry/metrics.yaml
Locations of pings.yaml
files (can be many):
- source/telemetry/pings.yaml
Dependencies**:
- glean-core
Retention Days***: N
(Optional) To be filled by the requester
Does the product require end-to-end encryption in the pipeline? No
If answered yes to the above, who should be granted access to the data? N/A
Notes and guidelines
* This is the identifier used to initialize Glean (or the id used on the store on Android and Apple devices).
** Dependencies can be found in the Glean repositories. Each dependency must be listed explicitly. For example, the default Glean probes will only be included if glean itself is a dependency.
*** Number of days that raw data will be retained. A good default is 180. We can change this later to accommodate longer retention periods, though we cannot recover data that is past the retention period (for example, we cannot recover data that is 200 days old if your retention period is 180 days).
Need additional help?
If you need new dependencies, please file new bugs for them, separately from this one. For any questions, ask in the #glean channel.
To be filled by the Glean team
Application friendly name: my_app_name
The following are only required for products requiring encryption:
Document namespace: my-app-name
Please NI Operations on this bug to request the creation of encryption keys and an analysis project.
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Comment 2•3 years ago
|
||
Hey Chico!
Would you kindly clarify what "Retention Days" value you need? Here is "N" but in the PR you filed is 365.
I'd also be curious if there's any specific reason why you are using two app ids instead of a single app id with different channels (e.g. prod and dev).
Assignee | ||
Updated•3 years ago
|
Reporter | ||
Comment 3•3 years ago
|
||
Hi Alessio,
- The "Retention Days" value we need is indeed 365, not N.
- A single app with different channels is actually what we need.
Sorry for the confusion!
Assignee | ||
Comment 4•3 years ago
|
||
(In reply to Chico Camargo from comment #3)
Hi Alessio,
- The "Retention Days" value we need is indeed 365, not N.
Perfect, thanks!
- A single app with different channels is actually what we need.
Excellent! Is viu.politica
the correct app id then?
Are you setting this as the app id in the client?
Are you setting the channel (prod/dev) in Glean.initialize
?
Sorry for the confusion!
No problem at all! We're happy to help. The creation of the server-side PR is usually on the Data Org, it was a nice surprise for us seeing you going that deep :-) If you don't have time to shepherd this, after you make the client changes, please let us know and we'll deal with the PR.
Reporter | ||
Comment 5•2 years ago
|
||
(In reply to Alessio Placitelli [:Dexter] from comment #4)
Excellent! Is
viu.politica
the correct app id then?
Are you setting this as the app id in the client?
Are you setting the channel (prod/dev) inGlean.initialize
?
Yes to all. I confirm that:
- the application id is
viu.politica
, and it is set in the client prod
anddev
are set as channels in theGlean.initialize
call.
No problem at all! We're happy to help. The creation of the server-side PR is usually on the Data Org, it was a nice surprise for us seeing you going that deep :-) If you don't have time to shepherd this, after you make the client changes, please let us know and we'll deal with the PR.
I see! In that case, now that I've made the client changes, would you deal with the PR? Let me know if you need any further information.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 6•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 7•2 years ago
|
||
Hey!
I left a few comments on the new PR I created. Would you kindly address them?
Why are the generated APIs committed in the codebase?
Reporter | ||
Comment 8•2 years ago
|
||
Sure! I've just answered them there.
As to the generated APIs committed to the codebase, we just reproduced what was done in the RegretsReporter extension, that this extension is based on: https://github.com/mozilla-extensions/regrets-reporter/tree/main/source/telemetry/generated
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 9•2 years ago
|
||
The product is enabled in the pipeline: https://dictionary.telemetry.mozilla.org/apps/viu_politica
Description
•