-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Class in log output shown as the class where log was instantiated #397
Comments
@lightsaway, it's not really a Log4Cats question. Choosing the caller is handled by Logback, and SLF4J knows nothing about it. You can probably set up Logback somehow, but it definitely would not just a config tweak. Looking at the code here, it seems like you'll need to inject custom framework packages into the |
Hi! We hit the same problem in my team, and I came up with a solution to address this (#439), without dealing with LoggerContexts. |
@gbogard, from what I can tell, this issue is about the |
@nigredo-tori, you're right, my apologies :) |
Given the following code:
and following logback.xml:
this produces following output:
As you can see the last log line shows that logging is coming from Mything(whereas in reality it is MyOtherThing) Wondering if there is any trickery to make this show MyOtherThing as a source?
The text was updated successfully, but these errors were encountered: