1256234 - Send Treeherder infra alerts to a new internal Treeherder email address

Status: RESOLVED FIXED

(Tree Management :: Treeherder: Infrastructure, defect)

Description

[Ed Morley [:emorley]]

In bug 1176487 I set the CloudAMQP alerts up to be sent to the public Treeherder mailing list.

However:
(a) it turns out they reveal things like the vhost address (which isn't too secret, but still
(b) are probably not relevant for everyone on the list

I think we should set up another internal/private Treeherder list/alias (eg [e-mail]) that forwards mails to just the core devs.

We can then get New Relic, CloudAMQP and others to use this email address.

Comment 1

[Kendall Libby [:fubar] (he/him)]

do we need to include any non-employees on the list? if we do, then it should be a mailman list, which is requested through Service Now (https://mozilla.service-now.com/, then search catalog for 'mailing list'). 

if it's employees only, we can self create a google group:  https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=43718013

Comment 2

[Ed Morley [:emorley]]

It sounds like a self-serve google group will be fine :-)

I've created one called 'treeherder-internal', which can be posted to via either the web UI or via [e-mail]

Group membership is required to view messages (I've added myself, wlach, camd, jgraham, jgriffin), but anyone can post.

The intended content for this list is very narrow in scope (eg infra alerts containing sensitive information that is only really relevant for people working on Treeherder itself), but happy to add other people if they really want.

Comment 3

[Ed Morley [:emorley]]

I've switched the following to the treeherder-internal@moco list:
* Heroku CloudAMQP alerts x 3
* Heroku prototype RDS Cloudwatch diskspace (other RDS instances and alert types to follow later)
* New Relic "treeherder devs" group (used by APM/servers alerts)
* New Relic legacy plugins notifications