All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Giles, Joshua" <Joshua.Giles@dell.com>
To: Ed Tanous <ed@tanous.net>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>,
	Gunnar Mills <gmills@linux.vnet.ibm.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: OpenBMC Logging Implementations: Interfaces and Error Messaging
Date: Sun, 24 Jan 2021 16:38:54 +0000	[thread overview]
Message-ID: <DM6PR19MB356141B80B3FDB392843099195BE9@DM6PR19MB3561.namprd19.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

Hello All,

We’re hoping to get clarity in two areas of Logging with the aim of proposals to benefit all.
These are interfaces and error messaging…

Logging interfaces
===============
Webui-vue appears to only display redfish Event Logging whereas “legacy” phosphor-logging is used by things such as generating SNMP traps.

Question: Will legacy event logging be deprecated in OpenBMC in favor of Redfish logging?  If not, do we merely access legacy logging out-of-band via rsyslog?

Error Messaging
=============
There appears to be some duplicate/unique error messages amongst the two implementations:

  1.  Phosphor-dbus-interfaces: e.g. https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Sensor/Threshold/Critical.interface.yaml
  2.  Redfish message registry: e.g. https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/34510/4/redfish-core/include/registries/openbmc_message_registry.hpp (SensorThreshHoldCriticalGoingHigh)

Question: Will the unique “legacy” errors defined in the phosphor-dbus-interfaces be available in the redfish message registry?  Is there a plan to consolidate these moving forward?

-Josh Giles

[-- Attachment #2: Type: text/html, Size: 6231 bytes --]

             reply	other threads:[~2021-01-25 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24 16:38 Giles, Joshua [this message]
2021-01-25 19:47 ` OpenBMC Logging Implementations: Interfaces and Error Messaging Ed Tanous
2021-01-26 15:56   ` Matt Spinler

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=DM6PR19MB356141B80B3FDB392843099195BE9@DM6PR19MB3561.namprd19.prod.outlook.com \
    --to=joshua.giles@dell.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=ed@tanous.net \
    --cc=gmills@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.