Upgrade

Upgrade

You must upgrade Discovery and other aspects to latest version.

Cleaning up the Node

  1. Open the Assignments & Tuning pane:

    Click Administration > Monitoring > Assignments & Tuning.

  2. In the Browse Views tab, select the MSAzure_Deployment View.
  3. Removing the Assignments:

    In the Assigned Item pane, select the Azure Aspects and click Delete Assignment.

  4. Deploy the new versions of Azure aspects.

Upgrading Discovery Aspect to latest version

  1. Open the Assignments & Tuning pane:

    Administration > Monitoring > Assignments & Tuning

  2. In the Browse Views pane, select the MS Azure RM Topology view and select each CI where version update is required.
  3. Click Show Assignments That Require an Update.

    All the Management Templates and Aspects that requires an update are listed.

  4. Select each of the Management Templates and Aspects and click Update Assigned Item.

    The Update Assigned Item dialog box appears.

  5. In the Update Options tab, follow these steps:

    1. Select the 2.200 from the Update to Version drop down list.
    2. Select the Use default parameter values from version selected above option and click Next.

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

    1. Select the SUBSCRIPTION_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 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.

  7. 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 SUBSCRIPTION_ID and specify corresponding dependent parameters.

  8. Click Finish to save the changes and close the wizard. The assigned item is updated to the specified Aspect version.

Upgrading Other Aspect to latest version

  1. Open the Assignments & Tuning pane:

    Administration > Monitoring > Assignments & Tuning

  2. In the Browse Views pane, select the MS Azure RM Topology view and select each CI where version update is required.
  3. Click Show Assignments That Require an Update.

    All the Management Templates and Aspects that requires an update are listed.

  4. Select each of the Management Templates and Aspects and click Update Assigned Item.

    The Update Assigned Item dialog box appears.

  5. In the Update Options tab, follow these steps:

    1. Select the 2.200 from the Update to Version drop down list.
    2. Select the Use default parameter values from version selected above option and click Next.

  6. In the Required Parameter tab, click Next.

  7. 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).

  8. Click Finish to save the changes and close the wizard. The assigned item is updated to the specified Aspect version.

Related Topics

Configure OMi MP for Microsoft Azure