Domain 2 of 3 · Chapter 4 of 4

Manage and monitor fleets across accounts and subscriptions

Unlock the complete study guide + 25 practice exams totaling 1,500 questions.

Bundled into the existing Building AI Applications with Azure Cosmos DB premium course — no separate purchase.

14-day refund guarantee on one-time purchases and your first subscription charge.

Included in this chapter:

  • Why fleets exist: isolated tenants, central control
  • Fleet, fleetspace and fleetspace account
  • Pooled throughput: dedicated RU/s first
  • The per-partition ceiling on pool RU/s
  • Which accounts can share a pool
  • Sizing and billing a pool
  • Deploying a fleet with Bicep
  • Three monitoring tools, three time grains
  • Watching pool consumption in platform metrics
  • Enabling fleet analytics
  • The fleet analytics star schema
  • Query patterns over fleet analytics
  • Recognizing fleet scenarios in exam questions

Fleet monitoring tools: platform metrics vs diagnostic logs vs fleet analytics

PropertyPlatform metricsDiagnostic logsFleet analytics (preview)
Where the data is keptPer account, except the pool's FleetspaceAutoscaledThroughput metric (fleet level)Per accountFleet-wide, in your Fabric or ADLS Gen2 destination
Aggregation1 minute, preaggregatedPer request, raw1 hour, preaggregated
Retention90 daysUser-definedUser-defined
Extra costNoneLog storage costsFabric or Azure Storage storage and query compute
Analysis toolMetrics explorerLog Analytics workspaceFabric SQL analytics endpoint or KQL (Kusto Query Language); Spark over ADLS Gen2
AlertsMetric alert rulesLog alert rulesFabric alert rules

Decision tree

Alert withinminutes?YesPlatformmetrics,metric alertNoRoot cause ofone request?YesDiagnosticlogsNoTrends acrossmany accounts?YesFleetanalyticsNoHow far thepool scaled?YesPlatformmetrics,fleet scopeNoPlatform metrics,account scope

Cheat sheet

  • Fleets retain account-per-tenant isolation while centralizing capacity and observability
  • The fleetspace is the sharing boundary for pooled throughput
  • A fleetspace can group accounts from different subscriptions and resource groups
  • An account can belong to only one fleetspace and one fleet at a time
  • A fleet resource's management region does not determine its accounts' data regions
  • Fleet membership does not require enabling a throughput pool
  • A fleetspace account resource registers an existing database account with a fleetspace
  • The current fleetspace API kind is NoSQL
  • Resources consume dedicated RU capacity before drawing extra capacity from the fleetspace pool
  • Pooling works best when many tenants have different activity peaks
  • Accounts sharing a throughput pool must have matching regional configurations
  • A pooled fleetspace cannot mix single-write and multi-write account configurations
  • Fleetspace regions and service tier cannot be changed after creation
  • A pool autoscales between its configured minimum and a maximum no greater than ten times that minimum
  • Pool throughput starts at one hundred thousand RU per second and uses thousand-RU increments
  • Fleetspace dedicatedRUs and maxConsumableRUs describe different capacity quantities
  • Pooled capacity is deployed and updated on the fleetspace resource
  • Pool capacity is not shared across Azure regions
  • Pool billing uses each region's highest scaled throughput during the hour
  • A physical partition can draw at most five thousand extra pooled RUs by default
  • Default fleet limits cap accounts per fleetspace and total pool throughput
  • FleetspaceAutoscaledThroughput shows the pool's scaled capacity
  • Capacity Type separates requests and RUs served by dedicated throughput from pooled throughput
  • PhysicalPartitionThroughput provides the dedicated baseline needed to diagnose a pooled partition limit
  • Fleet analytics supports hourly cross-account trends rather than request-level incident diagnosis
  • Fleet analytics exports open Delta tables to OneLake or ADLS Gen2
  • A Fabric destination needs a OneLake workspace backed by licensed or trial capacity
  • The Cosmos DB Fleet Analytics service principal needs Contributor on the Fabric workspace
  • An ADLS fleet analytics destination needs hierarchical namespace and blob data-write permissions
  • Fleet analytics can take an hour to begin populating an authorized destination
  • Fleet analytics retention and analysis costs belong to the customer's destination
  • Joining hourly tables to DimResource supplies account and subscription context
  • FactRequestHourly supports ranking accounts by request volume over a chosen time window
  • FactRequestHourly distinguishes total RU usage, peak request charge, payload totals, and response status
  • FactResourceUsageHourly compares provisioned capacity with observed utilization
  • Storage maxima describe a footprint rather than additive hourly consumption
  • FactAccountHourly exposes fleet-wide backup and key-rotation configuration history
  • FactMeterUsageHourly and DimMeter connect measured consumption to pricing meters
  • Fleet analytics tables can be queried through a Fabric SQL endpoint or a Delta-capable Spark reader

Unlock with Premium — includes all practice exams and the complete study guide.

References

  1. https://learn.microsoft.com/en-us/azure/cosmos-db/fleet
  2. https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-create-fleet
  3. https://learn.microsoft.com/en-us/azure/cosmos-db/fleet-analytics
  4. https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/dp-420
  5. https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput
  6. https://learn.microsoft.com/en-us/azure/templates/microsoft.documentdb/2026-03-15/fleets/fleetspaces
  7. https://learn.microsoft.com/en-us/azure/cosmos-db/fleet-pools
  8. https://learn.microsoft.com/en-us/azure/cosmos-db/provision-throughput-autoscale
  9. https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tiers-vcore
  10. https://learn.microsoft.com/en-us/azure/templates/microsoft.documentdb/2026-03-15/fleets
  11. https://learn.microsoft.com/en-us/azure/templates/microsoft.documentdb/2026-03-15/fleets/fleetspaces/fleetspaceaccounts
  12. https://learn.microsoft.com/en-us/azure/cosmos-db/insights-overview
  13. https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-enable-fleet-analytics
  14. https://learn.microsoft.com/en-us/azure/cosmos-db/fleet-faq
  15. https://learn.microsoft.com/en-us/fabric/fundamentals/roles-workspaces
  16. https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/storage
  17. https://learn.microsoft.com/en-us/rest/api/cosmos-db/collections
  18. https://learn.microsoft.com/en-us/azure/cosmos-db/fleet-analytics-schema-reference