Not sure about this one..

ipMonitor is primarily designed for representing the state of a large number of resources that you care about on your network, rather than if a server is ok or not.

 

Some resources transcend an individual location on a server / device. An example of this is a single Monitor that checks your entire email circuit to ensure availability. The Email Round Trip Monitor will check several devices in one pass (DNS, multiple MX-mail hosts, authentication, SMTP proxy, Exchange MTA, and pop3 / imap4 pickup) to see if the system is functioning correctly (and potentially quickly).

 

The vantage point you're seeing is the result of us lumping these things you care about all together by default, sorted by their current state. Everything should be "green" so it's a quick glance to determine if there is anything misbehaving. When something isn't green, the individual resource that has trouble is easily denoted as failing and its state bubbles up to the top (somebody pausing a website in IIS as an example of a resource failing, yet the device actually being ok).

 

However, this does not work well with administration. Our software automatically groups these Monitors (on creation) based on the source device. However, it also leaves you the ability to group these resources based on anyway you like. The "Groups" area in the software allows you to make arbitrary relationships between monitored things on your network, and the Groups make an easy vehicle for administration. 

 

Within the "Groups List", checkmark a group and use the "Load as Quick Filter" feature. This will help you administrate the individual resources fairly easily. As Fodome points out, these Groups will also reflect the state of your defined relationships' state in the "admin dashboard".

ipMonitor is primarily designed for representing the state of a large number of resources that you care about on your network, rather than if a server is ok or not.

 

Some resources transcend an individual location on a server / device. An example of this is a single Monitor that checks your entire email circuit to ensure availability. The Email Round Trip Monitor will check several devices in one pass (DNS, multiple MX-mail hosts, authentication, SMTP proxy, Exchange MTA, and pop3 / imap4 pickup) to see if the system is functioning correctly (and potentially quickly).

 

The vantage point you're seeing is the result of us lumping these things you care about all together by default, sorted by their current state. Everything should be "green" so it's a quick glance to determine if there is anything misbehaving. When something isn't green, the individual resource that has trouble is easily denoted as failing and its state bubbles up to the top (somebody pausing a website in IIS as an example of a resource failing, yet the device actually being ok).

 

However, this does not work well with administration. Our software automatically groups these Monitors (on creation) based on the source device. However, it also leaves you the ability to group these resources based on anyway you like. The "Groups" area in the software allows you to make arbitrary relationships between monitored things on your network, and the Groups make an easy vehicle for administration. 

 

Within the "Groups List", checkmark a group and use the "Load as Quick Filter" feature. This will help you administrate the individual resources fairly easily. As Fodome points out, these Groups will also reflect the state of your defined relationships' state in the "admin dashboard".