Post by fish on Aug 23, 2018 11:35:54 GMT
Im trying to understand usage and purpose of property OemRecordFormat in resource LogEntry. Could someone clarify this please? Below is the description from Schema.
description: "If the entry type is Oem, this will contain more information about the record format from the Oem."
longDescription: "The value of this property shall represent the OEM specific format of the Entry. This property shall be required if the value of EntryType is Oem.".
First question is what “record” is? I would assume that it is the same as “LogEntry”. If so, is there some reason for the different terminology? (Or does "record" refer only to the Message property of the LogEntry?)
The example that can be found in online mockup for “Simple Rack-mounted Server with Local Storage”, but also in “Redfish Resource and Schema Guide”, confuses me a bit also. Here the property OemRecordFormat contains a value of “Contoso” at the same time as the property “EntryType” has value “SEL”. But the Description/LongDescription of OemRecordFormat only talks about usage when “EntryType” has value “Oem”. Is this example faulty? (The example does not contain any OEM extensions of the LogEntry as far as I can see.)
And what is then the intention of the OemRecordFormat? Should it contain some specific description/specification of the OEM specific format used for the Message property, or for the entire LogEntry? Or should it be only some kind of “reference” or “Id” of the LogEntry format? I found an example usage of OemRecordFormat in HPE ILO5. In this case it seems to be only some kind of free-text “Id” of the LogEntry format. But the actual LogEntry OEM extensions are specified via the HPE schema of the OEM extension, and schema indicated via property @data.type, so I don’t see much need for it here either. I expect also that the “Name” property of the LogEntry could give the same indication of which type of log this is. (Which is valid in the HPE ILO5 example at least).
description: "If the entry type is Oem, this will contain more information about the record format from the Oem."
longDescription: "The value of this property shall represent the OEM specific format of the Entry. This property shall be required if the value of EntryType is Oem.".
First question is what “record” is? I would assume that it is the same as “LogEntry”. If so, is there some reason for the different terminology? (Or does "record" refer only to the Message property of the LogEntry?)
The example that can be found in online mockup for “Simple Rack-mounted Server with Local Storage”, but also in “Redfish Resource and Schema Guide”, confuses me a bit also. Here the property OemRecordFormat contains a value of “Contoso” at the same time as the property “EntryType” has value “SEL”. But the Description/LongDescription of OemRecordFormat only talks about usage when “EntryType” has value “Oem”. Is this example faulty? (The example does not contain any OEM extensions of the LogEntry as far as I can see.)
And what is then the intention of the OemRecordFormat? Should it contain some specific description/specification of the OEM specific format used for the Message property, or for the entire LogEntry? Or should it be only some kind of “reference” or “Id” of the LogEntry format? I found an example usage of OemRecordFormat in HPE ILO5. In this case it seems to be only some kind of free-text “Id” of the LogEntry format. But the actual LogEntry OEM extensions are specified via the HPE schema of the OEM extension, and schema indicated via property @data.type, so I don’t see much need for it here either. I expect also that the “Name” property of the LogEntry could give the same indication of which type of log this is. (Which is valid in the HPE ILO5 example at least).