[chef] Re: What is a simple method to arrange e-mail notification of failed convergence?

[Morgan Blackthorne < >]

What we use at Rosetta is the airbrake handler. This sends a message to our internal Hoptoad (now called Airbrake for the cloud version IIUC) server, which in turn sends out an email. Hoptoad also handles correlation of events so it can glob up a bunch of items together (albeit with multiple notifications, which is nice) and you can say that all the events for that type of error are fixed by one issue.

--

~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Mon, Nov 24, 2014 at 11:47 AM, Phil Mocek < " target="_blank"> > wrote:

What is a simple method of arranging to receive e-mail notification
whenever chef-client attempts and fails to converge a node?

I know Chef provides a [flexible framework for various handlers][1],
including exception handlers.  At this time, I don't need flexibility; I
need simplicity.  I just want to say, "For any of these nodes, when
convergence fails, send a message to "> ."  I
hoped I could override in a Chef environment definition a node attribute
used by the [chef-client cookbook][2] so that it would configure nodes
as described, but after various searches of the Chef docs, the whole
Web, and this list, I've yet to find indication that such is a possibility.


References:

 [1]: <https://docs.getchef.com/essentials_handlers.html>
 [2]: <https://supermarket.getchef.com/cookbooks/chef-client>

--
Phil Mocek
https://mocek.org