In June 2019 a new release of Cloud Event Management, including Runbook Automation has been made available. You can pick up the changes for your ICP installation or enjoy the automated update on the SaaS offering.

Knowledge Center documentation of new features

Our official documentation in the Knowledge Center once again contains the relevant updates for CEM and RBA. Browse to these pages for a brief update, as well as a historical view of past updates:

What’s New in June 2019

Completion of RBA features for CEM

In the past, CEM customers had to live without a few crucial RBA features, present in RBA PD or RBA standalone, but not in CEM. This has been rectified and now the complete feature set of RBA is always available. The two most prominent highlights in this regard, are the Trigger functionality and the Group Access feature:

The Group Access feature is a tool to manage runbook visibility for operators. It can be separately enabled from the Runbook Library page. If enabled, operators can only see runbooks, if they share at least one group with the runbook. A freshly created account without group memberships would consequently see no runbooks at all. By placing the operators and the runbooks in the group you want, you can fine-tune what the operators can see and do. A common demand from our customers is to hide critical runbooks from a larger audience and only make them available to a select few experts. RBA is using the same groups as CEM does, so you can enjoy the integrated experience.

A common use case for our RBA PD customers is launching a runbook directly from the OMNIbus event console. In the past, this functionality was provided by the Trigger Service. The Trigger Service however was not part of CEM deployments, so the triggers were not available in CEM deployments. For the June 2019 release, we integrated all Trigger Service functionality into the Runbook Service. This means CEM deployments get all the Trigger features, while the deployment for RBA PD will be somewhat smaller, by saving one running container.

Runbook Automation API

While we reworked the trigger functionality, we took the opportunity to extend our public v1 RBA API. It now contains eight(!) new API routes to manage triggres. You can use those new API endpoints to create triggers, get triggers, change triggers, as well as getting information about the event columns and filter from the configured Impact. Here is a short list of the new endpoints:

  • GET /triggers – Get all triggers
  • POST /triggers – Create a new trigger
  • GET /triggers/{triggerID} – Get a single trigger
  • PUT /triggers/{triggerID} – Change an existing trigger
  • DELETE /triggers/{triggerID} – Delete an existing trigger
  • GET /columns – Display the event columns existing in the connected
  • GET /filters – Get predefined filters
  • POST /filters – Test filters

Access the full RBA API for a full documentation.

Browser Support

Say goodbye to your MS Internet Explorer, say hello to MS Edge, which is now officially supported!

Certified IBM Cloud Pak

Cloud Event Management has achieved IBM certified Cloud Pak status. This ensures that Cloud Event Management meets the enhanced enterprise-grade criteria for security, integration, and workload availability. See Identifying IBM Cloud Paks to learn more.

Red Hat OpenShift support

You can deploy Cloud Event Management running on IBM Cloud Private with Red Hat OpenShift. If you want to install your CEM on OpenShift, follow the installation instructions.

Event enrichment using lookup tables

Lookup tables use information in your events to determine how to add other fields from external data sources, effectively letting you enrich incoming events with important additional data. Event policies can contain multiple lookup tables, so you can add a lot of extra information. The Knowledge Center page Create Lookup Tables describes how to set them up.

Event Integration with Netcool/OMNIbus

Our portfolio becomes better integrated with each release. With the latest CEM release you can forward events through the IBM Secure Gateway from the cloud securely to your on-premise OMNIbus. The event policies also received an update, to make this easily accessible. The Knowledge Center has more information on Sending events to OMNIbus and Setting up event policies.

Smaller Updates

Cloud Event Management has so many updates, they don’t fit all in here. The following updates are quality of life or maybe just the little thing you always wanted in CEM:

  • Azure Log Alert – Log Analytics now supported
  • Set up VMware vSphere as an event source in Cloud Event Management
  • Backup and restore your Kubernetes cluster resources and persistent volumes (ICP only)

Join The Discussion

Your email address will not be published. Required fields are marked *