Database - Azure Cosmos DB

Synopsis

Monitored resources

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.

Scale actions for Cosmos DB databases

Turbonomic can scale databases with provisioned throughput. It uses percentile calculations to measure RU utilization and then recommends actions to scale RUs up or down to optimize performance and costs.

Points to consider:

• For scale down actions, Turbonomic will never recommend scaling below the minimum RU value calculated by Azure or configured in a database policy. For details, see Minimum RU Capacity for Scale Down Actions.

• Scale out actions do not apply since there is only one tier for Cosmos DB.

• Turbonomic discovers but does not scale databases without provisioned throughput.

Utilization charts for scale actions

Turbonomic uses percentile calculations to measure resource utilization, and drive scaling actions that improve overall utilization and reduce costs. When you examine the details for a pending scaling action on a database, you will see charts that highlight resource utilization percentiles for a given observation period, and the projected percentiles after you execute the action.

The charts also plot daily average utilization for your reference. If you have previously executed scaling actions on the database, you can see the resulting improvements in daily average utilization. Put together, these charts allow you to easily recognize utilization trends that drive Turbonomic's scaling recommendations.

Reconfigure actions for Cosmos DB databases

Turbonomic recommends removing unused throughput that is assigned to a database to help reduce your cloud expenses. To remove this resource, reconfigure the database from Azure. It is not possible to execute reconfigure actions from Turbonomic.

Turbonomic generates a reconfigure action if a database and all the underlying document collections have their own provisioned throughput. In this scenario, provisioned throughput at the database level is not used by any document collection and is therefore safe to remove. This action translates into cost savings. When you review a database reconfigure action in Action Center, the Cost Impact column indicates the cost savings that you would realize if you execute the action.

Points to consider:

• Turbonomic does not generate a reconfigure action if a database manages at least one document collection without provisioned throughput. In this scenario, the document collection is assumed to be using provisioned throughput at the database level, so it is not safe to remove that resource.

• Reconfigure actions are generated in recommend mode since it is not possible to execute these actions from Turbonomic.

  You can disable the generation of reconfigure actions in custom policies for select databases or the default database policy (for a global effect).

Delete actions for Cosmos DB databases

To help reduce your cloud expenses, Turbonomic recommends deleting a database with provisioned throughput but without any underlying document collection. When you review a database delete action in Action Center, the Cost Impact column indicates the cost savings that you would realize if you execute the action.

This action can be executed in Turbonomic manually or automatically. You can disable the generation of delete actions in custom policies for select databases or the default database policy (for a global effect).

Action disruptiveness and reversibility

The Action Center view and Action Details page indicate the disruptiveness and reversibility of actions for Cosmos DB databases.

• Scale actions

  All scale actions are non-disruptive and reversible.

• Reconfigure and delete actions

  All reconfigure and delete actions are disruptive and irreversible.