You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 codedebug!(), error!() warn!()
are automatically sent, eliminating the need to useSender
objects.This solution needs to be redfish compliant.
https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2023.1.pdf
Acceptance Criteria
LogService
and is exposed over the Restful APISender
objects are replaced with conventional log statementsThe text was updated successfully, but these errors were encountered: