Re: [Devmon] Active connexion questions

[Simeon B. <sbe...@mc...>]

xbgmsharp wrote:
> It sound to me like a nice idea.
> Could you share you script.
> Where is your cisco pix template?
> I have probleme pix 7.0.2, do you?
> 

Attached is the pix template that I'm using, which is designed around v6.3. I 
don't have access to a pix 7.x. Here is how we get values into rrd's using our 
template:

If you look at the fwmem, fwcpu, and fwconn message files, they are formatted to 
send the status message formatted so that NCV will pick up the values. eg:

  mp: {MemPercUsed}
  mt: {MemTotal}

To get this to populate rrd's you need an NCV line and related configuration in 
hobbitserver.cfg:

  TEST2RRD="cpu=la,(...bunch of stuff...),fwconn=ncv,fwcpu=ncv,fwmem=ncv"
  GRAPHS="la,(...bunch of stuff...),fwconn,fwcpu,fwmem"
...
  NCV_fwcpu="c1:GAUGE,c5:GAUGE,c15:GAUGE"
  NCV_fwconn="c:GAUGE,h:GAUGE"
  NCV_fwmem="mt:GAUGE,mp:GAUGE"

Note how the rrd definitions have matching datasource names (mp,mt,c1,c5,etc)

To get hobbit to generate graphs with these rrd's, you need appropriate graph 
definitions in hobbitgraph.cfg:

  [fwcpu]
    TITLE Cpu usage
    YAXIS Percent
    -u 100
    -l 0
    DEF:c1=fwcpu.rrd:c1:AVERAGE
    DEF:c5=fwcpu.rrd:c5:AVERAGE
    DEF:c15=fwcpu.rrd:c15:AVERAGE
    LINE1:c1#F0000F:Cpu usage
    GPRINT:c1:AVERAGE:mean\: %%%.0lf
    GPRINT:c1:LAST:current\: %%%.0lf
    GPRINT:c1:MAX:peak\: %%%.0lf\l
  [fwconn]
    TITLE Connections
    YAXIS Connections
    DEF:c=fwconn.rrd:c:AVERAGE
    DEF:h=fwconn.rrd:h:AVERAGE
    CDEF:cK=c,1000,/
    CDEF:hK=h,1000,/
    AREA:c#0055FF:Connections
    LINE1:c#000000
    GPRINT:cK:AVERAGE:mean\: %.3lfK
    GPRINT:cK:LAST:current\: %.3lfK
    GPRINT:cK:MAX:peak\: %.3lfK\l
    LINE2:h#FF0000:Historic Peak\:
    GPRINT:hK:MAX: %.3lfK\l
  [fwmem]
    TITLE Memory usage
    YAXIS Percent
    -u 100
    -l 0
    DEF:mp=fwmem.rrd:mp:AVERAGE
    DEF:mt=fwmem.rrd:mt:AVERAGE
    CDEF:mtM=mt,1048576,/
    AREA:mp#0055FF:Used
    LINE1:mp#000000
    GPRINT:mp:AVERAGE:mean\: %%%.0lf
    GPRINT:mp:LAST:current\: %%%.0lf
    GPRINT:mp:MAX:peak\: %%%.0lf\l
    GPRINT:mtM:LAST:Total Memory\: %.0lfM\l

I prefer the NCV approach because it is clearly defined and is a stable part of 
hobbit. The downside is having to maintain configuration for one thing in two 
config files. Our decision to stick with NCV was based upon keeping the 
complexity in the configuration instead of the executables so we don't have to 
track changes in a bunch of 3rd party scripts. Devmon has been an exception to 
the 3rd-party-scripts rule since it handles a major system (snmp) that isn't 
(yet) a core part of hobbit.


-- 
S i m e o n  B e r k l e y

Systems Engineer
Mcclatchy Interactive