Configuring the Microsoft Azure monitor profile

This topic provides information about configuring the monitor profile for PATROL for Microsoft Azure to start monitoring.

To configure the KM, set the following preferences on the Add Monitoring Configuration dialog.

Monitoring Solution

Monitor Profile

Monitor Type

Microsoft AzureMicrosoft AzureMicrosoft Azure

Configuration details 

Click Add button to add the Azure account details.

FieldDescription
Azure Accounts Monitoring Configuration
Azure LabelEnter a display name that identifies this set of Azure monitoring configuration. A top-level container is created with this display name. This container holds all the monitored Azure resources. For example, BMC-Prod or BMC-Test. Input must match '^[A-Za-z0-9_-]+$' regular expression pattern.
Tenant ID

Enter the tenant ID of the Azure Active Directory. For more information, see Prerequisites for configuring Azure instance.

Application ID

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.

Application Key

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

Select Monitors 
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:

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

Storage Account

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:

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

App Services

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:

Microsoft SQL Server and Database

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:

Virtual Machine Scale Set

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:

Key Vaults

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

Corresponding monitor types:

Logic Apps

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

Corresponding monitor types:

Cosmos DB

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

Corresponding monitor types:

Kubernetes

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

Corresponding monitor types:

PostgreSQL

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

Corresponding monitor types:

Bus

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

Corresponding monitor types:

Azure Endpoint Details
Login Endpoint

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.

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

Management Endpoint

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.

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

Storage Endpoint Suffix

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.

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

Object Filtering Details
Subscription Filter

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

Subscription Filter TypeSelect whether to include or exclude the subscription IDs from monitoring.
Resource Group FilterEnter the resource group name (as seen on the Microsoft Azure portal) or a regular expression to filter the resource groups.
Resource Group Filter TypeSelect whether to include or exclude the resource groups from monitoring.
Virtual Machine FilterEnter the virtual machine name (as seen on the Microsoft Azure portal) or a regular expression to filter the virtual machines.   
Virtual Machine Filter TypeSelect whether to include or exclude the virtual machines from monitoring.
Storage Account FilterEnter the storage account name (as seen on the Microsoft Azure portal) or a regular expression to filter the storage accounts.    
Storage Account Filter TypeSelect whether to include or exclude the storage accounts from monitoring.
Enable Debug
Enable DebugSelect this check box to enable KM debug. The log file is created at <PATROL_HOME>\pmy\log directory on the PATROL Agent server.
Administration
JAVA Home

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.7.0_71/jre/bin/java path, specify /usr/java/jdk1.7.0_71/jre as the value of this field.

Enable Device Creation

Select/clear this check box to enable/disable device creation. By default, device creation is enabled (check box is selected).

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

Proxy Server Configuration
Use Proxy Configuration

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.
Server NameEnter the name or the IP address of the proxy server that is being used to route the HTTP request.
PortEnter the proxy server port number that is being used to connect specified proxy server.
User NameEnter the proxy server username that is being used to log in.
PasswordEnter the proxy server password that is being used to log in.

 

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

Comments