Microsoft Azure SQL Database

This template contains performance & statistics counters for monitoring Microsoft Azure IoT Hub.

Prerequisites:

  1. PowerShell modules: Az and Az.Accounts have to be installed prior to running this template on target machine.
  2. To connect with Azure account following parameters are required:
    • subcriptionID
    • ApplicationID
    • TenantID
    • Secret Key
      Note: Any Azure App (with its name & ID) having minimum role as 'Read-Only.'
  3. Application name for which metrics have to be calculated and its Resource Group Name.
  4. Time interval for which data has to be fetched (in hours).
  5. PowerShell 5.1 or greater

Script Arguments:

  • Login credentials to access Azure Portal. Azure details have to be passed in script arguments as per prerequisites (comma separated)
    Example:
    • <SubscriptionID> [string in GUID format]
    • <TenantID> [string in GUID format]
    • <ApplicationID> [string in GUID format]
    • <secretKey> [string]
    • <DatabaseName> [string]
    • <ResourceGroupName> [string]
    • <TimeInterval> [decimal] number of hours to pull for data
    • <NumRetries> [int] (Optional) [Default: 3]
    • <WaitTime> [decimal] number of seconds before retry (Optional) [Default: 0.5]

Notes:

  1. To install Azure Az PowerShell module, refer to: Install the Azure Az PowerShell module
  2. Administrator rights on the machine where template would be running. Script should run with administration privilege.
  3. The ApplicationID with which you are making a connection to Azure portal (as mentioned in Credential/Prerequisites) must be registered in Azure Active Directory as contributor or reader role for the monitored application.

Reference link: Tips for adding an Azure AD app for cloud monitoring in the Orion Platform

Portions of this document were originally created by and are excerpted from the following sources:

Last Updated: 2019-JUL-25

Deprecation Notice

Previous Template: Microsoft Azure SQL Database - Application Monitor Templates - Server & Application Monitor has been deprecated