* OriginOfCondition in Redfish Log Entry
@ 2021-07-09 21:35 Rahul Kapoor
0 siblings, 0 replies; only message in thread
From: Rahul Kapoor @ 2021-07-09 21:35 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
I wanted to get some context on the current design of Redfish Log Entry. I see that the existing implementation of LogEntry in log_services.hpp does not populate the property OriginOfCondition as described in https://redfish.dmtf.org/schemas/v1/LogEntry.v1_9_0.json within Links object.
I understand this is not a required property but I think it's essential to establish context of the event source should the implementation use DMTF ResourceEvent Registry (https://redfish.dmtf.org/registries/ResourceEvent.1.0.3.json) for logging events in Redfish LogService. I see some implementation in Event Service Manager module but I am interested in having this property available in redfish log entry for redfish clients that only pull events and don't subscribe.
The entries in OpenBMC Message Registry are quite descriptive about the source but my use case is based on ResourceEvent registry which is not as descriptive and entries would need a link to the associated resource.
Any feedback on the assessment above would be really helpful.
[-- Attachment #2: Type: text/html, Size: 3089 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-07-09 21:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-09 21:35 OriginOfCondition in Redfish Log Entry Rahul Kapoor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).