From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: SEL Event logs in Redfish
Date: Mon, 24 May 2021 10:11:34 -0700 [thread overview]
Message-ID: <360ae7ee-b341-0233-6d24-36a91706654a@linux.intel.com> (raw)
In-Reply-To: <bf927ab3-636a-7d25-e42e-1f5335b4201c@linux.vnet.ibm.com>
On 5/24/2021 8:15 AM, Bruce Mitchell wrote:
> On 5/24/2021 06:41, Jayashree D wrote:
>> Classification: Confidential
>> Hi Team,
>>
>> I need some clarification on SEL Logs.
>> In SEL Event logs, when the error is injected manually , I can able to
>> see the error logs in "ipmitool sel list" command.
>> Whether it will also reflect in Redfish API ?
I am mostly familiar with the journal-bases SEL logging. In that case,
phosphor-sel-logger will detect the error and log it to both IPMI SEL
and Redfish at the same time:
https://github.com/openbmc/phosphor-sel-logger/blob/master/include/threshold_event_monitor.hpp#L272.
It may also depend on how you are manually injecting the error.
>>
>> Could you please help me in this.
>>
>> Thanks,
>> Jayashree
>>
>> ::DISCLAIMER::
>> ________________________________
>> The contents of this e-mail and any attachment(s) are confidential and
>> intended for the named recipient(s) only. E-mail transmission is not
>> guaranteed to be secure or error-free as information could be
>> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
>> may contain viruses in transmission. The e mail and its contents (with
>> or without referred errors) shall therefore not attach any liability
>> on the originator or HCL or its affiliates. Views or opinions, if any,
>> presented in this email are solely those of the author and may not
>> necessarily reflect the views or opinions of HCL or its affiliates.
>> Any form of reproduction, dissemination, copying, disclosure,
>> modification, distribution and / or publication of this message
>> without the prior written consent of authorized representative of HCL
>> is strictly prohibited. If you have received this email in error
>> please delete it and notify the sender immediately. Before opening any
>> email and/or attachments, please check them for viruses and other
>> defects.
>> ________________________________
>>
>
> Hi Jayashree,
>
> I suggest you connect with Jason Bills on SEL.
>
>
next prev parent reply other threads:[~2021-05-24 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 13:41 SEL Event logs in Redfish Jayashree D
2021-05-24 15:15 ` Bruce Mitchell
2021-05-24 17:11 ` Bills, Jason M [this message]
2021-05-28 8:58 Jayashree D
2021-06-01 19:05 ` Bills, Jason M
2021-06-02 2:32 ` Lei Yu
2021-06-02 16:59 ` Bills, Jason M
2021-06-03 9:38 ` Lei Yu
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=360ae7ee-b341-0233-6d24-36a91706654a@linux.intel.com \
--to=jason.m.bills@linux.intel.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).