gistfile1.txt

ensu
-----

monitoring not only an ops problem. devs need to be on board, looped in

poor monitoring coverage

rather than making a large change, iteratively integrate sensu, gradually replacing nagios

exploring what success looks like; observations on whether or not it was better than the status quo

standalone checks?

checks have runbook baked in

sensu::check puppet type / wrapped with in-house code

handlers for irc/issue tracker; arbitrary api/tools (awsprune)

sensu plugins worth looking at for use with nagios

upon login alerts indicated / machine stats, error conditions
~