IT Operations Management (ITOM)

Bring your own code: How to simplify customizing event correlation software

Bring your own code: How to simplify customizing event correlation software

Stefan Bergstein

Extensibility and customization are key capabilities that every enterprise software should offer. As is so often the case, there is no one size fits all enterprise software solution, because your business process will always differ from any “standard”—that’s what gives you a competitive edge.


Leading event correlation and monitoring software will not force users to write code for simple customization of out-of-the-box behavior of the solutions. For example, event management systems such as HP Operations Manager offer de-duplication, pair-wise correlation and storm detection, and you can easily turn on each of these features with a few parameters. No coding is required to adjust these event management features to your needs. You can download HP Operations Manager here.


But what if you need even more customization? Is any complex coding required? Does the overall system become complex, or even worse, does it become fragile because of custom code that you inject?


A fresh approach to extensibility and customization

Old school extensibility is based on legacy APIs that requires code compilation, which would lead into your own custom processes. An alternative has been to use shell scripts — much simpler, but these usually do not perform or they create a huge resource overhead.

The HP Operations Manager i (OMi) development team really grasped all your feedback and came up with a fresh approach: Use embedded scripting for event management extensibility and customization.

With HP OMi, it is possible to easily tap into the event processing flow with endless flexibility for your creative customizations without the burden of compiling code and managing the lifecycle of your custom processes during runtime.


HP OMi currently features six different areas where a user is allowed to add custom functionality using groovy scripts:

  1. Event-processing interface (EPI)
  2. Custom actions
  3. Topology synchronization
  4. Certificates
  5. Event forwarding
  6. Service health

This new approach allows you to add business logic to the system in ways that would not be possible using the standard UI and configuration. If there is something you cannot do with the out-of-the-box product, then there may be a groovy script interface to allow you to add the functionality yourself.


Simple ways to get started

The event-processing interface (EPI) is a good example of what’s possible. Talking to many users and administrators of HP OM and the newer HP OMi I learned that custom event enrichment, as well as custom programmatic event changes, can provide the necessary advantages for adjusting the overall event management processes to fit to your organization’s needs.


Using the new approach, instead of implementing your own processes in C, C++ or Java, you can now load a simple groovy script into HP OMi. There’s no need to compile code, no need to bother if your custom process runs all the time. HP OMi will manage and execute your groovy script whenever a new event arrives that should be processed by your code.


So, how do you get started? The HP BSM Extensibility Guide contains an informative chapter about the event-processing interface. Besides concepts and examples for the event-processing interface, it offers also covers custom action scripts and troubleshooting tips and tricks.


But in case you want to get into action right away, here are two tools to check out:

1)  The
HP OMi Server script examples in the BSM Community Content space of HP Live Network.
There are simple scripts here that you can try out and play with. My favorite example is the event enrichment example ResolveLocationFromDB. This example script shows how you can enrich events with information from a custom database. For each event that arrives at the OMi server, the script will add location and contact information of the computing server to the event.
A colleague of mine wrote a very useful blog post about how to use External Nodes known from OM in OMi, which illustrates a good use case of event processing customization beyond the traditional event enrichment scenario. The BSM Community Content space has more examples for you, too, and I encourage you to share your scripts on HP Live Network.


2)  The other tool that I recommend is the HP OMi Script Development Kit
This tool helps you edit, validate, test, and debug HP OMi groovy scripts within Eclipse, outside of an HP OMi installation. The HP OMi Script Development Kit in Eclipse will allow you to:

  • Use auto-completion and online documentation for HP OMi's Event Processing Interface (EPI) APIs
  • Create and feed test events into an EPI scripts and get the resulting modifications back for verification
  • Get visual debugging support to step through EPI script execution
  • Import sample events from a running HP OMi system
  • Configure access to a running HP OMi Runtime Service Model (RTSM) instance for topology queries

Extensibility and customization of your HP operations event management solution has changed a lot with the new embedded scripting approach in HP Operations Manager i. The new “bring your own code” concept in HP OMi provides you with advanced event management capabilities that have never been easier to apply. Be sure to explore other examples on HP Live Network.


You can also download HP Operations Manager i here.


Do you like to read more about extensibility, content and integrations? Please check out the following posts:



  • operations bridge
About the Author

Stefan Bergstein

ITOM Software, Infrastructure Automation and Hybrid Cloud at Hewlett Packard Enterprise Software now part of Micro Focus