This document describes how to integrate op5 Monitor to BMC Proactive Net Performance Management (BPPM) using BMC Impact Poster (msend). It requires configuration to be added on the receiving end and these steps are not covered in this how-to
Attachment: msend is installed in /opt/plugins/custom
Attachment: monitor_msendwrapper.pl is installed in /opt/plugins/custom
The commands needed in op5 Monitor are added to /opt/monitor/etc/misccommands.cfg:
Classes specified are in 1:1 relation to the information included in a regular email-notification by default. It's easy to expand the commands above with other classes documented in the official msend documentation to include a lot more info if needed. We have an "extended" version which utilizes all available classes in Monitor to be submitted to BPPM but should only be used if the standard commands lacks information needed as it adds overhead to the call.
To use these commands you need to specify a contact much like when sending emails or text-messages and if needed added to a contact-group for example the default contact-group "support-group" which are used in templates so all hosts and services will be enabled at once. The contact set up in this specific case is named "msend-to-bem" and are a member of support-group, host_notification_command is set to host-msend-to-bem and service_notifcation_command is set to service-msend-to-bem
Further information about configure these commands and other useful information about op5 Monitor please visit our online manual.
Configuration for msend
Are specified directly in monitor_msendwrapper.pl and take special notice of "COMMANDLINE="-n @bmcis02:1828#mc -a OP5_EVENT -b " which are specific to this environment.
Manual tests without the use of the wrapper can be done using this line: /opt/plugins/custom/msend -n bmcis02 -n @bmcis02:1828#mc -a OP5_EVENT -m "testing as monitor user" and the result/connectivity could be verified on the receiving end.
To test the wrapper, uncomment the line in monitor_msendwrapper.pl: #`echo "$MSEND" "$COMMANDLINE" "$ARGS" >> /tmp/msend.log`; and manually execute the script. The log will show the actual command that will be used but no classes. To also expand classes and macros op5 Monitor must be running the script as a notification command. (Unless manually create a script setting these variables)
To test the full command and classes/macros have the line in monitor_msendwrapper.pl un-commended as stated above and trigger a event in op5 Monitor (ex use passive check-results) and take a look in mend.log. In this case nothing has been sent to BPPM only logged to this file. To test this for real comment out the line and make sure the last line in the script is uncommented. Verify on BPPM side what info gets sent.
Successful test should produce a line in msend.log looking something like this:
To be able to use the full functionality of msend capabilities such as buffering of events and heartbeat submission to BPPM requires further configuration. To date no such information are available so documentation is lacking this information but will be completed when and if this will be added.
Other documentation resources
http://www.op5.com/manuals/ contain all nescessary information on how to configure commands, contacts and what/when to notify on events and much more.