From: Rahul Kapoor <rahulkapoor@microsoft.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: OriginOfCondition in Redfish Log Entry
Date: Fri, 9 Jul 2021 21:35:06 +0000 [thread overview]
Message-ID: <MWHPR2101MB07300A6B60156F4913C3177EAB189@MWHPR2101MB0730.namprd21.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Hi,
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.
-Rahul
[-- Attachment #2: Type: text/html, Size: 3089 bytes --]
reply other threads:[~2021-07-09 21:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR2101MB07300A6B60156F4913C3177EAB189@MWHPR2101MB0730.namprd21.prod.outlook.com \
--to=rahulkapoor@microsoft.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).