One of the features of AWS is the ability to spin up and spin down servers at random and as needed, however, this does create an issue when it come to monitoring and alerting as each time an instance is spun up, it's ID changes and if you are trying to limit the amount of alerting being sent to a group, it makes it difficult to weed out the chaff. We have a series of servers that are always being turned on and off via OPsworks, and it creates a flood of emails. When trying to modify the AWS Cloud alert, there is no way to prevent it from not alerting on these dozen or so servers with the same name. What would be helpful in instances like this, and to also be able to group servers together for distribution lists is to use the tagging built in at AWS. We can have a tag that specifies either the group name, whether to alert or not and have the alert look at the tags for being able to identify the type of server and what to do with it.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.