Field descriptions:
  _CUSTOM_EVENT_PARAMS        This field indicates what script will actually be run by the eventhandler and the params it needs 
  _CUSTOM_EVENT_OPTIONS       client,ANNOTATE,ACK,debug 
  _CUSTOM_EVENT_OPTIONS : This is required and it contains the options you which to utilize, order of these doesn't matter
      [server|client] tells server where to run this, server it just shells out and runs it, client it assumes _CUSTOM_EVENT_PARAMS is an NRPE cmd alias it runs on associated client 
      ANNOTATE - Indicates that you want to take the output from the autoaction to be included in the ticket 
      ACK - ack the event depending on result from the autoaction
        Generally speaking OVO uses a zero return code to indicate an ack.  However some conditions act differently.  So you can specify which return code will ack message.  Example "ACK:1" will override it to ack on rc=1.  You don't need to do an "ACK:0" because it is default 
      debug - enables debugs 
      "stateid:12" - Runs only on warning and critical states 
      "attempt:2" - Runs only when attempt is equal 2.  The attempt is the nagios parameter.  

  _CUSTOM_ARG_EVENTHANDLER    regex to pull values from event output
  _CUSTOM_ARG_FETCH           regex to pull values for ticket text 
  _CUSTOM_OVO_TEMPLATE        just references what OVO template this condition came from
  _CUSTOM_ARG_CRON            regex to pull values for CRON actions
  notes                    We are using the notes field to mimic functionality from OVO in Nagios.  
                           For example our legend for that field is < <ci>:<object>:<application grp>:<knowledge item>:<msggrp>

------------------------------------
Example of the a server side config
define service{ 
  service_description     NG-TC-W2K3-BASE_1 
  display_name            checkServiceState lanmanserver 
  servicegroups           NG-TC-W2K3-BASE_service_group 
  hostgroup_name          NG-TC-W2K3-BASE 
  _CUSTOM_ANNOTATIONS         null 
  _CUSTOM_EVENT_PARAMS        test_script.pl --CUSTOM_ARG1-- 
  _CUSTOM_EVENT_OPTIONS       client,ANNOTATE,ACK,debug 
  _CUSTOM_ARG_EVENTHANDLER    Circuit Number\s*:\s*(\S+) 
  event_handler           svc_autoaction_wrapper 
  use                     generic-passive-service-noperf 
  notes                   :<workgroup>::<knowledge item code>:
} 


------------------------------------
Another Example of a server side config
define service {  
  service_description      Event_7024_W2K3_BASE__The_service_has_stopped
  display_name             Event 7024  W2K3_BASE: (SCM) The -service- service has stopped, error -error-  
  servicegroups            NG-BASE-W2K3_service_group  
  hostgroup_name           NG-BASE-W2K3  
  use                      generic-passive-service-noperf  
  _CUSTOM_TEXT                 W2K3_BASE: (SCM) --CUSTOM_ARG1--  
  _CUSTOM_ARG_FETCH            Here is the pitch from (.*) the star lefty  
  _CUSTOM_OVO_TEMPLATE         LOGFILE BASE-W2K3-SYS_Log  
  _CUSTOM_ARG_CRON             OBJECT=(\w+)\s 
  notes                    <ci>:<object>:<application grp>:<knowledge item>:<msggrp>
  }  

