-
Notifications
You must be signed in to change notification settings - Fork 350
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
Logging configuration does not affect integrations #2000
Comments
with the main runtime there were some code to translate the property to the log4j2 format, maybe we should do the same here ? or map directly to the quarkus ones ? |
Allowing the |
I am going to take care of this issue as part of the logging trait changes. |
This solves issue apache#2000
This solves issue apache#2000
@orpiske with your work on the logging trait, I think we could "simply" remove the |
+1 for that. I can send a PR this week with the proposed code to remove it. |
Great, thanks! |
Fixed with #2377. |
Setting
logging.level.org.apache.camel=DEBUG
does not affect integration logs.So if users set flag
--logging-level org.apache.camel=DEBUG
, that is currently translated into the property above and does not work.The correct mapping should be something like:
quarkus.log.category."org.apache.camel".level=DEBUG
We should also change the doc to point to the Quarkus documentation for configuring the log via properties.
The text was updated successfully, but these errors were encountered: