Developing Plugins For Use With Embedded Perl

Up ToUp To: Contents
See Also See Also: Embedded Perl Interpreter Overview, Plugin API


Stanley Hopcroft has worked with the embedded Perl interpreter quite a bit and has commented on the advantages/disadvanges of using it. He has also given several helpful hints on creating Perl plugins that work properly with the embedded interpreter. The majority of this documentation comes from his comments.

It should be noted that "ePN", as used in this documentation, refers to embedded Perl Nagios, or if you prefer, Nagios compiled with an embedded Perl interpreter.

Target Audience

Things you should do when developing a Perl Plugin (ePN or not)

Things you must do to develop a Perl plugin for ePN

  1. <DATA> can not be used; use here documents instead e.g.

    my $data = <<DATA;
    portmapper 100000
    portmap 100000
    sunrpc 100000
    rpcbind 100000
    rstatd 100001
    rstat 100001
    rup 100001
    %prognum = map { my($a, $b) = split; ($a, $b) } split(/\n/, $data) ;
  2. BEGIN blocks will not work as you expect. May be best to avoid.

  3. Ensure that it is squeaky clean at compile time i.e.

  4. Avoid lexical variables (my) with global scope as a means of passing __variable__ data into subroutines. In fact this is __fatal__ if the subroutine is called by the plugin more than once when the check is run. Such subroutines act as 'closures' that lock the global lexicals first value into subsequent calls of the subroutine. If however, your global is read-only (a complicated structure for example) this is not a problem. What Bekman recommends you do instead, is any of the following:

  5. Be aware of where you can get more information.

    Useful information can be had from the usual suspects (the O'Reilly books, plus Damien Conways "Object Oriented Perl") but for the really useful stuff in the right context start at Stas Bekman's mod_perl guide at

    This wonderful book sized document has nothing whatsoever about Nagios, but all about writing Perl programs for the embedded Perl interpreter in Apache (ie Doug MacEacherns mod_perl).

    The perlembed manpage is essential for context and encouragement.

    On the basis that Lincoln Stein and Doug MacEachern know a thing or two about Perl and embedding Perl, their book 'Writing Apache Modules with Perl and C' is almost certainly worth looking at.

  6. Be aware that your plugin may return strange values with an ePN and that this is likely to be caused by the problem in item #4 above

  7. Be prepared to debug via:

    perl -MO::Deparse <your_program>

  8. Be aware of what ePN is transforming your plugin too, and if all else fails try and debug the transformed version.

    As you can see below rewrites your plugin as a subroutine called 'hndlr' in the package named 'Embed::<something_related_to_your_plugin_file_name>'.

    Your plugin may be expecting command line arguments in @ARGV so also assigns @_ to @ARGV.

    This in turn gets 'eval' ed and if the eval raises an error (any parse error and run error), the plugin gets chucked out.

    The following output shows how a test ePN transformed the check_rpc plugin before attempting to execute it. Most of the code from the actual plugin is not shown, as we are interested in only the transformations that the ePN has made to the plugin). For clarity, transformations are shown in red:

                    package main;
                    use subs 'CORE::GLOBAL::exit';
                    sub CORE::GLOBAL::exit { die "ExitTrap: $_[0] 
    (Embed::check_5frpc)"; }
                    package Embed::check_5frpc; sub hndlr { shift(@_);
    #! /usr/bin/perl -w
    # check_rpc plugin for Nagios
    # usage:
    #    check_rpc host service
    # Check if an rpc serice is registered and running
    # using rpcinfo - $proto $host $prognum 2>&1 |";
    # Use these hosts.cfg entries as examples
    # command[check_nfs]=/some/path/libexec/check_rpc $HOSTADDRESS$ nfs
    # service[check_nfs]=NFS;24x7;3;5;5;unix-admin;60;24x7;1;1;1;;check_rpc
    # initial version: 3 May 2000 by Truongchinh Nguyen and Karl DeBisschop
    # current status: $Revision: 1.24 $
    # Copyright Notice: GPL
    ... rest of plugin code goes here (it was removed for brevity) ...

  9. Don't use 'use diagnostics' in a plugin run by your production ePN. I think it causes__all__ the Perl plugins to return CRITICAL.

  10. Consider using a mini embedded Perl C program to check your plugin. This is not sufficient to guarantee your plugin will perform Ok with an ePN but if the plugin fails this test it will certainly fail with your ePN. [ A sample mini ePN is included in the contrib/ directory of the Nagios distribution for use in testing Perl plugins. Change to the contrib/ directory and type 'make mini_epn' to compile it. It must be executed from the same directory that the file resides in (this file is distributed with Nagios). ]