|
Post by igork on Oct 6, 2022 13:46:11 GMT
Hello, Could you please clarify the question regarding MemoryMetrics object in the MemorySummary. According to the Redfish specification: www.dmtf.org/sites/default/files/standards/documents/DSP2046_2021.4.pdf Each memory DIMM has it's own Metrics. And for the MemorySummary we have such definition in the specification. Metrics (v1.8+) { object The link to the metrics associated with all memory in this system. See the MemoryMetrics schema for details on this property. @odata.id string read-only Link to a MemoryMetrics resource. See the Links section and the MemoryMetrics schema for details. } Since we can have only one Metrics object in the MemorySummary, does that mean we have to combine the information from all DIMMs metrics in one Metrics object? If so, then how it should be combined? Thank you, Igor
|
|
|
Post by mraineri on Oct 6, 2022 14:34:56 GMT
Yes, it's essentially a summation of metrics for all of the system's memory. How you determine each property is going to be dependent on the property itself; in a lot of cases it's just the sum of the values across all DIMMs in the system. In cases where it's not obvious, there is text in the long description for how to populate the property in this case or when to avoid it. For example, "BlockSizeBytes" says "When this resource is subordinate to the MemorySummary object, this property is not applicable." in its long description.
|
|
|
Post by igork on Oct 6, 2022 17:16:41 GMT
Thank you for the clarification.
|
|
|
Post by AMI_Mani on Apr 24, 2023 13:16:39 GMT
Hi, I'm unable to see any mockup related to memory metrics in redfish.dmtf.org/redfish/mockups, please provide the link if available As per my understanding, in Systems Instance(/redfish/v1/Systems/{ComputerSystemId}) we need to point to MemorySummary/MemoryMetrics URI like below "MemorySummary": { "TotalSystemMemoryGiB": 32, "TotalSystemPersistentMemoryGiB": 0, "MemoryMirroring": "DIMM", "Metrics": { "@odata.id": "/redfish/v1/Systems/{ComputerSystemId}/MemorySummary/MemoryMetrics" } Every Memory instance will have MemoryMetrics as /redfish/v1/Systems/{ComputerSystemId}/Memory/{MemoryId}/MemoryMetrics, in /redfish/v1/Systems/{ComputerSystemId}/MemorySummary/MemoryMetrics URI we need to combine all memory instances metrics data and show attributes of MemoryMetrics schema. Thanks, Mani
|
|
|
Post by mraineri on Apr 24, 2023 14:09:18 GMT
We do not have a published mockup of this specifically, but the URI you're showing is correct (/redfish/v1/Systems/{ComputerSystemId}/MemorySummary/MemoryMetrics). You're also correct in that this is going to be the combination of each of the memory-specific MemoryMetrics resources. However, some properties may not apply, or may require special handling. This should be called out in the long descriptions of the properties inside MemoryMetrics.
|
|