Azure monitored resources

Edit online

After validating your targets, Turbonomic updates the supply chain with the entities that it discovered. The following table describes the entity mapping between the target and Turbonomic.

Azure Turbonomic
Virtual Machine (VM) Virtual machine (VM)
Disk (Managed) Volume
Virtual Machine Scale Set (VMSS) Virtual machine spec
AKS cluster Container platform cluster
App Service - Plan Virtual machine spec
App Service - Web App App component spec
SQL Database (vCore or DTU) Database
SQL Managed Instance Database server
Azure Database for MySQL - Flexible Server Database server
Synapse Analytics (Dedicated SQL Pool) Database
Cosmos DB - Account Database server
Cosmos DB - Database Database
Cosmos DB - Container Document collection
Region Region

Points to consider:

  • Turbonomic supports discovery and management of entities in certain Azure regions, including Azure Government regions. For details, see Supported Azure Regions and Support for Azure Government.

  • When you first configure an Azure target, under some circumstances the target might show a No Quotas Available status. This means that Turbonomic cannot discover the available templates. This can happen when you initially set up the Azure account and you have not enabled any providers. If this occurs, you can install a single VM in your cloud subscription to make quotas available.

  • An Azure subscription can use locked storage or locked resource groups. For such subscriptions, Turbonomic discovers incomplete data. Locked resources affect Turbonomic discovery in either of these scenarios:

    • Locked resource group

      Turbonomic discovers all the entities in the resource group, but does not discover the resource group itself. For example, in the Top Accounts chart, the Resource Groups field will show no resource groups for a subscription that has a locked resource group.

    • Locked storage

      Turbonomic discovers all the entities in the resource group except the locked storage. It also discovers the resource group.

Monitored resources for virtual machines

Note:

For a list of supported instance types for virtual machines, see Supported Azure instance types.

Turbonomic monitors the following resources:

  • Virtual memory (vMem)

    Virtual memory (vMem) is the measurement of memory that is in use.

    It is highly recommended that you enable metrics collection in your environment. When metrics are available, Turbonomic can generate scale actions to optimize VM resource usage.

    For details, see Azure VM memory metrics collection.

  • Virtual CPU (vCPU)

    Virtual CPU is the measurement of CPU that is in use.

  • Storage amount

    Storage amount is the measurement of storage capacity that is in use.

  • Storage access (IOPS)

    Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

  • I/O throughput

    I/O throughput is the measurement of an entity's throughput to the underlying storage.

  • Net throughput

    Net throughput is the per-second sum of bytes that a virtual machine sent (egress) and received (ingress) through its connected network interfaces. This metric is a measurement of the volume of network traffic that a virtual machine handles.

Monitored resources for volumes

Turbonomic discovers and optimizes Azure managed volumes.

Note:

Azure unmanaged volumes that are attached to VMs are discovered but not optimized. Unmanaged volumes that are not attached to any VM are not discovered or optimized. For information about Azure's level of support for unmanaged volumes, see the Azure documentation.

For a list of supported managed volume types, see Supported Azure managed volume types.

Turbonomic monitors the following resources:

  • Storage amount

    Storage Amount is the storage capacity (disk size) of a volume.

    Turbonomic discovers Storage Amount, but does not monitor utilization.

    For a Kubeturbo (container) deployment that includes volumes, Kubeturbo monitors Storage Amount utilization for the volumes. You can view utilization information in the Capacity and Usage chart.

  • Storage access (IOPS)

    Storage access, also known as IOPS, is the measurement of IOPS capacity that is in use.

  • I/O throughput

    I/O throughput is the measurement of I/O throughput capacity that is in use.

Note:

Turbonomic also monitors the attachment state of volumes and generates delete actions for unattached volumes.

