Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Address notification email in metrics.yaml #1157

Closed
boek opened this issue Mar 22, 2019 · 5 comments
Closed

Address notification email in metrics.yaml #1157

boek opened this issue Mar 22, 2019 · 5 comments
Assignees
Milestone

Comments

@boek
Copy link
Contributor

boek commented Mar 22, 2019

Our initial batch of metrics will stop collecting next March. We should add an appropriate email to be notified or come up with another way to track renewing them.

┆Issue is synchronized with this Jira Task

@Dexterp37
Copy link
Contributor

Hey @boek ! I think this is important and not only about the metric expiration itself: this will be the advertised email for the "contact point" in the probe dictionary. Moreover, that's also used by data-stewards to verify, in the future, that the data is still useful/needed.

@vesta0 vesta0 added the P1 Current sprint label Apr 3, 2019
@vesta0 vesta0 added this to the MVP Backlog milestone Apr 3, 2019
@boek
Copy link
Contributor Author

boek commented Apr 3, 2019

@bbinto We need a product email to put here :)

@bbinto
Copy link
Contributor

bbinto commented Apr 4, 2019

@liuche any idea based on your previous knowledge?

Should we create an internal fenix-telemetry email list?

@liuche
Copy link
Contributor

liuche commented Apr 4, 2019

These emails shouldn't be incredibly intrusive, and the goal is to create a regular checkin for Product, both to a) be refreshed on what probes are being collected, because it's likely there are a lot of probes, b) reaffirm that those are still useful, not redundant, still relevant.

To that end, I'd suggest including an existing mailing list, that all Product will already be on, that can include a bigger group as well. The risk with a new mailing list is that there are already so many mailing lists for new people to be added to, that it risks being missed.

On the other hand, if there's a mailing list where the team is already receiving updates on telemetry, or crashes, that could be another good candidate.

The goal here though is for the Product owners to be seeing and choosing to refresh (or remove) probes as their expiry comes up.

@bbinto
Copy link
Contributor

bbinto commented Apr 8, 2019

Thanks @liuche - let's use fenix-core@mozilla.com

boek added a commit to boek/fenix that referenced this issue Apr 8, 2019
@ghost ghost assigned boek Apr 8, 2019
@ghost ghost added review and removed P1 Current sprint labels Apr 8, 2019
@ghost ghost removed the review label Apr 8, 2019
@data-sync-user data-sync-user changed the title Address notification email in metrics.yaml FNX2-16561 ⁃ Address notification email in metrics.yaml Aug 1, 2020
@data-sync-user data-sync-user changed the title FNX2-16561 ⁃ Address notification email in metrics.yaml FNX3-14734 ⁃ Address notification email in metrics.yaml Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX3-14734 ⁃ Address notification email in metrics.yaml FNX-4834 ⁃ Address notification email in metrics.yaml Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX-4834 ⁃ Address notification email in metrics.yaml FNX2-16561 ⁃ Address notification email in metrics.yaml Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX2-16561 ⁃ Address notification email in metrics.yaml Address notification email in metrics.yaml May 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants