Configuration parameters for the Azure Compute agent

The configuration parameters for the Azure Compute agent are displayed in tables which group them according to sections.

Table 1 - Credentials that are required for access to the Azure Subscription that contains the Azure Compute resources to monitor.
Table 2 - Create agent subnodes to define groupings of virtual machines. Each subnode name must be unique within your environment. It is suggested that you have no more than 50 virtual machines per subnode.

Table 1. Azure Subscription Credentials
Parameter name	Description	Silent configuration file parameter name
Subscription ID	The ID assigned by Azure for the Subscription that is monitored.	KAK_SUBSCRIPTION_ID
Tenant ID	The tenant ID that is assigned by Azure. Used to log in to the Azure service API.	KAK_TENANT_ID
Client ID	The client ID that is assigned by Azure to identify this agent as an external application that monitors the Azure compute services.	KAK_CLIENT_ID
Secret Key/Password	The secret access key or password that is created by Azure for the client application. Important: If your Secret Key/Password contains an equal sign (=), you must reenter it each time that you reconfigure the agent.	KAK_SECRET_PASSWORD

Table 2. Azure Compute Virtual Machine Subnode
Parameter name	Description	Silent configuration file parameter name
Subnode Name	Name of the Azure Compute Subnode for collection of data. Example, `azc1`. Subnode name must be unique in your environment. This alias is part of the managed system name (MSN) and it is used to visually identify the monitored environment in the Cloud APM console. Note: This alias can be anything that you choose to represent the Azure Compute subnode instance with the following restrictions. Letters from the Latin alphabet (a-z, A-Z), Arabic numerals (0-9), the hyphen-minus character (-), and the underscore character (_) can be used to create agent subnode instance names. The maximum length of an Azure Compute subnode name is 25 characters.	Each of the following parameters must use a period (.) followed by an agent Subnode Name as a suffix. The Subnode Name must be the same for each subnode parameter. New agent subnode instances must use a unique Subnode Name for its set of parameters. For example, one agent subnode instance can use `.azc1` and another agent subnode instance can use `.azc2` in place of `.subnode_name` in the parameter names that follow.
Filter Type	The type of filter to be applied.	KAK_FILTER_TYPE.subnode_name Valid values, ALL All TAG_NAME_VALUE Tag Name-Value Pair RESOURCE_GROUP Resource Group
Filter Value	The filter value corresponding to the selected Filter Type. This value can be a Resource Group or Tag Name-Value Pair. Leave it empty for Filter Type All. For command line configuration, a backslash might appear in the example displayed. Do not enter a backslash in the value you provide. Examples of filter type and filter value pairs: Azure Compute Subnode to monitor all virtual machines. Leave the filter value empty. Filter value is not needed and it is ignored for filter type All. Filter Type: All Filter Value: Azure Compute Subnode to monitor all virtual machines with a tag name of `DTAP` and a tag value that matches the string `prod`. Filter Type: Tag Name-Value Pair Filter Value: `DTAP:prod` Azure Compute Subnode to monitor all virtual machines with a resource group property that matches the string `linux-group1`. Filter Type: Resource Group Filter Value: `linux-group1`	KAK_FILTER_VALUE.subnode_name