Search results for zenoss

zenoss5-rabbitmq-5.3.2-1.lbn25.noarch

rabbitmq-server setup for Zenoss. This is a separate package to easily enable large-scale Zenoss deployment

ZenPacks.AndreaConsadori.Asterisk16-5.0.5_3.0-2.lbn19.noarch

This Monitoring ZenPack provides SNMP-based monitoring for Asterisk 1.6

ZenPacks.AndreaConsadori.Asterisk16-4.2.5_3.0-2.lbn19.noarch

This Monitoring ZenPack provides SNMP-based monitoring for Asterisk 1.6

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.

ZenPacks.atelepin.cbCiscoQOS-5.0.5_1.2-1.lbn19.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.

ZenPacks.atelepin.cbCiscoQOS-4.2.5_1.2-1.lbn19.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.

ZenPacks.atelepin.cbCiscoQOS-4.2.5_1.2-1.lbn19.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.

ZenPacks.community.ConstructionKit-5.0.5_2.5-1.lbn19.noarch

This ZenPacks automates to a large extent the development of other ZenPacks. It eliminates the bulk of "boilerplate" code that accompanies the typical "custom component" type of zenpack while providing many nice features. The goal is to reduce the maintenance cost (development time) associated with dependent ZenPacks by removing most of their code. ConstructionKit-dependent ZenPacks should consist only of a Definition.py class file that subclasses the provided "BasicDefinition" class, as well as any additional ZenPack-specific files such as modeler plugins, check scripts, and exported Zenoss templates, event classes, etc (objects.xml).

ZenPacks.community.ConstructionKit-4.2.5_2.5-1.lbn19.noarch

This ZenPacks automates to a large extent the development of other ZenPacks. It eliminates the bulk of "boilerplate" code that accompanies the typical "custom component" type of zenpack while providing many nice features. The goal is to reduce the maintenance cost (development time) associated with dependent ZenPacks by removing most of their code. ConstructionKit-dependent ZenPacks should consist only of a Definition.py class file that subclasses the provided "BasicDefinition" class, as well as any additional ZenPack-specific files such as modeler plugins, check scripts, and exported Zenoss templates, event classes, etc (objects.xml).

ZenPacks.community.ConstructionKit-4.2.5_2.5-1.lbn19.noarch

This ZenPacks automates to a large extent the development of other ZenPacks. It eliminates the bulk of "boilerplate" code that accompanies the typical "custom component" type of zenpack while providing many nice features. The goal is to reduce the maintenance cost (development time) associated with dependent ZenPacks by removing most of their code. ConstructionKit-dependent ZenPacks should consist only of a Definition.py class file that subclasses the provided "BasicDefinition" class, as well as any additional ZenPack-specific files such as modeler plugins, check scripts, and exported Zenoss templates, event classes, etc (objects.xml).