Configuring the Microsoft Azure monitor profile

Enter the application ID of the Web app/API application that you have created in the Microsoft Azure portal. For more information, see Prerequisites for configuring Azure instance.

Note: For all the resource groups that you want to monitor, ensure that the Application ID has access to them. In your environment, if multiple Application IDs have access to the resource groups that you want to monitor, add multiple accounts to the policy with different Application IDs.

Enter the client secret of the application that you created in the Azure portal. For more information, see Prerequisites for configuring Azure instance. 

Select this check box to monitor the performance and availability of the Data Analytics service.

Corresponding monitor types:

Azure Data Lake Analytics Container (PAF_DATA_LAKE_ANALYTICS_CNTR)

Azure Data Lake Analytics (PAF_DATA_LAKE_ANALYTICS)

Select this option to enable APP Services monitoring. The KM monitors and analyses the performance and availability of app service, app service environment, and app service plan.

App Services monitoring is enabled by default.

Corresponding monitor types:

• Azure App Services (PAF_APP_SVC_CNTR)
• Azure App Service Plan (PAF_APP_SVC_PLAN)
• Azure App Service Environment (PAF_APP_SVC_ENV)

Virtual Machine

Select this option to enable Virtual Machine monitoring. The KM monitors memory, disk, process, remote calls, and network usage of the virtual machines. Virtual Machine monitoring is enabled by default.

Note: Diagnostic must be enabled for Virtual Machines.

Microsoft Azure enables diagnostic Agent for each Resource Manager virtual machine and disables the basic metrics by default.

Corresponding monitor types:

• Azure Virtual Machines (PAF_VM_CNTR)
• Azure Virtual Machine (PAF_VIRTUAL_MACHINE)

Note: The Azure Virtual Machine monitor type represents Resource Manager virtual machines.

Select this option to enable Virtual Machine Scale Set monitoring. The KM monitors the network, disk, and CPU usage metrics of the Virtual Machine Scale Set Host and Instance.

Virtual Machine Scale Set monitoring is enabled by default.

Corresponding monitor types:

• Azure VM Scale Set (PAF_VM_SCALE_SET)
• Azure VM Scale Sets (PAF_VM_SCALE_SET_CNTR)
• Azure VM Scale Set Instances (PAF_VM_SCALE_SET_INSTANCE)
• Azure VM Scale Set Host Metrics (PAF_VM_SCALE_SET_HOST_METRIC)
• Azure VM Scale Set Instance Host Metrics (PAF_VM_SCALE_SET_INSTANCE_HOST_METRIC)

Select this check box to monitor the performance and availability of the Kubernetes service.

Corresponding monitor types:

• Azure Kubernetes Container (PAF_KUBERNETES_CNTR)
• Azure Kubernetes (PAF_KUBERNETES)

Select this check box to monitor the performance and availability of cosmos database.

Corresponding monitor types:

• PAF_COSMOS_DB_CNTR
• PAF_COSMOS_DB

Select this option to enable Microsoft SQL Server Database monitoring. The KM monitors the availability of the SQL Server and provides information about CPU usage, database size percentage, number of deadlocks, and database throughput unit limit of the SQL database.

Microsoft SQL Server and Database monitoring is enabled by default.

Corresponding monitor types:

• Azure SQL Server (PAF_SQL_SERVER)
• Azure SQL Database (PAF_SQL_DATABASE)

Select this check box to monitor the performance and availability of the PostgreSQL service.

Corresponding monitor types:

• Azure PostgreSQL (PAF_POSTGRESQL_CNTR)
• Azure PostgreSQL (PAF_POSTGRESQL)
• Azure PostgreSQL Replicas (PAF_POSTGRESQL_REPLICAS_CNTR)
• Azure PostgreSQL Replica (PAF_POSTGRESQL_REPLICA)

Select this check box to monitor the performance and availability of the Bus service including the bus queues and topics.

Corresponding monitor types:

• Azure Bus (PAF_BUS_CNTR)
• Azure Bus (PAF_BUS)
• Azure Bus Queues (PAF_BUS_QUEUE_CNTR)
• Azure Bus Queue (PAF_BUS_QUEUE)
• Azure Bus Topic (PAF_BUS_TOPIC_CNTR)
• Azure Bus Topic (PAF_BUS_TOPIC)

Select this check box to monitor the performance and availability of logic apps.

Corresponding monitor types:

• PAF_LOGIC_APPS_CNTR
• PAF_LOGIC_APPS

Select this check box to monitor the performance and availability of the Application Gateway service including WAF and Standard.

Corresponding monitor types:

• Azure Application Gateways (PAF_APP_GW_CNTR)
• Azure V2 Application Gateway (PAF_APP_GW_V2)
• Azure WAF Application Gateway (PAF_APP_GW_WAF)
• Azure Standard Application Gateway (PAF_APP_GW_STD)

Select this check box to monitor the performance and availability of the Connections service.

Corresponding monitor types:

• Azure Connections (PAF_CONNECTIONS_CNTR)
• Azure Connection (PAF_CONNECTION)

Select this check box to monitor the performance and availability of the DNS Zones service.

Corresponding monitor types:

• Azure DNS zones (PAF_DNS_ZONES_CNTR)
• Azure DNS zone (PAF_DNS_ZONE)

Select this check box to monitor the performance and availability of the Firewall service.

Corresponding monitor types:

• Azure Firewalls (PAF_AZURE_FIREWALLS_CNTR)
• Azure Firewall (PAF_AZURE_FIREWALL)

