On 01/07/14 18:19, Martin Sperl wrote:
Hi!
Is there any cookbook for how to handle servers in AWS that get started shut down elastically form the xymon side -- avoiding alerts and such?
Essentially automatically "disabling" servers (maybe even a different colour/status to see why?) either on the client side on shutdown via agent or via a callback from AWS but automatically reenabling it when they start up again?
Any experience?
No experience as such, but you could use the xymon client to send a disable status for the machine from the shutdown scripts. Just trigger it to run as one of the last processes on shutdown.
Then, on startup, you can either send an enable, or use the option to "enable on recovery".
You should probably test and ensure the following will work as expected:
- red status on something (eg, disk full)
- machine shutdown, disable sent
- machine startup, without enable, you send a disk red status (still full)
- xymon doesn't see the red status or alert for disk because it is still bad/disabled.
So, probably best to send an explicit enable on startup, and ensure that alerts and status updates are working.
Regards, Adam
-- Adam Goryachev Website Managers www.websitemanagers.com.au