Confirmed users
1,351
edits
ReleaseEngineering/How To/Process release email: Difference between revisions
ReleaseEngineering/How To/Process release email (view source)
Revision as of 20:00, 5 May 2012
, 5 May 2012added collapse email
m (keep table in alpha order) |
(added collapse email) |
||
| Line 8: | Line 8: | ||
!Field !! Wildcard !! Further Notes | !Field !! Wildcard !! Further Notes | ||
|- | |||
|Subject || collapse report || [[#Performance Metrics]] | |||
|- | |- | ||
|Subject || Humpty Dumpty Error * || [[#Puppet failing too many times on a slave]] | |Subject || Humpty Dumpty Error * || [[#Puppet failing too many times on a slave]] | ||
| Line 83: | Line 85: | ||
== How to best filter these emails == | == How to best filter these emails == | ||
These emails are best filtered by having "Humpty Dumpty Error" in their subject. Becuase the hostname on the slave might not be correct every/all the time, filtering on domain names might not catch all cases. | These emails are best filtered by having "Humpty Dumpty Error" in their subject. Becuase the hostname on the slave might not be correct every/all the time, filtering on domain names might not catch all cases. | ||
=Performance Metrics= | |||
== Why we get them == | |||
We get various emails containing raw data that relates to a performance bottle neck at some point in time. Typically these are produced by cron jobs, and so received regularly regardless of metric status. (I.e. they may not require any action.) | |||
== What is sending them == | |||
Since this is a "catch all" category, various tools send them. Check the full headers for information on sender and source machine as needed. | |||
== What to do when one is recieved == | |||
If you don't know what it's about, you don't need to deal with it beyond setting up a filter to ignore it. | |||
== How to silence or acknowledge this alert == | |||
It's not an alert, so they'll keep coming until the end of time. Filter them if you're not involved with them. | |||
== Future plans == | |||
Adhoc, so varies by email. Theoretically, these ''should'' be transitional, and moved into automation and alerting as soon as the metric is understood. | |||
== How to best filter these emails == | |||
Since these are adhoc, you'll need adhoc filters. It would be nice if folks used a common prefix on subjects, such as "<tt><nowiki>[releng metrics]</nowiki></tt>". | |||
<hr /> | <hr /> | ||
=Sample= | =Sample= | ||
== Why we get them == | == Why we get them == | ||