Configure Azure monitoring

While Dynatrace provides broad support for Azure Compute Services, including an intuitive, native integration using the Dynatrace VM-Extension or SiteExtension for App Services, the Azure overview page complements application and infrastructure data collected by OneAgent with Azure monitoring metrics and metadata from Azure Resource Manager (ARM).

To take advantage of this level of visibility into your Azure environment, you must connect Azure to your Dynatrace environment by doing the following:

Before you begin

The following are required to connect to your Azure environment:

  • Dynatrace Server version 1.144 or later.

  • Sufficient permissions to register an application with your Azure AD tenant, and assign the application to a role in your Azure subscription. Make sure you have the right permissions to perform these steps.

  • An Azure Service Principal to access Azure APIs.

  • An Environment ActiveGate version 1.143 or later (Versions 1.143 and later include several fixes and don't require manual enablement in your ActiveGate configuration. Note that Azure monitoring is currently not available for other types of ActiveGates.)

  • For ActiveGate versions 1.147 and later, Azure monitoring is enabled by default. For ActiveGate versions 1.146 and earlier, you must enable this feature within your ActiveGate configuration. To do this, add the following to the [collector] section the config.properties file:

    [collector]
    AzureAgentEnabled = true
    

    For ActiveGate versions 1.147 and later, this change is not needed because the entry is in config.properties by default, However, the name of the property and the section in which it is located have changed. The entry is shown below:

    [azure_monitoring]
    azure_monitoring_enabled = true
    

Create an Azure Service Principal

To create a Service Principal, you must register your application in the Azure Active Directory. To do this:

  1. Go to the Azure Management Portal and click Azure Active Directory.

  2. Click App registrations in the navigation pane of the selected Active Directory.

  3. Click New application registration at the top of the App registrations blade, then type the name of your application. Make sure that Web app / API is selected as the application type.

  4. Type the Sign-on URL based on your application name. This does not have to be an actual sign-on page (for example, http://mydynatrace.com).

    Configure Azure Monitor - create app register

  5. Click Create. When the application is created, copy the Application ID, and place it where you can easily retrieve it. This becomes your Client ID once you've set up your connection, and is required to configure Dynatrace to connect to your subscription.

    Configure Azure Monitor - create app ID

  6. Click Settings to display the Settings pane, then click Keys to display the Keys blade.

  7. Type a Key description, then select a key duration in the Expires list.

  8. Click Save at the top of the Keys blade. This saves the key and displays the key value in the Value field. Highlight the value and copy it, and place it where you can easily retrieve it (along with your Client ID).

    Configure Azure Monitor - create client ID

Important: This is your only chance to copy this value. You can't retrieve the key value after you leave the Key blade.

Find your Azure Tenant ID

With the Active Directory blade open, you can now get your Tenant ID. Click Properties in the navigation pane of the Azure Active Directory blade and copy the Directory ID. This is your Azure Tenant ID, which is needed to configure Dynatrace to connect to your subscription. Keep this ID with your Client ID and Key value.

Configure azure - Tenant ID

Find your Azure subscription and grant access

You need the subscription name and Client ID to complete the service endpoint and connect Dynatrace to your Azure subscription.

To get the subscription name and Client ID

  1. Click All services > General > Subscriptions.

  2. In the Subscriptions blade, select the subscription you're using.

  3. Copy the subscription ID at the top of the Subscription blade. Keep this ID with your Client ID, Key value, and Azure Tenant ID. Then click Access control (IAM) in the subscription navigation pane.

    Configure Azure Monitor - create subscription

  4. Click Add, then select Reader as the role.

  5. In the Select field, paste the Client ID (Application ID) you saved to find the application you created in Create an Azure Service Principal.

  6. Select the application and click Save to grant the Service Principal access to your subscription.

Configure Dynatrace to connect to your Azure subscription

To properly map the Azure monitoring metrics and Azure Resource Manager metadata to Dynatrace, you must to connect your Azure account to Dynatrace for monitoring. This includes providing either the Client ID or Tenant ID and the Secret Key from your Azure Management Portal for access.

  1. In the desired Dynatrace environment, click Settings > Cloud and virtualization > Azure.

  2. Type a descriptive name for the connection.

  3. Enter the Client ID you obtained when creating the Create an Azure Service Principal.

  4. Enter the Tenant ID, which is the Directory ID in the properties for the Active Directory in the Azure Management Portal.

  5. Enter the Secret Key, which is the key value obtained when creating the Create an Azure Service Principal.

    Configure Azure Monitor - connect to Dynatrace

  6. Click Connect to add the connection information to the list of Azure connections. You can edit connection information at any time.

View Azure monitoring metrics and metadata

Once you have set up Azure and configured Dynatrace to connect to your Azure subscription, you can get enhanced visibility into your Azure environment, particularly fully managed platform services (PaaS) where you can't deploy Dynatrace OneAgent directly on hosts. You can see the additional Azure monitoring metrics and metadata from the Azure Resource Manager (ARM).

The following services are included:

  • Virtual Machines

  • Virtual Machine Scale-Sets

  • App Services (Web Apps, API Apps and Mobile Apps)

  • Azure SQL

  • Redis Cache

  • API Management Service

  • Load-Balancer

  • Storage

  • Service Bus

    Azure overview page

Azure monitoring configuration limitations

  • Azure integration is not supported on multi-tenant, multi environment ActiveGates.
  • For Dynatrace 1.147 and later, a single configuration can have more then one subscription attached. Any attached subscriptions will be monitored. For Dynatrace Server 1.146 and earlier, you must add multiple configurations to monitor multiple subscriptions.
  • Azure integration is only available for the public cloud, not the sovereign clouds (such as Azure government) or Azure stack.
  • VMs detected by ARM currently aren't automatically associated with VMs monitored by Dynatrace OneAgent.
  • No metrics are currently available for Service Bus and Azure SQL.