SEL Event logs in Redfish

Lei Yu yulei.sh at bytedance.com
Thu Jun 3 19:38:05 AEST 2021


On Thu, Jun 3, 2021 at 1:01 AM Bills, Jason M
<jason.m.bills at linux.intel.com> wrote:
> >
> > There is a limitation about the way to log SEL event to
> > /var/log/redfish, that it only appears in redfish event logs, but not
> > in ipmi sel.
> When using journal-based logging, the IPMI sel events are in
> '/var/log/ipmi_sel'.

Yup, so if one need to log an event and make it appear on both SEL and
redfish event, the same event will have to be written into both files.

> >
> > On g220a it still uses the logging service to represent the event log
> > (see [1]), and ipmid is updated to consume the logging entries to get
> > the SEL entries.
> I would expect that the same logging approach would be used for both
> IPMI SEL and Redfish.  So, either both will use journal-based logging or
> both will use D-Bus logging. I don't know if it would work to mix them.

I don't think it will work to mix them, so the BMC build will need to
select at compile time by a config.

>
> > The missing part is in bmcweb that it does not support the event log
> > entries from DBus. We could probably add some new code to make it
> > support consuming data from logging service, and it could be
> > implemented under a config, so that the user could config which data
> > source to get event log at compile time.
> I believe that bmcweb supports Redfish event logs from D-Bus log entries
> with this option:
> https://github.com/openbmc/bmcweb/blob/master/meson_options.txt#L21.

Good to know!

-- 
BRs,
Lei YU


More information about the openbmc mailing list