-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Address notification email in metrics.yaml #1157
Comments
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. |
@bbinto We need a product email to put here :) |
@liuche any idea based on your previous knowledge? Should we create an internal fenix-telemetry email list? |
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. |
Thanks @liuche - let's use fenix-core@mozilla.com |
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
The text was updated successfully, but these errors were encountered: