Integrating with Azure Monitor

Azure Monitor sends notification about any potential critical condition of the applications and services, so that you can proactively take the corrective measures.

Related topics

Editing-and-deleting-integrations

Monitoring-the-on-premises-gateway-node-for-streaming-interruptions-and-node-health

You can view the collected data in various BMC Helix applications and derive the following benefits:

BMC Helix application	Type of data collected or viewed	Benefits
BMC Helix Operations Management	Events (Azure Monitor alerts are received as events)	Use a centralized event view to monitor and manage events, perform event operations, and filter events. Identify actionable events from a large volume of event data by processing events. For more information, see Monitoring events and reducing event noise.
BMC Helix AIOps	Situations (created from events)	Improve the mean time to resolve (MTTR) based on the situation-driven workflow. Lower the mean time to detect or discover (MTTD) and the time required for investigating tickets. For more information, see Monitoring situations.

As a tenant administrator, perform the following steps to configure a connection with Azure Monitor, verify the connection, and view the collected data in various BMC Helix applications.

- The [confluence_layout-cell] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
On the CONNECTORS tab, click in the SOURCES panel .
Click the Azure Monitortile.
Specify the following details for the source connection:
1. Specify a unique instance name.
  Best practice
  We recommend that you specify the instance name in the following format:
  <sourceType>_<sourceControllerServerName>{_<InstanceQualifier>}
  The instance qualifier helps you to distinguish the multiple instances configured from the same source server. For example, you can name your instances as Azure_Monitor_Alerts, Azure_Monitor_Alerts_TEST, and so on.
  Best practice
  We recommend that you specify the instance name in the following format:
  <sourceType>_<sourceControllerServerName>{_<InstanceQualifier>}
  The instance qualifier helps you to distinguish the multiple instances configured from the same source server. For example, you can name your instances as Azure_Monitor_Alerts, Azure_Monitor_Alerts_TEST, and so on.
2. Specify the Azure Monitor Tenant Id, Client Id, and Client Secret.
3. Specify the Azure resource URL (default value is https://management.azure.com/).
4. Specify the Azure authentication host (default value is management.azure.com).
5. Specify the Azure Active Directory (AD) authentication host (default value is login.microsoftonline.com).
6. Specify the number of maximum concurrent REST API requests that should be executed during a collection schedule (default value is 5).
7. Click Proxy and specify if you want to configure a proxy server. If yes, specify the host name and port number (default value is 8888).
Click VALIDATE AND CREATE.
The specified connection details are validated and the corresponding source connection is created in the Source Connection list.
Select the source connection that you created from the list if it is not selected already.
Important
The destination host connection is created and configured automatically for each tenant when the source connection is created.
Click a data type and specify the configuration parameters in the Collectors section as described in the following table:
Click CREATE COLLECTORS to create the required collector streams for the selected data types.
Click a data type and specify the configuration parameters in the Distributors section as described in the following table:
Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data types.
Click one of the following buttons:
- SAVE STREAM : Click this button if you want to edit the integration details before creating the instance. After you save the stream, the connector that you just created is listed in the SOURCES panel. Move the slider to the right to start the data stream.
- SAVE AND START STREAM : Click this button if you want to save the integration details and start receiving data immediately.
Important
For a data stream, the Run Latency (max/avg), Items (Avg per Run), and Last Run Status columns on the Streams page might show the status as No Runs during the data collection process. After completion of the process, these columns are updated with an appropriate status.
ImportantFor a data stream, the Run Latency (max/avg), Items (Avg per Run), and Last Run Status columns on the Streams page might show the status as No Runs during the data collection process. After completion of the process, these columns are updated with an appropriate status.
For more information about data streams, see Starting-or-stopping-data-streams.

Task 3: To verify the connection

In BMC Helix Intelligent Integrations , on the SOURCES panel, confirm that the data streams for the integration you created are running. Data streaming is indicated by moving colored arrows.

A moving dark blue arrow () indicates that the event stream is running. Event data is pushed according to the configured Collection Schedule interval.

To view data in BMC Helix applications

View data collected from Azure Monitor in BMC Helix applications.

To view events in BMC Helix Operations Management

In BMC Helix Operations Management, select Monitoring > Events.
Filter the events by the MSAzureAlert class.

Incoming events from Azure Monitor are processed in BMC Helix Operations Management through a set of deduplication rules to determine whether the incoming event is a duplicate event or a new event. For more information, see Event-deduplication-suppression-and-closure-for-reducing-event-noise.

For information about events, see Monitoring and managing events.

To view situations in BMC Helix AIOps

Before you view situations in BMC Helix AIOps, create a Business Service model in BMC Helix Discovery. For information about creating models, see Managing models

In BMC Helix AIOps, on the Overview page, view the situations for the event data received from Azure Monitor.

For information about situations, see Monitoring and investigating situations.