As you configure and assign actions, you should take several things into consideration.
For example, an email action assigned to a router and each of the devices that depend on that router for their Internet connectivity, would send email notifications not only from the router, but also from every single connected device, should the router go down.
In a situation like this, it consider using dependencies that allow you to restrict email notifications to only the router and the critical devices to which it is connected. For more information, see Dependencies overview.
If you want to be notified if and when any or all of the monitors on a device go down, assign the action to the device. If you are concerned with specific monitors on a device, assign the action to the monitor itself. If you an assign to both the device and a specific monitor, both actions fire when the monitor goes down.
Whenever possible, use action policies in lieu of configuring multiple actions for one device.
You may want to add device states for longer periods of downtime. Perhaps creating a Down at least 60 mins state, and sending an escalated message to show that the device is still down after an hour.
While Web Alarms are useful in many situations, they are not the most efficient way to monitor devices and services overnight.
Unless the device is vital to the daily-operation of your network or business, the color and shape of each device state easily informs you of current network device status.