Document collection

In Azure Cosmos DB, containers are entities that store data on one or more partitions. Containers are grouped using databases and managed through accounts.

Turbonomic discovers Azure Cosmos DB containers through your Azure targets, and represents them as document collection entities in the supply chain.

Synopsis

Cosmos DB topology
Synopsis
Provides: Resources for database operations supported by Azure Cosmos DB
Consumes: Request Units (RUs) from Azure Cosmos DB accounts
Discovered through: Azure targets

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 document collections

Turbonomic can scale document collections with standard (manually provisioned) dedicated 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 document collection 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 the following entities:

    • Document collections with auto-scaled dedicated throughput

    • Document collections with shared throughput, where throughput is provisioned at the database level and then shared by document collections within the database

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 document collection, you will see charts that highlight resource utilization percentiles for a given observation period, and the projected percentiles after you execute the action.

Utilization Charts for Scale Actions

The charts also plot daily average utilization for your reference. If you have previously executed scaling actions on the document collection, 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.

Note:

You can set scaling constraints in document collection policies to refine the percentile calculations. For details, see Aggressiveness and Observation Period.

Non-disruptive and reversible scaling actions

All scaling actions shown in the Action Center view and Action Details page are non-disruptive and reversible.