AWS monitored resources

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.

AWS Turbonomic
Elastic Compute Cloud (EC2) Virtual machine
EC2 Auto Scaling group Virtual machine spec
Relational Database Service (RDS) Database server
Elastic Block Store (EBS) Volume
Redshift provisioned cluster Data warehouse
Availability zone Zone
Region Region

Points to consider:

Monitored resources for virtual machines (EC2)

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 collection of metrics in your environment. Enabling metrics allows Turbonomic to generate scale actions to optimize VM resource usage. For Turbonomic to collect metrics, you must enable the collection of these metrics on the VMs in your environment.

    For details, see AWS 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 rate of message delivery over a port.

Monitored resources for virtual machine specs (Auto Scaling groups)

Turbonomic does not monitor resources for Auto Scaling groups, but allows you to park (stop or start) these groups on demand or according to a schedule.

Monitored resources for database servers

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.

  • Storage access (IOPS)

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

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

  • Connection

    Connection is the measurement of database connections utilized by applications.

Monitored resources for data warehouses (Redshift provisioned clusters)

Turbonomic monitors the following resources:

  • Number of replicas

    Number of replicas is the total number of nodes (leader node and compute nodes) in a Redshift provisioned cluster.

  • Storage amount

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

    Note:

    Turbonomic calculates storage amount. The calculated amount may not match the data returned by Redshift due to an AWS issue. For this reason, you may see a slight difference in the storage amounts shown in Turbonomic and in the AWS console.

  • Connection

    Connection is the measurement of database connections utilized by applications.

Monitored resources for volumes

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.