SevOne logo
You must be logged into the NMS to search.

Table of Contents (Start)

Azure Quick Start Guide (Public Preview)

For SevOne NMS 6.8 release, the Azure Plugin is for Public Preview only.


SevOne Documentation

All documentation is available from the IBM SevOne Support customer portal.

© Copyright International Business Machines Corporation 2024.

All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of IBM and its respective licensors. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of IBM.

IN NO EVENT SHALL IBM, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF IBM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IBM DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.

IBM, the IBM logo, and SevOne are trademarks or registered trademarks of International Business Machines Corporation, in the United States and/or other countries. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on ibm.com/trademark.

About

SevOne's Azure plugin allows you to collect metrics for Virtual Machines and Virtual Machine Scale Sets along with device metadata for each Resource type from an Azure environment. The Azure plugin allows you to monitor multiple different geographies for any given subscription. Multiple integrations can be created on a per subscription basis.

Device Creation

SevOne NMS Azure plugin regularly calls Azure APIs to retrieve information about Virtual Machines and Virtual Machine Scale Sets and then automatically create devices for each Azure resource.

Required Resources in Azure

To monitor an Azure account, the following are necessary.

  • Tenant ID

  • Subscription ID

  • App Registration

App Registration and Client Secret

For the Azure plugin to run, it will need to authenticate with Azure by being registered as an application and using a client secret.

  1. To register an application, please navigate to the Azure Portal, https://portal.azure.com.

  2. Navigate to the App registrations.
    images/download/attachments/174603574/azureAppRegistrations-version-1-modificationdate-1707108015305-api-v2.png

  3. Click New registration.

    You may need to request your administrator for access to create a new registration.

    images/download/attachments/174603574/azureNewRegistration-version-1-modificationdate-1707108015315-api-v2.png

  4. On Register an application page,

    1. Name - enter a name. For example, SevOne NPM.

    2. Under Supported account types, select check box Accounts in this organizational directory only.

    3. Click Register.
      images/download/attachments/174603574/azureNameAndRegister-version-1-modificationdate-1707108015309-api-v2.png

  5. Once registered, the Azure portal will navigate to the recently registered App.

    IMPORTANT

    Remember to copy and save the values in fields Application (client) ID and Directory (tenant) ID in the right panel. You will need these to start the Azure plugin in SevOne NMS.

    images/download/attachments/174603574/azureAddCertOrSecret-1-version-1-modificationdate-1707108015294-api-v2.png

  6. Click Add a certificate or secret or from the left navigation bar, choose Certificates & secrets.
    images/download/attachments/174603574/azureAddCertOrSecret-2-version-1-modificationdate-1707108015291-api-v2.png

  7. Click Client secrets tab in the right panel, and then click New client secret.

    1. Description - add a description. For example, Azure NMS Collector secret.

    2. Expires - select an expiry date for the secret. The recommended time is 6 months by Azure. For example, 4/24/2024.

      This procedure for creating a new client secret will need to be repeated when this secret expires after the selected expiry date.


    3. Click Add.
      images/download/attachments/174603574/azureNewClientExpirationDate-version-1-modificationdate-1707108015311-api-v2.png

  8. After the secret is added, you should see the new client secret within the Client secrets tab. The Value field is the client secret that the collector needs to authenticate.

    IMPORTANT

    Remember to copy and save the client secret in field Value. You will need this in SevOne NMS to be able to start the Azure plugin.


    images/download/attachments/174603574/azureClientSecret-version-1-modificationdate-1707108015155-api-v2.png

Assign a Role to the App

