How to add an event/alert on Zenoss for a string type SNMP OID?

One possible solution turns out to be very simple but searching the internet yields a lot of similar question that are either not answered or ended up taking a different approach or being a different problem to begin with.

Zenoss offers the ability to integrate with Nagios plugins, which might not draw your attention if you don't know how this integration works.

Basically, it means you can call an arbitrary command as long as it returns exit code 0 for success (clear event) and 1, 2 or 3 for error (generate event), as well as a properly formatted string on STDOUT.

Armed with that information, you can write a simple script that reads your SNMP data using snmpget, parses it and prints the message you want to appear on the event.

A simple and generic Perl example could be:

#!/usr/bin/env perl
use strict;
use warnings;
use 5.010;

my ( $target, $oid, $msg ) = @ARGV;

my $value = `snmpget -v1 -c <comunity> $target $oid`;
$value =~ /STRING: "([^"]*)"/;

exit 0 unless $1;

say "$msg $1";
exit 1;

save that as $ZENHOME/libexec/string_monitor on your zenoss server and chmod +x $ZENHOME/libexec/string_monitor

Then on Monitoring Templates, add a Data Source of type COMMAND and fill the Command Template field like this:

string_monitor ${here/manageIp} <OID> "Error reported on:"

A few things to remember if you're not familiar with Zenoss:

If you have a setup with a zenoss server and many collectors, this will be called from the collector your device is assigned to, not from your main server, so remember to have the script available on all collectors. When it tries to call string_monitor on the collector and it is not there you will end up with an event on the Event Console that reads "Code: 2 - Msg: Misuse of shell builtins"

That is very misleading as it is easy to imply there is a problem with your script when the error was that $ZENHOME/libexec/string_monitor was not found. :-)

This can be particularly confusing if you use the "Test" button when setting up the Data Source, in which case the request will be made from the main server instead and it will appear to work and then display the above error on the console instead.

Also, to make your process faster, you might want to ssh into the collector, sudo -i -uzenoss and run zencommand run -d your.targetdevice.com -v 10

This should generate a full run on that device and your event should appear on the event console (assuming it wasn't empty).

After you get it working, it is also possible to pass actual numeric data from your script into Zenoss, the format for the printed line is:

Error string to display|failing=7 warning=31 good=24

failing, good and warning will be passed as data points on that data source and you can use MinMax Thresholds or plot graphics on them.

For a simple start, I recommend getting it working with a minimal/dummy script and expanding from there:

#!/usr/bin/env perl
use strict;
use warnings;
use 5.010;
say "We got an error|my=1 sample=6 values=10";
exit 1;