The "Last Status" tab shows a summary of the results of the last event monitor run. At the time of the last event monitor run is recorded along with a count of the number of devices that were checked. Below is a table with one entry for each device. The table shows the device name, the result of the run and the set of data points that were collected while checking the device. The set of data points varies depending the type of event monitor. For example, Ping event monitors will show the average and maximum ping response times.

The dependencies section lists the other event monitors that the event monitor depends on. Use the "Settings" tab to define dependencies. With dependencies, one event monitor won't run if it depends on another one that is in an error state. For example you might have a ping event monitor that checks all of your critical servers. You might also have a high-level event monitor that does somethin such as check the results from a SQL database query.

By default, if the server running the database goes down you'll get one notification from the ping event monitor and another from the database event monitor. If you set the database event monitor to depend on the ping event monitor then you'll receive the ping notification but when the database check goes to run it will see that the ping failed and not send a second notification.