1. Monitoring Topology with ZenPing

The availability monitoring system within Zenoss provides active testing of the IT Infrastructure. The system currently consists of Zenping, Zenoss’ Layer-3 aware topology-monitoring daemon, and Zenstatus, a TCP status tester.

ZenPing is configured automatically. You can use the About page, Status tab to stop and start Zenping. ZenPing does the high-performance asynchronous testing of the ICMP status. The most important element of this daemon is that Zenoss has built a compete model of the your routing system. If there are gaps in Zenoss’ routing model, the power of ZenPing’s topology monitoring will not be available. If there are these gaps, this issue can be seen in the zenping.log file.

Zenmodeler goes out and discovers the routes to each device in the Zenoss network. Zenoss tries not to use Internet routing tables and prefers to rely on Zenmodeler to discover the relationships on its own and create its own network map.

Basically if any known route is broken, there will only be one ping event that is generated by the outage. Any additional outages beyond that will only flag that device and the next time a ping sweep occurs the errors beyond the known router will not occur.

Zenmodeler works from the Zenoss system to further away from the server.

This monitoring model breaks down if the routers do not share their routing tables and interface information.

1.1. Controlling the Ping Cycle Time

  1. From the left Navigation menu, select Monitors and select the Status monitor localhost and click the localhost link.

  2. Notice the list of machines being pinged by this monitor.

  3. In the “Edit” tab, change “Cycle Interval” to the desired interval.

  4. On the next configuration cycle, the ping monitor will ping at the interval you set.

1.2. Using the Predefined /Ping Device Class

The /Ping device class is an example of a configuration for devices that should only be monitored for availability. Zenoss will not gather performance data for devices placed under this class; it will only ping them. You can use it as a reference for your own configuration; or, if you have a device that you want be monitored for availability alone, you can place it under this class.