Filed from the IronCache pre-implementation coverage audit (2026-06-13): no existing issue adequately owned this.
Why this is needed
Define behavior for the diagnostic commands operators reach for during incidents: MEMORY USAGE (per-key sampled accounting consistent with the #41 allocator-bytes model), MEMORY STATS, MEMORY DOCTOR, and LATENCY DOCTOR. These are advisory-text and accounting generators whose output is tightly coupled to IronCache's divergent internals (thread-per-core, custom allocator, compression), so verbatim Redis output is impossible and the synthesized fields/advice must be specified and conformance-mapped. Grep for MEMORY USAGE/MEMORY DOCTOR/LATENCY DOCTOR returns nothing; #86 covers LATENCY at LATEST/HISTORY/RESET only; #40 covers only OBJECT ENCODING/DEBUG OBJECT; #41 decides accounting but does not expose it via MEMORY. Uncovered diagnostic surface.
Context
Relates to / partially overlaps #86. Part of the vision EPIC #1.
Why this is needed
Define behavior for the diagnostic commands operators reach for during incidents: MEMORY USAGE (per-key sampled accounting consistent with the #41 allocator-bytes model), MEMORY STATS, MEMORY DOCTOR, and LATENCY DOCTOR. These are advisory-text and accounting generators whose output is tightly coupled to IronCache's divergent internals (thread-per-core, custom allocator, compression), so verbatim Redis output is impossible and the synthesized fields/advice must be specified and conformance-mapped. Grep for MEMORY USAGE/MEMORY DOCTOR/LATENCY DOCTOR returns nothing; #86 covers LATENCY at LATEST/HISTORY/RESET only; #40 covers only OBJECT ENCODING/DEBUG OBJECT; #41 decides accounting but does not expose it via MEMORY. Uncovered diagnostic surface.
Context
Relates to / partially overlaps #86. Part of the vision EPIC #1.