Open kamilkloch opened 2 years ago
Thanks for the report! I guess this is a blaze-specific issue, right? I guess it should be transferred then, I think @danicheg can do that.
Should I open this issue in blaze? Update: Never mind, I guess issue can be directly transferred.
Sample log line:
Log entry claims this is
Http1ServerStage
fromhttp4s-blaze-server
. Actual logging takes place inHttp1Stage:271
fromhttp4s-blaze-core
.Problem is that
logger
instance gets passed around between components - either by accessing parent class' logger (org.http4s.blaze.pipeline.Stage
defines logger that is protected and used in derived classes), or by explicit passing around logger reference (org.http4s.blaze.server.Http1ServerParser
).This is an antipattern which renders the logs much less user-friendly.