-
ZenPacks.community.Splunk-4.2.5_1.1.1-2.lbn19.noarch
This ZenPack allows Splunk alerts to be sent to Zenoss as alerts; escalation can then be handled with Zenoss alerts.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.SuSE-4.2.5_1.1-1.lbn19.noarch
This SSH-based ZenPack extends the Linux Monitor and Linux Monitor AddOn ZenPacks to provide
additional functionality for SuSE Linux, specifically OS Make and Software inventory.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.VMwareESXiMonitor-4.2.5_2.0.1-1.lbn19.noarch
DESCRIPTION:
This ZenPack allows Zenoss to monitor VMware ESXi Hosts and VMs via the vSphere SDK for Perl. It creates the /Server/VMware/ESXi Device Class. All ESXi Hosts have to be added to this Device Class.
INSTALLATION:
First install the vSphere SDK for Perl on your Zenoss Collector Server. After that you can install the ZenPack as usually and restart Zenoss.
ZPROPERTIES:
The ZenPack will add two zProperties:
zVSphereUsername: Name of a User that has read-only access to the ESXi Host
zVSpherePassword: The corresponding Password
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.Varnish3-4.2.5_1.2-1.lbn19.noarch
A ZenPack to provide support for Varnish version 3.x metrics. It introduces a
new command parser that is intended to be run over SSH. Metrics are parsed from
the output of the varnishstat command on the Varnish 3.x server
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.deviceAdvDetail-5.0.5_2.9.0-1.lbn19.noarch
This ZenPack is extends Zenoss with possibility to display additional hardware details and could be used by other ZenPacks as well. Examples of details include:
dynamic deviceHardwareDetail tab
dynamic deviceOsDetail tab
dynamic deviceSoftwareDetail tab
Number of CPU Cores
Memory Modules section
Logical Drives sections
status indication for all hardware components
It also make changes deviceOSDetail tab to show only monitored Network Interfaces
Usage
Installing the ZenPack will add the following items to your Zenoss system.
Event Class
/Change/Set/Status
Threshold Class
StatusThreshold
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.f5-4.2.5_1.7-1.lbn19.noarch
The ZenPack has the following:
/Network/f5 Device Class
A Device template which graphs many of the same performance stats as would be seen in the Overview >> Performance section of the 10.x UI
Virtual Server Component Modeling
A component template for virtual servers.
Virtual Server filtering. This pack adds a new zProperty, zF5BigipVirtualServerNameFilter, which when set will limit which virtual servers are included during a modeling cycle.
Node Component Modeling
A component template for nodes.
Node filtering. This pack adds a new zProperty, zF5BigipNodesNameFilter, which when set will limit which nodes are included during a modeling cycle.
Pool Component Modeling
A component template for Pools.
Pool filtering. This pack adds a new zProperty, zF5BigipPoolsNameFilter, which when set will limit which pools are included during a modeling cycle.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.libvirt-4.2.5_1.97-1.lbn19.noarch
This ZenPack leverages the libvirt API for monitoring virtualization servers (e.g. XEN,
KVM, etc...). This uses the system python and libvirt python API to monitor various
virtualization platforms remotely. It provides a /Server/libvirtHost device class and
this module is tested using ssh as a transport for the libvirt API, it could be made
to use TLS or TCP with further development. It provides a libvirtvirtualHostlist
report as well.
You can set zLibvirtUsername and zLibvirtConnectType to customize access to the hosts,
though only qemu+ssh:// was tested at the moment.
libvirt supports:
* The Xen hypervisor on Linux and Solaris hosts.
* The QEMU emulator
* The KVM Linux hypervisor
* The LXC Linux container system
* The OpenVZ Linux container system
* The User Mode Linux paravirtualized kernel
* The VirtualBox hypervisor
* The VMware ESX and GSX hypervisors
* Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.puppet-4.2.5_1.21-1.lbn19.noarch
This ZenPack provides support for the following in Puppet (via ssh)
Report and listing of puppet clients for each master on a separate tab
Report of all puppet clients in a PuppetClientList report
Tracking of update times of clients
Device addition from puppet via events
The ZenPack provides a device class /Server/PuppetMaster, with a collector plugin PuppetModeler.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.zenJavaApp-4.2.5_2.1-1.lbn19.noarch
This zenpack allows a modified version of the standard JMX template to work
for multiple JVMs running on the same device. Each JMX-capable application is
detected by a modeler plugin that checks responsive ports from a given list of
potential ports.
Components:
The ZenPack has the following Objects
JavaApp Template provides a component-level modified version of the
standard "Java" template that ships with zenJMX ZenPack.
The ZenPack also provides:
A modeler plugin JavaAppMap that models available JMX-capable servers
A new zProperty zJavaAppPorts that contains a list of port numbers to be
scanned by the modeler plugin
A CLI-based jmx agent used by the modeling process
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
ZenPacks.community.zenMongoDB-4.2.5_1.1-1.lbn19.noarch
Monitoring for MongoDB (component)
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
