diff options
| author | Vijay Lobo <vijaylobo@gmail.com> | 2021-10-08 00:53:16 +0300 |
|---|---|---|
| committer | Shantappa Teekappanavar <shantappa.teekappanavar@ibm.com> | 2022-09-29 01:37:38 +0300 |
| commit | 9c11a172247a663dfbd708f0ded12024afd9fb1e (patch) | |
| tree | bb9dcdb29341e4810cc15773f55b968880a30492 /scripts | |
| parent | 0af99542b31a7ac59f9d76568c74a160a63baff2 (diff) | |
| download | bmcweb-9c11a172247a663dfbd708f0ded12024afd9fb1e.tar.xz | |
Redfish: Add resolution property
This property is used to provide suggestions on how to resolve the
situation that caused the log entry. Services can replace the resolution
defined in the message registry with a more specific resolution in a log
entry.
Tested:
curl command was run with a resolution property set in the d-bus object
curl -k -X GET https://$bmc:18080/redfish/v1/Systems/system/\
LogServices/EventLog/Entries
"Members": [
{
"@odata.id":
"/redfish/v1/Systems/system/LogServices/EventLog/Entries/1",
"@odata.type": "#LogEntry.v1_9_0.LogEntry",
"AdditionalDataURI":
"/redfish/v1/Systems/system/LogServices/EventLog/Entries/1/attachment",
"Created": "2022-08-05T18:44:34.201+00:00",
"EntryType": "Event",
"Id": "1",
"Message":
"xyz.openbmc_project.State.Error.CriticalServiceFailure",
"Modified": "2022-08-05T18:44:34.201+00:00",
"Name": "System Event Log Entry",
"Resolution": "1. Priority: High, Procedure: BMC0002\n",
"Resolved": false,
"Severity": "Critical"
},
...
]
Signed-off-by: Vijay Lobo <vijaylobo@gmail.com>
Change-Id: Ia28e97c17c1b9bd0e29b681727c3e36563ca7922
Signed-off-by: Shantappa Teekappanavar <shantappa.teekappanavar@ibm.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions