Install > Configure OMi MP for Azure

Configure OMi MP for Microsoft Azure

Deployment overview

OMi MP for Microsoft Azure is installed as an add-on content on OMi. A node must be installed with Operations Agent and configured as a managed node with capabilities to connect to the Azure account through the Internet. A managed node is required for each account that needs to be monitored.

The following section provides information about the tasks required to monitor Azure VMs in your environment. If you have deployed 2.10 version of Aspects, then go to Upgrading.

Add Nodes and Deploy Microsoft Azure Discovery Aspect

Task 1: Adding Nodes to the OMi Console

If the node already exists in RTSM, you can skip this step and proceed to Task 2.

Before you begin monitoring, you need to add the nodes to the OMi console.

  1. Open the Monitored Nodes pane from the Operations Console screen:

    Click Administration > Setup and Maintenance > Monitored Nodes.

  2. In the Node Views pane, select Predefined Node Filters > Monitored Nodes, click and then select Computer > <Select the relevant OS type>. The Create New Monitored Nodes dialog box appears.

  3. Specify the Primary DNS Name, IP Address, Operating System, and Processor Architecture of the node, and then click OK.

    The newly created node is saved as a Configuration Item (CI) instance in RTSM.

The node with Operations Agent needs to be activated on OMi Server and certificate must be granted.

Task 2: Deploying Discovery Aspects

OMi MP for Microsoft Azure monitors performance for both classic and Resource Manager (RM) resources. Since they differ in their topologies, OMi MP for Microsoft Azure provides separate Aspects to independently discover the respective topologies. In a heterogeneous environment, you must deploy both the Aspects.

If 2.10 version of Aspects are already deployed, then to upgrade to 2.20 follow the steps specified in the section Upgrade.

  1. Deploying Microsoft Azure Discovery Aspects

    To deploy the Microsoft Azure Discovery Aspects, follow the steps:

    1. Open the Management Templates & Aspects pane:

      Click Administration > Monitoring > Management Templates & Aspects.

    2. In the Configuration Folders pane:

      Click Configuration Folders > Cloud Management > Microsoft Azure > Aspects.

    3. Expand the Microsoft Azure Classic Discovery or Microsoft Azure RM Discovery or Microsoft Azure RM SQL Database Discovery Aspect, select version and then click Assign and Deploy Item.

    4. In the Configuration Item tab, select the Windows CI where the a proxy Operations Agent VM which monitors Azure is installed and click Next. You can select multiple items by holding down the CTRL or SHIFT key while selecting them.

    5. In the Required Parameter tab, you need to specify values for the following parameters:

      Aspects Mandatory Instance Parameter Dependent Parameters
      Microsoft Azure Classic Discovery

      SUB_ID

      SUB_NAME

      For each subscriptions, you must provide the services to be monitored.

      SUB_CERT

      Specify a value for the parameter taken from the .publishsettings file.

      OA_USERNAME

      Proxy Operations Agent node username.

      NA

      OA_PASSWORD

      Proxy Operations Agent node password.

      		 NA

      Microsoft Azure RM Discovery

      SUBSCRIPTION_ID

      Azure subscription ID for discovery and monitoring the RM resource.

      TENANT_ID

      Tenant ID for the particular subscription ID.

      CLIENT_ID

      Client ID of the application registered.

      CLIENT_KEY

      Client key of the application registered.
      1. Select the parameter and then click .The Edit Parameter window appears.

      2. Specify a value for the parameter.

        In Classic environment, value for the parameters is available in the .publishsettings file. In Resource Manager environment, value of username and password are the Service Principal credentials.

      3. Click OK

      4. Click Next.

    6. In the Parameter Summary tab, you can edit the default value of any parameter. If multiple subscriptions are required to be monitored, then add new instance of SUB_ID or SUBCRIPTION_ID to specify corresponding dependent parameters.

      1. Select the SUB_ID / SUBCRIPTION_ID parameter and then click .
      2. In Instance Values pane, click Create Instance Parameter.
      3. Specify value for the instance and click OK.
      4. In the Dependent Values pane, select the parameter and click . The Edit Parameter window opens.
      5. Click Value, specify the value, and then click OK.
      6. Click Next.
      Aspects Mandatory Instance Parameter Dependent Parameters
      Microsoft Azure Classic Discovery

      SUB_ID

      SUB_NAME

      For each subscriptions, you must provide the services to be monitored.

      SUB_CERT

      Specify a value for the parameter taken from the .publishsettings file.

      Microsoft Azure RM Discovery

      		 SUBSCRIPTION_ID

      TENANT_ID

      Tenant ID for the particular subscription ID.

      CLIENT_ID

      Client ID of the application registered.

      CLIENT_KEY

      Client key of the application registered.
    7. (Optional). In the Configure Options tab, if you do not want to enable the assignment immediately, clear the Enable Assignment(s) check box.
    8. Click Finish.

    You can modify the parameter value of any Aspect for tuning the monitoring after the deployment using the Assignments & Tuning pane (Administration > Monitoring > Assignments & Tuning) using MSAzure_Deployment View.

  2. Deploying Microsoft Azure Stack Discovery Aspect

    Deploy the Microsoft Azure Stack Discovery aspect to discover the Azure Stack Topology. The tenant, subscription, resource groups, VMs, and storage accounts are discovered by this aspect.

    Currently, only the Activity Log monitoring, Storage Service and Windows Event Log monitoring capabilities are supported. Therefore, deploy only the following aspects on the managed node based on the monitoring requirement:

    • Microsoft Azure Activity Logs (v2.200)

    • Microsoft Azure Storage Account Monitoring (v2.200)

    • Microsoft Azure Windows Event Log Monitoring (v2.200)

    For Storage Account and Windows Event Log monitoring, make sure to enable the diagnostics on the Virtual Machines on the Azure Stack Admin portal, respectively. This is a mandatory configuration, failing which the monitoring may not work as expected.

    Make sure that the managed nodes are different for Microsoft Azure and Microsoft Azure Stack monitoring.

    To deploy the Microsoft Azure Stack Discovery Aspect, follow the steps:

    1. Open the Management Templates & Aspects pane:

      Click Administration > Monitoring > Management Templates & Aspects.

    2. In the Configuration Folders pane:

      Click Configuration Folders > Cloud Management > Microsoft Azure > Aspects.

    3. Select the Microsoft Azure Stack Discovery aspect and then click Assign and Deploy Item.

    4. In the Configuration Item tab, select the Windows CI where the a proxy Operations Agent VM which monitors Azure stack is installed and click Next. You can select multiple items by holding down the CTRL or SHIFT key while selecting them.

    5. In the Required Parameter tab, you need to specify values for the following parameters:

      Mandatory Instance Parameter Description

      SUBSCRIPTION_ID

      		 The Azure Subscription ID for discovering and monitoring Azure RM Resources.

      TENANT_ID

      		 Tenant ID of the specified Subscription.

      CLIENT_ID

      		 The Client ID of the application registered with the Subscription
      CLIENT_KEY The Client Key of the application registered with the Subscription
      AZURESTACK_ARMENDPOINT Azure Stack Arm Endpoint
      AZURESTACK_ENVNAME Azure Stack Environment Name
      AZURESTACK_TOOLSPATH Path of the Azure Stack Tool Set downloaded from GitHub
      STORAGENAME The Storage Account Name to be monitored
      STORAGEKEY Storage Key of the Storage Account to be monitored
      1. Select the parameter and then click .The Edit Parameter window appears.

      2. Specify a value for the parameter.

      3. Click OK

      4. Click Next.

    6. In the Parameter Summary tab, you can edit the default value of any parameter. If multiple subscriptions are required to be monitored, then add new instance of SUB_ID or SUBCRIPTION_ID to specify corresponding dependent parameters.

      1. Select the SUBCRIPTION_ID parameter and then click .
      2. In Instance Values pane, click Create Instance Parameter.
      3. Specify value for the instance and click OK.
      4. In the Dependent Values pane, select the parameter and click . The Edit Parameter window opens.
      5. Click Value, specify the value, and then click OK.
      6. Click Next.
      Mandatory Instance Parameter Dependent Parameters
      SUBSCRIPTION_ID

      TENANT_ID

      CLIENT_ID

      CLIENT_KEY

      AZURESTACK_ARMENDPOINT

      AZURESTACK_ENVNAME

      AZURESTACK_TOOLSPATH
      STORAGENAME STORAGEKEY
    7. (Optional). In the Configure Options tab, if you do not want to enable the assignment immediately, clear the Enable Assignment(s) check box.
    8. Click Finish.

    After you deploy the Microsoft Azure Stack Discovery aspect, you can verify if the CIs are populated using the MS Azure RM Topology view in the View Explorer.

Task 3: Verifying Discovery

After you deploy the Discovery Aspects, you can verify if the CIs are populated in the View Explorer by following these steps:

  1. Click Workspaces > Operations Console > Event Perspective.

  2. In the View Explorer, select MS Azure Classic Topology or MS Azure RM Topology or MS Azure SQLDB view from the drop-down list.

    You can see the CIs associated with the views as shown in the following image.

    MS Azure Classic Topology

    MS Azure RM Topology

    MS Azure SQLDB

Task 4: Deploying Microsoft Azure Aspects

OMi MP for Microsoft Azure provide OOTB Aspects to monitor the performance of Microsoft Azure instances in your environment. Aspect must be deployed based on your Azure environment.

To monitor the performance of classic resource of Azure, deploy Microsoft Azure Classic Performance Monitoring Aspect. To monitor performance of RM resources, deploy Microsoft Azure RM Performance Monitoring Aspect. Microsoft Azure Performance Aspect is a base aspect for the prior aspects and must not be deployed independently for performance monitoring.

Microsoft Azure Service Health can be deployed on either classic or RM environment. Microsoft Azure Activity Logs and Microsoft Azure Storage Account Monitoring Aspect must be deployed only on RM environment. You can include additional metrics to meet your specific monitoring requirements.

To deploy the Microsoft Azure Aspects, follow these steps:

  1. Open the Management Templates & Aspects pane:

    Click Administration > Monitoring > Management Templates & Aspects.

  2. In the Configuration Folders pane:

    Click Configuration Folders > Cloud Management > Microsoft Azure > Aspects.

  3. Expand the Microsoft Azure Aspect, select latest version and then click Assign and Deploy Item.

  4. In the Configuration Item tab, select the Windows CI where the a proxy Operations Agent VM which monitors Azure and click Next.

  5. In the Required Parameter tab, you need to specify values for the following parameters:

    Aspects Mandatory Instance Parameter Dependent Parameters
    Microsoft Azure Activity Logs NA NA
    Microsoft Azure Classic Performance Monitoring

    SUB_ID

    SUB_NAME

    For each subscriptions, you must provide the services to be monitored.

    SUB_CERT

    Specify a value for the parameter taken from the .publishsettings file.

    Microsoft Azure RM Performance Monitoring

    		 NA

    NA
    Microsoft Azure Service Health NA NA
    Microsoft Azure Storage Account Monitoring
    Microsoft Azure Windows Event Log Monitoring
    1. Select the parameter and then click .The Edit Parameter window appears.

    2. Specify a value for the parameter.

      In Classic environment, value for the parameters is available in the .publishsettings file.

    3. Click OK

    4. Click Next.

  6. In the Parameter Summary tab, you can edit the default value of any parameter.

    • Microsoft Azure Storage Account Monitoring Aspect monitors the storage services such as blob, table, file, and queue. By default, all four storage service types are monitored. If you require to monitor specific service, then edit the Storage Service Type parameter to include the service as following:

      Service Syntax
      All services ALL (Default parameter value).
      Single service Specify the service in double quotes. For example, "Blob".
      Multiple services Specify the services in double quotes, separated by vertical bar symbol.
      For example, "Blob|File|Table".

    • Microsoft Azure Activity Logs Aspect monitors logs for failure in categories such as critical, error or warning. Errors that are encountered in all components of Azure environment are captured and sent to OMi. By default, critical issues are collected and forwarded to OMi. You can configure to collect other or all category of issues. Edit the SEVERITY parameter while deploying the Aspect. For including multiple category, separate using comma (,) (for example, Critical,Warning,Error).

    • In the Parameter Summary tab, make sure SUB_ID parameter is specified for Microsoft Azure Classic Performance Monitoring Aspect.

      1. Select the SUB_ID parameter and then click .
      2. In Instance Values pane, click Create Instance Parameter.
      3. Specify value for the instance and click OK.
      4. In the Dependent Values pane, select the parameter and click . The Edit Parameter window opens.
      5. Click Value, specify the value, and then click OK.
      6. Click Next.
  7. (Optional). In the Configure Options tab, if you do not want to enable the assignment immediately, clear the Enable Assignment(s) check box.
  8. Click Finish.

Related Topics

Administer

Upgrade

Send Help Center feedback