Add memory_metrics to canister_status.

docs/references/_attachments/ic.did

@@ -250,6 +250,16 @@ type canister_status_result = record {
     settings : definite_canister_settings;
     module_hash : opt blob;
     memory_size : nat;
+    memory_metrics : record {
+        wasm_memory_size : nat;
+        stable_memory_size : nat;
+        global_memory_size : nat;
+        wasm_binary_size : nat;
+        custom_sections_size : nat;
+        canister_history_size : nat;
+        wasm_chunk_store_size : nat;
+        snapshots_size : nat;
+    };
     cycles : nat;
     reserved_cycles : nat;
     idle_cycles_burned_per_day : nat;

docs/references/_attachments/interface-spec-changelog.md

@@ -3,6 +3,7 @@
 ### 0.34.0 (2025-03-07) {#0_34_0}
 * New canister method `canister_on_low_wasm_memory` invoked when the canister is low on main memory according to a new `wasm_memory_threshold` in canister settings.
 * New system APIs `ic0.cost_call`, `ic0.cost_create_canister`, `ic0.cost_http_request`, `ic0.cost_sign_with_ecdsa`, `ic0.cost_sign_with_schnorr`, and `ic0.cost_vetkd_derive_encrypted_key` for cycles cost calculation.
+* New field `memory_metrics` providing detailed metrics on the memory consumption of a canister in the response of the management canister's `canister_status` endpoint.
 
 ### 0.33.0 (2025-02-12) {#0_33_0}
 * New system API `ic0.subnet_self_size` and `ic0.subnet_self_copy`.

docs/references/ic-interface-spec.md

@@ -2348,7 +2348,9 @@ Indicates various information about the canister. It contains:
 
 -   A SHA256 hash of the module installed on the canister. This is `null` if the canister is empty.
 
--   The actual memory usage of the canister.
+-   The actual memory usage of the canister, representing the total memory consumed by the canister.
+
+-   A record containing detailed breakdown of memory usage into individual components (see [Memory Metrics](#ic-canister_status-memory_metrics) for more details).
 
 -   The cycle balance of the canister.
 
@@ -2368,6 +2370,26 @@ Indicates various information about the canister. It contains:
 
 Only the controllers of the canister or the canister itself can request its status.
 
+#### Memory Metrics {#ic-canister_status-memory_metrics}
+
+    * `wasm_memory_size`: Represents the Wasm memory usage of the canister, i.e. the heap memory used by the canister's WebAssembly code.
+
+    * `stable_memory_size`: Represents the stable memory usage of the canister.
+
+    * `global_memory_size`: Represents the memory usage of the global variables that the canister is using.
+
+    * `wasm_binary_size`: Represents the memory occupied by the Wasm binary that is currently installed on the canister. This is the size of the binary uploaded via `install_code` or `install_chunked_code`, e.g., the compressed size if the uploaded binary is gzipped.
+
+    * `custom_sections_size`: Represents the memory used by custom sections defined by the canister, which may include additional metadata or configuration data.
+
+    * `canister_history_size`: Represents the memory used for storing the canister's history.
+
+    * `wasm_chunk_store_size`: Represents the memory used by the Wasm chunk store of the canister.
+
+    * `snapshots_size`: Represents the memory consumed by all snapshots that belong to this canister.
+
+All sizes are expressed in bytes.
+
 ### IC method `canister_info` {#ic-canister_info}
 
 This method can only be called by canisters, i.e., it cannot be called by external users via ingress messages.
@@ -4770,6 +4792,8 @@ The controllers of a canister can obtain detailed information about the canister
 
 The `Memory_usage` is the (in this specification underspecified) total size of storage in bytes.
 
+The `Memory_metrics` are the (in this specification underspecified) detailed metrics on the memory consumption of the canister (see [Memory Metrics](#ic-canister_status-memory_metrics) for more details).
+
 The `idle_cycles_burned_per_day` is the idle consumption of resources in cycles per day.
 
 Conditions  
@@ -4809,6 +4833,7 @@ S with
             then null
             else opt (SHA-256(S.canisters[A.canister_id].raw_module));
           memory_size = Memory_usage;
+          memory_metrics = Memory_metrics;
           cycles = S.balances[A.canister_id];
           reserved_cycles = S.reserved_balances[A.canister_id]
           idle_cycles_burned_per_day = idle_cycles_burned_rate(