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.

Azure Monitor integration reference

To establish integration with Azure Monitor, configure the following connectors, flows, and connector targets. You need to set up tenant level configurations. BMC Helix Multi-Cloud Broker provides out-of-the-box mappings and application level configurations required for the integration. After you complete the integration, you can broker tickets from Azure Monitor to ITSM, update Azure Monitor ticket details from ITSM and so on. Each flow in the list of flows is essentially a feature that you can use. Depending upon your use case, you might have to configure multiple flows. BMC Helix Multi-Cloud Broker logically chains the flows and connector processes to complete the feature.

List of connectors and configuration values for integration with Azure Monitor

You must configure the following connectors when setting up integration with Azure Monitor. These connectors are integration points for the respective applications. For instance, to send the data from BMC Helix Multi-Cloud Broker to Azure Monitor, you must configure a flow from Multi-Cloud connector to Azure Alerts connector.

  • Configuration
    If you are integrating BMC Helix Multi-Cloud Broker with an on-premises instance of ITSM, enter the following values:

    FieldValue
    SiteSelect the site that you created for Remedy.
    AR serverEnter the name of your on-premises AR System server.
    AR server portEnter the port number for your on-premises AR System server.
  • Account
    Add a ITSM user account that has permissions to view business service requests and permissions to update incidents, change, or problem requests.


  • Configuration
    While activating BMC Helix Multi-Cloud Broker, BMC configures the Multi-Cloud connector. Do not modify the default Multi-Cloud connector configuration.
  • Account
    BMC sets up the account for the Multi-Cloud connector.
    Click to re-authenticate after you have changed the password for your tenant administrator user account in BMC Helix Innovation Studio.
    For information about changing the user password, see Creating or modifying Person data Open link .


  • Configuration
    If you are integrating BMC Helix Multi-Cloud Broker with Azure Monitor, enter the following values:

    FieldValue
    NameEnter a name for your connector configuration.
    DescriptionEnter a description for your connector configuration.
    Site

    Select the site required to establish a connection between Azure Monitor and BMC Helix Integration Service. You can either use the default cloud site or create your own site.

    Number of instancesRetain the default value.
    WebHook Message TypeSelect Basic or Secure. Select the same type when creating actions on Azure alerts in Microsoft Azure.
    Azure Tenant IdRequired only when you use secure webhook method.
    Application IdRequired only when you use secure webhook method.
    Application ID URIRequired only when you use secure webhook method.


  • Configuration
    To send email notifications for errors, specify values for the following fields:

    FieldValue
    NameEnter a name for the connector configuration.
    SiteSelect the appropriate site for your email server.
    Connection typeSelect the type of connection for your email server.
  • Account
    Add an email account to be used for sending error notifications.

List of flows and configuration values for integration with Azure Monitor

You can configure the following flows when setting up integration with Azure Monitor. Each flow is self descriptive, for example to create an incident in ITSM from Azure Monitor, you must configure Create Incident from Azure Alerts flow.

  • Trigger

    FieldValue
    Alert Type  Metric, Log, or Activity Log
  • Field Mapping

    Do not change the following default field mappings.

    FieldValue
    SummaryMonitoring Service, Monitor Condition and so on
    PriorityMonitoring Service, Monitor Condition and so on
    DescriptionDescription
    UrgencySeverity
    Incident TypeUser Service Restoration
    Vendor Ticket IdShort Alert Id

    Note

    While configuring Create Incident from Azure Alerts flow, you can extract the Azure asset name for which the alert is generated by mapping the LogAffected Configuration Item fields and Metric Condition Dimensions fields in the flow, and by adding transformations for the properties of these fields.


  • Trigger

    FieldValue
    Alert Type  Metric, Log, or Activity Log
  • Field Mapping

    Do not change the following default field mappings.

    FieldValue
    SummaryMonitoring Service, Monitor Condition and so on
    PriorityMonitoring Service, Monitor Condition and so on
    DescriptionDescription
    UrgencySeverity
    Incident TypeUser Service Restoration
    Vendor Ticket IdShort Alert Id

    Note

    While configuring Create Incident from Azure Alerts flow, you can extract the Azure asset name for which the alert is generated by mapping the LogAffected Configuration Item fields and Metric Condition Dimensions fields in the flow, and by adding transformations for the properties of these fields.


  • Trigger

    FieldValue
    Condition is Retain the webhook condition
    Source ID contains Azure Alerts
  • Field Mapping

    The following values are mapped out-of-the-box.

    FieldValue
    Parent Ticket Id source ID
    Alert Id Vendor Ticket Data
    Alert State Status

List of connector targets for integration with Azure Monitor

When a ticket is brokered from any vendor to ITSM, the ticket data first comes in BMC Helix Multi-Cloud Broker before being sent to ITSM. To send the data from BMC Helix Multi-Cloud Broker to ITSM, you must configure the MCSM ITSM connector target and set it in the Connector Process ITSM.


For the MCSM ITSM connector target, define the connection configuration and profile required by the connector process.

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

Comments