Monday, March 31, 2014

Event Integration From 3rd-party Monitoring Tools - Part 11: Develop your own adapter through email or iiSDK

What if your 3rd-party monitoring software cannot invoke an OS command to call msend API, and also cannot send a SNMP trap when an alert is raised?  There are two other methods available but you will need to develop your own adapter in order to integrate events from 3rd-party monitoring software into a BPPM cell.

If your 3rd-party monitoring software can send out an email when an alert is raised, you can consider developing your own email adapter.  You can choose a scripting language you are most comfortable for the development.

Step 1: Locate a computer that is capable of receiving emails, e.g., a UNIX machine with 'sendmail' process running.  

Step 2: Read each incoming email out of its inbox. 

Step 3: Parse both email header and email body.  You will need to understand the format of your email because each 3rd-party monitoring software has its own email format and possibly multiple formats depending on how you set it up.

Step 4: Call msend API with information from your parsed email.

Step 5: Follow the steps discussed in msend API from the posts "Event Integration From 3rd-party Monitoring Tools - Part 2, Part3, Part 4, Part 5" to complete your integration.

Please keep in mind that a custom-developed email adapter has no built-in guaranteed delivery mechanism.  You would need to use simple redundancy discussed in SNMP adapter for high availability.

The last but not the least method is to develop your own adapter using the free iiSDK provided by BMC. iiSDK  provides you a library of C or Java APIs that you can call from your C or Java program.  From your C or Java code you will build an executable program that runs as an adapter. 

Since you write your own code, you have more flexibility as what you want your adapter to do.  You can pull events from your 3rd-party monitoring software while you can only push events using msend API, SNMP adapter or email adapter.  You can also send events back to your 3rd-party monitoring software from BPPM cell to create a 2-way integration.  

Unless you are an experienced C or Java developer and also have the resource to maintain such a complex event adapter, I would suggest you to stay away from iiSDK. You won't get much support from BMC because iiSDK is free. 

What if you need a 2-way integration?  Actually the best way to send BPPM events back to your 3rd-party monitoring software (mostly with an incident ticket number and status) is to use the native interface/API offered by your 3rd-party monitoring software.  Comparing to using iiSDK, the native interface/API is faster, more reliable, less overhead, and much easier to maintain.

Please feel free to contact us if you need help for a custom-developed event adapter using either email or iiSDK.  We have extensive custom development experience and can give you a quick turn around for a cost-effective solution.

No comments:

Post a Comment