Confirmed users
72
edits
ReleaseEngineering/How To/Process release email: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Process release email (view source)
Revision as of 17:47, 17 April 2015
, 17 April 2015added detail about sns notifications
m (added sns plussed address) |
(added detail about sns notifications) |
||
| Line 123: | Line 123: | ||
== How to best filter these emails == | == How to best filter these emails == | ||
[release-runner] in the subject. | [release-runner] in the subject. | ||
=Amazon EC2 Instance scheduled for retirement= | =Amazon EC2 Instance scheduled for retirement= | ||
| Line 148: | Line 147: | ||
== How to best filter these emails == | == How to best filter these emails == | ||
Filter on the sender and subject line. | Filter on the sender and subject line. | ||
=SNS Notifications from AWS= | |||
==Example== | |||
Anything with the Subject "AWS Notification Message" | |||
== Why we get them == | |||
We use SNS to deliver notifications about various Amazon services as well as services like Papertrail. These are generally critical alerts that we've set up and should be dealt with/investigated in a timely fashion. At the moment, only AWS Cloudwatch and Papertrail use this service, but we will likely add more in the future after we get an SNS->irc bot set up because it allows for an easy HTTP/HTTPS endpoint push that other services already integrate with. | |||
== What is sending them == | |||
The Amazon SNS service notification topic "buildduty" | |||
* arn:aws:sns:us-west-2:314336048151:buildduty | |||
* arn:aws:sns:us-east-1:314336048151:buildduty | |||
== What to do when one is received == | |||
Determine what the issue is by parsing the output. Make sure someone is working on fixing the issue (if you're not sure how, at least contact buildduty for their input/advice). | |||
== How to silence or acknowledge this alert == | |||
Fix the underlying issue to stop the alert. | |||
== Future plans == | |||
In the near future we intend to send SNS notifications to an irc bot instead of via email. | |||
== How to best filter these emails == | |||
Ideally you should not filter them except into a high priority folder. You can filter on the Subject or the To address. | |||
<div id="chromecast"></div> | <div id="chromecast"></div> | ||
= Mail to release+chromecast@mozilla.com = | = Mail to release+chromecast@mozilla.com = | ||
== Why we get them == | == Why we get them == | ||