Select this check box to monitor the performance and availability of the Load Balancer service.

Corresponding monitor types:

• Azure Load balancers (PAF_LOADBALANCERS_CNTR)
• Azure Basic Load balancer (PAF_LOADBALANCER_BASIC)
• Azure Standard Load balancer (PAF_LOADBALANCER_STANDARD)

Select this check box to monitor the performance and availability of the Network Interfaces service.

Corresponding monitor types:

• Azure Network Interfaces (PAF_NETWORK_INTERFACES_CNTR)
• Azure Network Interface (PAF_NETWORK_INTERFACE_SVC)

Select this check box to monitor the performance and availability of the Private DNS Zones service.

Corresponding monitor types:

• Azure Private DNS zones (PAF_PRV_DNS_ZONES_CNTR)
• Azure Private DNS zone (PAF_PRV_DNS_ZONE)
• Azure Virtual Network Links (PAF_VIRTUAL_NW_LINK_CNTR)
• Azure Virtual Network Link (PAF_VIRTUAL_NW_LINK)

Select this check box to monitor the performance and availability of the Public IP Addresses service.

Corresponding monitor types:

• Azure Public IP Addresses (PAF_PUBLIC_IP_ADDRESSES_CNTR)
• Azure Standard Public IP Address (PAF_STANDARD_PUBLIC_IP_ADDRESS)
• Azure Basic Public IP Address (PAF_BASIC_PUBLIC_IP_ADDRESS)

Select this check box to monitor the performance and availability of the Virtual Network Gateway service including express route and VPN.

Corresponding monitor types:

• Azure Virtual Network Gateways (PAF_VIRTUAL_NETWORK_GW_CNTR)
• Azure Virtual Network Gateway (PAF_VIRTUAL_NETWORK_GW)
• Azure Virtual Network Gateway Express Route (PAF_VIRTUAL_NETWORK_GW_EXPRESS_ROUTE)

Select this check box to monitor the performance and availability of the Virtual Networks service.

Corresponding monitor types:

• Azure Virtual Networks (PAF_VIRTUAL_NETWORKS_CNTR)
• Azure Virtual Network (PAF_VIRTUAL_NETWORK)

Select this option to enable Storage Account monitoring. The KM provides information about billable requests, total egress, and ingress used by the Azure storage blob, storage queue, and the storage table. 

Storage Account monitoring is enabled by default.

Corresponding monitor types:

• Azure Storage Account (PAF_STORAGE_ACCOUNT)
• Azure Storage Blob (PAF_STORAGE_BLOB)
• Azure Storage Queue (PAF_STORAGE_QUEUE)
• Azure Storage Table (PAF_STORAGE_TABLE)

Note: The Azure Storage Account monitor type represents Resource Manager storage accounts.

Select this check box to monitor the performance and availability of key vaults.

Corresponding monitor types:

• PAF_KEY_VAULTS_CNTR
• PAF_KEY_VAULTS

Enter the Login Endpoint for the cloud from which you want to monitor the resources. For example, login.microsoftonline.de for German Endpoint. For more information about German Endpoint refer to the Microsoft Azure Germany developer guide. Similarly, for information about Endpoint details of other Azure Clouds, refer Microsoft documentation.

For example, for Azure Government cloud subscriptions, login endpoint can be login.microsoftonline.us.

The KM connects to the default global endpoint if this field is left blank. 

Enter the Management Endpoint for the cloud from which you want to monitor resources. For example, management.microsoftazure.de for German Endpoint. For more information about German Endpoint, refer to the Microsoft Azure Germany developer guide. Similarly, for information about Endpoint details of other Azure Clouds, refer Microsoft documentation.

For example, for Azure Government cloud subscriptions, management endpoint can be management.usgovcloudapi.net.

The KM connects to the default global endpoint if this field is left blank.

Enter the Storage Endpoint Suffix for the cloud from which you want to monitor resources. For example, core.cloudapi.de for German StorageEndpointSuffix. T For more information about German Endpoint, refer to the Microsoft Azure Germany developer guide. Similarly, for information about Endpoint details of other Azure Clouds, refer Microsoft documentation.

For example, for Azure Government cloud subscriptions, storage endpoint suffix can be core.usgovcloudapi.net.

The KM connects to the default global endpoint if this field is left blank.

Enter the subscription ID (as seen on the Microsoft Azure portal) or a regular expression to filter subscription IDs.

By default, the KM uses Java Runtime Environment (JRE) that is installed in the PATROL_HOME directory. To use your own JRE that is installed in a different location, specify the path for the Java home directory.

For example, if your Java executable exists in the /usr/java/jdk1.8.0/jre/bin/java path, specify /usr/java/jdk1.8.0/jre as the value of this field.

By default, when device mapping is enabled, all monitored Azure instances are displayed as a device on the Monitoring > Devices page. When device mapping is disabled, monitored information is shown under PATROL Agent. It saves you extra clicks to navigate the PATROL Agent hierarchy while viewing monitoring results.

Clear this check box to disable device mapping.

Note: If you modify this setting after KM discovery, restart the PATROL Agent to apply the changes.

Select the check box to enable the proxy configuration.

Notes:

• If the environment permits, the KM can connect to the proxy server using the Server Name and Port fields only. User Name and Password fields are optional.
• If you select this option and do not provide the Server Name, Port, and user credentials, the KM uses the system proxy configured on the server.
• If you modify any proxy configuration setting, restart the PATROL Agent to apply the changes.