Search results for zenoss

ZenPacks.Nova.Cisco.Mibs-4.2.5_1.1-2.lbn19.noarch

This ZenPack consists of all the publicly available (and edited to be loadable into Zenoss) MIBs for Cisco devices. The MIBs may be used for translating SNMP traps.

ZenPacks.oie.KannelMonitor-4.2.5_3.0.0-3.lbn13.noarch

KannelMonitor ------------- KannelMonitor uses the nagios check-kannel plugin to retrieve input queue and delivery volumes from any Kannel-based SMPP server. Once your Kannel Server has the check-kannel plugin installed, you can add Kannel monitoring to the device within Zenoss by simply binding the KannelMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the KannelMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Kannel Server metrics from this device.

ZenPacks.oie.KannelMonitor-4.2.5_3.0.0-3.lbn13.noarch

KannelMonitor ------------- KannelMonitor uses the nagios check-kannel plugin to retrieve input queue and delivery volumes from any Kannel-based SMPP server. Once your Kannel Server has the check-kannel plugin installed, you can add Kannel monitoring to the device within Zenoss by simply binding the KannelMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the KannelMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Kannel Server metrics from this device.

ZenPacks.oie.KannelMonitor-3.2.1_3.0.0-3.lbn13.noarch

KannelMonitor ------------- KannelMonitor uses the nagios check-kannel plugin to retrieve input queue and delivery volumes from any Kannel-based SMPP server. Once your Kannel Server has the check-kannel plugin installed, you can add Kannel monitoring to the device within Zenoss by simply binding the KannelMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the KannelMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Kannel Server metrics from this device.

ZenPacks.oie.KannelMonitor-5.0.5_3.0.0-3.lbn19.noarch

KannelMonitor ------------- KannelMonitor uses the nagios check-kannel plugin to retrieve input queue and delivery volumes from any Kannel-based SMPP server. Once your Kannel Server has the check-kannel plugin installed, you can add Kannel monitoring to the device within Zenoss by simply binding the KannelMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the KannelMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Kannel Server metrics from this device.

ZenPacks.oie.KannelMonitor-4.2.5_3.0.0-3.lbn19.noarch

KannelMonitor ------------- KannelMonitor uses the nagios check-kannel plugin to retrieve input queue and delivery volumes from any Kannel-based SMPP server. Once your Kannel Server has the check-kannel plugin installed, you can add Kannel monitoring to the device within Zenoss by simply binding the KannelMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the KannelMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Kannel Server metrics from this device.

ZenPacks.oie.KannelMonitor-4.2.5_3.0.0-3.lbn19.noarch

KannelMonitor ------------- KannelMonitor uses the nagios check-kannel plugin to retrieve input queue and delivery volumes from any Kannel-based SMPP server. Once your Kannel Server has the check-kannel plugin installed, you can add Kannel monitoring to the device within Zenoss by simply binding the KannelMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the KannelMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Kannel Server metrics from this device.

ZenPacks.PlixerInternational.Scrutinizer-4.2.4_1.2-1.lbn13.noarch

The Scrutinizer ZenPack provides direct integration between Zenoss and Scrutinizer. This integration allows network engineers to quickly switch between viewing the event details in Zenoss and the detailed network traffic analysis view in Scrutinizer. Network engineers need to quickly find and resolve network performance bottlenecks before they impact customers and end-users. One of the most effective ways to diagnose network performance problems is by analyzing NetFlow data.

ZenPacks.PlixerInternational.Scrutinizer-5.0.5_1.2-2.lbn19.noarch

The Scrutinizer ZenPack provides direct integration between Zenoss and Scrutinizer. This integration allows network engineers to quickly switch between viewing the event details in Zenoss and the detailed network traffic analysis view in Scrutinizer. Network engineers need to quickly find and resolve network performance bottlenecks before they impact customers and end-users. One of the most effective ways to diagnose network performance problems is by analyzing NetFlow data.

ZenPacks.PlixerInternational.Scrutinizer-4.2.5_1.2-2.lbn19.noarch

The Scrutinizer ZenPack provides direct integration between Zenoss and Scrutinizer. This integration allows network engineers to quickly switch between viewing the event details in Zenoss and the detailed network traffic analysis view in Scrutinizer. Network engineers need to quickly find and resolve network performance bottlenecks before they impact customers and end-users. One of the most effective ways to diagnose network performance problems is by analyzing NetFlow data.