[collectd] Collectd notification handler

DavidHalko davidhalko at gmail.com
Sat Apr 14 08:22:56 CEST 2012

I have a similar need, need a non-programming solution.

How about appending to a file or named pipe, where a reader program could interface to it? This type of extension would work for me.

How about an SNMP Trap extension? That is how everyone else does it, in the network management world... this would be awesome, since snmp would be fast and easy to integrate to (netsnmp trapd or standard network management platform.)

Maybe syslog? That is the standard unix way. Any syslog reader could take it from there.

The community really needs a standard way to deal with these things, so we don't have to program to use the notifications in high capacity settings.


Sent from my iPhone 

On Apr 13, 2012, at 4:53 PM, Jason Stelzer <jason.stelzer at gmail.com> wrote:

> I am trying to avoid the fork/exec overhead when large numbers of
> requests come in on a fairly busy collector.
> What I would like to do is simply pass along the notification to a
> daemon that will decide if the problem warrants an alert or not.
> I am considering following one of the notify_ plugins such as
> notify_desktop/notify_email as an example and creating a
> notify_network plugin that simply passes notifications along to a
> different host/port that can do a little work to mitigate flap and has
> rules like "greater than X for Y minutes", etc.
> The documentation for notification call backs is a big TODO here
> http://collectd.org/wiki/index.php/Plugin_architecture but I think the
> bigger question for me is how people generally go about building their
> plugins for collectd. What's the right combination of autoconf,
> automake and libtool? Should I just write a hacked up Makefile to
> compile the plugin and then see about contributing the code?
> The other alternative is the perl plugin but there don't seem to be
> any examples of how to configure it to handle notifications as opposed
> to reads.
> -- 
> J.
> _______________________________________________
> collectd mailing list
> collectd at verplant.org
> http://mailman.verplant.org/listinfo/collectd

More information about the collectd mailing list