HP OVO to Nagios template migration tool Files

File Date : 3/1/2011
File Name : README_ovo_to_nagios.txt
File Ver  : 1.0
Script    : ovo_to_nagios.pl 
Author    : Ryan Ash (State Farm Insurance)

LICENSE:

This Plugin is Licensed Under the BSD LICENSE:

Copyright (c) 2011, State Farm Insurance (R) 

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

o Neither the name of State Farm Insurance nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

ADDITIONAL DISCLAIMER:
  - I don't claim to be a perl master.  Nor do I expect this script meet everyone's needs without a tuning.  
  - Look for "NOTE:"  This will help you find section which you may have to update to fit your needs. 

ASSUMPTIONS: 
  The purpose of this script is to provide users of commercial monitoring tools an easier migration path to Nagios.  This script will not get 100% of the way to a working set of nagios cfg's and clients side cfg/ini/conf files.  It will however do extensive leg work if you have a large number of template conditions as we did.  It is very important that you review every single contition that is migrated using this script to ensure it was done accurately.  Every company writes their templates/conditions a different way and while writing this script I only had access to our conditions.   

SYSTEM REQUIREMENTS: 
  - This was built on HPUX with perl v5.10.0.  It has been testing on RHEL and hpux but there is no reason why it wouldn't work on *nix

INSTALLATION NOTES:
  - Ensure you have a working Perl install
  - Need to have your OVO templates backed up in the following format to allow the script to properly parse them  (See USAGE)

NEW FEATURES:
  1. n/a (initial release)

BUG FIXES:
  - n/a

INSTALL:
  1. untar file
  2. run with -h to familiarize yourself with the options
  3. execute.  You will likely have to tune the script to fit your needs so I hope you know some perl 
  4. Feel free to email the author with questions but I don't guarantee I will get back to everyone

USAGE: 
  1. First thing you will need is a backup of your OVO conditions from which this script can pull the conditions. Here is the command which can be used to create these backups.
		opccfgdwn -force download.dsf <path>/<directory>
    note: download.dsf is a ascii file which only contains "* ;"  
  2. I decided to use macros in the Nagios service/host definitions to help us satisfy our needs.  Below are the names of those macros and their function. You can obviously change these macro names to better fit your needs. 
    _CUSTOM_ALERT_TEXT - define the actual text that will be used in alert text.  This can include a variable
    _CUSTOM_ARG_FETCH - This is the means by which we obtain the values from the output to put in the _CUSTOM_ALERT_TEXT, this is simply a perl regex
    _CUSTOM_TEXT
    _CUSTOM_AUTOACTION - These two are simply informational and help you see what was actually in the OVO condition 
    _CUSTOM_EVENT_PARAMS - defines the actual script that will be run by the autoaction wrapper (see addtional tools used)
    _CUSTOM_ARG_EVENTHANDLER - grabs values from the output out the autoaction/eventhandler for usage in the alert text  

KNOWN ISSUES:
  - I hope to expand on this script taking into account other people's templates and conditions.  
  - I hope to provide the option to have your conditions/checks built for NSClient++ rather than always check_logfiles.exe 
  - Suppress conditions are not properly accounted for yet

ADDITIONAL PIECES:
  1. autoaction/eventhandler wrapper script "svc_autoaction_wrapper" (hopefully it will be shared in the future)
  2. windows perl cron script (hopefully it will be shared in the future)
  3. EXAMPLES_ovo_to_nagios.pl : contains some example config information and explainations

AUTHOR:
  I wrote this script while working on a migration from HP OVO to Nagios at State Farm Insurance.  State Farm graciously allowed me to share
  the code with the open source community.  I have been working on with in the realm of infrastructure management and monitoring for >8yrs.  
  It is my intention to provide some degree of ongoing support for this script.