Inconsistency in Metrics URI defined across metrics schemas

new

« Prev
1
Next »

aishwaryj
Minnow

Posts: 2

Inconsistency in Metrics URI defined across metrics schemas Apr 7, 2022 8:48:46 GMT

Quote

Post by aishwaryj on Apr 7, 2022 8:48:46 GMT

We have seen inconsistency in URI Redfish uris for MemoryMetrics and PortMetrics, the later one ends with /Metrics while the earlier one has /MemoryMetrics

Eg
MemoryMetrics URI
"/redfish/v1/Systems/{ComputerSystemId}/MemorySummary/MemoryMetrics"

PortMetrics URI
/redfish/v1/Systems/{ComputerSystemId}/Processors/{ProcessorId}/Ports/{PortId}/Metrics

Can the metrics URI be consistent across all resource type and ends in /Metrics ?

Last Edit: Apr 7, 2022 8:49:12 GMT by aishwaryj

mraineri
Administrator

Posts: 1,134

Inconsistency in Metrics URI defined across metrics schemas Apr 7, 2022 15:58:05 GMT

Quote

Post by mraineri on Apr 7, 2022 15:58:05 GMT

Generally speaking, we have been trying to follow that pattern for newer metrics resources. Unfortunately MemoryMetrics was one of the early metrics resources before we established that pattern, so there is a discrepancy with how other device metrics are shown. In addition, changing the URI pattern that this point can cause backwards compatibility issues with existing implementations.