This documentation supports the 20.08 version of BMC Helix Multi-Cloud Service Management.

To view the documentation for the previous version, select 20.02 from the Product version menu.

IT operations management integrations for cloud monitoring

BMC Helix Multi-Cloud Broker provides integration with IT operations management (ITOM) vendors such as TrueSight Operations Management and Azure Monitor to create incidents in ITSM to track the availability, consistency, reliability and quality of your services.

Cloud monitoring for TrueSight Operations Management

TrueSight Operations Management delivers end-to-end performance monitoring and event management. It uses AIOps to dynamically learn behavior, correlate, analyze, and prioritize event data so that IT operations teams can predict, find and fix issues faster. TrueSight Operations Management monitors the availability of your applications and generates events if any asset is unavailable or compromised. BMC Helix Multi-Cloud Broker creates incidents in Smart IT whenever an event is triggered. 

Currently, the following features are supported:

  • Incidents are created in ITSM based on the events.
  • Events are updated in TrueSight Operations Management based on updates to ITSM incident.
  • TrueSight Operations Management event information is displayed in the Smart IT interface.

Cloud monitoring for Azure monitor

BMC Helix Multi-Cloud Broker enables you to monitor your Azure resources by receiving the Azure alerts metadata through the webhook option. BMC Helix Multi-Cloud Broker currently supports Metric alerts and Activity log alerts monitoring data.  BMC Helix Multi-Cloud Broker receives the Azure alerts metadata (JSON) and creates incidents in ITSM based on the set of flows, connectors, connector targets, and vendor data that you configure in BMC Helix Multi-Cloud Broker.

The following image shows how BMC Helix Multi-Cloud Broker processes the Azure alerts and displays the alert information in ITSM:

Currently, the following features are supported:

  • Incidents are created in ITSM based on the Azure alerts.
  • Incidents are updated in Azure Monitor based on updates to ITSM incident.
  • Azure alerts or events information is displayed in the Smart IT interface.

Using BMC Helix Multi-Cloud Broker with Remedy Mid-Tier

You can integrate BMC Helix Multi-Cloud Broker with ITOM vendors without using Smart IT.  Instead of the Smart IT console, you can use Remedy Mid-Tier to view incidents. If you are using Remedy Mid-Tier, you cannot view the vendor ticket details. However, you can view the work logs to verify that tickets are being brokered.

Components used to create tickets

BMC Helix Multi-Cloud Broker uses connectors, flows, and processes to create ITSM tickets from monitoring service notifications. Whenever the monitoring service fires notifications, the flow created between Azure Alerts connector and Multi-Cloud connector is triggered and BMC Helix Multi-Cloud Broker receives the ticket details. From BMC Helix Multi-Cloud Broker, the data is passed on to ITSM using the process defined in BMC Helix Platform. 

The following table describes these components in detail:



Where you can configure the component


A connector is an integration with a BMC or third-party application, for example, ITSM, Atlassian Jira, and Remedyforce. Each connector supports a certain number of triggers, actions, or both.

You configure a connector in BMC Helix Integration Service.
FlowA flow is a connection between two connectors that lets you accomplish a certain task. Each flow has a source application and a target application. A triggering event in the source application causes an action to take place in the target application.You can configure a flow in BMC Helix Integration Service.
Connector TargetBMC Helix Multi-Cloud Service Management defines processes to call vendor application specific actions to perform different business functions. When triggered by using a rule, a process uses the actions defined to implement the business logic for a given business case. The process is associated with a connector target which provides the process with the information required to connect to a vendor service.You configure connector targets in BMC Helix Innovation Studio.

The following image illustrates the data flow between the applications:


The out-of-the-box configuration requires minimal changes for most scenarios. As an administrator, you can customize the configuration based on your organization's requirements.

How incidents are consolidated into ITSM

A ITSM incident is created when an Azure alert is fired and meets the trigger condition defined in the flow.

The following image illustrates how BMC Helix Multi-Cloud Broker uses connectorsflows, and processes when a vendor ticket is created:

Where to go from here

Enabling prebuilt integration with Azure Monitor

Was this page helpful? Yes No Submitting... Thank you