Allowed MetricProperties for Triggers Creation - discrete

Allowed MetricProperties for Triggers Creation - discrete Apr 13, 2021 14:39:55 GMT

Quote

Post by mraineri on Apr 13, 2021 14:39:55 GMT

In all cases, there will be a "#". Regardless of whether it's numeric or discrete, any time you make a reference to a property in a resource using a URI, you always need the "#" to show where the URI ends and the JSON-pointer segment begins.

I would recommend reviewing your first examples for "ReadingVolts" since the JSON-pointers do not appear correct based on the syntax RFC6901 requires. This is how to break down the URI structure:

/redfish/v1/Chassis/Self/Power#/Voltages/148_0/ReadingVolts

/redfish/v1/Chassis/Self/Power --> URI for the Power resource
/Voltages/148_0/ReadingVolts --> Path to the desired property within the Power resource

Breaking down the JSON-pointer further...

Voltages: Property to step into
148_0: Array index (since "Voltages" is defined as an array)
ReadingVoltes: Desired property

So, since "Voltages" is an array, I would expect the portion between Voltages and ReadingVolts to be the array index.

Redfish Specification Forum

Allowed MetricProperties for Triggers Creation - discrete

Post by abiramisekar on Apr 13, 2021 8:29:50 GMT

Post by mraineri on Apr 13, 2021 14:39:55 GMT