Who should be added to the `notification_emails`?
Categories
(Data Platform and Tools :: Glean: SDK, enhancement)
Tracking
(Not tracked)
People
(Reporter: Dexter, Unassigned)
Details
This was created from a discussion in bug 1710794.
[The proposal] seems to be missing notification_emails, but I think it's good, because we need to have a conversation about those. We were using
notification_emailsto set owners for Namespace Folders in Looker, but found that that list was not sufficient for who actually should be an owner. We may need another category of "Is responsible for this application" from a product perspective. We call themownersin Looker.https://github.com/mozilla/lookml-generator/blob/main/namespaces-allowlist.yaml#L3-L8
Comment 1•3 years ago
|
||
notification_emails has traditionally tried to satisfy all needs of Data Ownership... but usually ends up "just" being a starting place for finding out who knows the code under instrumentation. Its usefulness as an ownership signal for the resulting data, reporting, dashboards, and enclosing product is directly proportional to how technical the instrumentation is.
e.g. Webrender probes' emails are very good indicators of the ownership of the resulting data, reporting, and dashboading about webrender: they are the same people who instrumented the code. Search, on the other hand...
Updated•1 year ago
|
Comment 2•1 year ago
|
||
I think the notification emails are only useful if product takes ownership of their metrics and this is beyond our scope to think about who should get them. Closing this as WONTFIX
Description
•