-
ZenPacks.RomanTykhonov.OracleDB-4.2.5_2.0-2.lbn13.noarch
With SNMP Trap destination setup in Oracle Enterprise Manager it is the best way to monitor many Oracle Single Instance/RACs for FREE. (if you have Oracle Standard Edition - Perfomance Tab have to be disabled due to Standard Edition Licence Agreement)
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.TwoNMS.PrinterMIB-4.2.5_2.0.0-2.lbn13.noarch
This ZenPack monitors printers supporting the new RFC3805 PrinterMIB (supersedes
RFC1759). Version 2.0.0 creates separate components for toners, supplies and input
trays.
In case you don't see the Printer components then try deleting the printer + adding
it directly to the /Printer/PrinterMIB tree.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.ZenSystems.ApcUps-4.2.4_1.2-6.lbn13.noarch
The ZenPack has the following Device Class
/Devices/Server/Windows
Components are:
ApcUpsBattery which has details for:
Various elements of battery status
Modeler plugins are:
ApcUpsDeviceMap
Gathers Hardware and Software manufacturer and product
Serial number
Total number of battery packs
Number of bad battery packs
Basic output status
ApcUpsBatteryMap
Gathers battery data for status
Time on battery
Battery last replacement date
Battery replacement indicator
Device template ApcUps provides device-level performance information:
Data Sources
Voltage
Current
Remaining capacity and time
Temperature
Thresholds
Low capacity
Low time remaining
High temperature
Graph Definitions
Voltage
Current
Remaining capacity
Remaining time
Temperature
Device template ApcUpsInsAndOuts provides specific input / output performance information:
Data Sources
Input frequency and voltage
Output frequency, voltage, load and current
Thresholds
High load
Graph Definitions
Input frequency and voltage
Output frequency, voltage, load and current
A separate APC UPS Information menu delivers tabular and graphical information for the overall device
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.atelepin.cbCiscoQOS-4.2.5_1.2-1.lbn13.noarch
Background
==========
This project is a Zenoss extension (ZenPack) primarily intended for ISPs which extensively use different QoS on their network (like MPLS), and need to know statistics by each class.
About Cisco Base QOS on Cisco site
This is prerelease but all main functionality work. Almost think i need change or add write in the code as TODO or FIXME
Overview
========
Because ServicePolicy bound to Interface (IpInterface), installation create additional relation between cbServicePolicy and IpInterface. ZenPack contain automated modeler which grab QOS Object configuration from device. From this configuration modeler create particular class instance and create hierarchy of that objects (see more about nested object in cisco site).
In this release i collect only two statistic item PostPolicyBitRate and PostPolicyDropRate. From code point of view each statistic item is different component, but from user point of view, this item belong to cbServicePolicy and statistics should be visible as single item (for example on single graph). In this case cbServicePolicy work not only as container but also provide internal API to gather statistic from his child.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.chudler.GoogleAppEngine-4.2.5_1.0-1.lbn13.noarch
With this ZenPack you can monitor the status of your Google AppEngine applications.
It provides:
All Quota statistics (allowances, percent used, and raw used).
Application status (version deployed)
Monitoring of multiple google accounts
Automatic detection of new quotas types
Automatic detection of new applications and changes to existing applications
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.community.CiscoEnvMon-4.2.5_1.1-1.lbn13.noarch
Cisco Environmental monitoring including fans, temperature sensors, power supplies and expansion modules.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.community.DistributedCollectors-4.2.5_2.0.1-1.lbn13.noarch
Description:
This ZenPack provides UI for configuring multiple collectors with Zenoss Core. It implement
remote collector configuration method described in How to install distributed collectors
manual (http://community.zenoss.org/docs/DOC-2496).
Adding Remote Collector
1. install DistributedCollectors ZenPack on master server
2. install Zenoss on remote collector without any ZenPacks
3. configure "ssh public key authentication" on remote collector for user 'zenoss'
4. in "Collectors" -> select menu item "Add Remote Monitor..." and enter name or ip address
of remote collector
Updating Remote Collectors (after zenpacks install or remove)
1. in "Collectors" select all remote collectors you want update.
2. in "Collectors" -> select menu item "Update Remote Monitors..."
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.community.Fortigate-4.2.4_1.2.1-1.lbn13.noarch
Provides a /Network/Router/Firewall/Fortigate Device Class and a Fortigate template that can be \
bound to monitor CPU usage, Memory Utilization and Number of Sessions for a Fortigate Firewall.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.community.HPUXMonitor-4.2.5_2.2-2.lbn13.noarch
HPUX SNMP-based monitoring/coordination
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13
-
ZenPacks.community.LinuxMonitorAddOn-4.2.5_1.0-1.lbn13.noarch
This SSH-based ZenPack supplements the Linux Monitor ZenPack and provides perf monitoring
for Interfaces and adds routing and memory as well.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 13