Repository navigation
Other logging frontend adapters #3
Description
Description
Looks cool! However, the code out there is already implemented with tracing and log crates - I'd like those logs to be handled ad well.
Use Case
Have one logger implementation per executable that prints the logs from the whole ecosystem of crates, not just the statements written with sheen macros explicitly.
Possible Implementation
Implement adapters for log and tracing crates; in the tracing ecosystem this is called "subscriber", don't remember how it's called in the log ecosystem...
Activity
arferreira commentedon Jan 23, 2026
Hey @MOZGIII, thanks for opening this!
I'll prioritize
logcrate compatibility first since it's simpler and covers a lot of use cases.tracingsubscriber would come after.Would you like to take a shot at implementing either of these? Happy to help guide the approach. If not, no worries I'll pick it up soon.
MOZGIII commentedon Jan 23, 2026
Sorry, I didn't even try
sheenitself yet, so no - I won't be taking this at this time. Creating this issue is just my two cents on how to improve a crate like this further - just about all I have time for now.arferreira commentedon Jan 23, 2026
No worries, appreciate feedback! I'll keep this open and work on
logcompatibility for a future release.I'll you hit you for testing, okay?
MOZGIII commentedon Jan 23, 2026
Not sure if I'll even do that, but please do and we'll see
Offtop
Tbh I am using
tracingusually, but I'm a bit unhappy with thetracing-subscribercrate and stock facilities of it; would be nice to have something that is a one-liner to configure and allows switching log formats easily (without losing features - like mod/target filtering via theRUST_LOGenv var).That said, this crate is not that - and shouldn't try to be that.
I see it has both backend and frontend for the logging - and we do need improvements in both of those areas - but maybe they should be separate? Like, I don't really want to depend on a full logger in a lib crate - only on the frontend that I can use to place the log emits, but without pulling the whole ordeal needed for the actual logger as part of the lib crate code.
arferreira commentedon Jan 26, 2026
@MOZGIII Implemented both adapters:
Both are behind optional feature flags. Would love your feedback before merging.
I also left examples so you can take a look on that as well.
MOZGIII commentedon Jan 27, 2026
I'll check them out in a bit
MOZGIII commentedon Jan 27, 2026
That's roughly what I had in mind, yep; might look for other things to add adapter-wise - there might be more frontends I don't know
arferreira commentedon Jan 27, 2026
Don't forget you're very welcome for helping me on this!