All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tu <wltu@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Cc: Ed Tanous <edtanous@google.com>, Derek Chan <dchanman@google.com>,
	Nan Zhou <nanzhou@google.com>, Rui Zhang <ruizhan@google.com>
Subject: [bmcweb] Device Level Logging Services
Date: Wed, 26 May 2021 13:50:36 -0700	[thread overview]
Message-ID: <CAHwn2XnqABuyc3uMQDs+YgwYJL+yKLwCYn1myOVdZ=gkhw3L-A@mail.gmail.com> (raw)

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

Hi all,

Main discussion:
https://lore.kernel.org/openbmc/CAHwn2XknKWyv6Bsq48tkvA52rHKZRFoEJgUuZUmMj6uZb584JQ@mail.gmail.com/
(a
bit outdated)

This will be a sub-thread about logging services that will be used to
support Drive (and could support others).

For bmcweb, I am wondering if we can support custom logging services other
than the static ones that we have in
https://github.com/openbmc/bmcweb/blob/master/redfish-core/lib/log_services.hpp
.

I am thinking about supporting custom log service at a device level that
can be exported by different hardwares log entries that are more specific.
Then at each device resource can link  the Status.Condition to
the LogEntries.

Initial Idea,

For example, I want to have log entries for Drive devices.

ComputerSystemId could still be system or bmc and the Redfish endpoint will
be something like.

```
/redfish/v1/Systems/system/LogServices/Drive0LogService/Entries
```

On the D-bus side, the service exporting the log can add log entry
<https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Logging/Entry.interface.yaml>
 under.

We can have
```
/xyz/openbmc_project/logging/device/drive_0
|__/xyz/openbmc_project/logging/device/drive_0/entry/...
```

We can parse the `xyz.openbmc_project.ObjectMapper` at
`/xyz/openbmc_project/logging/device` with depth of 1 to get all the new
device log services and so on.

Please let me know if there are any questions about it. If no one is
against it, I'll work on implementing it.

Best,

Willy Tu




Best,

Willy Tu

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

             reply	other threads:[~2021-05-26 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 20:50 Willy Tu [this message]
2021-05-26 22:12 ` [bmcweb] Device Level Logging Services Bills, Jason M
2021-05-27  0:07   ` Willy Tu

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='CAHwn2XnqABuyc3uMQDs+YgwYJL+yKLwCYn1myOVdZ=gkhw3L-A@mail.gmail.com' \
    --to=wltu@google.com \
    --cc=dchanman@google.com \
    --cc=edtanous@google.com \
    --cc=nanzhou@google.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ruizhan@google.com \
    /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.