Currently Being Moderated

Barracuda Spam Appliances

VERSION 5  Click to view document history

Created on: Sep 14, 2009 1:31 PM by pwinkeler - Last Modified:  Nov 9, 2009 1:33 PM by Matt Ray

Average User Rating
(0 ratings)

Submitted byPaul Winkeler Paul Winkeler


Description:

This ZenPack consists of an rrd template called Barracuda which defined at /Devices/Network. You'll want to bind it to your Barracuda device which presumably sits somewhere below that point.

The template contains performance graphs for the inbound queue and the number of:
  • allowed
  • tagged
  • quarantined
  • virus
  • bad recipient
  • spam
messages received by the Barracuda. In addition, it has a threshold for the inbound queue size of 25 but that may need tweaking.

 

All this information is gathered from the Barracuda device by retrieving the contents of the stats.cgi page over an https connection with the "wget" utility. The output of this http GET command is an XML document which is then parsed by some Perl code called "check_cuda" which is provided as a datasource inside this ZenPack / template. The nice thing here is that by not using SNMP, this ZenPack will work for collecting data on even the 300 series (you need to purchase at least a Barracuda 400 for SNMP). It does its monitoring by watching the trailing 24 hour volume of messages and also the inbound message queue size in separate graphs. I only set a threshold on the inbound queue size and I haven't monitored enough of these units yet to know what is reasonable threshold but 45 gets me just a few warnings a day at a site that sees 100k+ messages a day.

 

If you have any questions, please feel free to contact me at pwinkeler@pbnj-solutions.com

 

 


Screenshots:

 

 


REQUIREMENTS:

     Zenoss Version: 2.2

     ZenPack Dependencies:

     External Dependencies:

 

  • The datasource is a Perl script called check_cuda. It uses generic Perl code but does rely on XML::Simple which you may have to install
  • The PERL script in turn uses wget to retrieve the Barracuda's basic statistics page; you may need to install it
  • The rrd Template assumes your Zenoss installation is at /usr/local/zenoss, you may need to change that assumption
  • Finally note that the template associated with this ZenPack defines it self under /Devices/Network so your Barracuda device should be located somewhere at or below this point.

     Installation:

 


Source: http://zenpacks.zenoss.org/trac-zenpacks/browser/zenpacks/ZenPacks.PBnJSolutions.Barracuda.Watcher

Tagged Releases:

     http://zenpacks.zenoss.org/trac-zenpacks/browser/tags/barracuda-1.2

Change History:

 


Trac tickets: http://zenpacks.zenoss.org/trac-zenpacks/report/1

Known issues:


19,846 Views Tags: network, spam, barracuda, application
mwoodling mwoodling  says:

John, there are problems with this Zenpack.  I am running Zenoss 2.4.5 (stack-installed) on CentOS 5.2.  When I try to test an error message that the path ending in "check_cuda" can't be found.  If you modify the path to be:

 

"/usr/bin/perl $$ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H $devname"

 

then you get farther:

 

Executing command
/usr/bin/perl $ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H mx4.heatseeker.com
against mx4.heatseeker.com
Can't locate utils.pm in @INC (@INC contains: /usr/local/zenoss/zenoss/libexec /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda line 7.
BEGIN failed--compilation aborted at /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda line 7.
DONE in 0 seconds

 

What is utils.pm and how to I add it?

 

What are the correct paths for:

 

  • "zZenPacksPBnJSolutionsBarracudaWatcherlibexec"
  • check_cuda's command template,
    • currently: "/usr/bin/perl $$ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H $devname"
    • default: "/usr/bin/perl $$ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H $devname

 

Matt

John Hamilton John Hamilton  says in response to mwoodling:

Matt,

I am not the author of this ZenPack, merely the guy who posted it.     Paul Winkeler is the one who wrote this ZenPack for us.  Best to post your questions in our ZenPacks Forum where you'll find many people willing to help.  zenoss-zenpacks

dveezy dveezy  says in response to John Hamilton:
This zenpack makes refrences to several invalid paths. I changed the path like you did, and copied utils.pm to the proper directory. I then completely restarted Zenoss, binded the Barracuda template to my \devices\network\barracuda class, then remodeled the devices, and I am successfully using the plug in on my INBOUND devices.

Bookmarked By (0)

More Like This

  • Retrieving data ...

More by pwinkeler