|
Post by AMI_Felix on Jun 1, 2022 6:23:29 GMT
Hi,
I know OriginOfCondition points to new resource instead of collection. In our design, when POST action URI like chassis force restart(/redfish/v1/Chassis/Self/Actions/Chassis.Reset). The AuditLog entry presented below:
{
"@odata.id": "/redfish/v1/Managers/Self/LogServices/AuditLog/Entries/3",
"@odata.type": "#LogEntry.v1_4_3.LogEntry",
"Created": "2022-05-31T14:34:01-04:00",
"Description": "Chassis.Reset - ForceRestart action was triggered which requires attention",
"EntryCode": "Informational",
"EntryType": "Event",
"EventTimestamp": "2022-05-31T14:34:01-04:00",
"Id": "3",
"Links": {
"OriginOfCondition": {
"@odata.id": "/redfish/v1/Chassis/Self/Actions/Chassis.Reset/ResetType"
}
},
"Message": "Chassis.Reset - ForceRestart action was triggered which requires attention",
"MessageArgs": [
"Chassis.Reset",
"ForceRestart"
],
"MessageId": "Security.1.0.Alert",
"Name": "Log entry 3",
"Severity": "OK"
}
I would like to seek confirmation, does the current "OriginOfCondition" link conform to the definition in LogEntry.v1_4_3.json? or it should indicate the resource to "/redfish/v1/Chassis/Self"?
Thanks.
|
|
|
Post by mraineri on Jun 1, 2022 13:26:35 GMT
Think of "OriginOfCondition" as the link a client can use to get further details about the event in question. A client cannot perform a GET on an action URI, so showing "/redfish/v1/Chassis/Self/Actions/Chassis.Reset/ResetType" is invalid. In this case, OriginOfCondition would be the Chassis resource (/redfish/v1/Chassis/Self).
|
|