Monitored resources for virtual machine specs

  • For App Service Plans:

    Turbonomic monitors the following resources:

    • Virtual memory (vMem)

      Virtual memory (vMem) is the measurement of memory that is in use.

    • Virtual CPU (vCPU)

      Virtual CPU is the measurement of CPU that is in use.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Number of replicas

      Number of replicas is the total number of VM instances underlying an App Service plan.

  • For Virtual Machine Scale Sets:

    Turbonomic monitors the following resources for individual VMs in a Virtual Machine Scale Set. It does not monitor resources at the Virtual Machine Scale Set level.

    • Virtual memory (vMem)

      Virtual memory (vMem) is the measurement of memory that is in use.

      It is highly recommended that you enable metrics collection in your environment. When metrics are available, Turbonomic can generate scale actions to optimize VM resource usage.

      For details, see Azure Memory Metrics Collection.

    • Virtual CPU (vCPU)

      Virtual CPU is the measurement of CPU that is in use.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

    • I/O throughput

      I/O throughput is the measurement of an entity's throughput to the underlying storage.

    • Net throughput

      Net throughput is the per-second sum of bytes that a virtual machine sent (egress) and received (ingress) through its connected network interfaces. This metric is a measurement of the volume of network traffic that a virtual machine handles.

Monitored resources for container platform clusters (AKS clusters)

Turbonomic does not monitor resources for the nodes (VMs) and volumes in an AKS cluster, but allows you to stop the cluster temporarily as a cost-saving measure, and then start it at a later time.

Note:

If the Kubeturbo agent is deployed to the AKS cluster, Turbonomic monitors resources for the containers, pods, nodes (VMs), and volumes in the cluster.

Monitored resources for app component specs (Web App service instances)

Turbonomic monitors the following resources:

  • Response time

    Response time is the elapsed time between a request and the response to that request. Response time is typically measured in seconds (s) or milliseconds (ms).

  • Virtual CPU (vCPU)

    Virtual CPU is the measurement of CPU that is in use.

Monitored resources for database servers

Turbonomic monitors the following resources:

  • Cosmos DB Account

    • Request unit (RU)

      Request unit (RU) is a performance currency that abstracts CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB. Azure Cosmos DB normalizes the cost of all database operations using RUs.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

  • SQL Managed Instance

    Note:

    Configure Azure database watcher to enable the discovery of metrics for vMem, maximum concurrent sessions, maximum concurrent workers, and DB cache hit rate.

    • Virtual CPU (vCPU)

      Virtual CPU is the measurement of CPU that is in use.

    • Virtual memory (vMem)

      Virtual memory (vMem) is the measurement of memory that is in use.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

      Note:

      Due to an Azure limitation, Turbonomic discovers IOPS for Next-gen General Purpose and Business Critical service tiers only.

    • Maximum concurrent sessions

      Maximum concurrent sessions is the maximum number of database connections at a time.

    • Maximum concurrent workers

      Maximum concurrent workers is the maximum number of database processes that can handle queries at a time.

    • DB cache hit rate

      DB cache hit rate is the measurement of Database Server accesses that result in cache hits, measured as a percentage of hits versus total attempts. A high cache hit rate indicates efficiency.

  • Azure Database for MySQL - Flexible Server

    • Virtual CPU (vCPU)

      Virtual CPU is the measurement of CPU that is in use.

    • Virtual memory (vMem)

      Virtual memory (vMem) is the measurement of memory that is in use.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

Monitored resources for databases

The resources that Turbonomic can monitor depend on the pricing model in place for the given database entity.

  • SQL Database - DTU Pricing Model

    • DTU

      DTU is the measurement of compute capacity for the database. DTU represents CPU, memory, and IOPS/IO Throughput bundled as a single commodity.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

  • SQL Database - vCore Pricing Model

    • Virtual memory (vMem)

      Virtual memory (vMem) is the measurement of memory that is in use.

    • Virtual CPU (vCPU)

      Virtual CPU is the measurement of CPU that is in use.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

    • I/O throughput

      I/O throughput is the measurement of an entity's throughput to the underlying storage.

  • Dedicated SQL Pool (for Azure Synapse Analytics)

    • DWU

      DWU (Data Warehousing Unit) is the measurement of compute capacity for the dedicated SQL pool. DWU represents CPU, memory, and IO Throughput bundled as a single commodity.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Connection

      Connection is the measurement of database connections utilized by applications.

  • Cosmos DB Database

    • Request unit (RU)

      Request unit (RU) is a performance currency that abstracts CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB. Azure Cosmos DB normalizes the cost of all database operations using RUs.

Monitored resources for document collections (Cosmos DB containers)

Turbonomic monitors the following resources:

  • Request unit (RU)

    Request unit (RU) is a performance currency that abstracts CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB. Azure Cosmos DB normalizes the cost of all database operations using RUs.