Skip navigation
Currently Being Moderated

Oracle (Sun) Hardware Monitor

VERSION 3  Click to view document history
Created on: Mar 15, 2011 8:23 PM by Nick Yeates - Last Modified:  Oct 10, 2011 2:11 PM by Nick Yeates

Submitted by: Ondřej Jakubčík


Description:

This Monitoring ZenPack allows Oracle (formerly Sun) Hardware to be monitored via incoming snmp-traps. Many event classes are created and events are properly dealt with.

 

Features:

  • Receiving and translating traps from Oracle Sun server's Service Processors/Monitoring Agents
  • clearing of events

 

It was created as a part of a bachelor thesis at Czech Technical University in Prague. Original thesis as submitted and successfully defended can be found at:

https://dip.felk.cvut.cz/browse/pdfcache/jakubon1_2010bach.pdf

 

Screenshots:

FIXME

Components:

(Optional)  Describe the technical components of the ZenPack here. What  specifically is monitored, what device classes, event classes,  templates, etc are included.

 

The ZenPack has the  following Device Class(es)

  • /Server/Example Device  Class  
    • ExampleTemplate Template provides:  
      • Data  Sources  
        • check_example (Command)
        • dsExample (SNMP)
      • Thresholds  
        • BrokenExample (Min/Max)
        • SlowExample (Min/Max)
      • Graph  Definitions  
        • Example Response Time
          • Response time
          • dsExample

 

The  ZenPack also provides MIBs/Event Rules/Reports/Daemons/portlets/etc.

 

Installation:

Describe  the install process if anything is needed before or after standard  ZenPack installation.

 


Requirements:

  • Zenoss  Versions Supported: 3.0
  • External Dependencies: libraries?
  • ZenPack Dependencies:
  • Installation  Notes: zopectl restart after installing this ZenPack.
  • Configuration: Configuration Properties?

History:

Change  History:

  • 1.0 initial release

Tested: This ZenPack was tested with versions XXX and YYY.

Source: https://github.com/zenoss/Community-Zenpacks/tree/master/ZenPacks.community.FOOBAR


Known  issues:

Attachments:
Note: binary attachments ending in .zip will need to be unzipped before use.
Comments (1)