Why do you want to remove CopperEgg monitoring before you scale down, after AWS auto scaling?
1. So that you do not get a Lost Connectivity alert on a server that was proactively shut down
2. So that you do not get a bunch of grey, inactive servers that accumulate in your dashboard and reduce your UI performance over time
How do you do this automatically for your Linux servers?
Thanks to Jesse for this blog and script that you can use to automatically remove a CopperEgg server and probe when powering off after an auto-scale or other expected system shutdown. This is especially useful to avoid the Connectivity Lost missing server alert and to remove the server from the UI