[bmcweb] Device Level Logging Services

[Willy Tu]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20210526/a3c1f9cc/attachment.htm>