Use the Azure Monitor Metrics Connector with Splunk DSP

Use the Azure Monitor Metrics Connector to collect metrics data from Microsoft Azure Monitor. Azure Monitor helps you understand how your applications are performing, and proactively identifies issues affecting them and the resources they depend on. Search for "Azure Monitor overview" in the Microsoft Azure documentation for more information about setting up and using Azure Monitor. See also Create an Azure Event Hubs pipeline.

To use the Azure Monitor Metrics Connector, start by creating a connection that allows it to access data from Azure Monitor. Then, add the Azure Monitor Metrics Connector to the start of your data pipeline and configure it to use the connection that you created.

Behavior of the Azure Monitor Metrics Connector

The Azure Monitor Metrics Connector has the following behavior:

• The connector collects metrics for the finest time-grain available in the Azure metric definition.
• The first time a scheduled job runs, the connector collects metrics for only one time interval. For all following scheduled jobs, the connector collects metrics from the last execution up to the current time, minus the number of minutes defined by the Delay parameter.

Create a connection using the Azure Monitor Metrics Connector

Create a connection so that the Azure Monitor Metrics Connector can access data from Azure Monitor and send the data into a DSP pipeline.

If you are editing a connection that's being used by an active pipeline, you must reactivate that pipeline after making your changes.

Prerequisites

Before you can use the Azure Monitor Metrics Connector, you must have an integration application that registers the connector in Microsoft Azure Active Directory (AD). If you don't have this integration application, ask your Azure AD administrator to create the application and create a client secret for it. For information about creating integration applications, search for "How to: Use the portal to create an Azure AD application and service principal that can access resources" in the Microsoft Azure documentation.

Make sure that the necessary permissions are assigned to the integration application. Depending on whether you are collecting metrics for a management group or a subscription, the application requires different permissions:

• If you are collecting metrics for a management group, make sure that your application has the following permissions:
  • Management Group Reader role for the management group.
  • Reader role for all subscriptions under that management group.
• If you are collecting metrics for a subscription, make sure that your application has the Reader role for that subscription.

Before creating a connection for the Azure Monitor Metrics Connector, make sure to have the following credentials from the integration application ready to enter in your connection information:

• Tenant ID, which is also known as a directory ID.
• Client ID, which is also known as an application ID.
• Client secret, which is also known as a key.

Steps

1. From the Data Management page, select the Connections tab.
2. Click Create New Connection.
3. Select Azure Monitor Metrics Connector and then click Next.
4. Complete the following fields:

   Field	Description
   Connection Name	A unique name for your connection.
   Azure Tenant ID	The tenant ID from Azure AD.
   Azure Client ID	The client ID from your integration application in Azure AD.
   Azure Client Secret	The client secret from your integration application in Azure AD.
   Subscription	The Azure subscription that you want to collect metrics for.
   Management Group	The Azure management group that you want to collect metrics for. If you also typed a subscription name in the Subscription field, the connector collects metrics for the subscription instead of the management group.
   Locations	(Optional) If you don't want to collect metrics for all Azure locations, type a list of the specific locations that you want to collect metrics for. You must type each location name in lowercase and without spaces. For example, "East US 2" is eastus2. Search for "Azure locations" in the Microsoft Azure documentation for a complete list of supported locations.
   Resource Groups	(Optional) If you don't want to collect metrics for all Azure resource groups, type a list of the specific resource groups that you want to collect metrics for.
   Metrics	(Optional) A list of resource types. Enter each resource type using the format <resource_provider>/<type>. Search for "Supported metrics with Azure Monitor" in the Microsoft Azure documentation for a list of supported metrics.
   Aggregations	(Optional) If you don't want to retrieve all the aggregations that are supported for your metrics, type a list of the aggregations that you want to retrieve. Valid Azure aggregations are Average, Count, Maximum, Minimum, and Total.
   Delay	(Optional) If you need to compensate for latency in the availability of Azure Monitor Metrics data points, type the number of minutes to delay the metrics data collection.
   Scheduled	This parameter is on by default, indicating that jobs run automatically. Toggle this parameter off to stop the scheduled job from automatically running. Jobs that are currently running are not affected.
   Schedule	The time-based job schedule that determines when the connector executes jobs for collecting data. Select a predefined value or write a custom CRON schedule. All CRON schedules are based on UTC.
   Workers	The number of workers you want to use to collect data.

   If your data fails to get into DSP, check the fields again to make sure you have the correct name, Azure tenant ID, Azure client ID, Azure client secret, subscription, and management group for your Azure Monitor Metrics connection. DSP doesn't run a check to see if you enter the valid credentials.

5. Click Save.

You can now use your connection in a data pipeline.