Does a component down cause an application down for alerting?

bmcmcm

If an application consists of 5 components, do all 5 have to be down for the application to be down, or would any component being down trigger the application to be down?

From a monitoring perspective the distinction between applications and components are sometimes lost on the server owners receiving the alerts. I'd like to keep it simple. So if a component is down that effectively renders the application down, one application down alert is preferable. If multiple components are down, I'd rather have one application down alert listing the components with trouble rather than several component alerts.

mbussey

For application status indicators this link should help. See number 1 below - if a component is down, application state is down

Status Icons and Identifiers

The status of an application is determined by these rules (in order of priority):

1. If an application has a down component, the application status is Down.
2. If an application has an unknown component, the application status is Unknown.
3. If an application has a critical component, the application status is Critical.
4. If an application has a warning component, the application status is Warning.
5. Otherwise, the application status is Up

You can control how alerts are generated and even create your own alert dependencies through alerting criteria.  If you want just an application down alert when an application component is in a down then this is absolutely possible in SAM.