Alerts and too many Emails

Hi Anita,

It will be down to the alert itself, I am guessing that the alert is Component based and not Application?

Try creating a new alert, but this time based of [the] Application and use the overall application status (warning, critical, etc) as the trigger.

There are some nice variables that you can insert into your emails, that will then detail the components at fault, within your application template. 

Which will take your one email for each component to one email for them all.

You could change it from a Component alert (when does the service go down) to an Application alert (when does the Application go down) and then use one of the "Components with status..." items in the E-Mail to list each component and whether its currently up or down or whatever.

If they're all running on multiple servers, throw all the components into a group and use a group alert and use the "Group Status Root Cause" item in the alert.

Thank you so much for your help, this is now working a treat, also the option of component with HTML orders the services into a list which is great when you are alerting on 30+ services.

Thanks Geoff, I had two separate alerts for two servers however I have created a component group and now one alert serve both :-)