Modified items

All recently modified items, latest first.

zope.decorator-3.4.0-4.lbn13.noarch: zope.decorator

zenoss4-rabbitmq-4.2.5-3.lbn13.noarch: rabbitmq-server setup for Zenoss. This is a separate package to easily enable large-scale Zenoss deployment

zenoss4-pgsqld-4.2.5-3.lbn13.noarch: PostgreSQL backend for Zenoss/ZODB

zenoss4-oracled-4.2.5-3.lbn13.noarch: Oracle backend for Zenoss/ZODB

zenoss4-mysqld-4.2.5-3.lbn13.noarch: MySQL backend for Zenoss/ZODB

zenoss4-4.2.5-3.lbn13.x86_64: Zenoss is an IT infrastructure monitoring product that allows you to monitor your entire infrastructure within a single, integrated software application. Key features include: * Monitors the entire stack o networks, servers, applications, services, power, environment, etc... * Monitors across all perspectives o discovery, configuration, availability, performance, events, alerts, etc. * Affordable and easy to use o unlike the big suites offered by IBM, HP, BMC, CA, etc... o unlike first generation open source tools... * Complete open source package o complete solution available as free, open source software

zenoss4-4.2.4-4.lbn13.armv6hl: Zenoss is an IT infrastructure monitoring product that allows you to monitor your entire infrastructure within a single, integrated software application. Key features include: * Monitors the entire stack o networks, servers, applications, services, power, environment, etc... * Monitors across all perspectives o discovery, configuration, availability, performance, events, alerts, etc. * Affordable and easy to use o unlike the big suites offered by IBM, HP, BMC, CA, etc... o unlike first generation open source tools... * Complete open source package o complete solution available as free, open source software

zenoss.extjs-devel-4.2.5_4.1.0-1.lbn13.noarch: JSBuilder compiler

zenoss.extjs-4.2.5_4.1.0-1.lbn13.noarch: A Zope package wrapper around the Ext JS JavaScript library. This package makes Ext source files traversable as browser resources under the name 'extjs': <script src="++resource++extjs/ext-all.js"></script> Refer to Ext documentation for load order, dependencies, etc.

zenoss-zep-rdbms-4.2.4-2.lbn13.noarch: Scripts/dependencies for setting up RDBMS backend/s for ZEP

zenoss-zep-pgsql-4.2.4-2.lbn13.noarch: This package sets up the postgresql backend for Zenoss/Zentinel. The root is automatically set to accept as a remote user.

zenoss-zep-oracle-4.2.4-2.lbn13.noarch: This package sets up the oracle backend for Zenoss/Zentinel. The root is automatically set to accept as a remote user.

zenoss-zep-mysql-4.2.4-2.lbn13.noarch: The root is automatically set to accept as a remote user.

zenoss-zep-javadoc-4.2.4-2.lbn13.noarch: Javadoc for zenoss-zep.

zenoss-zep-4.2.4-2.lbn13.noarch: Zenoss Event Processor

zenoss-utils-javadoc-4.2.4-0.1.lbn13.noarch: API documentation for zenoss-utils.

zenoss-utils-4.2.4-0.1.lbn13.noarch: Java utility packages for Zenoss/ZEP

