No footprints! As an agentless poller, you can monitor virtually any IP enabled device with minimal to no overhead. Tests can be created for ping response, TCP ports, UDP ports and protocol validation.
PingFirst and PingLast
PingFirst and PingLast are unique as a way to reduce polling overhead and increasing performance. If you specify PingFirst, then the ping test will run before any other tests for that particular device. If the ping test passes, the other tests are run. If the ping fails, the other tests do not run. PingLast does the opposite. If at least one of the other tests passes for a device, the PingLast test will not run, as you know the device is reachable. If all other tests fail, then it will run.
nandView supports up to four run groups for additional scalability and flexibility. You can choose to run tests in different run groups on different schedules (such as group 1 polling every five minutes, group 2 every thirty minutes) or with different timeout periods.
Need to import dozens of devices? A bulk import utility allows you to load a csv (comma separated values) for fast device/test creation, right from the web interface.
Just because the poller can connect to port 80, that doesn't guarantee the web server is actually running or configured correctly. nandView goes one step beyond, issuing actual protocol commands and checking if the reply is an expected value. It can even check on different ports than traditional - go ahead and run that web server on port 3852. nandView can monitor it.
What is sent to the server
What is expected in reply
GET / HTTP/1.1 Host: ip_address:port Connection: close