Question about Diagnostic Data support in LogService / LogEntry

[Zhenfei Tai]

Hi,

In the 2020.3 schema, a new action CollectDiagnosticData has been added
to LogService. On page 7 in the proposal doc
<https://www.dmtf.org/sites/default/files/Redfish_Diagnostic_Data_Logging_Proposal_05-2020-WIP_0.pdf>
the
highlighted parts in the json example seem contradictory.
<https://www.dmtf.org/sites/default/files/Redfish_Diagnostic_Data_Logging_Proposal_05-2020-WIP_0.pdf>

{
    "@odata.id": "/redfish/v1/Systems/system/LogServices/DiagnosticLog
/Entries",
    "@odata.type": "#LogEntryCollection.LogEntryCollection",
    "Description": "Collection of System Event Log Entries",
    "Members": [{
        "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog
/Entries/111",
        "@odata.type": "#LogEntry.v1_4_0.LogEntry",
        "Created": "2020-01-01T14:44:00Z",
        “EntryType”: “Event”,
        "DiagnosticDataType": "PreOS",
        "Id": "111",
        "Message": "User initiated dump",
        “MessageId”: “Diagnostics.1.0.UserInitiatedDiagnosticDump”,
        "Name": "System Event Log Entry",
        “AdditionalDataUri": "/redfish/v1/Systems/system/LogServices/
EventLog/attachement/111",
        “AddionalDataSizeBytes": 1048576
    }],
    "Members at odata.count": 1,
    "Name": "System Event Log Entries"
}

I have a few questions about the expected behavior:

   1. Should the Diagnostic entries be under the same URL? (i.e. should the
   highlighted parts all be EventLog?)
   2. How is the Entry associated with the AdditionalDataURI when creating
   the entries collection?
   3. How should the web service keep track of the association?


Thanks,
Zhenfei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200921/a466cf1f/attachment-0001.htm>