zenoss-snmp-module-1.0.0rc4-1.lbn13.noarch: This project provides a Net-SNMP pass_persist script for monitoring Zenoss. If you aren't familiar with Net-SNMP's pass_persist option, it allows an external script to provide responses for all GET and GETNEXT requires under a configured base OID. Currently zenoss-snmp-module provides support for the provided ZENOSS-PROCESS- MIB. See the following snmptranslate command for what the MIB provides: $ snmptranslate -Tp ZENOSS-PROCESS-MIB::zenossProcessMIB +--zenossProcessMIB(3) | +--zenSystemTable(1) | | | +--zenSystemEntry(1) | | Index: zenSystemName | | | +-- -R-- String zenSystemName(1) | Textual Convention: DisplayString | Size: 0..255 | +--zenProcessTable(2) | | | +--zenProcessEntry(1) | | Index: zenSystemName, zenProcessName | | | +-- -R-- String zenProcessName(1) | Textual Convention: DisplayString | Size: 0..255 | +--zenProcessMetricTable(3) | +--zenProcessMetricEntry(1) | Index: zenSystemName, zenProcessName, zenProcessMetricName | +-- -R-- String zenProcessMetricName(1) | Textual Convention: DisplayString | Size: 0..255 +-- -R-- String zenProcessMetricValue(2) | Textual Convention: DisplayString | Size: 0..255 +-- -R-- String zenProcessMetricCyclesSinceUpdate(3) Textual Convention: DisplayString Size: 0..255 $ snmpwalk -v2c -c public localhost ZENOSS-PROCESS-MIB::zenossProcessMIB ZENOSS-PROCESS-MIB::zenSystemName."localhost" = STRING: localhost ZENOSS-PROCESS-MIB::zenProcessName."localhost"."zenhub" = STRING: zenhub ZENOSS-PROCESS-MIB::zenProcessName."localhost"."zenwebtx" = STRING: zenwebtx ZENOSS-PROCESS-MIB::zenProcessName."localhost"."zencommand" = STRING: zencommand ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenhub"."services" = STRING: services ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenhub"."totalTime" = STRING: totalTime ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenhub"."totalEvents" = STRING: totalEvents ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenhub"."invalidations" = STRING: invalidations ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenhub"."totalCallTime" = STRING: totalCallTime ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenhub"."workListLength" = STRING: workListLength ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenwebtx"."devices" = STRING: devices ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenwebtx"."dataPoints" = STRING: dataPoints ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenwebtx"."eventCount" = STRING: eventCount ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenwebtx"."cyclePoints" = STRING: cyclePoints ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenwebtx"."queuedTasks" = STRING: queuedTasks ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenwebtx"."runningTasks" = STRING: runningTasks ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zenwebtx"."eventQueueLength" = STRING: eventQueueLength ZENOSS-PROCESS-MIB::zenProcessMetricName."localhost"."zencommand"."eventQueueLength" = STRING: eventQueueLength ZENOSS-PROCESS-MIB::zenProcessMetricValue."localhost"."zenwebtx"."devices" = STRING: 0.0 ZENOSS-PROCESS-MIB::zenProcessMetricValue."localhost"."zenwebtx"."dataPoints" = STRING: 0.0 ZENOSS-PROCESS-MIB::zenProcessMetricValue."localhost"."zenwebtx"."eventCount" = STRING: 0.0 ZENOSS-PROCESS-MIB::zenProcessMetricValue."localhost"."zenwebtx"."cyclePoints" = STRING: 0.0 ZENOSS-PROCESS-MIB::zenProcessMetricValue."localhost"."zenwebtx"."queuedTasks" = STRING: 0.0 ZENOSS-PROCESS-MIB::zenProcessMetricValue."localhost"."zenwebtx"."runningTasks" = STRING: 0.0 ZENOSS-PROCESS-MIB::zenProcessMetricValue."localhost"."zenwebtx"."eventQueueLength" = STRING: 0.0 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenhub"."services" = STRING: 2.35 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenhub"."totalTime" = STRING: 2.35 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenhub"."totalEvents" = STRING: 2.35 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenhub"."invalidations" = STRING: 2.35 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenhub"."totalCallTime" = STRING: 2.35 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenhub"."workListLength" = STRING: 2.35 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenwebtx"."devices" = STRING: 0.48 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenwebtx"."dataPoints" = STRING: 0.48 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenwebtx"."eventCount" = STRING: 0.48 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenwebtx"."cyclePoints" = STRING: 0.48 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenwebtx"."queuedTasks" = STRING: 0.48 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenwebtx"."runningTasks" = STRING: 0.48 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zenwebtx"."eventQueueLength" = STRING: 0.45 ZENOSS-PROCESS-MIB::zenProcessMetricCyclesSinceUpdate."localhost"."zencommand"."eventQueueLength" = STRING: 0.12 Troubleshooting Normally zenoss-snmp-module is run from within snmpd. This makes it difficult to troubleshoot problems. To test the script outside of snmpd, you can run zenoss-snmp-module as root. If things are working properly, this will appear to do nothing. See the following session as an example: PING PONG DUMP {'1.1.1.9.108.111.99.97.108.104.111.115.116': {'type': 'STRING', 'value': 'localhost'}, ... snipped ... It can also be useful to stop the snmpd service and run it in the foreground with just the useful debugging enabled: sudo service snmpd stop sudo snmpd -fV -Lo -Ducd-snmp/pass_persist -Doutput

zenoss-protobuf-python-0.2-9.lbn13.noarch: Python implementation of Zenoss Protocols

zenoss-protobuf-java-1.2-9.lbn13.noarch: Java implementation of Zenoss Protocols

« Previous 20 items Next 20 items » 1 ... 2335 2336 2337 2338 2339 2340 2341 ... 2449


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items