-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines - Server Integration
-
SESINickBeckenhome 2026-12-01
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Metric support sheet for cold collection
Atlas needs insert/delete throughput charts for cold collections (e.g. on the Metrics tab, alongside the existing Opcounters charts). mongod already exposes insert/delete operation counters via serverStatus.opcounters, but they are tier-blind: an insert or delete against a cold collection is indistinguishable from one against hot. There is no series anywhere for "how many inserts/deletes are hitting cold data".
SERVER-136303 covers the storage-level split (cold read/write I/O operations via PALI). This ticket is the operation-level ask: insert and delete ops split by tier, so the two metrics a customer first asks about on the write side are visible.
Ask: emit cold-tier counterparts of the existing opcounter metrics, split by tier:
- cold insert operations per second (counter, ops)
- cold delete operations per second (counter, ops)
Register them under metrics.disaggStorage.* (alongside the tier-split metrics from SERVER-136303) so the MaaS include list picks them up with no config change on the Atlas side.
Notes:
- Cold writes today happen during Lifecycle Management moves; move throughput is already on the LM page, but this gives the per-op-count view the Opcounters charts lack.
- Phase: Public Preview