For the Azure plugin to be able to retrieve the correct information from Azure, it will need to be assigned a role containing all of the permissions that it needs.

  1. To assign a role to the application you created in the last section, please navigate to the Azure Portal, https://portal.azure.com.

  2. Navigate to Subscriptions.

    images/download/attachments/174603574/azurePortalSubs-version-1-modificationdate-1707108015288-api-v2.png



  3. Click the name of the subscription that you want to monitor.

    images/download/attachments/174603574/azureSubscriptions-version-1-modificationdate-1707108015285-api-v2.png



  4. Click Access control (IAM) on the left navigation bar.

    IMPORTANT

    Remember to copy and save the Subscription ID value in the right pane. You will need this value in order to start the Azure plugin in SevOne NMS.

    images/download/attachments/174603574/azureSubscriptionIDAndAccessControl-version-1-modificationdate-1707108015282-api-v2.png


  5. Click Add, then click Add role assignment from the dropdown menu.

    images/download/attachments/174603574/azureAddRoleAssignment-version-1-modificationdate-1707108015278-api-v2.png



  6. In the Add role assignment page > tab Role,

    1. Type Monitoring Reader into the search bar.

    2. Click the Monitoring Reader entry in the table.

    3. Click Next.

      images/download/attachments/174603574/azureAddRoleAssignmentRole-version-1-modificationdate-1707108015276-api-v2.png



  7. In the Add role assignment page > tab Members,

    1. Click Select members.

    2. In the Select members panel,

      • Type the name of the app you registered into the Select search bar.

      • Click the correct entry for the app you registered in the results.

      • Click Select.

    3. Click Next.

      images/download/attachments/174603574/azureAddRoleAssignmentMembers-version-1-modificationdate-1707108015273-api-v2.png



  8. In the Add role assignment page > tab Review + assign,

    1. Review the information on the page to make sure everything is correct.

    2. Click Review + assign.

      images/download/attachments/174603574/azureAddRoleAssignmentReviewAndAssign-version-1-modificationdate-1707108015190-api-v2.png


Repeat steps 3 – 8 above for each subscription that you want to monitor, taking note of each Subscription ID. It is not necessary to create a new app registration for each subscription.

Enable Azure Plugin

Execute the following steps to monitor an Azure account. This will automatically create devices and collect metrics for various Azure resources within selected regions for that account.

  1. To access the Device Manager from the navigation bar, click the Devices menu and select Device Manager.

  2. Either add a device with the Azure plugin or edit an existing device to enable the Azure plugin.

    • Click Add Device to display the New Device page.

    • Click the wrench icon under the Actions column to display the Edit Device page.

  3. Click the plugin drop-down. By default, it is set to SNMP. Select Azure.

    images/download/attachments/174603574/azurePluginDeviceManager-version-1-modificationdate-1707108015318-api-v2.png

  4. Select the Enable Azure Integration check box.

  5. In the Tenant ID field, enter the ID of the Azure tenant you want to monitor. This is the same as the Directory (tenant) ID value that was noted above.

  6. In the Subscription ID field, enter the ID of the Azure subscription you want to monitor. This is the same as the Subscription ID that was noted above.

  7. In the Application Client ID field, enter the ID of Azure registered application for SevOne. This is the same as the Application (client) ID value that was noted above.

  8. In the Client Secret Value field, enter the value of the secret created for the Azure registered application. This is the same as the value noted in Value above.

  9. Click Save As New to save the current changes as a New Device, or click Save to confirm the changes in the Edit Device page.

  10. When the desired changes have been saved, click the Cancel button to return to the Device Manager page.

Create TopN View in SevOne NMS to view Azure resources

SevOne NMS contains a package with Azure-specific TopN views. To import, execute the following command.

$ SevOne-import --file /opt/SevOne-aws-collector/topn.spk

The import will fail unless the Azure collector has run successfully at least once.

OOTB Reports

Once the NMS Azure Plugin integration is setup and we see Devices and Objects populate in the Device manager, the following out-of-the-box (OOTB) reports are available in Data insights for you to get insights on your resources.

  • Azure Virtual Machines - report showing Azure Virtual Machine metrics.

  • Azure Virtual Machine Scale Sets - report showing Azure Virtual Machine Scale Set metrics.