Skip navigation
21059 Views 1 Reply Latest reply: Dec 16, 2009 3:14 AM by guyverix RSS
rpad2179 Rank: White Belt 37 posts since
Nov 12, 2009
Currently Being Moderated

Dec 16, 2009 1:53 AM

Zenoss modeling/monitoring queries

Hi,

 

Below snippet is part of Zenoss console where I'm  trying to monitor my application tabular data from our own SNMP  MIB.

------------------------------------------------------------

Host  Name          Total API's         Failed  API's       Latency (ms)

Boxer                             120                   25                     7

Tiger                              140                   21                     7.3

------------------------------------------------------------

Query:

Currently, the stats shown above in  each row are changing only when we run zenmodel (forcibly) from zenoss point of  view.

But in real time these stats will  change for every 60seconds in background.

 

Administrator need to wait 12 hours  (default modeling time) to see the changes in zenoss console where in background  the changes are occurring for every 1 minute. 

 

So, how I can change this data to  performance data (rather than modeler data) so that whenever there is a change  in SNMP MIB (every 60seconds), zenoss should show the latest data without  applying remodel on the device. Something like invoking zenmodel for every 1  minute.

 

Please let me know if there is any  way to handle this as per my requirement.

 

Code snippet from my own implemented  plug-in:

---------------------------------------------------------------------------

SystemTable =  tabledata.get("systemHostTable")

        if not SystemTable:

            log.warn('No SNMP  response from %s for the %s plugin',

                      device.id,  self.name() )

            log.warn( "Data= %s",  getdata )

            log.warn( "Columns= %s",  self.columns )

             return

 

        rm =  self.relMap()

 

        for oid, data in  RTEDTable.items():

            om =  self.objectMap(data)

 

           om.snmpindex =  oid.lstrip('.')

            log.info('om.snmpindex   %s' , om.snmpindex)

 

            om.hostName = data['hostname']

            om.ctype =  data['rtedHostComponentType']

            om.totalAPIs = data['totalAPIs']

            om.apiSuccess = data['apiSuccess']

            om.apiFail = data['apiFail']

 

            om.id =  self.prepId("host" +  om.cname )

           rm.append(om)

        return  rm

---------------------------------------------------------------------------

We created the above  code using the SanDevice example given in the Zenpacks forum. From the above code snippet, Please  let me know the significance of below statements:

> om.snmpindex

>  om.id

 

Your valuable thoughts/insights will  be definitely of great help to me in proceeding with my  work.

so, please keep post your comments  on this.

 

Thanks,

Ranjith Kumar

Mobile:0091- 99 087 666 30

  • guyverix ZenossMaster 846 posts since
    Jul 10, 2007
    Currently Being Moderated
    1. Dec 16, 2009 3:14 AM (in response to rpad2179)
    Re: Zenoss modeling/monitoring queries
    Take a look at jcurry's ZenPack creation tutorial.  In particular how she is getting rrd data defined for the bridge interfaces.  You can grab your table data in that fashion, and put it into your RRD files, and it will update in the normal cycle period.

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points