-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Description
Is your feature request related to a problem? Please describe.
Currently, inside the code, a Sender object is passed around to provide (eventually) log messages back to the client. I see an opportunity to improve this architecture, simultaneously adding value to the bmcd.
Describe the solution you'd like
A more elegant way is to create a logging Sink for the log crate that sends log messages to HTTP clients that are subscribed for logging information. This way, all the log statements inside our code debug!(), error!() warn!() are automatically sent, eliminating the need to use Sender objects.
This solution needs to be redfish compliant.
https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2023.1.pdf
Acceptance Criteria
- There is a logging sink that hooks into Rust's logging framework
- Bmcd implements the
LogServiceand is exposed over the Restful API - Logging instances inside the code using
Senderobjects are replaced with conventional log statements
Metadata
Metadata
Assignees
Labels
No labels